Starting the Cosminexus JMS Provider services (for the initial startup)

This subsection describes the procedure for starting a Cosminexus JMS Provider service during initial startup in the cases such as immediately after system setup. A service that is started using this procedure can be terminated with Appendix E.11 Terminating the Cosminexus JMS Provider services.

If you start the CJMSP resource adapter and application according to this procedure, both CJMSP resource adapter and application start when you restart the J2EE server (however, as a precondition, CJMSP Broker must be started first).

The following figure shows the procedure for starting the Cosminexus JMS Provider services (for the initial startup).

Figure E-5 Procedure for starting the Cosminexus JMS Provider services (for the initial startup)

[Figure]

Organization of this subsection: (1) Process preconditions; (2) Information and supplementary explanation required for execution

The coding, such as (A1), corresponds to the coding in the figure.

(A1)

The management command property file is stored in <CJMSP_HOME>/var/admin/config/admin.properties.

The specifiable property names and description are as follows. For details on the file, see 7.2 admin.properties (Management command property file) in the uCosminexus Application Server Definition Reference Guide.

admin.logger.MessageLogFile.trace.level: Specifies the message log level of a management command.

admin.logger.MessageLogFile.filepath: Specifies the file path to output the management command message log.

admin.logger.MessageLogFile.filenum: Specifies the maximum number of message log files created with a management command.

admin.logger.MessageLogFile.filesize: Specifies the maximum size of the message log file of a management command.

admin.logger.ExceptionLogFile.filepath: Specifies the file path to output the management command exception log.

admin.logger.ExceptionLogFile.filenum: Specifies the maximum number of exception log files created with a management command.

admin.logger.ExceptionLogFile.filesize: Specifies the maximum size of the exception log file of a management command.

(A2)

instance-name: If omitted, cjmsbroker is used by default.; If you want to use multiple instances, make sure that the names do not overlap.; To overlap the names, specify the -name option, and assign any non-existent name.

Directory-path: Specify the path where you want to output VAR_HOME.

Differences in options based on the modes

Normal mode
No option is specified (starts the Cosminexus JMS Provider services continuously without resetting the status).
Persistent data store reset mode
The persistence messages and persistence subscribers are deleted.
Persistent message clear mode
All the persistence messages are deleted.
Persistent subscription clear mode
All the persistence subscribers are deleted.

(A3)

host-name:port-number: Specify the host name and port number on which CJMSP Broker is running.; If you omit the port number when CJMSP Broker is started, the default port number 7676 is used. In this case, you can omit the -b option.

(A4)

The CJMSP Broker Property File is stored in <VAR_HOME>/instances/instance-name/props/config.properties.

This file is created when CJMSP Broker is started for the first time. Therefore, the (A2) and (A3) steps must be performed.

The specifiable property names and description are as follows. For details on the file, see 7.4 config.properties (CJMSP Broker Property File) in the uCosminexus Application Server Definition Reference Guide.

If you create a temporary destination, the value of imq.autocreate.queue.consumerFlowLimit or imq.autocreate.topic.consumerFlowLimit is set as the destination property.

imq.hostname: Specifies the default host name or IP address of all the connection services.

imq.portmapper.port: Specifies the port number for the port mapper of CJMSP Broker.

imq.jms.tcp.port: Specifies the port number of the jms service.

imq.admin.tcp.port: Specifies the port number of the admin service.

imq.persist.file.sync.enabled: Specifies the flag for synchronous or asynchronous disk write operations.

imq.autocreate.queue.consumerFlowLimit: Specifies the maximum number of messages that one processing unit can deliver to a consumer of a Queue.

imq.autocreate.topic.consumerFlowLimit: Specifies the maximum number of messages that one processing unit can deliver to a consumer of a Topic.

imq.metrics.interval: Specifies the time interval in seconds for the output of the metrics information to the log and console.

broker.logger.MessageLogFile.trace.level: Specifies the message log level of CJMSP Broker.

broker.logger.MessageLogFile.filenum: Specifies the maximum number of message log files created with CJMSP Broker.

broker.logger.MessageLogFile.filesize: Specifies the maximum size of the message log file of CJMSP Broker.

broker.logger.ExceptionLogFile.filenum: Specifies the maximum number of exception log files created with CJMSP Broker.

broker.logger.ExceptionLogFile.filesize: Specifies the maximum size of the exception log file of CJMSP Broker.

imq.instanceconfig.version: Specifies the config property version.

(A5)

instance-name: If omitted, cjmsbroker is used by default.; If you want to use multiple instances, make sure that the names do not overlap.; To overlap the names, specify the -name option, and assign any non-existent name.

Directory-path: Specify the path where you want to output VAR_HOME.

Argument: Specify the JavaVM options such as -Xms (maximum heap size), -Xmx (minimum heap size), and -XX:+HitachiVerboseGC (option to output the extended verbosegc information for garbage collection).

(A6)

Make sure that the State is OPERATING.

host-name:port-number: The host name and port number on which CJMSP Broker is running.; If you omit the port number when CJMSP Broker is started, the default port number 7676 is used. In this case, you can omit the -b option.

(A7)

server-name: Server name set up with Management Server

(A8): No specific value.

Appendix E.6 Starting the Cosminexus JMS Provider services (for the initial startup)

(1) Process preconditions

(2) Information and supplementary explanation required for execution