Chapter 8. Deploying sample on WebSphere Business Integration Server Foundation 301
8.5.1 Resources used by the private exchange application
At this point our Business Process Container is installed and configured. (If the
Business Process Container is not installed and properly configured you
must do
that before you continue.) Now you follow the general procedure for installing
BPEL-based process applications found in the WebSphere Business Integration
Server Foundation InfoCenter. Generally the steps are these:
1. Create your queue managers and JMS resources.
2. Define the Message Listener ports.
3. Install the EAR file.
4. Enable security (if needed, and if you have interruptible processes in your
application, you do need security enabled).
5. Start the application.
Create the WebSphere MQ resources
Our sample application needs an input and an output queue. Use the
WebSphere MQ Explorer to create the required queues (you also have to
configure them for WebSphere, but you do that separately).
1. Start the WebSphere MQ Explorer and select the queue manager you are
using (ours was WAS_BPE_ka6brmp).
a. Create the inbound queue. Only the name, PEAGGIN, is needed. See
Figure 8-16 on page 302.
Note: When Business Choreographer based applications are assembled, the
business process resides in a .far file packaged in the EAR. The name of the
process is used to identify the process template. Process template names
must be unique in the BPE DB. (If template names were not unique, you could
have process instances running with the same name and different maps.
Obviously this is a situation you want to avoid.) Consequently, if you try to
install an application that contains a process name that exists in the BPE DB,
the installation will fail. You do not have to rename your processes for every
version, as you can use the ValidFrom property for the process.
302 Using BPEL Processes in WebSphere Business Integration Server Foundation - Business Process Integration and Supply Chain Solutions
Figure 8-16 Create PEAGGIN Queue PEAGGIN
a. Click OK.
b. Create the outbound queue, PEAGGOUT. Once again you only need to
enter the queue name; see Figure 8-17 on page 303.
Chapter 8. Deploying sample on WebSphere Business Integration Server Foundation 303
Figure 8-17 Create the PEAGGOUT queue
c. Click OK.
2. Create the JMS resources. Start the WebSphere Administrative Console and
log on.
a. Click Resources
WebSphere MQ JMS Provider.
i. The queue connection factory is QCF.
ii. JNDI name is jms/QCF.
iii. Queue manager name is WAS_BPE_KA6BRMP.
3. Create the queue destinations:
a. Click Resources
WebSphere MQ JMS Provider.
b. Click WebSphere MQ Queue Destinations.
c. Click New.
d. Enter the required fields as:
i. Name: PEAGGIN.
304 Using BPEL Processes in WebSphere Business Integration Server Foundation - Business Process Integration and Supply Chain Solutions
ii. JNDI Name: jms/peaggin.
iii. Base Queue Name: PEAGGIN.
iv. Click OK.
e. Click New again and enter:
i. Name: PEAGGOUT for the output queue.
ii. JNDI Name: jms/peaggout.
iii. Base Queue Name: PEAGGOUT.
iv. Click OK.
4. Define the Listener Ports (shown in Figure 8-18).
a. Click Message Listener Service.
b. Click Listener Ports.
c. Create a new listener port called SenderQListenerPort.
Figure 8-18 Listener port definition
d. Enter connection factory JNDI name jms/QCF.
e. Enter destination JNDI name jms/PEAGGIN.
f. Click OK.
g. Click Save and Save again. Stay in the WebSphere Administrative
Console.

Get Using BPEL Processes in WebSphere Business Integration Server Foundation Business Process Integration and Supply Chain Solutions now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.