Contents

EICPublisher

EICPublisher is a simple command-line utility that can read .i3pub files and "finish publishing" them to the current CIC server. EICPublisher is a separate executable that is shipped with Interaction Designer.

Note: EICPublisher 2.3 will not publish .i3pub files generated with any previous release of Interaction Designer. Only .i3pub files generated with Interaction Designer 2.3 can be published with EICPublisher 2.3.

Usage:

To use EICPublisherU, enter the following command:

eicpublisheru [/help] [/?] [/verbose] [/noprompts] [/notifier={hostname}] [/user={username}] [/password={password}] {filespec | @{file}}

where

/help or /? causes display of help text

/verbose causes the program to output extra process status info to stdout

/noprompts causes the program to avoid prompting the user for any input

{hostname} specifies a target CIC server

{username} specifies a valid CIC user id that has rights to publish on the target CIC server

{password} specifies the password for {username}

{filespec} specifies the file(s) to be processed

@{file} specifies the a text file listing the files to be processed

The [ ] means that piece is optional. Note that the username must have "Publish and Manage Handlers" rights (granted through Interaction Administrator).

Examples:

Eicpublisheru /notifier=WhiteSands /user=JohnSmith /password=smithj FirstOne.i3pub

Publishes FirstOne.i3pub to WhiteSands.

Eicpublisheru /notifier=WhiteSands /user=JohnSmith /password=smithj c:\temp\First*.i3pub

Publishes all files that fit the mask "First*.i3pub" from the c:\temp directory.

Eicpublisheru /notifier=WhiteSands /user=JohnSmith /password=smithj @somefile.txt

Opens the file somefile.txt and publishes the intermediate files listed in there (one per line). So somefile.txt could contain:

c:\temp\FirstOne.i3pub

SecondOne.someotherextension

ThirdOne.i3pub

Note: The files don't have to have .i3pub extensions -- EICPublisher does not require files to have any specific extensions. When Interaction Designer generates the .i3pub file, it uses the same base name as the handler document. For example, if you have FirstOne.ihd open, and you generate an .i3pub file from it, you'll get FirstOne.i3pub. You can rename that file to anything you want, and EICPublisher will still process it. But the real handler name (FirstOne) is still contained in the .i3pub file, and that's the name that will be used when it's published, not the name of the .i3pub file.

Example:

Suppose you start Interaction Designer, open FirstOne.ihd, generate FirstOne.i3pub, then rename it to NotTheFirstOne.junk. You send NotTheFirstOne.junk to a customer and they run EICPublisherU on NotTheFirstOne.junk to publish it to their server. After processing is complete, the handler FirstOne will exist on the customer's CIC server, not NotTheFirstOne.