8.2.4 adminagent.xml (Administration Agent settings file)
- Organization of this subsection
(1) Format
You specify the facility name (indicating the types and start/stop operations of the logical server) and then specify the name and value of the environment variable.
- Setting the facility name:
<facility> <name>Facility-name</name> <class>com.cosminexus.mngsvr.adminagent.impl.CmdExecuter</class>
- Setting the name and value of an environment variable:
-
Add the following coding after setting the facility name as mentioned above:
<init-param> <param-name>adminagent.facility.CmdExecuter.env.Environment-variable-name</param-name> <param-value>Environment-variable-value</param-value> </init-param>
(2) File storage location
-
In Windows
Cosminexus-installation-directory\manager\config\
-
In UNIX
/opt/Cosminexus/manager/config/
(3) Functionality
Specify the settings for starting up the logical server or updating the settings files on behalf of the system administrator.
Edit this settings file when it is necessary to change the initial values of environment variables in this file or when it is necessary to add or delete the environment variables.
(4) Logical server types that you can specify in the facility name
The following table describes the types of logical servers and the start or stop operations that you can specify in the facility name:
|
Logical server type |
Start or stop type |
Facility name |
Remarks |
|---|---|---|---|
|
Performance tracer |
Start |
prf-start |
-- |
|
Stop |
prf-stop |
-- |
|
|
Smart agent (In Windows) |
Start |
osagent-start |
-- |
|
Stop |
osagent-stop |
-- |
|
|
Smart agent (In UNIX) |
Start |
osagent-start |
-- |
|
Naming service |
Start |
naming-service-start |
-- |
|
CTM domain manager |
Start |
ctm-dommng-start |
-- |
|
Stop |
ctm-dommng-stop |
-- |
|
|
CTM |
Start |
ctm-start |
-- |
|
Stop |
ctm-stop |
-- |
|
|
J2EE server |
Start |
j2ee-server-start |
When the J2EE server uses a database, you need to provide the database specific settings in the J2EE server start up environment variables. |
|
Stop |
j2ee-server-stop |
||
|
WEB server (In Windows) |
Start |
web-server-start |
-- |
|
Stop |
web-server-stop |
-- |
|
|
WEB server (In UNIX) |
Start |
web-server-start |
-- |
Legend: --: None
(5) Precautions
-
When you change the adminagent.xml file, you need to re-start the Administration Agent.
-
When you start or stop any of the logical servers, the environment variables that are set at the startup of the Administration Agent are inherited. If you do not want to inherit the environment variables, set the corresponding environment variable to blank.
-
The environment variables set in adminagent.xml, apply to the types of logical servers started from the Administration Agent of the corresponding host. You cannot set environment variables for each instance of the logical server.
- (Example 1)
-
When Japanese_japan.ja16sjis is set in the environment variable NLS_LANG during J2EE server startup:
<facility>
<name>j2ee-server-start</name>
<class>com.cosminexus.mngsvr.adminagent.impl.CmdExecuter</class>
<init-param>
<param-name>adminagent.facility.CmdExecuter.env.NLS_LANG</param-name>
<param-value>Japanese_japan.ja16sjis</param-value>
</init-param>
...
...
- (Example 2)
-
When the environment variable AIXTHREAD_SCOPE, set during invocation of the Administration Agent, is not inherited:
<facility>
...
...
<init-param>
<param-name>adminagent.facility.CmdExecuter.env.AIXTHREAD_SCOPE</param-name>
<param-value></param-value>
</init-param>
...
...
-
The values specified for Environment-variable-name and Environment-variable-value are not processed as in the case of command shells, hence environment variable replacements and processing using operators is not possible. Therefore, you cannot use system environment variables while specifying Environment-variable-name and Environment-variable-value.