
Setting Up an iIS Process System
7.After process client applications have been developed, run the iIS installation program on all runtime client nodes (those nodes that support an iIS process client application but do not support development).
8.In sites developing or running process client applications using the CORBA/IIOP interface to the iIS engine, start the CORBA/IIOP interface service using the IIOPServer Conductor Script command (see “IIOPServer” on page 287).
This setup procedure creates a functioning iIS process system in which developers can create process definitions and register them with an iIS engine and then develop process client applications and use them to perform the activities of an executing process instance.
CAUTION An iIS process system can only function in the iPlanet UDS environment in which it has been set up. For example, you cannot change the name of your iPlanet UDS
The iIS Installation Program
The setup procedure described in the previous section makes extensive use of the iIS installation program. The iIS installation program has four main installation options: central server node, engine server node, development client node, and runtime client node. Each installs, by default, the iIS system software appropriate for that type of node, and provides customizing options (such as installing iIS process management tools), as well.
This section describes what the installation program does on each of the following four node types:
•central server
•engine server
•client development (process development or client application development)
•runtime client
For