After you install and configure IBM® Business Process Manager, you
can use the wsadmin command to change the Process
Server settings that are used for connecting to the Process Center.
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
Use the following procedure to customize the Process Server
connection settings:
For example, you can complete the following
tasks:
- 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.
- 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.
- Get the process server configuration of the application
cluster.
- on a clustered environment, enter the following command:
wsadmin> ps = AdminConfig.getid("/Cell:/ServerCluster:application_cluster_name/BPMClusterConfigExtension:/BPMProcessServer:/")
- for a stand-alone server, enter the following command:
wsadmin> ps = AdminConfig.getid("/Cell:/Node:node_name/Server:server_name/BPMServerConfigExtension:/BPMProcessServer:/")
- Update the processCenterUrl variable.
wsadmin> AdminConfig.modify(ps, [['processCenterUrl', 'https://new_server_name/ProcessCenter']])
- Update the processCenterInternalUrl variable,
which is the same as ProcessCenterUrl but with the
literal string Internal appended at the end for the
context root.
wsadmin> AdminConfig.modify(ps, [['processCenterInternalUrl', 'https://new_server_name/ProcessCenterInternal']])
- 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']])
To
bring the server offline, disable polling by setting the
heartBeatInterval value
to a negative number:
wsadmin> AdminConfig.modify(ps, [['heartBeatInterval', '-1']])
-1 is
the special value to use for an offline server.
- Verify your updates.
wsadmin> print AdminConfig.show(ps)
The
output looks something like the following example:
...
[heartBeatInterval 60]
...
[processCenterUrl https://hostname:9082/ProcessCenter]
- Save the changes and exit.
wsadmin> AdminConfig.save()
wsadmin> exit
- Review the Business Process Manager security roles by navigating
in the WebSphere Application Server administrative console to . See IBM Business Process Manager roles.
- Note the authentication alias for the ProcessCenterUser
and BPMAuthor roles.
- If it does not exist, create the ProcessCenterUserAlias.
See Modifying authentication aliases. For ProcessCenterUserAlias,
use a valid user name and password from the Process Center environment.
The user does not need any special authorization in Process Center.
- Optional: If you plan to use a user other than
DeAdmin (the default) to deploy snapshots from Process Center to the
runtime Process Server, create a new BPMAuthorAlias. This
user is used during heartbeat to connect to the Process Center. For
BPMAuthorAlias, use a valid user name and password from the Process
Server environment that has the authority to access and deploy snapshots
to the runtime Process Server. This user is saved in the LSW_SERVER
table in the Process Center database and used when the process application
is deployed to this Process Server.
- In the Business Process Manager security roles screen,
map the ProcessCenterUser role to ProcessCenterUserAlias and the
appropriate alias to the BPMAuthor role.
- Because Process Center connects to Process Server by HTTPS
by default, you must verify that the Process Server root signer SSL
certificate is imported into Process Center. If you configure the processCenterUrl variable
or the processCenterInternalUrl variable to use HTTPS,
then you also must verify that the Process Center root signer certificated
is imported in Process Server. Follow the steps in Configuring SSL communication.
Tip: If you want to
change the Process Center to connect to Process Server by HTTP, complete
the following steps. Then you do not need to import the Process Center
root signer certificates into Process Server.
- Stop the Process Center environment. In a network deployment environment,
stop the deployment manager and the nodes.
- Update the following server settings with the wsadmin AdminConfig
commands.
- 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.
- Get the Process Center configuration of the application cluster.
- For a clustered environment, specify the following command syntax:
wsadmin> pc = AdminConfig.getid("/Cell:/ServerCluster:application_cluster_name/BPMClusterConfigExtension:/BPMProcessCenter:/")
- For a stand-alone environment, specify the following command syntax:
wsadmin> pc = AdminConfig.getid("/Cell:/Node:node_name/Server:server_name/BPMServerConfigExtension:/BPMProcessCenter:/")
- Update the useHTTPSURLPrefixes property:
wsadmin> AdminConfig.modify(pc, [['useHTTPSURLPrefixes', 'false']])
- Verify your updates:
wsadmin> print AdminConfig.show(pc)
- Save the changes and exit:
wsadmin> AdminConfig.save()
wsadmin> exit
- Stop the Process Server environment. In a network deployment environment,
stop the deployment manager and the nodes.
- Update the following server settings with the wsadmin AdminConfig
commands.
- 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.
- 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:/")
- Update the useHTTPSURLPrefixes property:
wsadmin> AdminConfig.modify(ps, [['useHTTPSURLPrefixes', 'false']])
- Verify your updates:
wsadmin> print AdminConfig.show(ps)
- Save the changes and exit:
wsadmin> AdminConfig.save()
wsadmin> exit
- Restart the Process Server cluster or server. For network
deployment Process Server environments, synchronize the nodes and
restart the application cluster member.
Results
The settings that are used to connect Process Server to Process
Center are now customized and the same changes are applied to the
custom nodes.