Copyright © Cloud Software Group, Inc. All Rights Reserved

Starting iProcess Engine

The iProcess Engine server processes are controlled by Process Sentinels. Process Sentinels must be started first, they then control the start-up of the server processes. If you are using more than one server to host iProcess Engine (a node cluster), Process Sentinels must be started on each server.

Before you can start iProcess Engine, you must make sure that:

1.	The iProcess database instance is running.

2.	All required message queues are running.

3.	The event manager is running. (This means that the event queues and agents are running.)

The following sections explain how to start the Windows (see Windows Version) and UNIX versions (see UNIX Version) of iProcess Engine.

Windows Version

In the Windows version, the iProcess Engine functions are provided by the iProcess nodename Process Sentinels service (where nodename is the name of your iProcess Engine installation).

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

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

You can start the Process Sentinels service in three different ways (unless you have installed iProcess Engine to a Windows cluster):

•	At system startup - see An operating system group that gives you permissions to start a service, normally the Administrators group..

•	Manually, from the Windows Control Panel - see Manually Starting the Process Sentinels Service.

•	Using the swstart.bat script located in the SWDIR\bin directory- see Using the swstart.bat Script.

To be able to start iProcess Engine, you must be logged in to either as an iProcess Engine Administrator user, or as a user who is a member of both:

•	The iProcess Administrators local group (which gives you permissions on files and directories in SWDIR).

•	An operating system group that gives you permissions to start a service, normally the Administrators group.

If you have installed iProcess Engine to a Windows cluster, use the Bring online service in the Microsoft Cluster Administrator to start iProcess Engine. Do not attempt to start iProcess Engine on a Windows cluster by using Control Panel > Services or the swstart command located in the SWDIR\bin directory.

Configuring System Startup Behavior

When you install iProcess Engine, you choose whether or not the Process Sentinels service:

•	Starts automatically on system startup (the default option).

•	Needs to be started manually.

•	Is disabled (cannot be started).

If you subsequently want to change this setting, do the following:

1.	From the Start menu, select Settings > Control Panel.

2.	Double-click the Administration Tools item.

3.	Double-click the Services item. The Services dialog appears.

4.	Select the iProcess Nodename Process Sentinels service item (where Nodename is the name of your iProcess Engine installation) and click the Startup button. The Service dialog appears.

5.	Set the Startup Type item to:

−	Automatic, if you want the Process Sentinels service to start automatically on system startup.

−	Manual, if you want to manually start the Process Sentinels service (see the following).

−	Disabled, if you want to disable the Process Sentinels service.

Do not change any other options in the Service dialog. Doing so may cause iProcess Engine to fail.

Manually Starting the Process Sentinels Service

To manually start the Process Sentinels service:

1.	From the Start menu, select Settings > Control Panel.

2.	Double-click the Administration Tools item.

3.	Double-click the Services item. The Services dialog appears.

4.	Select the iProcess Nodename Process Sentinels service item (where Nodename is the name of your iProcess Engine installation).

5.	Click the Start button. This will start the Process Sentinels service and the iProcess Engine server processes.

You can use the Processes tab of the Windows Task Manager to view the processes as they start up. See Server Processes for a list of processes that are started.

Using the swstart.bat Script

To start the Process Sentinels service using the swstart.bat script located in the SWDIR\bin directory:

1.	Start the Process Sentinels by using the following command:

swstart -p

2.	Start the iProcess Engine server processes normally by using the following command:

swstart

Or, start the iProcess Engine server processes in quick start mode by using the following command:

swstart -q

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.

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.

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. See Administering Process Attributes for more information.

Starting the Process Sentinels

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

To start Process Sentinels on a server:

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

2.	Enter the command:

SWDIR/bin/swstart -p

If you add this command to your UNIX start-up routine script the Process Sentinels will always be running on startup.

Starting the Server Processes

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

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, follow these steps:

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

2.	Run the following command to start iProcess Engine server processes normally:

SWDIR/bin/swstart

Or, run the following command to start iProcess Engine server processes in quick start mode:

SWDIR/bin/swstart -q

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

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.

 

Copyright © Cloud Software Group, Inc. All Rights Reserved