For starting the Smart Agent on cluster software, you set up the localaddr file and htc.clienthandleraddr file of each node. Note that the settings are different for the multi-homed host environment and for the non multi-homed host environment.

The following table describes the settings for the localaddr file of the Smart Agent when a cluster environment is built on a multi-homed host environment or a multi-homed host environment.

Table A-1 Settings for the localaddr file of the Smart Agent

Host environment on which the cluster service and Smart Agent are running	Settings for the localaddr file of the Smart Agent
	When Smart Agent is set as failover target	When Smart Agent is not set as failover target
Multi-homed host environment	Fixed IP address (primary IP address) IP address that you want to explicitly specify in the Smart Agent Cluster IP address	Fixed IP address (primary IP address) IP address that you want to explicitly specify in the Smart Agent
Non multi-homed host environment	Fixed IP address (primary IP address) Cluster IP address	Fixed IP address (primary IP address)

The following points describe the detailed settings for each environment. The details on the htc.clienthandleraddr file are also described.

(a) Multi-homed host environment

• When Smart Agent is set as a target for failover
  Make sure that you specify settings for the fixed IP address (primary IP address), IP address that you want to explicitly specify in the Smart Agent^#, and the cluster IP address used by the Smart Agent in the localaddr file.
  Also, you define the htc.clienthandleraddr file in such a manner so that the cluster IP address is returned for the processes connected to the Smart Agent.
  
• When Smart Agent is not set as a target for failover
  Make sure that you specify settings for the fixed IP address (primary IP address) and the IP address that you want to explicitly specify in the Smart Agent^# in the localaddr file. You do not specify the cluster IP address.
  Also, you define the htc.clienthandleraddr file in such a manner so that the fixed IP address is returned for the processes connected to the Smart Agent.
  

  #

  If you specify the localaddr file, the Smart Agent will only recognize the IP address specified in the localaddr file. If you do not specify the localaddr file, the Smart Agent will recognize the IP addresses that can be acquired from gethostbyname() by default.

(b) Non multi-homed host environment

• When Smart Agent is set as a target for failover
  Make sure that you specify settings for the fixed IP address (primary IP address) and the cluster IP address used by the Smart Agent in the localaddr file.
  Also, you define the htc.clienthandleraddr file in such a manner so that the cluster IP address is returned for the processes connected to the Smart Agent.
  
• When Smart Agent is not set as a target for failover
  Make sure that you specify settings for the fixed IP address (primary IP address) in the localaddr file. You do not specify the cluster IP address.
  Also, you define the htc.clienthandleraddr file in such a manner so that the fixed IP address is returned for the processes connected to the Smart Agent.
  

For communication between Smart Agents exist on different network domains or for communication between the Smart Agent and the processes connected to the Smart Agent present on different network domains, you must specify the settings for the Smart Agents or for the processes connected to the Smart Agents. Specify the settings in the agentaddr file, vbroker.agent.addr property, and the environment variable OSAGENT_ADDR of each node.

(a) Settings of the Smart Agents

For communications between the Smart Agents exist on different network domains and for setting up the Smart Agent as a failover target, you make sure to specify the cluster IP address in the agentaddr file of the Smart Agent that communicates with the target Smart Agent.

(b) Settings in the processes connected to Smart Agents

For starting a Smart Agent and the processes connected to the Smart Agent on different network domains and for setting a Smart Agent as a failover target, you make sure to specify the cluster IP address of the Smart Agent that becomes the failover target in either of the agentaddr file of the processes connected to the Smart Agent, vbroker.agent.addr property, or the environment variable OSAGENT_ADDR.

For setting the CORBA Naming Service as the failover target, you specify the start property of the CORBA Naming Service.

You set up the following start property in the nameserv command, and start the CORBA Naming Service:

 
-J-Dvbroker.se.iiop_tp.host=cluster-IP-address-or-cluster-network-name
 

Also, you apply the cluster IP address or cluster network specified in this property in the following key settings of the usrconf.properties (user property file for J2EE server) file:

• IP address or host name specified in the ejbserver.naming.host key
• Provider URL specified in the ejbserver.jndi.namingservice.group.specify-group-name.providerurls key

For details on the usrconf.properties file, see 2.4 usrconf.properties (User property file for J2EE servers) in the uCosminexus Application Server Definition Reference Guide. For starting the CORBA Naming Service using the nameserv command, see Appendix D.2 How to start the system in the uCosminexus Application Server Command Reference Guide.

To set up the J2EE server as the failover target, specify the cluster IP address in the vbroker.se.iiop_tp.host key, and start the J2EE server. Furthermore, use and manage the vbroker.se.iiop_tp.scm.iiop_tp.listener.port key of the usrconf.properties file in such a manner so that the same port number can be used for the port number that the J2EE server uses in all the nodes.

To start the Smart Agent in the cluster environment, the following environment variable and option settings must be specified in the Smart Agent.

Specify the options only when you want to set the Smart Agent as a failover target.

• Environment variable name: OSAGENT_CLIENT_HANDLER_PORT
• Option: -m

The following figure shows an example of the IP address settings:

Setting example 1

Figure A-1 Example of the IP address settings when the Smart Agent is set as a target for failover

The points from 1 to 5 in the figure are as follows:

1. Specify 'hostA fixed IP address (A.A.A.A) subnet broadcast' and 'cluster IP address (C.C.C.C) subnet broadcast' in the localaddr file of hostA.
2. Specify ' hostB fixed IP address (B.B.B.B) subnet broadcast' and 'cluster IP address (C.C.C.C) subnet broadcast' in the localaddr file of hostB.
3. Specify 'Fixed IP address of client (F.F.F.F) subnet cluster IP address (C.C.C.C)' in the htc.clienthandleraddr file of hostA and hostB.
4. Specify the environment variable 'OSAGENT_CLIENT_HANDLER_PORT' and -m option in the Smart Agent started on hostA and hostB.
5. Specify the cluster IP address (C.C.C.C) in the agentaddr file of hostC.

Setting example 2

Figure A-2 Example of the IP address settings when smart agent is not set as a target for failover

The points 1 to 5 in the figure are as follows:

1. Specify 'hostA fixed IP address (A.A.A.A) subnet broadcast' in the localaddr file of hostA.
2. Specify 'hostB fixed IP address (B.B.B.B) subnet broadcast' in the localaddr file of hostB.
3. Specify 'Client's fixed IP address (F.F.F.F) subnet hostA stationary IP address (A.A.A.A)' in the htc.clienthandleraddr file of hostA.
4. Specify 'Client's fixed IP address (F.F.F.F) subnet hostB stationary IP address (B.B.B.B)' in the htc.clienthandleraddr file of hostB.
5. Specify A.A.A.A and B.B.B.B in the agentaddr file of hostC.
6. Specify the environment variable OSAGENT_CLIENT_HANDLER_PORT in the Smart Agent running on hostA and hostB.