Chapter 27. Building and testing message flows for Create 547
27.6 Deploying RedMaint_RetrieveTenantByContent
To deploy this flow:
1. Go back to the Broker Administration perspective.
2. Using the technique that is described in 26.8, “Deploying the Message Flows”
on page 511, add the changed flow to the Broker Archive file.
3. Save this updated BAR file.
4. Redeploy to the RedMaintenance Execution Group.
27.7 Unit testing RedMaint_RetrieveTenantByContent
If your Message Flow is functioning correctly, as soon as it is deployed
successfully, the message that is on it from the previous test will be picked up by
the flow. The new RM_Maintenance message should now be sitting on the
REDMAINT.REQUESTQUEUE waiting for the RMConnector (Figure 27-29).
Figure 27-29 Request queue
548 WebSphere Business Integration Adapters
To test the message flow:
1. Verify the message on the request queue to ensure that it has all of the
required data, the correct ObjectEventId, and verb (Create).
2. Start the RMConnector.
3. Check the connector log and the application log for a successful creation of a
new maintenance record.
4. Check the database for the new row (the dates set by default in the
application for a new maintenance for actual and expected completion with be
today’s date).
5. Verify the message on the response queue for the new maintenance ID on
the business object (Figure 27-30).
Figure 27-30 Response message
You are now ready to complete the round trip for a creation request.

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

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.