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

Previous: Examples – Installing, Configuring, and Administering Sun Cluster HA for BroadVision One-To-One Enterprise
Next: Operation of the Sun Cluster HA for BroadVision One-To-One Enterprise Fault Monitor

Alternative Configuration

Depending on the flexibility and granularity of administration that you require for each back-end resource, you can set up only one failover resource group to use n logical hostnames and to contain all of the back-end and root host resources.

Note –

See Alternative Configuration: Cluster With One Resource Group for the BroadVision One-To-One Enterprise Back-End and Root Host Servers for an illustration of this alternative configuration.

To set up this alternative configuration, perform the following procedures.

Alternative Configuration: How to Configure and Verify the BroadVision One-To-One Enterprise, Database, and HTTP Server Installation
Alternative Configuration: How to Install Sun Cluster HA for BroadVision One-To-One Enterprise Packages
Alternative Configuration: How to Register and Configure Sun Cluster HA for BroadVision One-To-One Enterprise
Alternative Configuration: How to Verify the Sun Cluster HA for BroadVision One-To-One Enterprise Installation

Note –
With these procedures, you set up two resource groups. One failover resource group contains root host and back-end resources. One scalable resource group contains the Interaction Manager resource. Throughout the alternative configuration procedures, the failover resource group that contains root host and back-end resources is denoted as failover-resource-group.

Alternative Configuration: How to Configure and Verify the BroadVision One-To-One Enterprise, Database, and HTTP Server Installation

Perform this procedure to test starting and stopping the back-end processes on all of the nodes on which the back-end host and root host can run in a failover configuration. Additionally, perform this procedure to test the BroadVision One-To-One Enterprise Interaction Managers that you configured in the cluster.

Create a failover resource group to contain the BroadVision One-To-One Enterprise back-end and root host resources.
# scrgadm -a -g failover-resource-group [-h nodelist]
-g failover-resource-group

Specifies the name of the resource group that contains the back-end and root host logical hostnames and resources. The name of the failover resource group can be your choice but must be unique for resource groups within the cluster.

[-h nodelist]

Specifies an optional, comma-separated list of physical node names or IDs that identify potential masters. The order here determines the order in which the Resource Group Manager (RGM) considers primary nodes during failover.

Verify that you have added all of the logical hostnames that you use to your name service database.

Additionally, add all of the logical hostnames that you use to the /etc/inet/hosts file on each cluster node. Therefore, if the name service goes down, the nodes can still find the name-to-address mapping on their local hosts file.

Run the scrgadm(1M) command to add the logical hostnames that the failover resource group will use.

# scrgadm -a -L -g failover-resource-group -l root-host-logical-hostname-1 [-n netiflist]
# scrgadm -a -L -g failover-resource-group -l back-end-logical-hostname-1 [-n netiflist]
# scrgadm -a -L -g failover-resource-group -l back-end-logical-hostname-2 [-n netiflist]
...
# scrgadm -a -L -g failover-resource-group -l back-end-logical-hostname-n [-n netiflist]

-l root-host-logical-hostname: Specifies the logical hostname that the root host resource uses.
-l back-end-logical-hostname-n: Specifies the logical hostname that each back-end resource uses.
[-n netiflist]: Specifies an optional, comma-separated list that identifies the IP Networking Multipathing groups that are on each node. The netiflist must represent all of the nodes in the resource group's nodelist. If you do not specify this option, the scrgadm command attempts to discover a network adapter on the subnet that the hostname list identifies for each nodelist node.

Create a scalable resource group for the Interaction Managers.
# scrgadm -a -g im-resource-group -y Maximum_primaries=n -y Desired_primaries=n
-g im-resource-group

Specifies the name of the scalable resource group that contains the Interaction Managers. This name can be your choice but must be unique for resource groups within the cluster.

-y Maximum_primaries=m

Specifies the maximum number of active primary nodes allowed for this resource group. If you do not assign a value to this property, the default is 1.

-y Desired_primaries=n

Specifies the desired number of active primary nodes allowed for this resource group. If you do not assign a value to this property, the default is 1.

From one cluster node, run the scswitch(1M) command to move the failover resource group into the managed state and bring it online.
# scswitch -Z -g failover-resource-group
Note –
You do not need to bring the scalable resource group online because the scalable resource group does not yet contain resources. You must bring the failover resource group online because the BroadVision One-To-One Enterprise back-end processes cannot start if the logical hostname resource is unavailable.

Check that the database is accessible.

See your database documentation for details.

Ensure that you have configured the database to enable BroadVision One-To-One Enterprise back-end servers to access the database from any cluster node.

See your database documentation for details.

As the BroadVision user, log in to the cluster node that hosts the failover resource group.

Follow the steps in the BroadVision One-To-One Enterprise Installation and Administration Guide to run the following BroadVision commands.
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 bvconf bootstrap command on the root host to initialize the BroadVision One-To-One Enterprise installation.
  
  Note –
  Do not run the bvconf command as superuser.
  % bvconf bootstrap -r root-host-logical-hostname
4. Set the BV_LOCAL_HOST environment variable as back-end-logical-hostname or im-hostname.
5. Source the bv1to1.conf.sh file or the bv1to1.conf.csh file, depending on the shell that you use.
6. For each back-end host and Interaction Manager host, run the bvconf execute command to configure and start the BroadVision One-To-One Enterprise installation.
  % bvconf execute -local -var shared -r root-host-logical-hostname

Run the BroadVision command bvconf gateway to generate gateway configuration files for the HTTP gateway applications.

This command generates the files and writes them to the $BV1TO1_VAR/etc/appName.cfg file.
% bvconf gateway -A appName
-A appName

Specifies the gateway application name, which is defined in the $BV1TO1_VAR/etc/bv1to1.conf configuration file. See the BroadVision One-To-One Enterprise Installation and Administration Guide for details.

Copy the gateway application configuration file to the /etc/opt/BVSNsmgr directory on each of the cluster nodes that runs HTTP instances.

Note –
Ensure that you copy the gateway application configuration file with the extension .cfg.

See the BroadVision One-To-One Enterprise Installation and Administration Guide for details.

Configure and start the HTTP servers.

See your HTTP server documentation for details. Additionally, see the BroadVision One-To-One Enterprise Installation and Administration Guide for information on HTTP server configuration.

From a BroadVision client, connect to the BroadVision site, and check the installation.

If the BroadVision One-To-One Enterprise software is functioning correctly, perform the following steps to shut down the Interaction Managers, back-end processes, and root host processes.
1. Shut down the Interaction Managers.
  1. Set the BV_LOCAL_HOST environment variable as im-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 command.
    # bvconf shutdown -local
2. Shut down the back-end processes.
  1. Set the BV_LOCAL_HOST environment variable as back-end-logical-hostname-n.
  2. Source the bv1to1.conf.sh file or the bv1to1.conf.csh file, depending on the shell that you use.
  3. Run the following command.
    # bvconf shutdown -local
3. 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 command.
    # bvconf shutdown -local

Run the scswitch command to switch the failover resource group to another cluster node, such as node2.
# scswitch -z -g failover-resource-group -h node2

Restart the BroadVision One-To-One Enterprise software.

Connect to the cluster from a BroadVision client, and check that the BroadVision One-To-One Enterprise software functions correctly.

Repeat Step 15 through Step 18 on all of the potential primaries of the BroadVision One-To-One Enterprise resource groups.

Alternative Configuration: How to Install Sun Cluster HA for BroadVision One-To-One Enterprise Packages

Use this procedure to install the Sun Cluster HA for BroadVision One-To-One Enterprise packages. You need the Sun Java Enterprise System Accessory CD Volume 3 to perform this procedure. This procedure assumes that you did not install the data service packages during your initial Sun Cluster installation. If you installed the Sun Cluster HA for BroadVision One-To-One Enterprise packages as part of your initial Sun Cluster installation, proceed to Alternative Configuration: How to Register and Configure Sun Cluster HA for BroadVision One-To-One Enterprise to install and configure Sun Cluster HA for BroadVision One-To-One Enterprise. Otherwise, use this procedure to install the Sun Cluster HA for BroadVision One-To-One Enterprise packages. Perform this procedure on all nodes that can run Sun Cluster HA for BroadVision One-To-One Enterprise.

Load the Sun Java Enterprise System Accessory CD Volume 3 into the CD-ROM drive.

Run the scinstall utility with no options.

This step starts the scinstall utility in interactive mode.

Choose the menu option, Add Support for New Data Service to This Cluster Node.

The scinstall utility prompts you for additional information.

Provide the path to the Sun Java Enterprise System Accessory CD Volume 3.

The utility refers to the CD as the “data services cd.”

Specify the data service to install.

The scinstall utility lists the data service that you selected and asks you to confirm your choice.

Exit the scinstall utility.

Unload the CD from the drive.

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.

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.

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.

Become superuser on one cluster node.

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.

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

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

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.

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

Alternative Configuration: How to Verify the Sun Cluster HA for BroadVision One-To-One Enterprise Installation

Perform the following steps to verify the Sun Cluster HA for BroadVision One-To-One Enterprise installation.

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

Become the BroadVision user.

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.

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

Run the scswitch command to switch the failover resource group to another cluster node, such as node2.
# scswitch -z -g failover-resource-group -h node2

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