760 WebSphere Business Integration Adapters
31.1 Developing the WebSphere Business Integration
Connect send service
This section provides instructions on building a service that passes a message to
WebSphere Business Integration Connect, so that it can be transmitted to
RedContract. After testing this service, it is integrated in the process model.
Based on the output of the first staff activity, the request is sent to the inhouse
technician or to the contractor via WebSphere Business Integration Connect.
31.1.1 Define JNDI resources
WebSphere Business Integration Connect uses its own queue manager and two
queues for receiving and sending documents. We first define these resources to
WebSphere Application Server by following these steps:
1. Remove the Maintenance_ProcessesEAR project from the server.
2. Restart the server.
3. Open the Administrative Console.
4. Define the queue connection factory as follows:
Display name: partner_a.bcg.queue.manager
JNDI name: jms/partner_a.bcg.queue.manager
Queue Manager: partner_a.bcg.queue.manager
Bindings: Client
Channel Name: java.channel
Hostname: studentx
Port: 9999
5. Define the queue destination for sending as follows:
Display name: XML_OUT
JNDI name: jms/XML_OUT
Base queue name: XML_OUT
Expiry: UNLIMITED
6. Define the queue for receiving as follows:
Display name: XML_IN
JNDI name: jms/XML_IN
Base queue name: XML_IN
Expiry: UNLIMITED
7. Restart the server.
Chapter 31. Integrating and automating the process 761
31.1.2 Building the send service
In the same way that we built the WSDL for the InhouseSend service, we build
the WSDL to send a message to WebSphere Business Integration Connect by
following these steps:
1. Right-click the project Maintenance_processes and select New Empty
Service.
2. Set the package name to wbic.send and the file name to WBICSend. Click
Finish.
Figure 31-1 Create empty service
3. Add a port type WBICSend_Porttype.
4. Add an operation send to this port type.
5. Add an input and a message.
6. Set the type of the message to type Maintenance in the schema definition file
ContractorRequest.xsd, as shown in Figure 31-2 on page 762.
762 WebSphere Business Integration Adapters
Figure 31-2 Set type of the input message
Figure 31-3 on page 763 shows the interface portion of the WSDL.
Chapter 31. Integrating and automating the process 763
Figure 31-3 Interface portion of the WSDL
7. Save this WSDL file.
8. Similar to what was done for the InhouseSend service, create a new WSDL
file, WBICSendService.wsdl.
764 WebSphere Business Integration Adapters
9. Add import statements for the schema definition and for the abstract WSDL
file, as shown in Figure 31-4.
Figure 31-4 Import the interface and schema
10.Add a binding, WBICSend_Binding. Set the protocol to JMS and the message
type to TextMessage.

Get WebSphere Business Integration Adapters: An Adapter Development and WebSphere Business Integration Solution now with O’Reilly online learning.

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