Protecting Your Data : Failover Clusters : Using a cluster-enabled database with the AdminServer
Using a cluster-enabled database with the AdminServer
Configuring a cluster-enabled database for use with the AdminServer is a two-step process. First the AdminServer must be started in a manner that identifies that it is running in a cluster, and then the database must be configured through OpenEdge Management or OpenEdge Explorer to indicate that it is in a clustered environment.
Start the AdminServer in a cluster
Enter the following command:
proadsv -start -cluster -host cluster-alias
Note: In an unclustered environment, PROADSV binds to the hostname localhost. However, in a clustered environment, localhost may not be available so the AdminServer must bind to the cluster alias.
Next configure a cluster-enabled database to run under the AdminServer:
1. Verify that the database resides on shared disk resources that are available to the currently active node in the cluster.
2. Start OpenEdge Management or OpenEdge Explorer and connect to the AdminServer for the cluster.
a. From the list frame on the left, choose the database container.
b. Select OpenEdge > Database.
c. Select the database you want to configure to run under the AdminServer.
d. Click Configuration.
e. Select the Cluster enabled check box.
Selecting the Cluster enabled check box indicates you have already configured the database as cluster-enabled using the PROCLUSTER commands. This allows the database to register with the cluster manager at start time.
3. Update the database parameter file dbname.pf that resides in the same directory as the database .db file.
The file should contain the following:
-cluster protected
-properties /usr/dlc/properties/conmgr.properties
-servergroup database.defaultconfiguration.defaultservergroup
-m5
-adminport adminserverport# substitute the port name or number
4. Start the database using OpenEdge Management or OpenEdge Explorer.
