WebSphere Business Integration Adapters: An Adapter Development and WebSphere Business Integration Solution

Chapter 31. Integrating and automating the process 821

8. Verify that all connectors are running, that the message flows are running,

and that the back-end application is running.

9. Use the Maintenance Web application to create a new maintenance request.

Do you get a process instance in the Test server?

31.3 Building the receive process

The full process is not yet finished. When the maintenance reviewer has sent a

request to the contractor, the contractor eventually sends a response back to

RedMaint. This response might be a progress update or a message indicating

that the request has been completed. These messages arrive on the queue

XML_IN. Somebody needs to pick them up and pass them on to the back-end

application.

We have limited the instructions to a minimum in this section. You have

performed all the tasks that are required to completed this section before.

31.3.1 Creating the service WBICReceive

Similar to the WBICSend service, you need to create a WBICReceive service.

Use the exact same steps as in 31.1.2, “Building the send service” on page 761.

The only difference is the queue name, XML_IN. You also need to define the

queue destination in JNDI.

31.3.2 Building the EJB to process the incoming message

The next step is to create an EJB to process the incoming response from

RedContract. As before, build this EJB based on the WSDL of the WBICReceive

service. For assistance with this step, refer to 31.2.1, “Generating the EJB that is

called by an MDB” on page 785. You should use a different EJB project.

31.3.3 Building the message-driven bean

Similar to 31.2.2, “Generating the MDB” on page 794, create an MDB that is

based on the WSDL of the EJB and the WSDL of the WBICReceive service. Do

not forget to correct the JNDI names in the deployment descriptor and the

listener port. Correct also the listener port and define this listener port to the Test

server.

822 WebSphere Business Integration Adapters

31.3.4 Generating proxy for adapter

This time, the EJB does not need to invoke a process. It is sufficient to invoke the

adapter. Generate a service proxy for the adapter. Use the same test procedure

as explained in 31.2.7, “Testing the proxy and the adapted process model” on

page 812.

31.3.5 Updating EJB to call adapter proxy

When the proxy has been tested, copy the appropriate lines of code in the EJB.

Populate the RM_Maintanance business object based on the incoming message

from the RedContract company, and invoke the update method of the adapter.

31.3.6 Deploying and testing

Add the new project to the server. Use the sample ContractorResponse.xml to

build a response message that matches the data in the database. Send this

response from WebSphere Business Integration Connect Express to

WebSphere Business Integration Connect. Watch this response being picked up

by the MDB that invokes the EJB who invokes the adapter service proxy. The

service proxy writes the message to the queue of the adapter.