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

492 WebSphere Business Integration Adapters

Figure 26-22 Configuration Manager response

This message does not mean that your BAR file has successfully deployed. It

merely indicates that the Configuration Manager has accepted your request

and initiated a deploy.

22.Double-click the Event Log in the Domains view to open the Broker Domain

Event Log. This log contains messages that pertain to deployment events.

Check for a successful deployment message. This is not the same as the

Windows Event Viewer.

26.5 Unit testing the flow

Now that you have the first of your flows running, you can test the transformation

of a front-end request to a back-end business object. Before you start, clear any

left-over messages from previous unit testing by following these steps:

1. Open the browser window for the front-end application.

2. Enter a Tenant Id. We chose 100 or 101, because these have maintenance

records in the back-end.

3. If the JMSConnector is set for manual polling, then instigate a poll cycle.

We are now expecting that the broker has picked the message up from the

DELIVERY queue, transformed it, and put it to the REQUEST queue for the

RMConnector.

4. Verify that this message exists by using rfhutil in browse mode, as shown in

Figure 26-23 on page 493.

Chapter 26. Building and testing message flow for Retrieve 493

Figure 26-23 RM request queue

5. Click the Data tab to see the message for the transformed object, as shown in

Figure 26-24 on page 494.

494 WebSphere Business Integration Adapters

Figure 26-24 Transformed message

6. Check the traces that we have supplied for you if you need some clues:

– InputMessageFromFrontEnd shows the message tree as it was delivered

to the broker on the MQInput (see Example A-1 on page 867).

– RedTenantDelivery_Retrieve shows the path that the message took after

the RouteToLabel and the message tree as it was prior to the Compute

(see Example A-2 on page 870).

– RedMaintRequest shows the message tree after the Compute, that is,

what should have gone to the REQUEST queue (see Example A-3 on

page 872).

Tip: If you do not see this information, check the Windows Event Viewer, not

the Domain Event Log. The Windows Event Viewer contains run-time errors

from the broker, while the Event Log only contains deployment time errors.

Chapter 26. Building and testing message flow for Retrieve 495

The final test for the first message flow is to let the RMConnector pick up your

message and process it correctly by doing the following:

1. Ensure that the RedMaintenance application is running.

2. Start the RMConnector.

You should see the RMConnector process the message from the REQUEST

queue and place the result of the retrieve operation on the RESPONSE

queue for the broker (REDMAINT.RESPONSEQUEUE).

3. Check the application log for a successful retrieve (see Figure 26-25).

Figure 26-25 RedMaintenance log

4. Using rfhutil, browse the message from the

REDMAINT.RESPONSEQUEUE and verify that it resembles that shown in

Figure 26-26 on page 496.