Sun Microsystems iPlanet Integration Server 3.0, Руководство по системе управления

Страница: 108 / 368

Starting an Engine
108 iPlanet Integration Server • Process System Guide • August 2001
Primary Engine Unit Startup Phases
The primary engine unit must perform a number of startup operations to come
fully online. These operations depend on whether the primary engine unit is
recovering from failure, is restarting an engine on an existing database, or is
starting up for the first time (cold start). The primary engine unit startup phases are
documented in the following table to assist you in diagnosing problems in engine
startup (the phases are listed in sequential order):
Startup Phase Description Phase #
REMOVE_PRIMARY Removes any existing “primary”
registration in the Name Service.
This phase not included in a cold
start. 51
CREATE_ENGINE Instantiates an engine object. 52
ATTACH_HISTORY_MANAGER Beginning of the database logon
phase. 53
INIT_HISTORY_DB Database logon phase, in which a
router is created and registered
with the Name Service, a
communication channel with a
database service is opened, and a
database service logon to the
database is successfully completed. 54
HISTORY_INITIALIZED Completion of the database logon
phase. 55
COLD_DELETE For a cold start, deletes any
existing database tables. 56
COLD_CREATE For a cold start, creates the
required database schema (tables). 57
RECOVER_OBJECTS Recovers all current state objects
from the database and places them
in engine state memory. This phase
not included in a cold start. 61
REGISTER_PRIMARY Places a “primary” registration in
the Name Service. This allows all
other objects to locate the primary
engine unit. 62
INFORM_GOVERNOR Communicates to governor that
state has changed to online. 63