A quick overview of a large application integration project I just wrapped up where we use a service approach to integrate 50 interfaces from 23 applications. At least check out the diagrams and lessons learned at the end.

1. Application Integration
Using SOA as the Foundation
Bob Slook
bslook@gmail.com

2. SOA Based Application Integration
Project Background
• Business
– Multiple Countries
– Multiple Lines of Service
• Project Objectives
– Replacement of their current Integration Framework
– Set the foundation for a broader SOA effort
• Project Components
– 50 Interfaces
– 21 Applications
– 8 Operating Systems
Future Plans
• Expose Interfaces as Business Services
• Build Additional Services off of the Foundation
• Build a BPM layer to Integrated Applications in Real Time
2
bslook@gmail.com

3. SOA Based Application Integration
Project Scope
Provider Transformation Consumer
(Source Application) Engine (Target Application)
Existing File File Existing
Source Target
Drop off Pick up
Appl. Processes Processes
Appl.
DB DB
3
bslook@gmail.com

4. SOA Based Application Integration
Key Characteristics
• Hub and Spoke Pattern
– Central Transformation
– Distributed Web Service for Integration with the Applications
• Three Service Models Implemented
– File base
– Queue based
– Database based
• Metadata Driven Interface Processes
– Logical Interface Definitions
– Implementation Model Attributes
• Centrally Monitored and Managed
– Central Event Scheduler
– Central Monitoring
– Central Error Reporting
4
bslook@gmail.com

5. SOA Based Application Integration
Major Architectural Components
Oracle 10g RAC
Business Process Modeling
Tomcat and Business Activity
Monitoring Scheduling
Tidal Monitoring Tidal Tidal
Java 1.5 Software Intersperse
Software Data
Job Intersperse Monitoring
Scheduler
Monitoring Console
BEA WebLogic Integrator
9.2 WLI
Process Runtime
Legacy Definitions
Applications
Interface
BEA AquaLogic Service Bus
Web
2.6
Services BEA
WebLogic
Monitoring
BEA WebLogic Application Server Console
9.2
Legacy
Applications
Infrastructure
New
Functionality
5
bslook@gmail.com

6. SOA Based Application Integration
Architecture
Process Client
User Client User Client
Scheduler Scheduler (batch)
Role: Control
System
(Event Initiation Centrally as in a Batch Type Interface)
Administra-
tion and
Monitoring Service Proxy BPM Layer
Service Bus
Policy Application AquaLogics Service Bus
Life Cycle Management Service Routing
Monitoring
Dashboards Role: Coordination
(Event Initiation by the provider
as in a Reat Time Interface)
Tidal Console
Edge Events Business Process
WLI Console Metadata
Apache/Tomcat Integrator Hub Apache/Tomcat
ALSB Console
MSG Business Process Flow MSG
Existing Façade Business Process Flow Façade Existing
Source Drop off File Interface Interface File Pick up Target
Appl. Processes WS WS Processes Appl.
Business Process Flow
DB Business Process Flow Business Process Flow DB
Business Process Flow
Provider Transformation Engine Consumer
(Source Application) (Target Application)
6
bslook@gmail.com

7. SOA Based Application Integration
Technical Infrastructure
7
bslook@gmail.com

8. SOA Based Application Integration
Application Monitoring
8
bslook@gmail.com

9. SOA Based Application Integration
Lessons Learned
• Change Requires Focus on the Future not Existing Conventions
– A clear vision of the future state is required
– Endpoint application changes are required
• Distributed Architectures Are Complicated
– Consider all the things that can go wrong
– Don’t under estimate the need for monitoring
– Design in security
– Comprehensive governance is essential
• Products Are Immature
– Experience and commitment is essential
– Budget for a vendor coordinator
– Design a bug tracking and patch management plan
• Java Implementations Are Not All The Same
– Test, test and test some more
– Test again
9
bslook@gmail.com