Sun Cluster 3.1 Data Service for BroadVision One-To-One Enterprise

How to Connect the Command Center to BroadVision One-To-One Enterprise Servers

Use this procedure to connect the Command Center to BroadVision One-To-One Enterprise servers that are configured on a cluster. This procedure provides you two options to connect the Command Center to BroadVision One-To-One Enterprise servers.

  1. Which option do you prefer?

    • Force the Dynamic Control Center (DCC) to use POOP instead of IIOP

      If yes, proceed to Step 2

    • Set the IT_LOCAL_ADDR_LIST property to include the IP addresses of all of the cluster nodes and logical hostnames

      If no, skip to Step 3

  2. Force the Dynamic Control Center (DCC) to use POOP instead of IIOP. To do so, set the value of the My Computer/HKEY_CURRENT_USER/Software/BroadVision/Dynamic Control Center/4.2/Options/Use IIOP Windows registry entry to 0.

  3. Set the IT_LOCAL_ADDR_LIST property to include the IP addresses of all of the cluster nodes and logical hostnames that will run the orbix daemon.

Example - Connecting Command Center to Sun Cluster HA for BroadVision One-To-One Enterprise

This example uses the following sample IP addresses to add to the bv1to1.conf file.

root host

10.10.102.225

back-end host

10.10.102.226

Interaction Manager host

10.10.102.222

Interaction Manager host

10.10.102.223

Based on these sample IP addresses, add the following line to the bv1to1.conf file, under the global export section, before the IT_DAEMON_PORT property.


IT_LOCAL_ADDR_LIST = “127.0.0.1”
               + “10.10.102.222”           
               + “10.10.102.223”           
               + “10.10.102.225”           
               + “10.10.102.226”
               ;           

Note –

DCC cannot recover from a failover. Contact BroadVision One-To-One Enterprise support for more information.