Kbase P133249: How to store the AdminServer configuration on the shared storage of a cluster?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/24/2009 |
|
Status: Unverified
GOAL:
How to store the AdminServer configuration on the shared storage of a cluster?
GOAL:
Is it possible to store the properties file on the cluster quorum?
FACT(s) (Environment):
OpenEdge 10.x
Windows
FIX:
Most configuration files can be stored on the cluster shared storage space, however the location of the file AdminServerPlugins.properties is hardcoded to be relative to the DLC directory when AdminServer is started as a service.
Therefore either one of the following two setups are recommended:
A) shared installation of OpenEdge
In this setup, each node in the cluster will run the OpenEdge installation with the same target directory (on the shared storage). Each installation after the first will overwrite the contents of the directory but this should cause no side-effect as long as the following prerequisites are met:
- the list of components is the same
- the visible path of the installation is the same on all nodes
Then the AdminServer can be started from the shared storage on all nodes. Care should be taken that the permissions to access the shared storage match the permissions of the user account used to start AdminServer.
B) local installation of OpenEdge, with configuration files on shared storage
In this setup it is assumed that OpenEdge is installed on all nodes on the cluster. Then the following steps can be used:
- the properties file are placed on a shared location
- the file DLC/properties/AdminServerPlugins.properties is edited on all nodes to add/edit the following key in section [PluginPolicy.Progress.AdminServer]:
args=-dbproperties <shared>\conmgr.properties -dbaproperties
<shared>\agent.properties -smdbproperties <shared>\smdatabase.properties
-ubproperties <shared>\ubroker.properties -mgmtproperties
<shared>\management.properties
(only the files actually in use need to be mentioned -- use proadsv -help for more information)
Then the AdminServer can be restarted to make use of the shared configuration. Care should be taken that the permissions on the shared storage match the permissions of the user account used to start AdminServer.