test

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

Alternative Configuration: How to Register and Configure Sun Cluster HA for BroadVision One-To-One Enterprise

To register and configure Sun Cluster HA for BroadVision One-To-One Enterprise, perform the following steps.

Note –

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

  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. Set the Network_resources_used property for each resource to point to the proper logical hostname.

      If you created two or more back-end resources in one resource group, and you do not set the Network_resources_used property, the validate method will fail.


      # scrgadm -a -j root-host-resource -g failover-resource-group -t SUNW.bv 
-y Network_resources_used=root-host-logical-hostname -x BVUSER=bvuser
-x BV1TO1_VAR=path-to-bv1to1_var-directory
# scrgadm -a -j back-end-resource-1 -g failover-resource-group -t SUNW.bv 
-y Network_resources_used=back-end-logical-hostname-1 -x BVUSER=bvuser
 -x BV1TO1_VAR=path-to-bv1to1_var-directory
...
# scrgadm -a -j back-end-resource-n -g failover-resource-group -t SUNW.bv 
-y Network_resources_used=back-end-logical-hostname-n -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.

      Note –

      You should have created all of the logical hostnames that were defined in the Network_resource_used property in the failover resource group (see Step 3 of the procedure, Alternative Configuration: How to Configure and Verify the BroadVision One-To-One Enterprise, Database, and HTTP Server Installation).

    2. Create the Interaction Manager resource in the scalable resource group that you created in Step 4 of the procedure, Alternative Configuration: How to Configure and Verify the BroadVision One-To-One Enterprise, Database, and HTTP Server Installation.


      # 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 the resource group that now includes the BroadVision One-To-One Enterprise back-end and root host resources.


    # scswitch -Z -g failover-resource-group
# scswitch -Z -g im-resource-group