IBM BPM, V8.0.1, All platforms > Install IBM BPM > IBM BPM Advanced for z/OS: Process Server > Configure IBM BPM Advanced for z/OS: Process Server > Configure components > Configure additional components

Configure Process Server

You can use the administrative console to configure an application server or cluster as an IBM Process Server. By configuring a server or cluster as a Process Server, you enable the server or cluster to support process applications and their associated services. Process Portal is also configured.

If you have not already configured Business Space, perform Configure Business Space first.

This task describes how to use the administrative console to configure a server or cluster as a Process Server.

For information about configuring a server or cluster as a Process Server using wsadmin scripting, including parameter definitions and examples, see the configureProcessServer command in the Reference documentation.

If you are using a stand-alone server profile, or have previously configured Process Server support for the server or cluster (for example, by running the ND wizard), you cannot perform the following procedure because it has already been done for you. You can review your current configuration but cannot change it in the administrative console.


Procedure

  1. Launch the administrative console

  2. From the administrative console, select a path for configuring a server or a cluster.

    To configure a server, click Servers > Server Types > WebSphere application servers > server_name > Process Server.

    To configure a cluster, click Servers > Clusters > WebSphere application server clusters > cluster_name > Process Server

  3. Set the parameters to configure the server or cluster as a Process Server.

    For a description of all parameters, go to the panel and select Page help.

  4. Save the configuration.


Results

You have configured the server or cluster as a Process Server. Process Portal is also configured.


What to do next

Configure any other BPM components and products that are part of your installation. Typically, when configuring BPM components using the administrative console, the sequence of configuration tasks to perform after you have configured Process Server, would be as follows:

  1. Verify Process Portal.

  2. Configure Performance Data Warehouse

  3. Configure SCA

  4. Configure Business Process Choreographer

  5. Configure Common Event Infrastructure (optional)

A TeamWorksConfiguration.running.xml file is generated from several local configuration XML files when each server starts. This file is located at BPM_ROOT\profiles\ profile_name\config\cells\ cellName\nodes\ nodeName\servers\ serverName\process-center\TeamWorksConfiguration.running.xml.

Check the contents of TeamWorksConfiguration.running.xml.

You might need to edit the configuration files used to generate the TeamWorksConfiguration.running.xml file.

If changes are required for the URL, IP addresses, and ports, then update the 99Local.xml and the 100Custom.xml configuration files and restart the server(s). You must update these files when you add a web server to your cluster because information from these files are used for generating application URLs. Verify that you make identical changes for these files on all affected nodes, the 99Local.xml and 100Custom.xml files are local to the systems on which they reside. They are not replicated automatically between nodes. For more information about updating the xml files, see the The 99Local.xml and 100Custom.xml configuration files and Customize the Process Server or Process Center cluster to work with a web server topics.

Configure additional components


Related tasks:
Configure the Business Space component for Process Portal
Configure SCA support for a server or cluster
Configure Business Process Choreographer
Configure Common Event Infrastructure
Configure Performance Data Warehouse
Verifying Process Portal