Developing JSF applications for business processes and human tasks

Business Process Choreographer Explorer provides several JavaServer Faces (JSF) components. You can extend and integrate these components to add business-process and human-task functionality to Web applications.

Why and when to perform this task

You can use WebSphere Integration Developer to build your Web application.

Steps for this task

  1. Create a dynamic project with JSF support.

    Change the Web Project Features properties of the Web project to include the Faces Base Components.

  2. Add the prerequisite Business Process Choreographer Explorer Java archive (JAR files).
    Add the following files to the WEB-INF/lib directory of your project:
    • bpcclientcore.jar
    • bpeclientmodel.jar
    • htmclientmodel.jar
    • bpcjsfcomponents.jar
    These files are in the following directories:
    • On Windows systems: install_root\ProcessChoreographer\client
    • On UNIX and Linux systems: install_root/ProcessChoreographer/client
  3. Add the Business Process Choreographer Explorer JSF components to the JSF application.
    1. Add the tag libraries that are used by the JSF components to the JavaServer Pages (JSP) files.
      The components use the following tag libraries:
      • <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
      • <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" % >
      • <%@ taglib uri="http://com.ibm.bpe.jsf/taglib" prefix="bpe" % >
    2. Add an <f:view> tag to the body of the JSP page, and an <h:form> tag to the <f:view> tag.
    3. Add the JSF components to the JSP files.

      Depending on your application, add the list component, the details component, the command-bar component, or the message component into the JSP files.

    4. Configure the managed beans in the JSF configuration file.

      By default, the configuration file is the faces-config.xml file. This file is in the WEB-INF directory of the Web application. Depending on the component that you add to your JSP file, you also need to add the references to the query and other wrapper objects to the JSF configuration file.

    5. Implement the custom code and add the references to the JSF configuration file to implement the managed beans.
  4. Deploy the application.

    Map the EJB references to the Java™ Naming and Directory Interface (JNDI) names or manually add the references to the ibm-web-bnd.xmi file.

    The following table lists the reference bindings and their default mappings.
    Table 1.
    Reference binding JNDI name Comments
    ejb/BusinessProcessHome com/ibm/bpe/api/BusinessFlowManagerHome Remote session bean
    ejb/LocalBusinessProcessHome com/ibm/bpe/api/BusinessFlowManagerHome Local session bean
    ejb/HumanTaskManagerEJB com/ibm/task/api/HumanTaskManagerHome Remote session bean
    ejb/LocalHumanTaskManagerEJB com/ibm/task/api/HumanTaskManagerHome Local session bean
Your Web application that contains the Business Process Choreographer Explorer components is deployed.

Terms of use | | Broken links

Last updated: Tue Feb 21 17:21:51 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)