Chapter 10. Scenario: Connectivity to third-party JMS providers 331
10.10 Testing the flow
In this section, we explain the integration testing between the integration module
and the message flow in WebSphere Integration Developer. The flow was tested
using the Integration Test Client.
The test client is invoked from the context menu of the business integration
module, StockQuoteModule, in the Business Integration view.
1. Select StockQuoteModule, right-click, and select Test → Test Module.
2. On the Configuration tab, in the Emulators section, remove
StockQuotePartner.
3. In the Initial request parameters area (Figure 10-21), enter the values for the
StockBO business object attributes.
4. Click Continue.
Figure 10-21 Testing the module
5. Since this is a one-way request, no response is returned. The messages are
delivered to the JMS providers. You can look in the SystemOut log for the
Process Server application server to view messages or errors produced by
the business process application (Example 10-1 on page 332).
332 Using IBM WebSphere Message Broker as an ESB with WebSphere Process Server
Example 10-1 Standard output from the Integration Test Server
[9/27/07 9:08:28:078 CDT] 0000008e SibMessage I [:] CWSID0020I: The messaging
engine configuration reload is complete.
[9/27/07 9:08:31:031 CDT] 000000bb ResourceMgrIm I WSVR0049I: Binding MQQCF as
jms/MQQCF
[9/27/07 9:08:31:109 CDT] 000000bb ResourceMgrIm I WSVR0049I: Binding MQINPUTQ as
jms/MQINPUTQ
[9/27/07 9:08:31:188 CDT] 000000bb ResourceMgrIm I WSVR0049I: Binding WPS
DataSource_CF as eis/jdbc/WPSDB_CMP
[9/27/07 9:08:31:219 CDT] 000000bb ResourceMgrIm I WSVR0049I: Binding QCF as
jms/QCF
[9/27/07 9:08:31:266 CDT] 000000bb ResourceMgrIm I WSVR0049I: Binding WPS
DataSource as jdbc/WPSDB
[9/27/07 9:08:31:281 CDT] 000000bb ResourceMgrIm I WSVR0049I: Binding
DynamicArtifactRepositoryDataSource as
jdbc/wbiserver/DynamicArtifactRepositoryDataSource
[9/27/07 9:08:31:297 CDT] 000000bb SystemOut O *** WARNING *** Both transport and
store protocols are undefined; this mail session will be unusable
[9/27/07 9:08:31:297 CDT] 000000bb ResourceMgrIm I WSVR0049I: Binding
WSRRMailSession as mail/WSRRMailService
[9/27/07 9:08:31:328 CDT] 000000bb ApplicationMg A WSVR0200I: Starting application:
StockQuoteModuleApp
[9/27/07 9:08:31:656 CDT] 000000bb ArtifactLoade I
com.ibm.ws.al.bootstrap.WASBootstrap appStart(DeployedApplication) CWLAG0205I:
Artifactloader initializing is complete for module StockQuoteModuleApp.
[9/27/07 9:08:31:875 CDT] 000000bb Core I SCA_STARTING_APP_MODULE
[9/27/07 9:08:32:203 CDT] 000000bb Core I SCA_STARTED_APP_MODULE
[9/27/07 9:08:33:047 CDT] 000000bb EJBContainerI I WSVR0207I: Preparing to start
EJB jar: StockQuoteModuleEJB.jar
[9/27/07 9:08:33:094 CDT] 000000bb EJBContainerI I WSVR0037I: Starting EJB jar:
StockQuoteModuleEJB.jar
[9/27/07 9:08:33:188 CDT] 000000bb ActivationSpe E J2CA0306I: Application
StockQuoteModuleApp#StockQuoteModuleEJB.jar#ServiceSIBusMessageBean has provided no
<activation-config-property> for the ActivationSpec class
com.ibm.ws.sib.ra.inbound.impl.SibRaActivationSpecImpl of ResourceAdapter
cells/widCell/nodes/widNode/resources.xml#J2CResourceAdapter_1180031608156. This may
have undesirable effects.
[9/27/07 9:08:33:266 CDT] 000000bb ApplicationMg A WSVR0221I: Application started:
StockQuoteModuleApp
[9/27/07 9:09:16:203 CDT] 0000008f SystemOut O ************** Transfer Request
sent to SIBus
**********************
Chapter 10. Scenario: Connectivity to third-party JMS providers 333
Verifying the output
In SonicMQ, the messages were verified by using the JMSTest Client in the
SonicMQ management console to view them. In the test client, the following
actions were performed:
1. A connection was created to the broker at tcp://localhost:2506.
2. A queue session was created on the connection.
3. A receiver was created on the queue session for the jms_OUTQ queue.
4. After each message was sent to the business process, the queue was
checked for messages.
In SwiftMQ, the messages were viewed using the Queue Manager Swiftlet for
router2 in the SwiftMQ console. The message count in the usage statistics for the
ITSOQ queue contained the messages that were received.
334 Using IBM WebSphere Message Broker as an ESB with WebSphere Process Server
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.