test

Sun Cluster Data Service for BroadVision One-To-One Enterprise Guide for Solaris OS

Registering and Configuring Sun Cluster HA for BroadVision One-To-One Enterprise

This section contains the procedures you need to configure Sun Cluster HA for BroadVision One-To-One Enterprise.

Setting Sun Cluster HA for BroadVision One-To-One Enterprise Extension Properties

The sections that follow contain instructions for registering and configuring resources. For information about the Sun Cluster HA for BroadVision One-To-One Enterprise extension properties, see Appendix A, Sun Cluster HA for BroadVision One-To-One Enterprise Extension Properties. The Tunable entry indicates when you can update a property.

To set an extension property of a resource, include the following option in the scrgadm(1M) command that creates or modifies the resource:


-x property=value
-x property

Identifies the extension property that you are setting

value

Specifies the value to which you are setting the extension property

You can also use the procedures in Chapter 2, Administering Data Service Resources, in Sun Cluster Data Services Planning and Administration Guide for Solaris OS to configure resources after the resources are created.

ProcedureHow to Register and Configure Sun Cluster HA for BroadVision One-To-One Enterprise

Use this procedure to register and configure Sun Cluster HA for BroadVision One-To-One Enterprise.

Note –

Before you start Sun Cluster HA for BroadVision One-To-One Enterprise, check that your database is accessible.

Steps

  1. Shut down all of the BroadVision One-To-One Enterprise servers, including the root host, back-end, and Interaction Manager servers.

    Note –

    Perform this step after you test the BroadVision One-To-One Enterprise installation.

  2. Run the ps(1) command to check that all of the BroadVision One-To-One Enterprise processes and the orbix daemon (orbixd) are stopped on all of the cluster nodes.

  3. Become superuser on one cluster node.

  4. Run the scrgadm command to register the resource type for Sun Cluster HA for BroadVision One-To-One Enterprise.


    # scrgadm -a -t SUNW.bv
    -a

    Adds the resource type for the data service.

    -t SUNW.bv

    Specifies the resource type name that is predefined for your data service.

  5. Run the scrgadm command to create the root host, back-end, and Interaction Manager resources.

    1. Create root host and back-end resources in the failover resource groups that you created in Step 2 of How to Configure and Verify the BroadVision One-To-One Enterprise Software, Database, and HTTP Server Installation.

      Note –

      The bvuser and BV1TO1_VAR should be the same for all of the resources.


      # scrgadm -a -j root-host-resource -g root-host-resource-group \
 -t SUNW.bv -x BVUSER=bvuser \
 -x BV1TO1_VAR=path-to-bv1to1_var-directory
# scrgadm -a -j back-end-resource-1 -g back-end-resource-group-1 \
 -t SUNW.bv -x BVUSER=bvuser \
 -x BV1TO1_VAR=path-to-bv1to1_var-directory
# scrgadm -a -j back-end-resource-2 -g back-end-resource-group-2 \
 -t SUNW.bv -x BVUSER=bvuser \
 -x BV1TO1_VAR=path-to-bv1to1_var-directory
...
# scrgadm -a -j back-end-resource-n -g back-end-resource-group-n \
 -t SUNW.bv -x BVUSER=bvuser \
 -x BV1TO1_VAR=path-to-bv1to1_var-directory
      -j root-host-resource

      Specifies the name of the root host resource.

      -x BVUSER=bvuser

      Specifies your BroadVision username.

      -x BV1TO1_VAR=path-to-bv1to1_var-directory

      Specifies the path to the $BV1TO1_VAR directory.

      -j back-end-resource-n

      Specifies the name of the back-end resource.

    2. Create the Interaction Manager resource in the scalable resource group.

      Note –

      The bvuser and BV1TO1_VAR should be the same for all of the resources.


      # scrgadm -a -j im-resource -g im-resource-group \
-t SUNW.bv -x BVUSER=bvuser \
-x BV1TO1_VAR=path-to-bv1to1_var-directory
      -j im-resource

      Specifies the name of the Interaction Manager resource.

  6. Run the scswitch command to enable and bring online the resource groups that now include the BroadVision One-To-One Enterprise resources.


    # scswitch -Z -g root-host-resource-group
# scswitch -Z -g back-end-resource-group-1
# scswitch -Z -g back-end-resource-group-2
...
# scswitch -Z -g back-end-resource-group-n
# scswitch -Z -g im-resource-group

ProcedureHow to Verify the Sun Cluster HA for BroadVision One-To-One Enterprise Installation and Configuration

Use this procedure to verify that you installed and configured Sun Cluster HA for BroadVision One-To-One Enterprise correctly.

Steps

  1. From a web browser, log in to an application that you have configured with the BroadVision One-To-One Enterprise software.

  2. Log in to the node that hosts the root host resource group.

  3. Become the BroadVision user.

  4. Shut down the root host processes.

    1. Set the BV_LOCAL_HOST environment variable as root-host-logical-hostname.

    2. Source the bv1to1.conf.sh file or the bv1to1.conf.csh file, depending on the shell that you use.

    3. Run the following BroadVision command.


      # bvconf shutdown -local
    Note –

    The Sun Cluster HA for BroadVision One-To-One Enterprise fault monitors will restart the root host.

  5. Ensure that your web browser connection to BroadVision One-To-One Enterprise is still active.

  6. Run the scswitch command to switch the root host resource group to another cluster node, such as node2.


    # scswitch -z -g root-host-resource-group -h node2

  7. Ensure that your web browser connection to BroadVision One-To-One Enterprise is still active.

  8. Repeat Step 2 through Step 7 for each back-end resource group.

Next Steps

You have completed your Sun Cluster HA for BroadVision One-To-One Enterprise installation and configuration. See the following sections for supplemental information.

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

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

Steps

  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 1 - 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”
               ;