9.4.5 Setting a Property File for Executing Management Actions

(1) Storage location of the file

The storage location of maction.properties is as follows:

• In Windows

  Cosminexus-installation-directory\manager\config\maction.properties

• In UNIX

  /opt/Cosminexus/manager/config/maction.properties

To Page Top

(2) Example of setting the file

The following is an example of setting the property file used for executing Management actions in Windows:

# Defining the Management action
maction.restart.command=c\:\\tmp\\command1.bat
maction.restart.timeout=12
maction.restart.timeout.forced_stop=true
maction.restart.exclusive_time=60
maction.restart.max_executable_actions=1
 
# Mapping of the message ID and Management action
maction.message.KDJE11111-E.mactions=restart
maction.message.KDJE22222-E.mactions=restart
 
# Mapping of the logical server and Management action
maction.server.j2ee1.mactions=restart
maction.server.j2ee2.mactions=restart
maction.server.j2eeClstr1.mactions=restart

This setting example defines restart as an ID to identify Management action (Management action ID). This section describes the operation and settings of the Management action of restart:

• Run the command file command1.bat as a command to execute the Management action.

• Set 12 seconds as a timeout for the Management action execution command.

• If the Management action execution command is timed out, the command is forcefully terminated.

• Set the suppression time of the Management action as 60 seconds, and the number of concurrent executions of Management actions as 1.^#

• Execute this management action if messages KDJE11111-E and KDJE22222-E are output from the J2EE server j2ee1, j2ee2, and j2eeClstr1.

#

Management actions are distinguished by Management action IDs, and you can execute the same Management action for multiple servers and for different message IDs. By setting the suppression time and the number of concurrent executions, and controlling the execution of Management actions, you can prevent the aggregation and duplication of Management actions. For details on the execution control, see 9.3 Controlling the Execution of Management Action.

To Page Top

(3) Notes

The following are the precautions related to the property file for executing Management actions:

• Priority of properties

  The logical server and cluster specified by the following keys contain the inclusive relation of the J2EE server < J2EE server cluster < service unit < physical tier:

  • maction.server.Logical-server-name.mactions

  • maction.unit.Web-system-name.service-unit-name.mactions

  • maction.tier.Web-system-name.Physical-tier-type-name.mactions

  Therefore, to define different Management actions for each logical server containing inclusive relationships such as a J2EE server cluster and J2EE servers that are the components of that J2EE server cluster, execute any one of the Management actions with the priority order described below:

  1. A J2EE server from where a Management event is issued

  2. A J2EE server cluster including the J2EE server from where a Management event is issued

  3. A service unit including the J2EE server from where a Management event is issued

  4. A physical tier including the J2EE server from where a Management event is issued

  A Web system, service unit, and physical tier are the concepts to build a system using the Smart Composer function. For the Smart Composer functionality, see 1.1.3 Smart Composer functionality in the uCosminexus Application Server System Setup and Operation Guide.

• Specification order of Management actions

  If the specification order of Management actions differs in the following two keys, the specification order of the maction.message.message-ID.mactions key is given priority:

  • maction.message.message-ID.mactions

    This key maps message IDs with Management actions.

  • maction.server.Logical-server-name.mactions

    This key maps logical servers with Management actions.

  (Examples)

  In this example, act1 is given priority.

  maction.message.KDJE99999-E.mactions=act1,act2

  maction.server.J2EE01.mactions=act3,act2,act1

To Page Top