Setting Up an iIS Process System
Runtime Client Installation
On a runtime client node, which must be installed after the central server node, the iIS installation program performs the operations described in the following table:
Operation | Software Module | FORTE_ROOT |
|
| directory |
|
|
|
Installs iIS TOOL client libraries. | WFClientLibrary | userapp |
| WFProcMgrLibrary |
|
| WFAdminLibrary |
|
Installs iIS C++ client development DLL. | WFClientAPI | userapp |
Installs iIS process management client | WFConsole | userapp |
applications. | WFScript |
|
Installs iIS system libraries. | OFCustomIF | userapp |
| WFCustomIF |
|
| WFEnvDefinition |
|
Installs message catalog file | en_us.cat | install/nls/conductr |
|
|
|
Configuring and Starting Your iIS Engines
When your iIS process system software is installed on the various nodes in your environment (including an iIS central development repository), an iIS application system designer can begin implementing the various design elements, process developers can begin creating process definitions, and client application developers can begin writing iIS client applications.
However, before long it will be necessary to have a test engine running in your environment. Configuring and starting an iIS process engine requires familiarity with iIS process management tools (see Chapter 3, “The iIS Console”) and is described fully in Chapter 4, “Managing Engines.”
