UNIX Version

In the UNIX version, the iProcess Engine functions are provided by the "worker" and "watcher" Process Sentinel processes.

By default, after having been started, Process Sentinel tests the event mechanism automatically and starts the iProcess Engine server auto-start processes.

Note: This behavior is controlled by the PM_AUTO_BOOT process attribute, only the value of the PM_AUTO_BOOT attribute is set to 1, processes will be started automatically. For more information, see Administering Process Attributes.

Starting the Process Sentinels

You need to start Process Sentinels on each server in your iProcess Engine.

To start Process Sentinels on a server, perform the following steps:

1. Log in to iProcess Engine as a background user.
2. Enter the command:

SWDIR/bin/swstart -p

Note: If you add this command to your UNIX start-up routine script, the Process Sentinels always start running on start up.

Starting the Server Processes

Use the swstart script located in the $SWDIR/bin directory to start all the required server processes.

Note: If you are using a node cluster, you can run this script from any server that is part of the node cluster and it will start all the processes on all of the servers in iProcess Engine.

To start the iProcess Engine server processes, perform the following steps:

  1. Log in to iProcess Engine as a background user.

  2. Start and run iProcess Engine server in the following ways:

    • Normally, by using the following command:

      SWDIR/bin/swstart

    • In quick start mode, by using the command:

      SWDIR/bin/swstart -q

As each server process is started, a start-up message is displayed.

Note: When the iProcess Engine server is restarted or quick started, the iProcess Objects Server processes apply the RESTART_SPO_CACHE_PROC attribute to cache a specified number of procedure versions, and the WIS processes apply the RESTART_WIS_CACHE_THRESHOLD attribute to cache the work queues at a specified work item number. See RESTART_WIS_CACHE_THRESHOLD and RESTART_SPO_CACHE_PROC for more information.