Kbase P89977: How to add a secondary broker as a resource to the resource group on Windows Advanced server cluster
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
26/03/2010 |
|
Status: Verified
GOAL:
How to add a secondary broker as a resource to the resource group on Windows Advanced server cluster.
GOAL:
How to start a secondary broker in a Windows cluster.
FACT(s) (Environment):
Fathom High Availability Clusters 1.0A
Fathom High Availability Clusters 1.0B
Progress 9.1E
OpenEdge 10.0B
OpenEdge 10.1x
OpenEdge 10.2x
Windows
FIX:
Follow these steps to add a secondary broker
In this example, a database E:\testdb2k3\testdb.db, has been registered as a resource with the cluster manager using the command:
procluster e:\testdb2k3\testdb.db enable
1) Go to cluster administrator.
2) Select Resource types from the list.
3) Right click on resource type ?Progress database.?
4) Click New and then click Resource to see the New Resource dialog box.
5) Fill in the Name for your resource, for example, SECONDARY.
6) Click Next. The Possible Owners dialog box appears.
7) Select the same owners as that of the database. They may have been filled in by default, and if so, leave them as is.
8) Click Next. The Dependencies dialog box appears.
9) In this dialog box, you specify the resources your new resource, the secondary broker, is dependent on. Select your database resource
For example: e:\testdb2k3\testdb.db
10) Click Next. The resource Properties dialog box appears.
11) Fill in the dialog box as follows:
a) For Database file spec enter the full path of your database.
For example: e:\testdb2k3\testdb.db
b) For Working Directory enter the path to your database.
For example: e:\testdb2k3\
c) For Start Command enter the database server executable.
For example: D:\progress\openedge\bin\_mprosrv.
d) For Start Options enter your parameter file.
For example:? ?pf E:\testdb2k3\secondary_param_file.pf?
Where the secondary_param_file.pf only has entries relevant to the secondary login broker for example:
-m3
-S <secondaryloginport>
-Mpb <n>
For example this .pf must not have the "-cluster protected" argument.
e) Leave Stop Command and Stop Options blank.
This solution allows you to start the database primary broker and the secondary broker with the existing start command:
procluster e:\testdb2k3\testdb.db start.
It also allows you to stop all the processes dependent on the database (biw, apw, wdog, secondary broker) with the existing stop command:
procluster e:\testdb2k3\testdb.db stop.