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 a remote client application

Plan for a remote Business Process Choreographer client application that uses the Business Process Choreographer APIs and runs on an IBM BPM Advanced client installation.

If you want an application to use the Business Process Choreographer APIs, you can use an IBM BPM Advanced client installation to run the applications remotely against a full IBM BPM Advanced installation. The client is easier to configure and administer than a full IBM BPM Advanced installation.

You can even install the IBM BPM Advanced client on top of an existing WebSphere Application Server installation that has federated profiles and those federated WebSphere Application Server profiles can take advantage of the IBM BPM Advanced client functionality immediately. This scenario is not possible with the full IBM BPM Advanced because IBM BPM Advanced does not support augmentation of already federated profiles.


Procedure

  1. Plan to install an IBM BPM Advanced client.

    • You can you can install the client on servers and clusters in standalone and managed profiles. If you want to use the IBM BPM Advanced client in a cluster, then install the IBM BPM Advanced client on all WebSphere Application Server installations that host cluster members.

    • If you want WebSphere Portal Server to access Business Process Choreographer, you must have a compatible IBM BPM Advanced client installed. For more information about compatibility between IBM BPM Advanced and WebSphere Portal, refer to the Technote http://www.ibm.com/support/docview.wss?uid=swg21580260.

    • Any existing profiles, including already federated profiles, can use the IBM BPM Advanced client immediately, because the client installation does not augment the base profile.

    • If there is no existing WebSphere Application Server installation, a WebSphere Application Server ND installation will be created.

  2. Decide which type of Business Process Choreographer client application you will use:

  3. If you are going to develop a custom client application that will use Business Process Choreographer, plan which interfaces the application will use. You can handle processes and tasks using one of the following:

    • Web services API, Java™ Messaging Service (JMS) API or representational state transfer (REST) API – remote client applications that are based on these APIs do not need any WebSphere Process Server installation.
    • JavaServer Faces (JSF) components

    • Enterprise JavaBeans (EJB) API

    If you develop a client application, which uses the Business Process Choreographer EJB APIs, it must be packaged in the way that is described in Access the remote interface of the session bean.

  4. Decide or identify the type of cell where the IBM BPM Advanced client will be installed:

    1. In a cell where a managed server or cluster is located, on which Business Process Choreographer is configured, the default configuration of the Remote Artifact Loader (RAL) allows the unsecured transmission of artifacts between the client and the server. This is known as the "single-cell" scenario.

    2. In a cell that does not have a managed server or cluster with Business Process Choreographer configured on it, there are different dmgrs. This is known as the "cross-cell" scenario.

      If your client application uses the EJB API, you must define a namespace binding so that the client application can locate the server or cluster where Business Process Choreographer is configured.


Results

You have planned for a remote Business Process Choreographer client application.


Related concepts:
Comparison of the programming interfaces for interacting with BPEL processes and human tasks


Related tasks:
Developing client applications for BPEL processes and tasks