Configuration of Process Choreographer Web client - connect to a remote Business Process Container
 Technote (troubleshooting)
 
Problem(Abstract)
Since version 5.0.2, the Process Choreographer Web client has a rich set of new functionality. Among other things, it is now possible to deploy the Web client on a different server than the Business Process Container.

This document describes how the Web client needs to be configured to connect to a remote Business Process Container.
 
Resolving the problem
Your condition:
  • You are working on WebSphere® Application Server, Enterprise Edition, version 5.0.2
  • You have an ND environment established
  • In your ND environment, you have already one or more Business Process Containers up and running

You want to:
  • Set up a Process Choreographer Web client in your ND environment to connect to one of your Business Process Containers


Restrictions
  • The steps described in this tech note are only valid with version 5.0.2. of WebSphere Application Server Enterprise Edition. For version 5.1 and subsequent releases, please use the description in the info center (see link below).
  • The server on which the Process choreographer web client is running must be an Enterprise Edition server.
  • The server on which the Process choreographer web client is running must be in the same cell as the server with the Business Process Container to which you want to connect.

Steps for you to take:

  • Edit the EAR file that contains the Process Choreographer Web client: In the /installableApps/processportal.ear!/processportal.war!/WEB-INF/struts-config.xml file, set the 'remote' property to true:
    <plug-in className="com.ibm.bpe.portal.Configuration">
      <set-property property="remote" value="
    true"/>
    </plug-in>

  • Deploy the Process Choreographer Web client using the Deployment manager. Each deployed Web client can only connect to one Business Process Container.
    During deployment, you cannot use the default JNDI names for EJBs. Instead, use the following names (where <bpeNode> and <bpeServer> refer to the Business Process Container to which you want to connect)
    ejb/BusinessProcessHome cell/nodes/<bpeNode>/servers/<bpeServer>/com/ibm/bpe/api/BusinessProcessHome
    ejb/ClassLoaderProxyHome cell/nodes/<bpeNode>/servers/<bpeServer>/ejb/bpe/InternalClassLoader
    ejb/compensation/StandardExecutorHome cell/nodes/<bpeNode>/servers/<bpeServer>/ejb/bpe/StandardExecutor
    ejb/compensation/SphereSessionBeanHome cell/nodes/<bpeNode>/servers/<bpeServer>/ejb/bpe/SphereSessionBean
    ejb/compensation/ContextualProcletHome cell/nodes/<bpeNode>/servers/<bpeServer>/ejb/bpe/ContextualProclet
    ejb/LocalBusinessProcessHome [will not be used, since you are connecting remotely to the Business Process Container and therefore cannot use its local EJB interface]

    If you have not changed the default JNDI names of your Business Process Container, you only have to prefix the default JNDI names that appear during Web client deployment with the cell/nodes/<bpeNode>/servers/<bpeServer>/ string that describes the location of your Business Process Container.

 
Related information
WebSphere Info Center
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Enterprise Edition (EE)
Operating system(s): Windows
Software version: 5.0.2
Software edition:
Reference #: 1137661
IBM Group: Software Group
Modified date: Apr 30, 2004