iIS Process System Software
For the purpose of system setup, the primary considerations are that the iIS process engine is the workhorse of your iIS process system and that it accesses a potentially very large database. Your engine server node or nodes should therefore be a very high performance server with plenty of available memory. If you are unsure at this point how to configure your iIS engine, designate all likely nodes as engine server nodes. This approach gives you the most flexibility later on.
Another design issue concerns the iIS development repository. You might want iIS developers to use an existing iPlanet UDS repository, or you might prefer to create one or more central development repositories for exclusive use by iIS developers.
In addition, you might decide that the repository server needed to support iIS development should reside on a server other than the central server node hosting the Environment Manager, as shown in Figure
In any case, before beginning your iIS setup procedure, fill in a table similar to the one that follows:
iIS Function | Node type: Server/Client | Node Names |
|
|
|
Central server | Server |
|
|
|
|
Repository server | Server |
|
|
|
|
Engine servers | Server |
|
|
|
|
Process development | Client or server |
|
|
|
|
Client application | Client or server |
|
development |
|
|
|
|
|
System management | Client or server |
|
|
|
|
Runtime client application | Client or server |
|
|
|
|