Overview of the runtime logic of process choreographer

This topic will give you a high-level understanding of the sequence of the manual and automatic actions that take place when installing, configuring, and using process choreographer.

If you use process choreographer, having a high-level understanding of the internal logic sequences and dependencies can help you diagnose and solve problems faster.

Run-time logic sequence

To get your first business process running on an application server and have users using a browser to access the process choreographer Web client to process work items, the necessary tasks and subtasks are performed in the following sequence:

  1. To have a working business process container:
    1. Create the database and tables.
    2. If using WebSphere MQ as the JMS provider, create the queue manager and queues.
    3. Install and configure the business process container application, either:
      • Using the Install Wizard (recommended)
      • Manually
      In this phase, the following resources are configured:
      • JDBC provider, driver, and class path
      • Data source user ID and password
      • Database custom properties
      • JMS provider, queue manager, user ID, password, scheduler calendar, and security mapping for the role of business process administrator
      • Create or reuse JMS resources: connection factory and queues
      • Install the Web client (recommended)
    4. If you installed the business process container on a cluster using the Install Wizard, the business container is configured on all application servers in the cluster to have identical connection factory properties. These properties must be customized manually according to whether you are using a central queue manager or a cluster of queue managers.
    5. The name of the business process container application depends on where you installed it. It has the prefix BPEContainer_ followed by the InstallationScopeIdentifier.
      • If you installed the business process container on a single application server, the application is named BPEContainer_nodeName_serverName.
      • If you installed the business process container on a cluster, the application is named BPEContainer_clusterName.
    6. If you will use V5.0-style processes that have a duration specified on the staff activity server property page, set the JNDI name of the calendar EJB to use.
    7. Activate the business process container by restarting the application server. On a cluster, you must restart them all.
    8. g. To ensure that the business process container has started successfully, check that there are no error messages in the SystemOut.log file for the application server. On a cluster check the log for all application servers in the cluster.
  2. Install an enterprise application that contains a business process using either the administrative console or the wsadmin command.
    1. If you do not have your own application to try, you can install the travel booking sample from the samples gallery.
    2. Errors will occur if the process choreographer cannot be accessed, because all business process templates must be stored in the database. These problems can be caused if the database system is not running, if any database clients are not correctly configured, or if errors were made defining the data source.
    3. After the enterprise application is installed, it is in the state stopped, and any process templates that it contains are in the state started. No process instances can be created until the application is started. Select it and click Start to start the application. When the application server is restarted, the enterprise applications on it are started automatically.
    4. At this point, the input queues are read for the first time. Errors will occur at this stage if the queue manager is not running, or if any mistakes were made defining the JMS provider or JMS resources.
  3. Configure the WebSphere Application Server security environment for secured applications, including assigning users and groups to roles defined in business process applications and configuring authentication mechanisms.
  4. Configure the Web client by running the bpeportal.jacl script.
  5. Start the Web client by opening the page http://app_server_host:port_number/bpe/webclient.
    1. If the Web client application BPEWebClient_InstallationScopeIdentifier is not installed you will get an error.
    2. If the Web browser can contact the Web client application, enter a user ID and password on the log on screen.
    3. If the user ID is known to the system, and the password is correct, any existing work items will be displayed in the To Do list.
    4. If your user ID is authorized, you can start an instance of a process template, enter any input message parameters.
      • If the business process contains an activity that requires human interaction, a work item is added to the To Do lists of all the potential owners. If you are one of these potential owners, you can display your My To Dos page to work with the work item.
      • If the process instance is a non-interruptible process (that is not a BPEL-based process implementing a one-way operation) it will displays an output message when the process ends.
      • If the database table for the application's persistent data has not been created, the following error message will occur, the first time that a user attempts to use the application: Message: BPEA0024E with ILMC0009W. This error can be avoided by selecting the option to automatically create the database tables, while installing the application for the first time.
  6. Reaching this point means that your process choreographer system is fully functional. Most users will either use the standard Web client, in the ways described in Managing processes, or they will use a customized version of the Web client to work with work items, process templates, and precess instances.
  7. At the end of the process choreographer life-cycle, if you want to remove process choreographer from your machine, you must stop delete, and uninstall things in a particular order:
    1. Uninstalling enterprise applications that contain business processes is described in Uninstalling BPEL-based process applications and Managing processes and requires the following actions:
      1. To prevent the creation of any new process instances, you must stop all process templates in the enterprise applications, as described in Managing processes.
      2. Log onto the Web client as a process administrator and make sure that all process instances have stopped, you can either wait for them to end or force them to stop, as described in Working with process instances.
      3. Stop all enterprise applications that contain business processes. If any process instances belonging to the application are still running, this step will fail.
      4. Uninstall the enterprise applications that contain business processes. If the application contains an interruptible process, the corresponding tables are deleted from the databases on the deployment targets. If the tables cannot be deleted, for example, because you do not have the database access rights to delete tables, an exception is written to the SystemOut.log file.
    2. Uninstall the business process container, as described in Uninstalling the business process container.
    3. Manually delete the database and queue manager.

People involved

To get process choreographer fully operational can require the following people:


Related tasks
Troubleshooting process choreographer



Searchable topic ID:   c5_logic
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/workflow/concepts/c5_logic.html

Library | Support | Terms of Use | Feedback