54 Managing Information Access to an EIS Using J2EE and Services Oriented Architecture
Behavioral view
Figure 2-11 illustrates the behavioral view of the logical architecture.
Figure 2-11 EIS integration logical architecture behavioral view
Figure 2-11 illustrates the logical EIS system process with its main activities. A
real-world production EIS system process will have more activities. The following
sections discuss some of the main activities of the EIS system process.
Configuration
The configuration activity (or activities) must use the supplied business process
context (a context name, a context ID, and so on) to get the input parameter
values of the EIS component, as well as to determine if the EIS component is
local or remote to the EIS system process.
Example 2-5 on page 55 is a sample EIS system process configuration. This
sample shows some of the elements and attributes that you can define for your
business processes. See “Versioning” on page 23 for a discussion about
versioning in context to a back-end system integration architecture.
EIS Service Endpoint
context-id + request-business-object
Request Handling
Cache
Security
Response Handling
Response-business-object
or
EIS-service-fault
Interaction Layer
Processing Layer
Map EIS
component-response
start validate Config-file
Local/remote
end
Map EIS
component-request
Invoke remote
EIS component
Map EIS
component-request
Configuration error
EIS component error
Remote EIS adapter error
General/Catch-All error
EIS System Process
Business Delegate
JMS
TCP/IP
Web Service
SOAP/HTTP
SOAP/JMS
Adapter
EIS
Invoke local
EIS component
EIS
EIS system process exception handler
Chapter 2. Architecture 55
Example 2-5 Sample EIS system process configuration
<eis-integration>
<context businessprocess="StockTrading/debit-account">
<eis location="local">
<integration style="JCA-IMS"
feature="com.itso.trader.feature.ims.DebitAccount"/>
</eis>
</context>
<context businessprocess="StockTrading/reserve-stock">
<eis location="remote">
<integration style="JCA-CICS"
feature="com.itso.trader.feature.cics.ReserveStock"/>
<proxy class-name="com.itso.trader.RemoteEISProxy" method="process"/>
</eis>
</context>
<context businessprocess="account-enquiry">
<eis location="local">
<integration style="JCA-CICS"
version="1"
feature="com.itso.trader.feature.cics.BuyStock"/>
<integration style="JCA-CICS"
version="2"
feature="com.itso.trader.feature.cics.version2.BuyStock"/>
</eis>
</context>
<context businessprocess="RecordAudit">
<eis location="local">
<integration style="JDBC"
version="1"
feature="com.itso.trader.feature.jdbc.AuditEntry"/>
<integration style="JCA-IMS"
version="2"
feature="com.itso.trader.feature.ims.AuditEntry"/>
</eis>
</context>
</eis-integration>
Mapping
The EIS system process must map its process variable(s) into the EIS
component variable. The EIS system process must map the request to the EIS
component, and the response from the EIS component into its own process
variable(s). It must map:
???? The request domain or generic data object for the EIS component request
The EIS feature uses the request object to create a EIS request byte buffer or
JDBC SQL Statement.
56 Managing Information Access to an EIS Using J2EE and Services Oriented Architecture
???? Configuration values
EIS component uses the configuration values to handle the back-end system
integration. See “EIS component” on page 49 for a discussion about the EIS
component.
???? The EIS response data object into its process variable(s)
Invoke EIS component
Invoke a local or a remote EIS component, using either a local EIS component
partner link, or the remote EIS component proxy. See Table 2-9 on page 39 for
discussion about local versus remote EIS components.
Exception handler
The EIS system process must handle any system or application type errors.
Possible system and applications errors that must be handled are:
???? EIS system process exceptions
– Bugs in the system process
– Developer bugs that can cause a NullPointerException in Java snippets
– Mapping requests or responses
???? Configuration activity errors
– Bad or invalid business process context values
– No configuration sources
– Parsing errors on the configuration sources
???? EIS component errors
– Any local component exceptions
– Any remote component exceptions, including system errors or J2C
connector errors
???? A general / Catch-All
Chapter 2. Architecture 57
Figure 2-12 shows a detailed view of EIS components with their relationships.
Figure 2-12 EIS component model
EIS component adapter(s)
Figure 2-11 on page 54 indicates that the invoke remote activity calls the remote
EIS component via an adapter. Exposing your remote EIS component using a
JMS adapter allows you to have assured delivery of your messages, even in
cases of system outages. See Chapter 6, “EIS integration using Java Message
Service” on page 121 for a detailed discussion about using JMS and Message
Orientated Middleware (MOM) in your EIS integration architecture.
Another benefit that you might want to consider when using JMS is that you can
control the time-out value between sending to your remote EIS component and
receiving a response. You can specify a time-out when you receive data from a
JMS response queue. You might want to consider this when integrating with a
remote or external EIS where you have potential latency in the network. Given
the context of your use case and the SLA you have with your business, using a
JMS adapter in front of your EIS component allows you to explore architecture,
design, and even different patterns for your EIS integration solution.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.