IBM BPM, V8.0.1, All platforms > Install IBM BPM > Plan for IBM BPM > Plan to configure Business Process Choreographer > Plan for a custom configuration

Plan for the Business Flow Manager and Human Task Manager

The core of a Business Process Choreographer configuration consists of the Business Flow Manager and the Human Task Manager.

You must plan their configuration parameters.


Procedure

  1. Make sure you know the Java™ Message Service (JMS) provider user ID that will be used as the run-as user ID for the Business Flow Manager message driven bean. In the administrative console, and in Table 5, it is known as the JMS API Authentication User.
  2. Make sure you know the Java Message Service (JMS) provider user ID that will be used as the run-as user ID for the Human Task Manager message driven bean. In the administrative console, and in Table 5, it is known as the Escalation User Authentication User.
  3. Make sure you know which groups or user IDs the security roles for administrator and monitor will map onto. For details, see Table 6.

  4. If you want the Human Task Manager to send email notifications of escalation events, identify the host name or IP address where the Simple Mail Transfer Protocol (SMTP) email server is located. Plan what the sender address should be for email notifications.

    If the email service requires authentication, make sure you know the user ID and password to use to connect to the service.

  5. Decide on the context root for the web service binding of the API.

    • When configured on a server:

      • The default for the Business Flow Manager is /BFMIF_ nodeName_ serverName.

      • The default for the Human Task Manager is /HTMIF_ nodeName_ serverName

    • When configured on a cluster:

      • The default for the Business Flow Manager is /BFMIF_ clusterName

      • The default for the Human Task Manager is /HTMIF_ clusterName

  6. If you are going to use the Business Process Choreographer Explorer, the Business Space, or a client that uses the Representational State Transfer (REST) API or the JAX web services API, decide on the context roots for the REST API and the JAX web services API.

    • The defaults for the Business Flow Manager are /rest/bpm/bfm and /BFMJAXWSAPI.

    • The defaults for the Human Task Manager are /rest/bpm/htm and /HTMJAXWSAPI.

    • When configured on a server, or on a single cluster, or on multiple clusters that are mapped to different web servers, you can use the default values.

    • When configured in a ND environment on multiple deployment targets that are mapped to the same web server, do not use the default values. The context root for each Business Process Choreographer configuration must be unique for each combination of host name and port. You will have to set these values manually using the administrative console after configuring Business Process Choreographer.

  7. Decide whether you want to initially enable audit logging for the Business Flow Manager, or Human Task Manager, or both.

  8. If you are going to use the Business Process Choreographer Explorer reporting function, decide whether you want the Business Flow Manager to be initially configured to generate Common Event Infrastructure logging events.


Results

You have planned all the initial configuration parameters for the Business Flow Manager and Human Task Manager. You can change any of these setting anytime later using the administrative console.