Appendix E.25 Deleting the Cosminexus JMS Provider service instances

This subsection describes the procedure for deleting the running instances of a Cosminexus JMS Provider service.

You perform this procedure when the previous instances are no longer required because the instance name was changed.

Note
This operation deletes all the information existing for a destination.
Before you execute this operation, make sure that there is no un-processed persistent message and persistent subscriber information.

The following figure shows the procedure for deleting the Cosminexus JMS Provider service instances.

Figure E-24 Procedure for deleting the Cosminexus JMS Provider service instances

[Figure]

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

(1) Process preconditions

(2) Information and supplementary explanation required for execution

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

(A1)
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
VAR_HOME path containing the instances you want to delete
Deletes the directory (default name cjmsbroker) corresponding to the CJMSP Broker instance name.
If you perform this processing, the files and directories related to all the instances are deleted, except the prop and log directories.
If the instance directory is not required, go to the following directory through the explorer and delete the directory manually:
<VAR_HOME>/instances
When starting CJMSP Broker next time, if you use the deleted instance name to start CJMSP Broker again, the instance is re-created.