I.4 Notes on replicated disk installation and on using the replication functionality provided by the virtual platform (In Linux)

This subsection separately describes notes that apply to each piece of component software when performing replicated disk installation.

Organization of this subsection

(1) Notes on Component Container
(2) Notes on Component Container - Redirector
(3) Notes on Reliable Messaging
(4) Notes on Component Transaction Monitor
(5) Notes on Performance Tracer
(6) Notes on HTTP Server
(7) Notes on TPBroker
(8) Notes on Service Coordinator

(1) Notes on Component Container

The notes on Component Container are as follows. For Component Container, the work you need to perform differs according to the system configuration you are setting 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.

Work to perform before replication

The following explains the work you need to perform on the replication source machine before performing replication.

Implement steps 1 and 2 on the replication source machine. If you are using Management Server, implement step 3 as well.

Procedure

Stop the following programs on the replication source machine:

J2EE servers (if you are using global transactions, settle any pending transactions before closing the J2EE server programs.)

Web container server

Administration Agent

Management Server

HTTP Server
On the replication source machine, delete any files in the following directories. Do not delete the directories themselves.

/opt/Cosminexus/CC/admin/logs/*

/opt/Cosminexus/CC/admin/logs/CC/maintenance/*

/opt/Cosminexus/CC/admin/logs/CC/maintenance/mmap/*

/opt/Cosminexus/CC/admin/logs/CC/rmi/*

/opt/Cosminexus/CC/admin/logs/CC/rmi/mmap/*

/opt/Cosminexus/CC/admin/logs/mmap/*

/opt/Cosminexus/CC/admin/logs/TPB/logj/comtrc/*

/opt/Cosminexus/CC/admin/logs/TPB/logj/mdltrc/*

/opt/Cosminexus/CC/admin/logs/TPB/logj/*

/opt/Cosminexus/CC/client/logs/*

/opt/Cosminexus/CC/client/logs/mmap/*

/opt/Cosminexus/CC/client/logs/system/ejbcl/mmap/*

/opt/Cosminexus/CC/client/logs/system/ejbcl/*

/opt/Cosminexus/CC/client/logs/system/TPB/logj/comtrc/*

/opt/Cosminexus/CC/client/logs/system/TPB/logj/mdltrc/*

/opt/Cosminexus/CC/client/logs/system/TPB/logj/*

/opt/Cosminexus/CC/web/containers/server-name/logs/TPB/logj/comtrc/*

/opt/Cosminexus/CC/web/containers/server-name/logs/TPB/logj/mdltrc/*

/opt/Cosminexus/CC/web/containers/server-name/logs/TPB/logj/*

/opt/Cosminexus/CC/web/containers/server-name/logs/*

/opt/Cosminexus/CC/web/redirector/servers/server-name/logs/*

/opt/Cosminexus/CC/web/redirector/servers/server-name/logs/mmap/*

/opt/Cosminexus/CC/web/redirector/logs/*

/opt/Cosminexus/CC/web/redirector/logs/mmap/*

/opt/Cosminexus/manager/spool/default/*

/opt/Cosminexus/manager/spool/lsinfo/*

/opt/Cosminexus/manager/tmp/*

/opt/Cosminexus/manager/setup/log/*

/opt/Cosminexus/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/*

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:/opt/Cosminexus/CC/server/public
- Manager-log-output-directory:/opt/Cosminexus/manager/log
- snapshot-log-output-destination-directory:Manager-log-output-directory/snapshot
- Audit-log-output-directory:/opt/Cosminexus/auditlog
- Message-log-output-directory-of-audit-log:/opt/Cosminexus/auditlog
- Exception-information-output-directory-of-audit-log:/opt/Cosminexus/auditlog

When using the Management Server, modify the settings in the property files on the replication source machine.

The work you need to perform differs according to whether Management Server is running on the replication source machine.

If Management Server is not running on the replication source machine

If the replication destination machine is a multihomed host, specify adminagent.adapter.bind_host=regular-expression-matching-management-IP-address-of-replication-destination in the Administration Agent property file (adminagent.properties) on the replication source machine.

If Management Server is running on the replication source machine

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 replication destination machine is a multihomed host, specify a `regular-expression-matching-management-IP-address-of-replication-destination`.
`mserver.properties`	`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 a `regular-expression-matching-management-IP-address-of-replication-destination`.
`.mngsvrutilrc` and `mngsvrutilcl.properties`	`mngsvrutil.target_name`
`.cmxrc` and `cmxclient.properties`	`cmx.connect.host`

Work to perform after replication

The following explains the work you need to perform on the replication destination machine after performing replication.

Implement steps 1 and 2 on the replication source machine. If you are using Management Server, implement step 3 as well.

Procedure
1. If any of the following properties are specified in the user property file for J2EE servers (usrconf.properties) or the user property file for server management commands (usrconf.properties), change the values on the replication destination machine.
  
  Change to an appropriate value for each property.
  
  vbroker.se.iiop_tp.host
  
  ejbserver.ctm.CTMMyHost
  
  ejbserver.naming.host
  
  ejbserver.rmi.naming.host
2. If any of the following properties are specified in the user property file for J2EE servers (usrconf.properties) or the user property file for Web container servers (usrconf.properties), change the values on the replication destination machine.
  
  Change the value of each property to the IP address of the replication destination.
  
  webserver.connector.http.bind_host
  
  webserver.connector.nio_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. When using the Management Server, perform the following operations on the replication destination machine:
  
  1. Defining the host added by the replication process
  
  2. Deleting the definition of the replication source host from the replication destination host (only when replicating the computer on which Management Server is running)
  
  3. Defining the logical server added by the replication process
  
  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.

Work to perform before replication

The following explains the work you need to perform on the replication source machine before performing replication.

Implement steps 1 and 2 on the replication source machine. If you are using Management Server, implement step 3 as well.

Procedure

Stop the following programs on the replication source machine:

Batch servers (you can stop batch servers without shutting down the resource adapters.)

Administration Agent

Management Server
On the replication source machine, delete any files in the following directories. Do not delete the directories themselves.

/opt/Cosminexus/CC/admin/logs/*

/opt/Cosminexus/CC/admin/logs/CC/maintenance/*

/opt/Cosminexus/CC/admin/logs/CC/maintenance/mmap/*

/opt/Cosminexus/CC/admin/logs/CC/rmi/*

/opt/Cosminexus/CC/admin/logs/CC/rmi/mmap/*

/opt/Cosminexus/CC/admin/logs/mmap/*

/opt/Cosminexus/CC/admin/logs/TPB/logj/comtrc/*

/opt/Cosminexus/CC/admin/logs/TPB/logj/mdltrc/*

/opt/Cosminexus/CC/admin/logs/TPB/logj/*

/opt/Cosminexus/CC/client/logs/*

/opt/Cosminexus/CC/client/logs/mmap/*

/opt/Cosminexus/CC/web/containers/server-name/logs/*

/opt/Cosminexus/manager/spool/default/*

/opt/Cosminexus/manager/spool/lsinfo/*

/opt/Cosminexus/manager/tmp/*

/opt/Cosminexus/manager/setup/log/*

/opt/Cosminexus/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:/opt/Cosminexus/CC/server/public
- Manager-log-output-directory:/opt/Cosminexus/manager/log
- snapshot-log-output-destination-directory:Manager-log-output-directory/snapshot
- Audit-log-output-directory:/opt/Cosminexus/auditlog
- Message-log-output-directory-of-audit-log:/opt/Cosminexus/auditlog
- Exception-information-output-directory-of-audit-log:/opt/Cosminexus/auditlog

When using the Management Server, modify the settings in the property files on the replication source machine.

The work you need to perform differs according to whether Management Server is running on the replication source machine.

If Management Server is not running on the replication source machine

If Management Server is running on the replication source machine

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 replication destination machine is a multihomed host, specify a `regular-expression-matching-management-IP-address-of-replication-destination`.
`mserver.properties`	`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 a `regular-expression-matching-management-IP-address-of-replication-destination`.
`.mngsvrutilrc` and `mngsvrutilcl.properties`	`mngsvrutil.target_name`
`.cmxrc` and `cmxclient.properties`	`cmx.connect.host`

Work to perform after replication

The following explains the work you need to perform on the replication destination machine after performing replication.

Implement step 1 on the replication destination machine. If you are using Management Server, implement step 2 as well.

Procedure
1. If any of the following properties are specified in the user property file for batch servers (usrconf.properties) or the user property file for server management commands (usrconf.properties), change the values on the replication destination machine.
  
  Change to an appropriate value for each property.
  
  vbroker.se.iiop_tp.host
  
  ejbserver.naming.host
  
  ejbserver.rmi.naming.host
2. When using the Management Server, perform the following operations on the replication destination machine:
  
  1. Defining the host added by the replication process
  
  2. Deleting the definition of the replication source host from the replication destination host (only when replicating the computer on which Management Server is running)
  
  3. Defining the logical server added by the replication process
  
  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)

To Page Top

(2) Notes on Component Container - Redirector

This subsection describes the notes on Component Container - Redirector.

Work to perform before replication

The following explains the work you need to perform on the replication source machine before performing replication.

Implement steps 1 and 2 on the replication source machine.

Procedure
1. Stop the following program on the replication source machine:
  
  HTTP Server
2. On the replication source machine, delete any files in the following directories. Do not delete the directories themselves.
  
  /opt/Cosminexus/CCR/web/redirector/servers/server-name/logs/*
  
  /opt/Cosminexus/CCR/web/redirector/servers/server-name/logs/mmap/*
  
  /opt/Cosminexus/CCR/web/redirector/logs/*
  
  /opt/Cosminexus/CCR/web/redirector/logs/mmap/*

To Page Top

(3) Notes on Reliable Messaging

This subsection describes the notes on Reliable Messaging.

Work to perform before replication

The following explains the work you need to perform on the replication source machine before performing replication.

Implement steps 1 and 2 on the replication source machine.

Procedure
1. Deploy Reliable Messaging on the J2EE server. If Reliable Messaging is running, stop Reliable Messaging on the J2EE server.
2. On the replication source machine, delete any log files in the following directories. Do not delete the directories themselves.
  
  Work-directory/ejb/server-name/logs/RM/maintenance
  
  The default work-directory is /opt/Cosminexus/CC/server/public.
Work to perform after replication

The following explains the work you need to perform on the replication destination machine after performing replication.

Implement steps 1 to 5 on the replication destination machine.

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.

To Page Top

(4) Notes on Component Transaction Monitor

Work to perform after replication

After performing replication, delete the entire contents of the directory specified in the CTMSPOOL environment variable from the replication destination machine.

To Page Top

(5) Notes on Performance Tracer

After performing replication, delete the entire contents of the directory specified in the PRFSPOOL environment variable from the replication destination machine.

To Page Top

(6) Notes on HTTP Server

This subsection describes the notes on HTTP Server.

Work to perform before replication

Before performing replication, stop all HTTP Server programs on the replication source machine and any pending operations on related files.
Work to perform after replication

The following explains the work you need to perform on the replication destination machine after performing replication.

Implement steps 1 to 3 on the replication destination machine.

Procedure
1. As needed, change the directive settings after replication.
  
  Network-related directives
  
  ServerName, <VirtualHost>, BindAddress, Listen, and NameVirtualHost
  
  File system-related directives
  
  <Directory>, <DirectoryMatch>, AccessFileName, Alias, AliasMatch, AuthGroupFile, AuthUserFile, CoreDumpDirectory, CustomLog, DocumentRoot, ErrorLog, HWSRequestLog, HWSTraceIdFile, HWSTraceLogFile, Include, LoadFile, LoadModule, PidFile, QOSResponse, ScriptAlias, ScriptAliasMatch, ScriptLog, ServerRoot, SSLCACertificateFile, SSLCACertificatePath, SSLCacheServerPath, SSLCacheServerPort, SSLCacheServerRunDir, 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.

To Page Top

(7) Notes on TPBroker

This subsection describes the notes on TPBroker.

Work to perform after replication

The following explains the work you need to perform after replication. 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.

To Page Top

(8) Notes on Service Coordinator

This subsection describes the notes on Service Coordinator.

Work to perform before replication

The following explains the work you need to perform on the replication source machine before performing replication.

Implement steps 1 and 2 on the replication source machine.

Procedure
1. From the uCosminexus Service Platform Setup and Operation Guide, implement the operations until Setting up the software required for the execution environment.
2. Implement the "Work to perform before replication" for the following component software:
  
  Component Container
  
  Reliable Messaging
  
  HTTP Server
  
  TPBroker
Work to perform after replication

The following explains the work you need to perform after replication. Implement step 1 and step 2.

Procedure
1. On the replication destination machine, perform the "Work to perform after replication" for the following component software:
  
  Component Container
  
  Reliable Messaging
  
  Component Transaction Monitor
  
  Performance Tracer
  
  HTTP Server
  
  TPBroker
2. On the replication source and destination machines, perform the work from Setting up an HCSC server onward in the uCosminexus Service Platform Setup and Operation Guide.

To Page Top