Kbase P113968: How to add a DataServer broker as a resource to the resource group on Windows Advanced server.
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  06/03/2006 |
|
Status: Unverified
GOAL:
How to add a DataServer broker as a resource to the resource group on Windows Advanced server.
GOAL:
How to start a DataServer broker in a Windows cluster.
FACT(s) (Environment):
DataServers
Progress 9.1E
OpenEdge 10.0B
Windows
FIX:
Follow these steps to add a DataServer broker
In this example, a database E:\testdb2k3\holder.db, has been registered as a resource with the cluster manager using the command:
procluster e:\testdb2k3\holder.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 DataServer broker, is dependent on. Select your database resource
For example: e:\testdb2k3\holder.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\holder.db
b) For Working Directory enter the path to your database.
For example: e:\testdb2k3\
c) For Start Command enter the DataServer broker executable.
For example: D:\progress\openedge\bin\_probrkr.EXE
d) For Start Options enter the service name.
For example:? ?S <Service name for _probrkr.EXE>?
e) Leave Stop Command and Stop Options blank.
This solution allows you to start the schema holder broker and the DataServer broker with the existing start command:
procluster e:\testdb2k3\holder.db start.
It also allows you to stop the schema holder broker with the existing stop command:
procluster e:\testdb2k3\holder.db stop.