Status: Verified
GOAL:
How to make Progress AdminService Cluster aware ?
GOAL:
How to configure AdminServer on a Windows Cluster ?
FACT(s) (Environment):
Progress 9.1E
OpenEdge 10.0B
Windows 2003 Enterprise Edition
OpenEdge 10.1X
Fathom Clusters
FIX:
The Progress AdminService is not registered on a Cluster by default. In order to make it cluster aware, please follow the steps below.
This solution assumes:
a) Progress/OpenEdge is installed locally on each cluster node in the same directory
b) All Progress/OpenEdge installations have the same service pack level installed. For OpenEdge 10.0B the minimum supported service pack level is 10.0B01 (Service pack 1)
c) The only cluster configuration Progress supports currently is Active/Standby.
1) Open the Cluster Manager
2) Resources -> New -> Resource Name: Progress AdminServer (or the name of your own)
Description: your own (not necessary)
Resource Type: Generic Service
Group: Cluster Group (or your own group)
enable the check box "Run this resource in a separate resource monitor"
-> next
Move desired cluster nodes as Possible Owners
-> next
Move "Cluster IP Address" and "Quorum shared device" (this solution assumes, that AdminServer will be autostarting database(s) as well) to "Resource dependencies". Do *NOT* move "Cluster Name" there, database(s) won't start if it is.
-> next
Service name: AdminService9.1E (AdminService10.0B as appropriate)
Start parameters: <none>
-> next
Registry key: (add) SOFTWARE\PSC\AdminService\<version> eg: 9.1E, 10.0B, 10.1B etc. - this step is optional - using it, the registry key between nodes will be replicated if any change is made to them.
Note/Warning: If you happen to delete the registry key (or its content) on a primary node, this change will be populated further, so the AdminServer registry keys will be lost 3) Open Progress Explorer and configure the NameServer/AppServer/WebSpeed ... and database(s). Make sure that a database is set to AutoStart and the check box "Start this database is a Cluster mode" has been enabled.
4) Make sure that PSC_CLUSTER_PATH is set correctly on each cluster node by pointing to the Progress/OpenEdge installation:
My Computer -> properties -> Advanced -> Environment variables -> System variables
5) Open proenv and register the database(s) on the cluster by using "procluster <db> enable -pf <db>.pf [BIW WDOG APW=2]" (without [])
the [BIW WDOG APW=2] section is optional and the number of APW's is configurable,
example of <db>.pf:
-cluster protected
-properties c:\progress\91e\properties\conmgr.properties
-servergroup <db>.defaultconfiguration.defaultservergroup
-adminport <port>
-m5 Note #1: Make sure that all the databases are located on the Quorum (shared cluster) storage (read: any shared storage available on the cluster).
Note #2: Concerning <db>.defaultconfiguration.defaultservergroup - the <db> is not the physical name of the database, but the "Logical name" of the database object specified in the Progress Explorer
6) Make sure that the content of %DLC%/properties is identical on each cluster node, eg that after setting up all the unified brokers/databases on the active cluster the content of the %DLC%/propertie.s directory is copied to the remaining nodes. 7) Modify following registry keys on each cluster node (if replicating these keys over the cluster, the change on a primary node will suffice):
HKEY_LOCAL_MACHINE\SOFTWARE\PSC\AdminService\<ver>\StartupCmd\Chimera
HKEY_LOCAL_MACHINE\SOFTWARE\PSC\AdminService\<ver>\ShutdownCmd\Chimera
Add "-cluster -host <clustername>" at the end of the Chimera key, where the <clustername> is a virtual name of the cluster, without "" and <>.
Note #1: Replace <ver> with 10.1B for example, if you are using OpenEdge 10.1B in a registry key above. 8) Open Cluster Manager and bring the AdminServer resource online..