The notes on Component Container are as follows. With Component Container, the preconditions and operations to be implemented vary depending on the system configuration to be set up.

(a) When a system (J2EE server) executing J2EE applications is used

This subsection describes the notes on Component Container when a system (J2EE server) executing J2EE applications is used.

Preconditions

Customize the various Component Container settings, set up the applications, and then install the replicated disk. However, after installing the replicated disk, customize various settings in accordance with the system requirements. For example, change the settings such as those for the load balancers allocated at the front end, or the settings related to DBMS allocated at the back end in the system configuration, according to the system requirements.

Note that replicated disk installation is not supported with the following computers:

• Computer on which the SFO server is running
• Computer on which an EJB client application is running

Operations to be executed before installing the replicated disk

This section describes the operations to be executed on the replicated disk installation source computer before you install the replicated disk.

Implement step 1 and step 2 on the replicated disk installation source computer. If you are using Management Server, implement step 3 as well.

Procedure

1. Terminate the following programs on the replicated disk installation source computer:
   
   • J2EE servers
     You can terminate the J2EE server while the J2EE applications and resource adapters are running. However, if you are using a global transaction, conclude the started transaction and then terminate the J2EE server.
     
   • Web container servers
   • Administration Agent
   • Management Server
   • HTTP Server, or Microsoft IIS
2. If log files exist under the following directories on the replicated disk installation source computer, delete the log files:
   

   Note

   Do not delete the directories.

   • Application-Server-installation-directory\CC\admin\logs\*
   • Application-Server-installation-directory\CC\admin\logs\CC\maintenance\*
   • Application-Server-installation-directory\CC\admin\logs\CC\maintenance\mmap\*
   • Application-Server-installation-directory\CC\admin\logs\CC\rmi\*
   • Application-Server-installation-directory\CC\admin\logs\CC\rmi\mmap\*
   • Application-Server-installation-directory\CC\admin\logs\mmap\*
   • Application-Server-installation-directory\CC\admin\logs\TPB\logj\comtrc\*
   • Application-Server-installation-directory\CC\admin\logs\TPB\logj\mdltrc\*
   • Application-Server-installation-directory\CC\admin\logs\TPB\logj\*
   • Application-Server-installation-directory\CC\client\logs\*
   • Application-Server-installation-directory\CC\client\logs\mmap\*
   • Application-Server-installation-directory\CC\client\logs\system\ejbcl\mmap\*
   • Application-Server-installation-directory\CC\client\logs\system\ejbcl\*
   • Application-Server-installation-directory\CC\client\logs\system\TPB\logj\comtrc\*
   • Application-Server-installation-directory\CC\client\logs\system\TPB\logj\mdltrc\*
   • Application-Server-installation-directory\CC\client\logs\system\TPB\logj\*
   • Application-Server-installation-directory\CC\web\containers\server-name\logs\TPB\logj\comtrc\*
   • Application-Server-installation-directory\CC\web\containers\server-name\logs\TPB\logj\mdltrc\*
   • Application-Server-installation-directory\CC\web\containers\server-name\logs\TPB\logj\*
   • Application-Server-installation-directory\CC\web\containers\server-name\logs\*
   • Application-Server-installation-directory\CC\web\redirector\servers\server-name\logs\*
   • Application-Server-installation-directory\CC\web\redirector\servers\server-name\logs\mmap\*
   • Application-Server-installation-directory\CC\web\redirector\logs\*
   • Application-Server-installation-directory\CC\web\redirector\logs\mmap\*
   • Application-Server-installation-directory\manager\spool\default\*
   • Application-Server-installation-directory\manager\spool\lsinfo\*
   • Application-Server-installation-directory\manager\tmp\*
   • Application-Server-installation-directory\manager\setup\log\*
   • Application-Server-installation-directory\manager\setup\log\maintenance\*
   • Work-directory\ejb\server-name\logs\watch\*
   • Work-directory\ejb\server-name\logs\CC\maintenance\*
   • Work-directory\ejb\server-name\logs\CC\rmi\*
   • Work-directory\ejb\server-name\logs\connectors\*
   • Work-directory\ejb\server-name\logs\connectors\application-display-name\*
   • Work-directory\ejb\server-name\logs\connectors\TEST#application-display-name\*
   • Work-directory\ejb\server-name\logs\TPB\logj\mdltrc\*
   • Work-directory\ejb\server-name\logs\TPB\logj\comtrc\*
   • Work-directory\ejb\server-name\logs\TPB\logj\*
   • Work-directory\ejb\server-name\logs\http\comm\*
   • Work-directory\ejb\server-name\logs\http\thr\*
   • Work-directory\ejb\server-name\logs\http\*
   • Work-directory\ejb\server-name\logs\*
   • Manager-log-output-directory\maintenance\*
   • Manager-log-output-directory\maintenance\mmap\*
   • Manager-log-output-directory\message\*
   • Manager-log-output-directory\message\mmap\*
   • Manager-log-output-directory\trace\*
   • Manager-log-output-directory\trace\mmap\*
   • Manager-log-output-directory\*
   • Manager-log-output-directory\snapshot-log-output-destination-directory\*
   • Audit-log-output-directory\*
   • Message-log-output-directory-of-audit-log\*
   • Message-log-output-directory-of-audit-log\mmap\*
   • Exception-information-output-directory-of-audit-log\*
   • Exception-information-output-directory-of-audit-log\mmap\*

   Reference note

   The default directories are as follows:

   • Work-directory:Application-Server-installation-directory\CC\server\public
   • Manager-log-output-directory:Application-Server-installation-directory\manager\log
   • snapshot-log-output-destination-directory:Manager-log-output-directory\snapshot
   • Audit-log-output-directory:Application-Server-installation-directory\auditlog
   • Message-log-output-directory-of-audit-log:Application-Server-installation-directory\auditlog
   • Exception-information-output-directory-of-audit-log:Application-Server-installation-directory\auditlog

3. If you are using Management Server, change the property file settings on the replicated disk installation source computer.
   The operations differ depending on whether Management Server is running on the replicated disk installation source computer.
   

   If Management Server is not running on the replicated disk installation source computer

   If the replicated disk installation destination computer is a multi-homed host, specify adminagent.adapter.bind_host= regular-expression-matching-with-management-IP-address-for-replicated-disk-installation-destination in the Administration Agent property file (adminagent.properties) of the replicated disk installation source computer in advance.

   If Management Server is running on the replicated disk installation source computer

   Set up the properties described in the following table:

   File name	Property	Value
   .cmxrc and cmxclient.properties	cmx.lb	keepvs
   adminagent.properties	adminagent.adapter.allowedHosts	If the mngsvr.myhost.name property of mserver.properties is set up, specify the same value. If the mngsvr.myhost.name property of mserver.properties is not set up, specify the regular expression matching with the management IP address for the host.
   mserver.properties	mngsvr.myhost.name	If the replicated disk installation destination computer is a multi-homed host, set up regular-expression-matching-with-management-IP-address-for-replicated-disk-installation-destination.
   	webserver.connector.http.bind_host
   adminagent.properties	adminagent.adapter.bind_host
   .mngsvrutilrc and mngsvrutilcl.properties	mngsvrutil.connect.host	If a value other than the loopback address is set up, specify regular-expression-matching-with-management-IP-address-for-replicated-disk-installation-destination.
   	mngsvrutil.target_name
   .cmxrc and cmxclient.properties	cmx.connect.host

Operations to be executed after installing the replicated disk

This section describes the operations to be executed on the replicated disk installation destination computer after you install the replicated disk.

Implement step 1 to step 3 on the replicated disk installation destination computer. If you are using Management Server, implement step 4 as well.

Procedure

1. If the following properties are specified in the user property file for J2EE servers (usrconf.properties), and user property file for server management commands (usrconf.properties), change the values in the replicated disk installation destination computer.
   Change to an appropriate value for each property.
   
   • vbroker.se.iiop_tp.host
   • ejbserver.ctm.CTMMyHost
   • ejbserver.naming.host
2. If the following properties are specified in the user property file for J2EE servers (usrconf.properties), and user property file for Web container servers (usrconf.properties), change the values in the replicated disk installation destination computer.
   Change each property value to the IP address of the replicated disk installation destination.
   
   • webserver.connector.ajp13.bind_host
   • webserver.connector.http.bind_host
   • webserver.connector.inprocess_http.bind_host
   Reset each property value to a unique value for each J2EE server or Web container server.
   
   • webserver.container.server_id.value
   • webserver.session.server_id.value
3. If a value other than localhost or 127.0.0.1 is used in the following property of the worker definition file (workers.properties), change the value to the IP address of the replicated disk installation destination:
   
   • worker.worker-name.host
4. If you are using Management Server, implement the following operations on the replicated disk installation destination computer:
   

   1. Defining the host added by installing the replicated disk

   2. Deleting the host definition of the disk replication source defined on the installation destination host (only when replicating the computer on which Management Server is running)

   3. Defining the logical server added by installing the replicated disk

   4. Setting up the logical server added in 3 (specifying the real server name)

   5. Reading the setup file of the logical server added in 3

   6. Allocating the setup file of the logical server added in 3

   7. Re-allocation after the EAR and RAR files are deleted with the server management commands (only when the application management functionality of J2EE servers is used)

(b) When a system (batch server) executing batch applications is used

This subsection describes the notes on Component Container when a system (batch server) executing batch applications is used.

Preconditions

You can install the replicated disk after you customize various Component Container settings. However, after installing the replicated disk, customize various settings in accordance with the system requirements. For example, change the DBMS-related settings according to the system requirements.

Operations to be executed before installing the replicated disk

This section describes the operations to be executed on the replicated disk installation source computer before you install the replicated disk.

Implement step 1 and step 2 on the replicated disk installation source computer. If you are using Management Server, implement step 3 as well.

Procedure

1. Terminate the following programs on the replicated disk installation source computer:
   
   • Batch servers
     You can terminate the batch servers while the resource adapters are running.
     
   • Administration Agent
   • Management Server
2. If log files exist under the following directories on the replicated disk installation source computer, delete the log files:
   

   Note

   Do not delete the directories.

   • Application-Server-installation-directory\CC\admin\logs\*
   • Application-Server-installation-directory\CC\admin\logs\CC\maintenance\*
   • Application-Server-installation-directory\CC\admin\logs\CC\maintenance\mmap\*
   • Application-Server-installation-directory\CC\admin\logs\CC\rmi\*
   • Application-Server-installation-directory\CC\admin\logs\CC\rmi\mmap\*
   • Application-Server-installation-directory\CC\admin\logs\mmap\*
   • Application-Server-installation-directory\CC\admin\logs\TPB\logj\comtrc\*
   • Application-Server-installation-directory\CC\admin\logs\TPB\logj\mdltrc\*
   • Application-Server-installation-directory\CC\admin\logs\TPB\logj\*
   • Application-Server-installation-directory\CC\client\logs\*
   • Application-Server-installation-directory\CC\client\logs\mmap\*
   • Application-Server-installation-directory\CC\web\containers\server-name\logs\*
   • Application-Server-installation-directory\manager\spool\default\*
   • Application-Server-installation-directory\manager\spool\lsinfo\*
   • Application-Server-installation-directory\manager\tmp\*
   • Application-Server-installation-directory\manager\setup\log\*
   • Application-Server-installation-directory\manager\setup\log\maintenance\*
   • Work-directory\ejb\server-name\logs\watch\*
   • Work-directory\ejb\server-name\logs\CC\maintenance\*
   • Work-directory\ejb\server-name\logs\CC\rmi\*
   • Work-directory\ejb\server-name\logs\connectors\*
   • Work-directory\ejb\server-name\logs\TPB\logj\mdltrc\*
   • Work-directory\ejb\server-name\logs\TPB\logj\comtrc\*
   • Work-directory\ejb\server-name\logs\TPB\logj\*
   • Work-directory\ejb\server-name\logs\*
   • Manager-log-output-directory\maintenance\*
   • Manager-log-output-directory\maintenance\mmap\*
   • Manager-log-output-directory\message\*
   • Manager-log-output-directory\message\mmap\*
   • Manager-log-output-directory\trace\*
   • Manager-log-output-directory\trace\mmap\*
   • Manager-log-output-directory\*
   • snapshot-log-output-destination-directory\*
   • Audit-log-output-directory\*
   • Message-log-output-directory-of-audit-log\*
   • Message-log-output-directory-of-audit-log\mmap\*
   • Exception-information-output-directory-of-audit-log\*
   • Exception-information-output-directory-of-audit-log\mmap\*

   Reference note

   The default directories are as follows:

   • Work-directory:Application-Server-installation-directory\CC\server\public
   • Manager-log-output-directory:Application-Server-installation-directory\manager\log
   • snapshot-log-output-destination-directory:Manager-log-output-directory\snapshot
   • Audit-log-output-directory:Application-Server-installation-directory\auditlog
   • Message-log-output-directory-of-audit-log:Application-Server-installation-directory\auditlog
   • Exception-information-output-directory-of-audit-log:Application-Server-installation-directory\auditlog

3. If you are using Management Server, change the property file settings on the replicated disk installation source computer.
   The operations differ depending on whether Management Server is running on the replicated disk installation source computer.
   

   If Management Server is not running on the replicated disk installation source computer

   If the replicated disk installation destination computer is a multi-homed host, specify adminagent.adapter.bind_host=regular-expression-matching-with-management-IP-address-for-replicated-disk-installation-destination in the Administration Agent property file (adminagent.properties) of the replicated disk installation source computer in advance.

   If Management Server is running on the replicated disk installation source computer

   Set up the properties described in the following table:

   File name	Property	Value
   adminagent.properties	adminagent.adapter.allowedHosts	If the mngsvr.myhost.name property of mserver.properties is set up, specify the same value. If the mngsvr.myhost.name property of mserver.properties is not set up, specify the regular expression matching with the management IP address for the host.
   mserver.properties	mngsvr.myhost.name	If the replicated disk installation destination computer is a multi-homed host, set up regular-expression-matching-with-management-IP-address-for-replicated-disk-installation-destination.
   	webserver.connector.http.bind_host
   adminagent.properties	adminagent.adapter.bind_host
   .mngsvrutilrc and mngsvrutilcl.properties	mngsvrutil.connect.host	If a value other than the loopback address is set up, specify regular-expression-matching-with-management-IP-address-for-replicated-disk-installation-destination.
   	mngsvrutil.target_name
   .cmxrc and cmxclient.properties	cmx.connect.host

Operations to be executed after installing the replicated disk

This section describes the operations to be executed on the replicated disk installation destination computer after you install the replicated disk.

Implement step 1 on the replicated disk installation destination computer. If you are using Management Server, implement step 2 as well.

Procedure

1. If the following properties are specified in the user property file for batch servers (usrconf.properties), and user property file for server management commands (usrconf.properties), change the values in the replicated disk installation destination computer.
   Change to an appropriate value for each property.
   
   • vbroker.se.iiop_tp.host
   • ejbserver.naming.host
2. If you are using Management Server, implement the following operations on the replicated disk installation destination computer:
   

   1. Defining the host added by installing the replicated disk

   2. Deleting the host definition of the disk replication source defined on the installation destination host (only when replicating the computer on which Management Server is running)

   3. Defining the logical server added by installing the replicated disk

   4. Setting up the logical server added in 3 (specifying the real server name)

   5. Reading the setup file of the logical server added in 3

   6. Allocating the setup file of the logical server added in 3

   7. Re-allocation after the RAR files are deleted with the server management commands (only when the application management functionality of J2EE servers is used)

This subsection describes the notes on Component Container - Redirector.

Preconditions

You can install the replicated disk after you customize various Component Container - Redirector settings. However, after installing the replicated disk, customize various settings in accordance with the system requirements. For example, change the settings such as those for the load balancers allocated at the front end, or the settings related to the J2EE servers or Web container servers allocated at the back end in the system configuration, according to the system requirements.

Operations to be executed before installing the replicated disk

This section describes the operations to be executed on the replicated disk installation source computer before you install the replicated disk.

Implement step 1 and step 2 on the replicated disk installation source computer.

Procedure

1. Terminate the following program on the replicated disk installation source computer:
   
   • HTTP Server, or Microsoft IIS
2. If log files exist under the following directories on the replicated disk installation source computer, delete the log files:
   

   Note

   Do not delete the directories.

   • Application-Server-installation-directory\CCR\web\redirector\servers\server-name\logs\*
   • Application-Server-installation-directory\CCR\web\redirector\servers\server-name\logs\mmap\*
   • Application-Server-installation-directory\CCR\web\redirector\logs\*
   • Application-Server-installation-directory\CCR\web\redirector\logs\mmap\*

This subsection describes the notes on Reliable Messaging.

Operations to be executed before installing the replicated disk

This section describes the operations to be executed on the replicated disk installation source computer before you install the replicated disk.

Implement step 1 and step 2 on the replicated disk installation source computer.

Procedure

1. Deploy Reliable Messaging on the J2EE server. If Reliable Messaging is running, stop Reliable Messaging on the J2EE server.
2. If log files exist under the following directory on the replicated disk installation source computer, delete the log files:
   

   Note

   Do not delete the directories.

   • Work-directory\ejb\server-name\logs\RM\maintenance
     The default work-directory is Application-Server-installation-directory\CC\server\public.
     

Operations to be executed after installing the replicated disk

This section describes the operations to be executed on the replicated disk installation destination computer after you install the replicated disk.

Implement step 1 to step 5 on the replicated disk installation destination computer.

Procedure

1. If you changed the host name or IP address for the replicated system, update the following Reliable Messaging settings:
   
   • Update the settings for the environment variable HRM_CMD_HOST to the host name or IP address of the replicated system.
   • If you change the host name or IP address of the transmit destination system by using the transmit between queues functionality, use the following procedure to re-create the address existing in the transmit source system and the transmit queue, which uses that address:
     1. Make sure there are no messages in all the transmit queues that are using the transmit source system address.
     2. Delete all the transmit queues that are using the transmit source system address.
     3. Delete the transmit source system address.
     4. Specify the changed host name or IP address and create a new transmit source system address.
     5. Create a new transmit queue for using the transmit source system address.
     
2. Change the configuration property RMSystemName and the environment variable HRM_SYSTEM_NAME so that the Reliable Messaging system name is unique.
3. Create a management information table corresponding to the system name changed in step 2.
   For details on how to create a management information table, see the manual Cosminexus Reliable Messaging.
   
4. When you use HiRDB as DBMS and the configuration uses an XA transaction, change the configuration properties description and XAOpenString of the integration destination DB Connector so that XAOpenString of the integration destination DB Connector for Reliable Messaging is unique among the resource adapters connected to the same HiRDB.
5. Start Reliable Messaging and create the required queues.

After you install the replicated disk, delete everything under the directory specified in the environment variable CTMSPOOL on the replicated disk installation destination computer.

After you install the replicated disk, delete everything under the directory specified in the environment variable PRFSPOOL on the replicated disk installation destination computer.

This subsection describes the notes on HTTP Server.

Operations to be executed before installing the replicated disk

Before you install the replicated disk, terminate all the operations of all the HTTP Server programs and related files on the replicated disk installation source computer.

Operations to be executed after installing the replicated disk

This section describes the operations to be executed on the replicated disk installation destination computer after you install the replicated disk.

Implement step 1 to step 3 on the replicated disk installation destination computer.

Procedure

1. As and when required, change the settings for the directives after installing the replicated disk.
   
   • Network-related directives
     ServerName, <VirtualHost>, BindAddress, Listen, and NameVirtualHost
     
   • File system-related directives
     <Directory>, <DirectoryMatch>, Alias, AliasMatch, AuthGroupFile, AuthUserFile, CustomLog, DocumentRoot, ErrorLog, HWSRequestLog, HWSTraceIdFile, HWSTraceLogFile, Include, LoadFile, LoadModule, PidFile, QOSResponse, ScriptAlias, ScriptAliasMatch, ScriptLog, ServerRoot, SSLCACertificateFile, SSLCertificateFile, SSLCertificateKeyFile, SSLCertificateKeyPassword, SSLCRLDERPath, SSLCRLPEMPath, TransferLog, TypesConfig, and UserDir
     
2. If a file specified in the PidFile directive is copied, delete the file before you start HTTP Server.
3. If the log-related files are copied, delete the unnecessary files as and when required.

This subsection describes the notes on TPBroker.

Preconditions

For details on how to integrate a system with JP1/SC/DPM, see the TPBroker Operation Guide.

Operations to be executed after installing the replicated disk

This section describes the operations to be executed after you install the replicated disk. Implement step 1 and step 2.

Procedure

1. If you are using the replication functionality based on image filing provided by the virtual platform, and if the following settings are specified, change the specified host name and IP address in accordance with the system:
   
   • agentaddr file (can also be specified in the environment variable OSAGENT_ADDR_FILE or property vbroker.agent.addrFile)
   • localaddr file (can also be specified in the environment variable OSAGENT_LOCAL_FILE or property vbroker.agent.localFile)
   • htc.clienthandleraddr file (can also be specified in the environment variable HVI_OSAGENT_CLIENTHANDLERADDR_FILE)
   • Property vbroker.agent.addr
   • Property vbroker.se.server-engine.host
   • Property vbroker.se.server-engine.proxyHost
   • Property vbroker.orb.initRef
   • Property vbroker.orb.defaultInitRef (only C++)
   • Command line option ORBInitRef
   • Command line option ORBDefaultInitRef (only C++)
   • Command line option ORBagentAddr
   • osagent command line option -a
   • Environment variable OSAGENT_ADDR
   Also, after you change the host name and IP address, re-create and re-allocate the IOR file that was created before you changed the host name and IP address.
   
2. If you are using the replication functionality in the virtual environment, and if a global transaction is used, delete the status file of the in-process transaction service if present, so that the virtual environment replication source does not include the status file of the in-process transaction service.

This subsection describes the notes on Service Coordinator.

Operations to be executed before installing the replicated disk

This section describes the operations to be executed on the replicated disk installation source computer before you install the replicated disk.

Implement step 1 and step 2 on the replicated disk installation source computer.

Procedure

1. From the uCosminexus BPM/ESB Service Platform System Setup and Operation Guide, implement the operations until Setting up the required software in the execution environment.
2. Implement the "Operations to be executed before installing the replicated disk" for the following component software:
   
   • Component Container
   • Reliable Messaging
   • HTTP Server
   • TPBroker
   • DABroker Library (compatibility function)^#

   # Applicable only in Windows x86.

Operations to be executed after installing the replicated disk

This section describes the operations to be executed after you install the replicated disk. Implement step 1 and step 2.

Procedure

1. On the replicated disk installation destination computer, implement the "Operations to be executed after installing the replicated disk" for the following component software:
   
   • Component Container
   • Reliable Messaging
   • Component Transaction Monitor
   • Performance Tracer
   • HTTP Server
   • TPBroker
2. From the uCosminexus BPM/ESB Service Platform System Setup and Operation Guide, implement the operations subsequent to Setting up HCSC server on the replicated disk installation source computer, and replicated disk installation destination computer.

This subsection describes the notes on using DABroker Library.

Operations to be executed before installing the replicated disk

This section describes the operations to be executed on the replicated disk installation source computer before you install the replicated disk.

Implement step 1 on the replicated disk installation source computer.

Procedure

1. On the replicated disk installation source computer, delete the DABroker Library temporary files, log files, and trace files existing beneath the following directories:
   
   • Application-Server-installation-directory/DAB/tmp/*
   • Application-Server-installation-directory/DAB/spool/*.txt
   • Application-Server-installation-directory/DAB/spool/*.txt.lock
   • Application-Server-installation-directory/DAB/spool/*.log
   • Application-Server-installation-directory/DAB/spool/*.log.lock
   • Application-Server-installation-directory/DAB/spool/*.lock
   • Application-Server-installation-directory/DAB/spool/db_access/*
   • Application-Server-installation-directory/DAB/spool/dabcltrc/*
   • Application-Server-installation-directory/DAB/spool/dabdump/*