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
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.