2.1.6 Management Server settings for using HCSC-Manager

Perform the settings for using HCSC-Manager in a machine that has the execution environment of HCSC-Manager connection destination. The following points show setting procedures:

Organization of this subsection

(1) Setting mserver.properties (Management Server environment settings file)
(2) Setting mserver.cfg (option definition file for Management Server)
(3) Checking adminagent.properties (Administration Agent properties file)
(4) Starting Administration Agent (restarting if started)
(5) Starting Management Server (restarting if started)
(6) Checking MBean start

(1) Setting mserver.properties (Management Server environment settings file)

Add properties in mserver.properties (Management Server environment settings file) of the execution environment. Properties added in mserver.properties storage location and mserver.properties is described here:

(a) Storage location of mserver.properties

<Service Platform installation directory>\manager\config\mserver.properties

(b) Added properties

com.cosminexus.mngsvr.management.enabled=true
com.cosminexus.mngsvr.management.connector.enabled=true
com.cosminexus.mngsvr.management.port=28099^#1
ejbserver.naming.port=28900^#2
ejbserver.server.edition.settingforce=
mngsvr.myhost.name=localhost

Note #1

Specify the connection port number from HCSC-Manager. If specification is omitted, 28099 set by default.

Note #2

Specify the connection port number from HCSC-Manager. If specification is omitted, 28900 set by default.

Note: Always specify before starting Management Server. If you start Management Server before specifying, commands beginning with csc may throw errors.

To Page Top

(2) Setting mserver.cfg (option definition file for Management Server)

Add properties in mserver.cfg (option definition file for Management Server) of the execution environment.

Properties added in mserver.cfg storage location and mserver.cfg is described here.

(a) Storage location of mserver.cfg

<Service Platform installation directory>\manager\config\mserver.cfg

(b) Adding properties

When Oracle is used in the database

web.add.class.path=< JAR file name of Oracle JDBC Thin Driver (full path)>^#

Note #

The following shows an example of the path to be specified when you use the JAR file of Oracle JDBC Thin Driver 18.3.0.0.0:

Oracle-Client-installation-directory/jdbc/lib/ojdbc8.jar

When HiRDB is used in the database

When HiRDB/Single Server, HiRDB/Parallel Server or HiRDB Server is installed

In Windows

add.library.path=<HiRDB installation directory>\CLIENT\UTL

In UNIX

add.library.path=<Operation directory of HiRDB>/client/lib

When HiRDB/Run Time or HiRDB/Developer's Kit is installed

In Windows

add.library.path=<HiRDB installation directory>\utl

In UNIX

add.library.path=<HiRDB installation directory>/client/lib

When HiRDB Type4 JDBC Driver is used in JDBC driver

web.add.class.path=<JAR file name of HiRDB Type4 JDBC Driver (full path)>^#

Note #

The applicable JAR file is "pdjdbc2.jar" under the HiRDB installation directory.

To Page Top

(3) Checking adminagent.properties (Administration Agent properties file)

(a) Storage location of adminagent.properties

<Service Platform installation directory>\manager\config\adminagent.properties

(b) Property to be checked

Check whether "2" is set in the following property or whether the property is omitted:

adminagent.j2ee.watch.level=2

To Page Top

(4) Starting Administration Agent (restarting if started)

You must start Administration Agent after Management Server environment settings file and option definition file for Management Server are set. Restart Administration Agent if it is already started.

For details on how to start Administration Agent, see "4.1.17 Starting the Administration Agent" in "Application Server System Setup and Operation Guide".

To Page Top

(5) Starting Management Server (restarting if started)

You must start Management Server after Management Server environment settings file and option definition file for Management Server are set. Restart Management Server if it is already started.

For details on how to start Management Server, see "4.1.18 Starting the Management Server" in "Application Server System Setup and Operation Guide".

To Page Top

(6) Checking MBean start

Check whether 22 items are output by KEOS27010-I message in the latest mngmessage[n].log file under <Service Platform installation directory>\manager\log\message\.

One of the following items is output in the variable value file name of KEOS27010-I message:

50cscbp.xml
50cscmsg.xml
50cscmt.xml

Important note

In 07-50 or higher version, the operation to copy the file under "<Service Platform installation directory>\CSC\mbean-plugins" in "<Service Platform installation directory>\manager\mbean-plugins" is not required.

If the following files exist, delete the files and then perform procedures (3) to (5):

<Service Platform installation directory>\manager\mbean-plugins\config\50cscbp.xml
<Service Platform installation directory>\manager\mbean-plugins\config\50cscmsg.xml
<Service Platform installation directory>\manager\mbean-plugins\lib\cscbp_mbean.jar
<Service Platform installation directory>\manager\mbean-plugins\lib\cscmsg_mbean.jar

To Page Top