Appendix A. Deploying the sample code 305
???? IMSService.jar
The file contains the IMS access code generated with WebSphere Studio
Application Developer Integration Edition. It includes:
– The WSDL files including the IMS binding: Trader.wsdl, TraderIMS*.wsdl
– The utility classes: INPUT, OUTPUT, WSIF Format Handlers
– The proxy class to call the IMS transaction: TraderProxy.java
– The JUnit test class to test the proxy: TraderProxyTest.java
???? TraderEISCompEAR.ear
This EAR file contains the TraderEISCompEJB module and utility Jars
required to compile the module (IMSService.jar, IMSServiceEJB.jar). The
TraderEISCompEJB module includes the following EJBs:
– The IMS feature session bean: TraderIMSFeature
– The EIS component session bean: TraderIntegration
– The MDB that processes incoming messages and calls TraderIntegration:
TraderIntegrationMDB
– The session bean to sent the reply back to clients: TraderReply
???? IMSServiceEAR.ear
This EAR file contains the client code for the EIS component. The EJBs have
been used to test the Trader EIS component. Later they have also been
included in the Trader system process (BPEL) to call the EIS component. The
EAR includes utility JARS required to compile the module (IMSService.jar,
TraderEISCompEJB.jar) and the IMSServiceEJB module which has the
following EJBs:
– The session bean to create and send the JMS request to the Trader EIS
component: TraderIntegrationTest
– The MDB to receive and log the reply from the EIS component:
TraderRepl yTest
???? TraderLogEJB.jar
The EJB module contains the two EJBs used to log the request message sent
to the EIS component (see 9.4.1, “Transaction support” on page 289s). The
module contains:
– The entity bean used to log the request in the database: LogCMP
– The session that creates the LogCMP objects on request: LogSB