This section contains the procedures you need to configure Sun Cluster HA for BroadVision One-To-One Enterprise.
Use the extension properties in Table 1–4 to create your resources. Use the command line scrgadm -x parameter=value to configure extension properties when you create your resource. Use the procedure in “Administering Data Service Resources” in Sun Cluster Data Services Planning and Administration Guide for Solaris OSto configure the extension properties if you have already created your resources. You can update some extension properties dynamically. You can update others, however, only when you create or disable a resource. The Tunable entries indicate when you can update each property. See “Standard Properties” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS for details on all Sun Cluster properties.
Table 1–4 Sun Cluster HA for BroadVision One-To-One Enterprise Extension Properties
Property Category |
Property Name |
Description |
---|---|---|
BroadVision One-To-One Enterprise configuration |
BVUSER |
The BroadVision user UNIX ID. Replace bvuser with your preferred username. Default: None Tunable: At creation |
BV1TO1_VAR |
The environment variable that is set as bvuser. Default: None Tunable: At creation |
|
Probe |
Monitor_retry_interval |
The time (in minutes) over which the Resource Group Manager (RGM) counts fault monitor failures. The number of times that the fault monitor fails can exceed the value that the extension property Monitor_retry_count specifies. If the number of failures exceeds the value of Monitor_retry_count within the time period that Monitor_retry_interval specifies, the Process Monitor Facility (PMF) does not restart the fault monitor. Default: 2 Tunable: Any time |
Monitor_retry_count |
The number of PMF restarts that the Sun Cluster software allows for the fault monitor. Default: 4 Tunable: Any time |
|
Probe_timeout |
The time-out value in seconds for the probes. Default: 180 Tunable: Any time |
|
Daemons |
START_ORB_SERVERS |
Type Boolean. By default, the data service starts the orbix daemon and all of the BroadVision daemons in the resource. The orbix daemon starts the orbix servers whenever needed. If you want the data service to start the orbix servers, set this property to TRUE. Default: FALSE Tunable: Any time |
Use this procedure to register and configure Sun Cluster HA for BroadVision One-To-One Enterprise.
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.
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 |
Adds the resource type for the data service.
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.
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.
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 |
Specifies the name of the root host resource.
Specifies your BroadVision username.
Specifies the path to the $BV1TO1_VAR directory.
Specifies the name of the back-end resource.
Create the Interaction Manager resource in the scalable resource group.
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 |
Specifies the name of the Interaction Manager resource.
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 |
Use this procedure to verify that you installed and configured Sun Cluster HA for BroadVision One-To-One Enterprise correctly.
From a web browser, log in to an application that you have configured with the BroadVision One-To-One Enterprise software.
Log in to the node that hosts the root host resource group.
Become the BroadVision user.
Shut down the root host processes.
Set the BV_LOCAL_HOST environment variable as root-host-logical-hostname.
Source the bv1to1.conf.sh file or the bv1to1.conf.csh file, depending on the shell that you use.
Run the following BroadVision command.
# bvconf shutdown -local |
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 root host resource group to another cluster node, such as node2.
# scswitch -z -g root-host-resource-group -h node2 |
Ensure that your web browser connection to BroadVision One-To-One Enterprise is still active.
Repeat Step 2 through Step 7 for each back-end resource group.
You have completed your Sun Cluster HA for BroadVision One-To-One Enterprise installation and configuration. See the following sections for supplemental information.
Sun Cluster HA for BroadVision One-To-One Enterprise Extension Properties
Operation of the Sun Cluster HA for BroadVision One-To-One Enterprise Fault Monitor
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.
Which option do you prefer?
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.
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.
This example uses the following sample IP addresses to add to the bv1to1.conf file.
10.10.102.225
10.10.102.226
10.10.102.222
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” ; |
DCC cannot recover from a failover. Contact BroadVision One-To-One Enterprise support for more information.