2.7.1 Environment setup in 1 to N cluster configuration

Set "HA" as the cluster to be set in HCSC server configuration definition file for all HCSC servers configuring clusters in 1 to N cluster configuration. You cannot set up 1 to N cluster configuration if cluster type is "LB".

While using standard asynchronous reception (MDB (WS-R)/MDB (DB queue)), the requester must be set to send a request to HCSC server group suitable for HA cluster.

Important note: Create a unique GUI display name of HCSC cluster in the system.

Re-executing a business process from another HCSC server in case of server fault

The following information must be stored in the common disk device in order to re-execute a business process from another HCSC server:

Operation folder
Common folder
I/O enabled file used in the file adapter

Store the following information in the local disk device. However, the same value must be set in each HCSC server.

Text file of main text in mail used in the mail adapter, and the attached file
Definition file used in HCSC server operations
Definition file used in HCSC component

Re-executing a business process using the operation folder

You cannot re-execute a business process from another HCSC server if the business process uses the operation folder and if the business process is executed in a version lower than 09-51.

You can re-execute a business process if the common folder is used instead of the operation folder or if the business process has been executed in 09-51 or higher version. However, you cannot re-execute a business process executed in a version lower than 09-51 because the common folder cannot be used for business processes using the following components:

FTP reception
HTTP reception

The following points show the environment setup procedures to operate HCSC server in 1 to N cluster configuration.

Organization of this subsection

(1) Setting up an execution environment (executing node and standby node)
(2) Setting up an operating environment
(3) Setting up DB server

(1) Setting up an execution environment (executing node and standby node)

To set up the execution environment, implement the following operations by executing node and standby node:

(a) Installing Service Platform

Install Service Platform in each machine.

For details on how to install Service Platform, see "2.1.2 Installing Service Platform".

(b) Management Server settings

Implement Management Server settings to use HCSC-Manager in the operating environment by the execution environment of HCSC-Manager connection destination.

For details on how to perform settings of Management Server, see "2.1.6 Management Server settings for using HCSC-Manager".

(c) SOAP mode settings

To change HCSC server to 1 to N cluster configuration, SOAP modes used in the configured execution environment and operating environment must match. Different SOAP mode environments cannot co-exist.

The container extension library of J2EE server must be set in order to set SOAP mode. For details on how to set up container extension library of J2EE server, see "3.1.2(4)(e) Setting up the container extension library".

(d) HCSC server configuration settings

Implement in each machine the settings related to the execution environment such as HCSC server configuration according to the configured HCSC server type (executing node/standby node). Setting contents and setting methods are the same as in the load balance cluster configuration and HA cluster configuration. For details on setting contents and how to set up, see "2.3 Settings related to execution environment".

The following items show configuration examples when HCSC server is configured in executing node or standby node as well as HCSC server configuration setting procedures.

Setting up an executing node HCSC server

The following figure shows an example of setup when HCSC server (HCSC server2) suitable for the load balance cluster is added in HA cluster configuration (HCSC server1/HCSC server4).

Figure 2‒9: Setup example of HCSC server in executing node (example when HCSC server2 is added)

While setting procedures for setting up HCSC server in executing node are basically the same as setting procedures of the load balance cluster configuration, please note the following points:

Specify "HA" for the cluster type set in HCSC server configuration definition file.
Specify a unique name for RM system name set in HCSC server setup definition file between HCSC servers in executing node in the cluster. Error does not occur in setup if a duplicate RM system name is set but dead lock occurs when Reliable Messaging starts.

For details on how to set the load balance cluster configuration, see HCSC server configuration settings in "2.5.1 Environment setup during load balancing cluster configuration".

Setting up HCSC server in standby node

The following figure shows an example of setting up HCSC server 5 in standby node of HCSC server 2 in machine 4 in the configuration shown in the figure in "Setting up an executing node HCSC server":

Figure 2‒10: Example of setting up HCSC server in executing node (example when HCSC server is set up in machine 4)

While setting procedures for setting up HCSC server in standby node are basically the same as the setting procedures of HA cluster configuration, please note the following points:

Specify a unique name for J2EE server name set in HCSC server configuration definition file to set up HCSC server in standby node in 1 machine.
Specify the same name for RM system name in HCSC server setup definition file as in HCSC server in executing node in the load balance cluster configuration. Error does not occur in setup if you set RM system name different from executing node but the process using Reliable Messaging is not inherited.

For details on how to perform of HA cluster configuration, see HCSC server configuration settings in "2.6.1 Environment setup in HA class configuration".

To set HCSC server configuration definition file, HCSC server setup definition file and HCSC server runtime definition file in the settings related to the execution environment, note the following contents:

Points to be considered when setting HCSC server configuration definition file

Set the following values for HCSC server configuration definition file during setup.

For details on how to set the HCSC server configuration definition file, see "2.3.1 Setting HCSC server configuration definition file".

For details on contents to be set in HCSC server configuration definition file, see "6.4.2 HCSC server configuration definition file" in "Service Platform Reference Guide".

Setting items	Setting values
Cluster display name	Same value as in cluster
Cluster type	Same value as in cluster
manager name	Unique value in system
manager IP address	Physical IP address for management
Web server IP address ( to invoke synchronous service (Web service))	Same value as in cluster
Web server IP address (to invoke asynchronous service (MDB(WS-R))	IP address of each HCSC server reception (specify identical IP address as in executing node and standby node (virtual IP address))
NameServer IP address	Same value as in cluster

Points to be considered when setting HCSC server setup definition file

To set HCSC server setup definition file, note the following contents. For details on how to set the HCSC server setup definition file, see "2.3.2 Setting HCSC server setup definition file". For details on contents to be set in HCSC server setup definition file, see "6.4.3 HCSC server setup definition file" in "Service Platform Reference Guide".

Properties in which to set the same value in all HCSC servers

For properties shown in the following table from among the properties set in HCSC server setup definition file, the same value must be set in all HCSC servers in N to 1 cluster.

Table 2‒24: Properties in which to set same value in HCSC server in N to 1 cluster
Property in which same value is set	Value set in property
request-ejb	Existence of use of standard synchronous reception (SessionBean)
request-soap	Existence of use of standard synchronous reception (Web service)
request-jms	Existence of use of standard asynchronous reception (MDB(WS-R))
request-jms.maxmessage	Maximum number of messages in standard asynchronous reception (MDB(WS-R)) queue
request-dbq	Existence of use of standard asynchronous reception (MDB(DB queue))
request-dbq.maxmessage	Maximum number of messages in standard asynchronous reception (MDB(DB queue)) queue
request-jms-rdarea	RD area name in standard asynchronous reception (MDB(WS-R))
request-dbq-rdarea	RD area name in standard asynchronous reception (MDB(DB queue))
request-dbq-maxlen	Maximum message length in standard asynchronous reception (MDB(DB queue))
rm-displayname	Reliable Messaging display name
dbcon-xadisplayname^#1	DB Connector display name for XATransaction or LocalTransaction
dbcon-nodisplayname^#1	DB Connector display name for NoTransaction
dbtype	Used database type
jdbc-type	JDBC driver type
jdbc-url^#2	Database URL for JDBC
jdbc-dbhostname	Database host name
jdbc-dbconnectinfo	Database connection information
db-character-sets	Database character code type
db-tbl-split-key	Existence of use of table range partition functionality by date data
db-tbl-split-corcheck-use	Existence of enhancement of correlation set duplication check

Note #1: DB Connector settings are the same in all HCSC servers in the load balance cluster.
Note #2: In the host name to be specified, specify the machine in which the database is stored.

Points to be considered when setting HCSC server runtime definition file

To set HCSC server runtime definition file, the same value must be set in all HCSC servers in the load balance cluster.

Add the following property if CTM is used:

request-ejb.ctm=true

Add the following property if J2EE server name is different in HCSC server configuring the cluster:

request-ejb.optional.name=<Optional name of synchronous requester service (SessionBean) shared in the cluster>

For details on how to set the HCSC server runtime definition file, see "2.3.3 Setting HCSC server runtime definition file".

For details on contents to be set in HCSC server runtime definition file, see "6.5.6 HCSC server runtime definition file" in "Service Platform Reference Guide".

(e) Installing cluster software

Install cluster software. For details on how to install, see the used cluster software document.

To Page Top

(2) Setting up an operating environment

Set up the operating environment in HCSC server machine configuring the cluster.

For details on how to configure the operating environment and execution environment, see "1.5 Configuration pattern of an operating environment in the cluster configuration " in "Service Platform Overview".

Implement the following operations to set up the operating environment:

Environment settings

Implement repository settings and environment variable settings as the environment settings of the operating environment.

For details on how to perform environment settings, see "2.1.3 Environment settings".

Embedding HCSC-Manager Plug-in in Eclipse

Embed HCSC-Manager Plug-in in Eclipse.

For details on how to embed the HCSC-Manager Plug-in in Eclipse, see "2.1.5 Embedding HCSC-Manager plug-in in Eclipse".

Setting user permission

Set user permission related to the operating environment. For details on setting contents and how to set, see "2.4 Settings Related to the Operating Environment".

To Page Top

(3) Setting up DB server

Set up DB server isolated from HCSC server configuring the cluster and share it with HCSC server in the cluster.

Install the database to be used in the machine used as DB server. For details on how to install, see documents of the used database.

To Page Top