Once a database is configured to start under the AdminServer, apart from using the DBMAN -start command line utility, the database can also be started multi-user with PROSERVE with the same pre-configured startup parameters in the conmgr.properties file and will register with the AdminServer that is currently running by using the following three parameters:
- -adminport : To have the database register with the AdminServer, What are the parameters "-port=" and -adminport=" used for by the AdminServer?
- -properties : default <DLC>\properties\conmgr.properties are used when not specified and the DLC environment variable has been set
- -servergroup : default <db>.defaultconfiguration.defaultservergroup, where the "Logical name" of the database object specified in the conmgr.properties is used, not the physical database name
Another means of finding these parameters is reviewing the command line used by AdminServer written to the admserv.log file as message (7402) enclosed between brackets ([ ... ]). The -
classpath is not strictly needed, but may be used when troubleshooting the cause of the startup failure when started under the AdminServer or with DBMAN.
Example 1: Start a database with two login brokers using the servergroups from one configuration, additionally specifying
ServerType to restrict client/server connections which was not pre-configured, to register with the AdminServer once started:
$ proserve dbname -servergroup ldbname.defaultconfiguration.defaultservergroup -ServerType sql -adminport 7846
$ proserve dbname -m3 -servergroup ldbname.defaultconfiguration.servergroup-1 -ServerType 4GL -adminport 7846
Where
"ldbname" is the display name of the
logical database configuration. The physical database name may be different.
When there are issues with the AdminServer running or simply when needing to start a database without being managed, but assuring the same parameter configuration is used without having to interpret conmgr.properties names into equivalent command-line startup parameters
Example 2: Starting a database with the primary login broker, adding additional parameters as needed, which will not register with the AdminServer
$ proserve dbname -servergroup ldbname.defaultconfiguration.defaultservergroup -Mm 8192
Example 3: Starting a database with the primary login broker, using a different conmgr.properties file or when the DLC environment variable is not set
$ proserve dbname -servergroup ldbname.defaultconfiguration.defaultservergroup -properties <full-path>\conmgr.properties
NOTE: Proserve without the -servergroup and -adminport does not normally register with the AdminServer and therefore the AdminServer / OEM will have no awareness of the database state (running or offline).
