Professional Documents
Culture Documents
Business Integration Platforms: by Bernardo Diaz
Business Integration Platforms: by Bernardo Diaz
By Bernardo Diaz
berdiaz@yahoo.com
Enterprise Solutions
1. Introduction
2. Key Concepts
3. Level 1: EAI
4. Level 2: Web Services Bus
5. Level 3: Automated SOA
6. JBI Integration
1. Introduction
Invoice Financial
Marketing
Mgmt Services
Strategic Physical
Production
Mgmt Resources
2. Key Concepts
a. Why to Integrate? Solution…
1. To consolidate data into 1. Integrate all the resources
strategic information inside of the organization
2. To increase the ROI of Legacy
Systems 2. Integrate with related
3. To adapt the business organizations
processes of the company to
the dynamic market demands 3. Automate process definitions
4. To offer strategic services to and external interactions with
customers, partners and other companies
providers
5. To achieve process
automation
6. To improve decision making
2. Key Concepts
b. Basic Integration Elements 1. Business Entities
Request 3. Services
Mssg S S S S S S S S S
4. Messages
F ro n t - C u s to m e rs R e q u e s ts Involved Subsystems:
Front
MDB EJB
C o la E n t r a d a Facade
A d a p ta tio n La y e r FilterManager
C o la S a lid a Mediator
MQ Server
Proxy
Capa de Adaptación
ServiceManager WorkFlowManager
S e rvic e M a n a g e m e n t La y e r
ServiceFactory
TransactionExecuter
S e r v ic e K
S e r v ic e 1 S e rv ic e 2
S e rvic e s La y e r
Capa de Servicios
B IT E C
R M C A
R e v C h a in
Level 1: EAI
c. PRODUCT FEATURES.
5. Predefined Connectors:
J2EE – HTTP, EJB, JMS
SAP – BAPIS
Daleen Technologies
SQL – Custom Queries, Stored Procedures
Level 1: EAI
c. PRODUCT FEATURES.
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
Level 1: EAI
c. PRODUCT FEATURES.
14. Audit
17. Can be installed in any J2EE compliant application server and java compliant
operating system.
1. Generic WS Facades
3. Security
4. WS-C / WS-T
3. Different specification
5. WS-Policy approaches (BPM)
6. CS – WS
4. There is no a single solution
7. WS-… ETC. to every problem, new
customer needs arise
frequently
Level 2: Web Services Bus
b. Web Services = Use only established standards SOAP, WSDL, WS-I,
WS-Security
1. Enables transparent
publishing of Level1 and
Level 2 services.
3. Interoperable: If based on
the WS-I recommendation
Level 2: Web Services Bus
c. PRODUCT FEATURES.
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.
Level 3: Automated SOA
b. ARCHITECTURE.
Level 3: Automated SOA
b. ARCHITECTURE.
Level 3: Automated SOA
c. PRODUCT FEATURES. 1. The first step toward automated
governance is to define metadata in
the form of attributes and action
commands.