2.5.1 Environment setup during load balancing cluster configuration

Figure 2-4 shows system setup using load balancer and Figure 2-5 shows system setup using CTM.

Figure 2‒4: System setup using load balancer

Figure 2‒5: System setup using CTM

In case of new setup in version 08-70 or higher version, you can store HCSC-Manager environment in each execution environment. This enables you to omit the number of operating environment servers.

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 execution environment, operating environment and DB server setup methods.

Organization of this subsection

(1) Setting up an execution environment
(2) Setting up an operating environment
(3) Setting up DB server

(1) Setting up an execution environment

Implement the following operations to set up the execution environment.

(a) Installing Service Platform

For details on installation methods of 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 Management Server settings, see "2.1.6 Management Server settings for using HCSC-Manager".

(c) SOAP mode settings

SOAP modes used in the configured execution environment and operating environment must match for load balance cluster configuration of HCSC server. 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 container extension library settings of J2EE server, see "3.1.2(4)(e) Setting up the container extension library".

(d) HCSC server configuration settings

Perform settings related to the execution environment of HCSC server configuration. For details on setting contents and how to execute setting, see "2.3 Settings related to execution environment".

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

Points to be considered when setting HCSC server configuration definition file

To set HCSC server configuration definition file, consider the following contents. 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".

Cluster display name

Set the same value in all HCSC servers in the load balance cluster.
Cluster type

Set "LB".
Manager name

Set a unique identifier in Manager unit in HCSC-Manager.
Manager IP address

Set the physical IP address.
Web server IP address ( to invoke synchronous service (Web service))

Set IP address value of the load balancer in all HCSC servers in the load balance cluster.
Web server IP address (to invoke asynchronous service (MDB(WS-R))

Set each HCSC server IP address. Set in jms-physical-reception in load balance cluster configuration.
NameServer IP address

Set IP address of global CORBA naming service in all HCSC servers in the load balance cluster. However, Specify localhost if CTM is not used.
HCSC server name

Set a unique identifier in the load balance cluster to set up an environment using the database.

Set a unique identifier in HCSC-Manager to set up an environment that does not use either the database or Reliable Messaging.

Points to be considered when setting HCSC server setup definition file

To set HCSC server setup definition file, consider 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

The same value must be set in all HCSC servers in the load balance cluster for properties shown in the following table from among the properties set in HCSC server setup definition file.

Table 2‒22: Properties in which to set the same value in HCSC servers in load balance cluster
Property in which same value is set	Value set in property
db-use	Existence of database use
rm-use	Existence of use of Reliable Messaging
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))
request-userdef-soap	Existence of use of SOAP reception
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
activitynumber-maximum-compatible	Maximum identification number of an activity instance

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".

To Page Top

(2) Setting up an operating environment

Set up the operating environment in HCSC server machine configuring the cluster. 1 to 1 mapping of the operating environment and execution environment is recommended. For configuration of operating environment and execution environment, see "1.2.3 Configuration of the operating environment and the execution environment".

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 environment settings, see "2.1.3 Environment settings".

Embedding HCSC-Manager Plug-in in Eclipse

Embed HCSC-Manager Plug-in in Eclipse.

For embedding 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 methods, 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 load balance cluster and share it with HCSC server in the load balance 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