Managing iIS Process Engines with Conductor Script

The following Conductor Script commands start up the Enterprise engine in the preferred order.

findengine galaxy.enterprise findnode server1 startgovernor startdbservice load1 9 findnode server2 startunit primero findnode server3 startunit secundo startdbservice load2 8 findnode server4

Monitoring Engines and Engine Components

After you have started an engine, you should ensure that it has started successfully and monitor it periodically.

You can get status information about the engine as a whole and about each of the individual engine components. Conductor Script uses iIS engine agents to gather engine component data. Each agent has a set of instruments that report relevant information.

Monitoring the Engine

Typically you want to know which engine components are up and running.

To check the engine runtime configuration

1.Use the ListEngines command to see which engines are running in your environment.

2.Use the FindEngine command to make the engine of interest current.

3.Use the ShowStatus command to display the runtime configuration of the current engine.

Chapter 8 Using the Conductor Script Utility 239

Page 239
Image 239
Sun Microsystems 3 manual Monitoring Engines and Engine Components