298 WebSphere Business Integrator Server Foundation V5.1 Handbook
For each option, a WSDL file for the binding will be generated. This WSDL file
can be used to generate a service proxy to access the business process; simply
right-click it.
For the SOAP bindings, the generated proxies can be of type Web Services
Invocation Framework (WSIF) or Java API for XML-based RPC (JAX-RPC).
JMS binding proxy
If the deployed code for the BPEL process was generated for a JMS binding
(refer to section “JMS binding for deployed business processes” on page 293), a
WSDL file for this binding will be generated in the same package as the BPEL
process. This WSDL file can be used to generate a service proxy to access the
business process; simply right-click it.
For a JMS binding, only a proxy of type Web Services Invocation Framework
(WSIF) can be generated.
9.2 Web client
This section provides details about the Web client interface for WebSphere
Process Choreographer. The Web client is a Web application, installed by
default together with the Business Process Container.
The BPEL Editor provides interfaces to customize certain pages for the Web
client. The following is a list of activities with customizable pages:
򐂰 Staff
򐂰 Receive
򐂰 Reply
򐂰 Pick
We will show only the Staff activity customization; the rest of the activities are
very similar in terms of their pages and customization.
The process itself has customizable pages; these are discussed in the following
section.
9.2.1 Customizing process pages
When you create customized or additional pages for your Web client, you need
to place them in a Web project. There are two options available:
򐂰 Import the Web client Enterprise Application in WebSphere Studio Application
Developer Integration Edition, then customize the pages and add new ones.
Chapter 9. Process choreographer: clients 299
This option provides the most flexibility but requires the most knowledge
about the default Web client.
You can import the Web client from the
<WebSphere_Studio_root>/runtimes/ee_v51/installableApps directory; the
file is called processportal.ear.
This option is beyond the scope of this redbook.
򐂰 Create a new Web project and use it together with the default Web client
Enterprise Application.
This option is useful if you only want to make minor changes to the Web client
or if you only want to create customized pages for the activities.
We will discuss this option in the following sections.
Perform the following steps to create your own customized pages for the Web
client.
1. Create a new Web project and provide a name, for example: NJWebClient.
Add the new Web project to the Enterprise Application where your process
runs, if it is not added automatically.
2. Fix the context root for your Web application to reflect the one you want to set
up to serve the custom pages for the Web client.
3. Copy the following JAR files under the WEB-INF/lib folder:
jaxen-full.jar
–jstl.jar
processportal.jar
saxpath.jar
standard.jar
You can get the JAR files from any installed Web client, for example:
<WebSphere_Studio_root>/runtimes/ee_v51/installedApps/localhost/
BPEWebClient_localhost_server1.ear/processportal.war.
4. Create a
tld folder under WEB-INF and copy the webclient.tld file into the
directory.
300 WebSphere Business Integrator Server Foundation V5.1 Handbook
Figure 9-10 WEB-INF folder
5. Open the web.xml file and click Add to add the
WebContent/WEB-INF/tld/webclient.tld JSP tag library under the
References
JSP tag libraries tab.
You can get the TLD file from any installed Web client, for example:
<WebSphere_Studio_root>/runtimes/ee_v51/installedApps/localhost/
BPEWebClient_localhost_server1.ear/processportal.war.
6. Create your custom pages. It is recommended that you create subfolders for
each set of custom page, for example ApproveStaff for the Approve Staff
activity.
7. We will create three JSPs in the following section: Input.jsp, Output.jsp,
Mapping.jsp. Create all three of them under the ApproveStaff folder.
9.2.2 Staff activity
In WebSphere Studio Application Developer Integration Edition V5.1, it is
possible to define specific JSPs for staff activities. These JSPs can provide
additional functionality to the WebSphere Web Client by including upfront data
validation (performed in the Mapping JSP) and the ability to provide a more
descriptive user interface.

Get WebSphere Business Integration Server Foundation V5.1 Handbook now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.