I am continuing to get my head around the integration between Process Center and Process Server in that it's possible to have a connected Process Server to which you can actively deploy snapshots, using the so-called online/connected deployment. The following screen show shows what the connected Process Server looks like:
While it is easy to configure when you first create a Deployment Environment, I had a situation recently where a member of our team inadvertently clicked the Take Server Offline button.
When you click the button, it shows this prompt:
If you click Yes, then the Process Server is, from that point forward, offline.
To get it back, it's necessary to do the following things:
Remove the offline server via the Remove Offline Server button. In the first instance, when one clicks the Remove Offline Server button, there is a friendly warning:
Update the Process Server configuration to "re-tell" it where to find Process Center. it's necessary to use wsadmin to reconfigure the PS > PC relationship:
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/wsadmin.sh -lang jython
ps = AdminConfig.getid("/Cell:/ServerCluster:PSAppCluster/BPMClusterConfigExtension:/BPMProcessServer:/")
AdminConfig.modify(ps, [['processCenterUrl', 'https://bpm855.uk.ibm.com:9443/ProcessCenter']])
AdminConfig.modify(ps, [['processCenterInternalUrl', 'https://bpm855.uk.ibm.com:9443/ProcessCenterInternal']])
AdminConfig.modify(ps, [['heartBeatInterval', '60']])
AdminTask.updateBPMConfig( [ '-clusterName', 'PSAppCluster', '-environmentName', 'ProcessServer', '-environmentType', 'TEST' ] )
Restart the Process Server
Once done, the Process Server should now show back up in the Servers tab of the Process Center.
To summarize, the previous changes, including AdminTask.updateBPMConfig, are run on Process Server in order to "push" it's configuration back to the Process Center. In other words, Process Server "broadcasts" its availability to Process Center.
One thing of which to be aware ....
Process Center uses a Java2 Connector (J2C) Authentication Alias to allow it to "know" the credentials with which to connect to Process Server.
*IF* you change the credentials ( e.g. the password ) on the Process Server box, it's necessary to update the J2C alias on the Process Center box.
This is, as far as I can establish, a two-way relationship. Therefore, if you change the password on either box, make sure that you update the alias on the other side.
In my particular case, I have TWO deployment environments located in a single WebSphere Application Server cell. Therefore, all of the aliases are in one place: -
Just remember to update the J2C aliases if or when you change the credentials on either side.
One final point: The IBM Business Process Manager doumentation in the IBM Knowledge Center covers much of this information so please reference the official documentation if in doubt: Modifying IBM Process Server connection properties
File:Offline dot.png (modified) credit: (cc) Some rights reserved by DraGoth