1. Enterprise Solutions BITEC: Business Integration Platform
Por Bernardo Díaz Arias

2. Enterprise Solutions Introduction Key Concepts Level 1: EAI
Level 2: Enterprise Service Bus
Level 3: B2B
JBI Integration

3. 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.

4. Integration Server = ESB
2. Key Concepts
a. Why to Integrate?
Solution…
Invoice
Mgmt
Human
Resources
Financial
Services
Strategic
Mgmt
Human
Resources
Physical
Resources
Integration Server = ESB
Accounting IT
Marketing
Invoice
Mgmt
Financial
Services
Marketing
Strategic
Mgmt
Production
Physical
Resources

5. 2. Key Concepts a. Why to Integrate? Solution…
Integrate all the resources inside of the organization
Integrate with related organizations
Automate process definitions and external interactions with other companies
To consolidate data into strategic information
To increase the ROI of Legacy Systems
To adapt the business processes of the company to the dynamic market demands
To offer strategic services to customers, partners and providers
To achieve process automation
To improve decision making

6. 2. Key Concepts b. Basic Integration Elements Integration Server
Business Entities
Connectors & Adapters
Services
Messages
Common Language (Messaging protocol)
Dynamic Business Rules
Integration Server
Synchronous / Asynchronous Invocation
Business
Entity 1
Business
Entity 2
Business
Entity 3
Request Mssg S S S S S S S S S
Integration Server
Common Language XML S S S S S S S S S
Response Mssg
Business
Entity 4
Business
Entity 5
Business
Entity 6

7. 2. Key Concepts
c. Integration Types
ESB = Enterprise Service Bus

8. 2. Key Concepts
c. Integration Types

9. 2. Key Concepts
d. Integration Levels

10. 2. Key Concepts d. Integration Levels
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.

11. 2. Key Concepts e. Service Types Level 1: EAI Atomic Services
Level 2: Web Services Bus
Level 3: Automated SOA
Atomic Services
Data Services
Business Services
Workflow Services
Automated Services

12. 2. Key Concepts f. 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.

13. 3. Level 1: EAI
b. ARCHITECTURE.

14. 3. Level 1: EAI
c. FEATURES.
Integrates heterogeneous Business Entities through a common data bus
It is based on the concept of services published by legacy systems
Uses custom adapters as message or communication channels
Enables either synchronous / asynchronous invocation of any published service
Uses predefined connectors:
J2EE – HTTP Servlets / Struts
J2EE – EJB session, stateless
J2EE – MDB
SAP – BAPIS
Daleen Technologies
SQL – Custom Queries
SQL – Stored Procedures

15. 3. Level 1: EAI
c. FEATURES.
Dynamic Business Rules can be applied during pre or post processing of the transaction.
Supports multiple data or message formats (transformations, mappings)
Common Language. Has an internal xml based metadata language to define Invocations, transactions, services and workflow.
Service Compositions:
1 Invocation : n-transactions
1 transaction : n-services
1 business service : n-atomic services
All the features have declarative support through xml configuration files

16. 3. Level 1: EAI
c. FEATURES.
Supports distributed transactions (XA-2PC)
Embedded compensation logic
Includes timeout and retries features
Audit
Workflow Levels:
Declarative, static
Dynamic, through metadata-policies inside the message header
Automated, through a BPM Engine

17. 3. Level 1: EAI
c. FEATURES.
Based on standard Java technologies (spec J2EE 1.3 or greater).
Can be installed in any J2EE 1.3 compliant application server and java compliant operating system.
Life cycle enabled components
Pluggable Components
Parallel Processing. Components can be pooled declaratively according to work loads.

18. 4. Level 2: Web Services Bus
a. BUSINESS CASE: A network of government agencies that share information
through public services.

19. 4. Level 2: Web Services Bus
b. ARCHITECTURE.
Generic WS Facades
Interoperability. WS-I / WSDL compliant services.
Security
Service Registry + Smart Routing = Service Broker

20. 4. Level 2: Web Services Bus
c. 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.

21. 4. Level 2: Web Services Bus
c. FEATURES.
A Service Directory can be added (published itself as a web service node) to centralize the location of each service.
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 there
must be a WS Bus performing the role of service broker.

22. 5. Level 3: Automated SOA a. FEATURES.
The first step toward automated governance is to define metadata in form of attributes and action commands.
Several management nodes could be implemented but interaction begins with distributed security policies.
Interaction could be implemented in a dynamic fashion among nodes, based on conversational support.
MetaServices: A Web Service Integration Network seems as a federated topology due to the fact that management is encapsulated as Metadata Web Services.
Full automation can be achieved by including a BPEL Engine.

23. 5. Level 3: Automated SOA
b. ARCHITECTURE.

24. 5. Nivel3: SOA Y B2B WSIF WS - Security BPEL4WS / WS-BPEL WS-C / WS-T
d. UNESTABLISHED TRENDS.
Lack of consensus and standardization
Parallel specification efforts toward the same objectives
Different specification approaches (Super protocol vs. Stack of granular sub protocols)
There is no a single solution to every problem, new customer needs arise frequently
WSIF
WS - Security
BPEL4WS / WS-BPEL
WS-C / WS-T
WS-Policy
CS – WS
WS-… ETC.

25. 6. JBI – JSR 208 Existing SOA solutions should be JBI compliant
The JBI Container could be extended by adding the new WS-X protocols.
Interoperability reaches a new meaning: “Integrating the integration”.

26. And Finally…
Thank you for your time !!!