Planning the Sun Cluster HA for BroadVision One-To-One Enterprise Installation and Configuration

This section contains the information you need to plan your Sun Cluster HA for BroadVision One-To-One Enterprise installation and configuration.

Configuration Restrictions

Your data service configuration might not be supported if you do not observe these restrictions.

Use a BroadVision One-To-One Enterprise software version that is qualified with your release of Sun Cluster.

For restrictions that apply to all data services, see the Sun Cluster Release Notes for Solaris OS.

Configuration Requirements

Your data service configuration might not be supported if you do not adhere to these requirements.

Use the requirements in this section to plan the installation and configuration of Sun Cluster HA for BroadVision One-To-One Enterprise. These requirements apply to Sun Cluster HA for BroadVision One-To-One Enterprise only. You must meet these requirements before you proceed with your Sun Cluster HA for BroadVision One-To-One Enterprise installation and configuration.

• 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 Standard Data Service Configurations.

• Start your database before you start the BroadVision One-To-One Enterprise servers.

Standard Data Service Configurations

Use the standard configurations in this section to plan the installation and configuration of Sun Cluster HA for BroadVision One-To-One Enterprise. Sun Cluster HA for BroadVision One-To-One Enterprise supports the standard configurations in this section. Sun Cluster HA for BroadVision One-To-One Enterprise might support additional configurations. However, you must contact your Enterprise Services representative for information on additional configurations.

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

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

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 Sun Java System 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 Software Installation Guide for Solaris OS for details on cluster interconnect and private hostnames.

The figure below illustrates a sample configuration that meets these guidelines. the figure shows a cluster with three logical hostnames configured into separate resource groups.

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 Enterprise 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 Enterprise 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 Software Installation Guide for Solaris OS for details on cluster interconnect and private hostnames.

The figure below shows a cluster with three logical hostnames configured into one resource group. This configuration requires alternative steps. See Alternative Configuration for more information.

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.

Configuration Considerations

Use the information in this section to plan the installation and configuration of Sun Cluster HA for BroadVision One-To-One Enterprise. The information in this section encourages you to think about the impact your decisions have on the installation and configuration of Sun Cluster HA for BroadVision One-To-One Enterprise.

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

Configuration Planning Questions

Use the questions in this section to plan the installation and configuration of Sun Cluster HA for BroadVision One-To-One Enterprise. Insert the answers to these questions into the data service worksheets in the Configuration Worksheets in Sun Cluster Data Services Planning and Administration Guide for Solaris OS. See Configuration Considerations for information that might apply to these questions.

• Will you run Sun Cluster HA for BroadVision One-To-One Enterprise as a failover or as a scalable data service?

• If you run Sun Cluster HA for BroadVision One-To-One Enterprise as a scalable service, what nodes will host the scalable service?

• What resource groups will you use for network addresses and application resources and the dependencies between them?

• What is the logical hostname (for failover services) or shared address (for scalable services) for clients that will access the data service?

• Where will the system configuration files reside?

  See “Determining the Location of the Application Binaries” on page 3 of the Sun Cluster Data Service for BroadVision One-To-One Enterprise Guide for Solaris OS for the advantages and disadvantages of placing the BroadVision One-To-One Enterprise binaries on the local file system as opposed to the cluster file system.