Kbase P6086: When components within Progress Explorer are set to autostart, what order do they startup in?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/31/2005 |
|
Status: Unverified
GOAL:
When components within Progress Explorer are set to autostart, what order do they startup in?
GOAL:
What order does the database startup in compared to other components within the Progress explorer?
FIX:
When setting components to autostart, components will start in alphabetical sequence. So for instance here is the order of components that currently reside within the ubroker.properties and conmgr.properties file;
ADAPATER,
AIA,
APPSERVER,
DB,
MSS DSV,
NAMESERVER,
ODBC DSV,
ORACLE DSV,
SONIC,
WEBSPEED.
Within each component if there are multiple brokers set to autostart, they too will startup in alphabetical order.
If the broker tries to start before the database has actually started, then the broker (any broker) will never startup up correctly due to the fact that database is not up and running.
The Autostared Database servers should be available befoer any Broker is started, (WebSpeed, AppServer and Dataserver). The brokers will first check to see if the associated dbs are running. If the returned status indicated that the database startup has not completed yet, then the command-line plugin will wait for a while and try again. The number of retries and retry interval are piggybacked of two preferences properties:
admSrvrRegisteredRetry and admSrvrRegisteredRetryInterval.
The status of the database startup synchroization is logged in cmdplugin.log. Even if the synchronization fails, the process of auto-starting broker
ameserver continues. There might be a need to fine-tone these two preference properties, if there are many databases require auto-starting and the horsepower of the system is limited.