Admin Stuffs: IBM BPM Using wsadmin commands to customize the Process Server settings used to connect to Process Center

Using the WebSphere wsadmin command-line administration tool, you can run commands to update the server configuration that is used to connect a Process Server in your runtime environment to a different Process Center. You can also use wsadmin commands to connect an offline server or to modify other connection properties. Although a few settings are updated using authentication alias configuration, the rest of the properties can be updated using wsadmin commands.

Before you begin

Restriction: The BPMAuthor role must point to the same user in both the Process Center and the Process Server, and must have the same password.

About this task

Typically, each Process Server in a runtime environment is connected to a Process Center; a single Process Center can be connected to multiple servers. You can install process application snapshots from the Process Center to one or more of these connected Process Servers. Using wsadmin commands, you can customize many Process Server settings that are used to connect to Process Center, such as the following settings:

Update the host and port name of the Process Center connection details.
Change Process Server from an offline server to a Process Center connected server (online server), and vice-versa.
Change the Process Center connection URL.

Procedure

To customize the settings that are used by Process Server to connect to a Process Center, complete the following steps.

Note: For network deployment Process Server environments, complete the following steps on the deployment manager node, synchronize the nodes, and restart the application cluster member.

Stop the Process Server environment. In a network deployment environment, stop the deployment manager and the nodes.
Complete the following steps to update the server settings with the WebSphere command-line administration tool (wsadmin) AdminConfig commands.
1. Start the wsadmin scripting tool. To start wsadmin using the Jython language, run the following command from the bin directory of the IBM BPM installation:
```
wsadmin -conntype NONE -lang jython -profileName profileName
```
  For IBM BPM Express, profileName is the name of the stand-alone profile (and may be omitted if this is the only profile). For IBM BPM Standard and IBM BPM Advanced, profileName is the name of the deployment manager profile.
2. Get the process server configuration of the application cluster.
  - For a clustered environment, specify the following command syntax:
```
wsadmin> ps = AdminConfig.getid("/Cell:/ServerCluster:application_cluster_name
```
```
/BPMClusterConfigExtension:/BPMProcessServer:/")
```
  - for a stand-alone environment, specify the following command syntax:
```
wsadmin> ps = AdminConfig.getid("/Cell:/Node:node_name/Server:server_name 
```
```
/BPMServerConfigExtension:/BPMProcessServer:/")
```
3. Update the processCenterUrl variable. This setting specifies the URL that IBM Process Server uses to connect to a pre-8.5.0.1 Process Center. It uses Form-based Authentication. A pre-8.5.0.1 Process Center supports only the processCenterUrl setting and it does not support the processCenterInternalUrl setting that is described in the next step. To ensure that the Process Server can connect to a Process Center from any release of IBM BPM, this setting should always be specified.
```
wsadmin> AdminConfig.modify(ps, [['processCenterUrl', 'https://new_server_name 
```
```
/ProcessCenter']])
```
4. Update the processCenterInternalUrl variable, which is the same as ProcessCenterUrl but with the literal string Internal appended at the end for the context root. This setting specifies the URL that IBM Process Server uses to connect to an IBM BPM 8.5.0.1 or later Process Center. It uses Basic Authentication rather than Form-based Authentication. It has the same format as the processCenterUrl setting, except that it also has the literal string Internal appended at the end for the context root. An 8.5.0.1 or later Process Center supports both the processCenterUrl setting and the processCenterInternalUrl setting. However, the processCenterInternalUrl is the preferred method of communication and it is automatically used when it is available. To ensure that the Process Server can connect to a Process Center from any release of IBM BPM, this setting should always be specified. The setting should be set to the same host and port as the processCenterUrl.
```
wsadmin> AdminConfig.modify(ps, [['processCenterInternalUrl', 
```
```
'https://new_server_name/ProcessCenterInternal']])
```
5. To change the state of an offline Process Server to online, update the heartBeatInterval value to a number that is greater than 0 (zero). The heartbeat interval is the polling interval, in seconds, that is used by the Process Server to communicate its location and characteristics to the Process Center. For example, to set the value to 60 seconds, enter the following command:
```
wsadmin> AdminConfig.modify(ps, [['heartBeatInterval', '60']])
```
  To bring the server offline, disable polling by setting the heartBeatInterval value to a number that is less than or equal to 0 (zero). For example:
```
wsadmin> AdminConfig.modify(ps, [['heartBeatInterval', '-1']])
```
6. Verify your updates.
```
wsadmin> print AdminConfig.show(ps)
```
  The output looks something like the following example:
```
[heartBeatInterval 60]
```
```
[processCenterUrl https://hostname:9082/ProcessCenter]
```
7. Save the changes and exit.
```
wsadmin> AdminConfig.save()  wsadmin> exit
```