Sun Microsystems iPlanet Integration Server 3.0, Process System Manual

Page: 238 / 368

Managing iIS Process Engines with Conductor Script
238 iPlanet Integration Server • Process System Guide • August 2001
As indicated in the table, the engine unit partition has a startup argument which
specifies that when the engine unit comes ONLINE, that it create the required
tables in the engine database. This argument should be used when you start an
engine for the first time, or if you explicitly want to delete the existing database
schema.
Example Manual Startup Scenario
You can override the component partitioning scheme in the engine configuration
file by starting each engine component manually. As an example, take the engine
partitioning scheme illustrated in
Figure 4-2 on page 88 . Assume the iPlanet UDS
environment is named “Galaxy”, and the engine is named “Enterprise.” The
partitioning scheme is summarized in the following table:
NOTE A cold start purges and deletes any tables that already exist,
including the registration table and the current state and history log
tables. Be careful when using this option, since you can lose
unrecoverable information.
Component Component Name Location (Node Name)
Governor Server1
Primary engine unit primero Server2
Backup engine unit secundo Server3
Database service main1 (priority=10) Server4
Database service main2 (priority=10) Server4
Database service main3 (priority=10) Server4
Database service load1 (priority=9) Server1
Database service load2 (priority=8) Server3