Date post: | 23-Dec-2015 |
Category: |
Documents |
Upload: | jordan-dean |
View: | 216 times |
Download: | 1 times |
Enterprise Solutions
1. Introduction 2. Key Concepts
3. Level 1: EAI4. Level 2: Enterprise Service Bus5. Level 3: B2B
6. JBI Integration
1. Introduction
This material is not intended to show standard business integration concepts or terminology but the result of our expertise achieved through the years.
2. Key Concepts
InvoiceMgmt
Human Resources
Financial Services
Accounting IT Marketing
ProductionPhysical
ResourcesStrategic
Mgmt
StrategicMgmt
Invoice Mgmt
Human Resources
Financial Services
Marketing
PhysicalResources
Integration Server = ESB
Solution…a. Why to Integrate?
2. Key Concepts
a. Why to Integrate? Solution…
1. To consolidate data into strategic information
2. To increase the ROI of Legacy Systems
3. To adapt the business processes of the company to the dynamic market demands
4. To offer strategic services to customers, partners and providers
5. To achieve process automation
6. To improve decision making
1. Integrate all the resources inside of the organization
2. Integrate with related organizations
3. Automate process definitions and external interactions with other companies
2. Key Concepts
b. Basic Integration Elements
Business Entity 1
Integration Server
Business Entity 2
Business Entity 3
Business Entity 4
Business Entity 5
Business Entity 6
Common Language XML
S S S S S S S S S
S S S S S S S S S
Request Mssg
Response Mssg
1. Business Entities
2. Connectors & Adapters
3. Services
4. Messages
5. Common Language (Messaging protocol)
6. Dynamic Business Rules
7. Integration Server
8. Synchronous / Asynchronous Invocation
2. Key Concepts
Level 1. Enterprise Application Integration. Integration of legacy systems inside the organization (Backend Integration). EAI = Basic ESB
Level 2. Public level Integration (front-end integration), Integration among organizations (B2B). At this level the ESB must be WS enabled.
Level 3. Automated Integration. Implies the use of meta-services based on management policies to define security, versioning, dynamic routing and conversational support. By adding a Business Process Management Engine and repository, full governance can be accomplished.
d. Integration Levels
2. Key Concepts
1. Level 1: EAI
2. Level 2: Web Services Bus
3. Level 3: Automated SOA
e. Service Types
1. Atomic Services2. Data Services
3. Business Services
4. Workflow Services5. Automated Services
2. Key Conceptsf. Business Process Management
Could be implemented at any level (1, 3), inside the organization or among organizations.
It is suited exclusively for long running transactions that span asynchronous services.
Complex decision making rules determine the routing between activities (services).
Unfortunately there is lack of consensus and standardization among proposals (XPDL, BPEL, BPML).
The use of WS technologies enables to encapsulate any Workflow engine implementation as another Web Service.
b. ARCHITECTURE.
3. Level 1: EAI
B IT E C
Adapta ti on Laye r
Se rvi ce M anagement Laye r
Se rvi ces Laye r
MQ Server
Capa de Servicios
Capa de Adaptación
MDB EJBFacade
Mediator
Proxy
Capa de Administración de Servicios
ServiceManager
S e rv ice 1S e rv ice K
R e vC h a inRMCA
S e rv ice 2
Esquema Asíncrono Esquema Síncrono
WorkFlowManager
C o la En tra d a
C o la Sa lid a
TransactionExecuterServiceFactory
FilterManager
Front
3. Level 1: EAIc. FEATURES.
1. Integrates heterogeneous Business Entities through a common data bus
2. It is based on the concept of services published by legacy systems
3. Uses custom adapters as message or communication channels
4. Enables either synchronous / asynchronous invocation of any published service
5. Uses predefined connectors: J2EE – HTTP Servlets / Struts J2EE – EJB session, stateless J2EE – MDB SAP – BAPIS Daleen Technologies SQL – Custom Queries SQL – Stored Procedures
3. Level 1: EAIc. FEATURES.
6. Dynamic Business Rules can be applied during pre or post processing of the transaction.
7. Supports multiple data or message formats (transformations, mappings)
8. Common Language. Has an internal xml based metadata language to define Invocations, transactions, services and workflow.
9. Service Compositions:
1 Invocation : n-transactions 1 transaction : n-services 1 business service : n-atomic services
10. All the features have declarative support through xml configuration files
3. Level 1: EAIc. FEATURES.
11. Supports distributed transactions (XA-2PC)
12. Embedded compensation logic
13. Includes timeout and retries features
14. Audit
15. Workflow Levels: Declarative, static Dynamic, through metadata-policies inside the message header Automated, through a BPM Engine
3. Level 1: EAIc. FEATURES.
16. Based on standard Java technologies (spec J2EE 1.3 or greater).
17. Can be installed in any J2EE 1.3 compliant application server and java compliant operating system.
18. Life cycle enabled components
19. Pluggable Components
20. Parallel Processing. Components can be pooled declaratively according to work loads.
4. Level 2: Web Services Busa. BUSINESS CASE: A network of government agencies that share informationthrough public services.
4. Level 2: Web Services Busb. ARCHITECTURE.
1. Generic WS Facades
2. Interoperability. WS-I / WSDL compliant services.
3. Security
4. Service Registry + Smart Routing = Service Broker
4. Level 2: Web Services Busc. FEATURES.
An EAI Bus can be transformed into a Web Service Bus:
By adding a WS-I compliant channel without modifying existing services.
Every organization should publish a subset of previously integrated services of interest
At this level, security must be implemented to guarantee authentication, authorization and data protection. Lack of standardization forces to implement custom solutions based on header metadata, encryption and digital signatures.
4. Level 2: Web Services Busc. FEATURES.
4. A Service Directory can be added (published itself as a web service node) to centralize the location of each service.
5. By using the capabilities of WSDL and the Apache/Jakarta framework WSIF, the service directory can be evolved into a Service Broker, by adding smart routing capabilities.
Finally inside each org there must be an EAI Bus and in the WS Network theremust be a WS Bus performing the role of service broker.
5. Level 3: Automated SOA1. The first step toward automated
governance is to define metadata in form of attributes and action commands.
2. Several management nodes could be implemented but interaction begins with distributed security policies.
3. Interaction could be implemented in a dynamic fashion among nodes, based on conversational support.
4. MetaServices: A Web Service Integration Network seems as a federated topology due to the fact that management is encapsulated as Metadata Web Services.
5. Full automation can be achieved by including a BPEL Engine.
a. FEATURES.
5. Nivel3: SOA Y B2B
1. WSIF
2. WS - Security3. BPEL4WS / WS-BPEL4. WS-C / WS-T5. WS-Policy 6. CS – WS
7. WS-… ETC.
d. UNESTABLISHED TRENDS.1. Lack of consensus and
standardization
2. Parallel specification efforts toward the same objectives
3. Different specification approaches (Super protocol vs. Stack of granular sub protocols)
4. There is no a single solution to every problem, new customer needs arise frequently
6. JBI – JSR 208
1. Existing SOA solutions should be JBI compliant
2. The JBI Container could be extended by adding the new WS-X protocols.
3. Interoperability reaches a new meaning: “Integrating the integration”.