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
- Create a dynamic project with JSF support.
Change
the Web Project Features properties of the Web project to include the Faces
Base Components.
- 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
- Add the Business Process Choreographer Explorer JSF components
to the JSF application.
- 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"
% >
- Add an <f:view> tag to the body of the JSP
page, and an <h:form> tag to the <f:view> tag.
- 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.
- 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.
- Implement the custom code and add the references to the JSF
configuration file to implement the managed beans.
- 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.