Managing iIS Process Engines with Conductor Script
Starting Individual Engine Components
You can start an individual engine component on any node on which it is installed. Each component is an application consisting of a single server partition that must establish communication channels with other components.
Except for the governor, as each of these partitions is started, it must be provided a component name and the name of the engine to which it belongs. The partition uses this engine name along with its component name to explicitly register itself with the iPlanet UDS Name Service. As each component starts up, it looks in the Name Service registry for the names of other components with which it must establish a communication channel. When all necessary communication channels are established, the primary engine unit can log on to its database and perform other operations needed to come fully online.
The engine startup protocol is designed to allow components to start in any order. They simply wait for the other components to which they must connect. However, because an engine unit will eventually time out if it cannot log on to its database or establish a communication channel with its partner or the governor, there is a preferred order for engine startup if there might be a delay in starting a component.
➤To start an engine where delays might be involved
1.Start the governor.
2.Start at least one database service.
3.Start each engine unit.
➤To start an individual engine component (governor, database service, or engine unit)
1.Use the FindEngine command to the engine you want to start to the current engine.
2.Use the FindNode command to set node for the component to the current node.
3.Use the appropriate Conductor Script Start command to start the engine component on the current node.
