304 Managing Information Access to an EIS Using J2EE and Services Oriented Architecture
Working with the Chapter6and9 sample files
The ch06and09projects.zip contains projects that can be imported into
WebSphere Studio Application Developer Integration Edition V5.1.1 and the
ch06and09workspace.zip can be extracted to a WebSphere Studio Application
Developer Integration Edition workspace that contains the same projects. The
The projects are:
򐂰 IMSConnector
򐂰 IMSServiceEAR
򐂰 IMSServiceEJB
򐂰 Servers
򐂰 TraderEISCompEAR
򐂰 TraderEISCompEJB
򐂰 TraderLogEJB
򐂰 TraderSP
򐂰 TraderSPEAR
򐂰 TraderSPEJB
򐂰 TraderSPWeb
򐂰 J2C Tool Plugin Import Service
Note that the samples.zip file contains many of the same projects found in the
ch06and09projects.zip, but it also has modelling and design files. You should
extract the samples.zip file to a temporary folder. It contains:
򐂰 A readme.doc file
򐂰 ITSO Residency.zip
This file contains the business process models developed to describe the
Stock Trade scenario. It is a WebSphere Business Integration Modeler export
file. It contains the business items Analysis Details, Order Details, and Trade
Details. It includes process models Stock Analysis, Stock, Brokerage, and
Stock Trade.
򐂰 JMSJCADesign.zip
The file contains the EJB code model for the Trader EIS Component
developed with XDE developer. The code model includes the StockOrderBO,
StockOrderRequest, and StockOrderConfirmation java classes. It also
contains the TraderIMSFeature EJB and the TraderIMSIntegration EJB. UML
diagrams as shown in 6.4, “Develop EIS integration using JMS” on page 137
have been created from this model.
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
306 Managing Information Access to an EIS Using J2EE and Services Oriented Architecture
򐂰 TraderSPService.zip
The zipped file that contains the service project with BPEL process and
WSDL definitions. It includes:
The BPEL system process: TraderSystemProcess.bpel
The WSDL interface of the BPEL process: TraderSPInterface.wsdl
The service description of the J2C IMS service: TraderEIS*.wsdl
The service description of the EIS component (EJB):
TraderIntegration(EJB)*.wsdl
The service description of the EIS component (JMS):
TraderIntegrationSend(EJB)*.wsdl
The service description of the Log service: LogRequest(EJB).wsdl
The XML schema definitions of the business objects used in the WSDL
files: *.xsd

Get Managing Information Access to an Enterprise Information System Using J2EE and Services Oriented Architecture 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.