Configuration Guidelines for Sun Cluster HA for BroadVision One-To-One Enterprise

When you design a Sun Cluster HA for BroadVision One-To-One Enterprise configuration, consider the following guidelines.

Use a BroadVision One-To-One Enterprise software version that is qualified with Sun Cluster 3.0.
Install the BroadVision One-To-One Enterprise software on the cluster file system.
Create a BroadVision user that is identical on all of the cluster nodes.
Install all of the necessary patches that are supplied by BroadVision to enable the BroadVision One-To-One Enterprise software to run in the Sun Cluster environment.
Configure the Interaction Managers, back-end servers, and root hosts in the $BV1TO1_VAR/etc/bv1to1.conf configuration file, as shown in "Supported Configurations".
Start your database before you start the BroadVision One-To-One Enterprise servers.

Supported Configurations

See your Enterprise Services representative for the most current information about BroadVision One-To-One Enterprise versions and configurations that are supported.

BroadVision One-To-One Enterprise configurations that are supported include the following.

For all of the supported configurations, set up your highly available database and HTTP server to match "Sun Cluster HA for DBMS and HTTP Server Configuration".

Sun Cluster HA for DBMS and HTTP Server Configuration

Configure Sun Cluster HA for DBMS and HTTP server as follows.

Configure Sun Cluster HA for Oracle or Sun Cluster HA for Sybase ASE to use a logical hostname.
Configure Sun Cluster HA for iPlanet Web Server or Sun Cluster HA for Apache to use a logical hostname (for failover configuration) or to use a shared address (for scalable configuration).

Cluster With Multiple Resource Groups for the BroadVision One-To-One Enterprise Software

Configure the BroadVision One-To-One Enterprise root host, back-end, and Interaction Manager processes as follows.

Configure the root host resource to use one logical hostname in one resource group.
Configure back-end resources to use the remaining logical hostnames in multiple resource groups.
Configure the Interaction Manager resource on one of the following locations.
- All of the cluster nodes.
- All of the cluster private hostnames. See the Sun Cluster 3.0 12/01 Software Installation Guide for details on cluster interconnect and private hostnames.
Figure 11-1 illustrates a sample configuration that meets these guidelines.

Figure 11-1 Sample Configuration: Cluster With Three Logical Hostnames Configured Into Separate Resource Groups

Note -
Configure Interaction Manager resources on all of the cluster nodes or on all of the cluster private hostnames. If you configure the Interaction Managers on all of the cluster private hostnames, set up the HTTP servers on the same cluster. Alternatively, if you configure the Interaction Managers on all of the cluster nodes, the HTTP servers can be set up outside of the cluster.

Alternative Configuration: Cluster With One Resource Group for the BroadVision One-To-One Back-End and Root Host Servers

Depending on the flexibility and granularity of administration that you require for each back-end resource, you can configure Sun Cluster HA for BroadVision One-To-One back-end servers to use only one resource group. To set up this alternative configuration, configure the BroadVision One-To-One Enterprise root host, back-end, and Interaction Manager processes as follows.

Configure root host and all of the back-end resources to use n logical hostnames inside of the same failover resource group.
Configure the Interaction Manager resource on one of the following locations.
- All of the cluster nodes.
- All of the cluster private hostnames. See the Sun Cluster 3.0 12/01 Software Installation Guide for details on cluster interconnect and private hostnames.
This configuration, which Figure 11-2 illustrates, requires alternative steps. See "Alternative Configuration" for more information.

Figure 11-2 Sample Configuration: Cluster With Three Logical Hostnames Configured Into One Resource Group

Note -
Configure Interaction Manager resources on all of the cluster nodes or on all of the cluster private hostnames. If you configure the Interaction Managers on all of the cluster private hostnames, set up the HTTP servers on the same cluster. Alternatively, if you configure the Interaction Managers on all of the cluster nodes, the HTTP servers can be set up outside of the cluster.

Pre-Installation Considerations

See "Installing and Configuring the BroadVision One-To-One Enterprise Software, the Database, and the HTTP Server" and specifically, "Supported Configurations", before you install the BroadVision One-To-One Enterprise software. Additionally, consider the following cluster-related tasks.

BroadVision user home directory - Create an identical BroadVision user (bvuser) on all of the cluster nodes. Place the BroadVision user home directory on the cluster file system. Direct all of the BroadVision users on all of the cluster nodes to the same home directory.
BroadVision One-To-One Enterprise software - Install the BroadVision One-To-One Enterprise software on the cluster file system so that all of the cluster nodes can access the same BroadVision One-To-One Enterprise binaries and configuration files.