How to synchronize nodes for OpenPages with WebSphere
Brian Laskey 270003US2W Visits (8060)
Occasionally a use-case comes up where some advanced configuration is required through WebSphere Application Server when administering the OpenPages application. WebSphere App Server Network Deployment itself has a capability they refer to as synchronization which distributes certain managed files to all nodes within a cell. The central administration is controlled through a special WebSphere server called the Deployment Manager (a.k.a. "Dmgr"). Generally speaking when you make some changes to WebSphere through their administrative console (htt
I noticed that sometimes there isn't a general set of steps for how to do this, it's mostly referenced as part of making some kind of configuration change in the OpenPages product Installation or Administration guides. For this post I am referencing OpenPages 7.0 or later, as well as WebSphere 22.214.171.124 or higher.
What you need to know:
How to Synchronize Nodes via Command Line
This is my own suggested way to synchronize nodes for OpenPages coming from my experience in different scenarios, as a developer we often have to synchronize nodes far more frequently than should ever be the case for a user of OpenPages, always refer to the official documentation when in doubt, and in case of issues you may want to work with your support representatives.
When Do You Need to Sync Nodes?
This is a great question. I was once specifically told from someone in the WebSphere team that you should always do it to be safe. Which is not always the most practical advice. Unfortunately, the WebSphere documentation does not make explicitly clear what properties settings or changes actually require the syncNodes to take effect. Given that there are countless properties and configuration items that would take too long to try to explain here, Here are my own observations or "rules of thumb" I follow:
It is generally required to syncNodes whenever making WebSphere admin console changes that effecting the Cell or Cluster as a whole, such as Global Security settings which are global. Same goes for making updates to the deployment of Enterprise applications on the server (i.e. under Applications > All Applications ... ), for example when enabling Global Security, or as mentioned before changing your SSL configuration settings or using a different SSL certificate.
On the other hand, I generally have not needed to syncNodes when making Server specific changes through the admin console, for example changing the JVM parameters for an individual server (i.e. under Servers > WebSphere Application Servers > ...O
Lastly changing anything within the OpenPages application itself will not require syncNodes, for example changing registry entries in the Administration > Settings menu, or making changes to the properties files in aurora/conf, these are not managed at the WebSphere server level so are not part of the syncNodes behavior.
Finding the Deployment Manager SOAP Port
The standard, default ports used for the OpenPages Dmgr is: 8879
For IBPM Dmgr it is: 8880
In some cases the default ports are unavailable or otherwise configured to be something else. Using the wrong port number is a common cause of errors. If you do not know you can find out what port is being used by through WAS admin console: