Modifying IBM Process Server connection properties

You can update the server configuration to connect a Process Server in your runtime environment to a different Process Center, to connect an offline server, or to modify other connection properties. A few settings can be updated using the Authentication Alias Configuration and the rest using the WebSphere command-line administration tool (wsadmin) AdminConfig commands.

Before you begin

IBM® Business Process Manager uses an authentication alias that is mapped to the ProcessCenterUser role to connect the Process Center to the Process Server. By default, the authentication alias is defaulted to the DeAdmin authentication alias. To change the authentication alias for the Process Center role, see Modifying authentication aliases.

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.

Customize the settings used by Process Server to connect to a Process Center, using the following steps:

Procedure

Complete the following steps to update the authentication alias settings.
1. Log in to the administrative console.
2. Go to Security > Global Security > Java Authentication and Authorization Service > J2C authentication data.
3. Update the authentication alias that you want to configure. Typically there are three authentication aliases that you want to modify: BPM_DB_ALIAS, CellAdminAlias and DeAdminAlias.
Complete the following steps to update the server settings using 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 BPM Express, profileName is the name of the stand-alone profile (and may be omitted if this is the only profile). For BPM Standard and 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.
```
wsadmin> AdminConfig.modify(ps, [['processCenterUrl', 'http://new_server_name/ProcessCenter’]])
```
4. Update the processCenterInternalUrl variable.
```
wsadmin> AdminConfig.modify(ps, [['processCenterInternalUrl', 'http://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 larger 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']])
```
6. Verify your updates.
```
wsadmin> print AdminConfig.show(ps)
```
7. Save the changes and exit.
```
wsadmin> AdminConfig.save()
wsadmin> exit
```
Restart the deployment manager after you have completed your updates.
Restart the Process Server cluster or server.