copyright © 2007 – the openeai software foundation integrating enterprises with openeai...
TRANSCRIPT
Copyright © 2007 – The OpenEAI Software Foundation
Integrating Enterprises with OpenEAI Frameworks for SOA
Tom Cervenka ([email protected])Tod Jackson ([email protected])Steve Wheat ([email protected])
SOA for Your Enterprise and Beyond
[email protected] Copyright © 2007 – The OpenEAI Software Foundation
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the slides entitled "GNU Free Documentation License“.
Copyright © 2007 – The OpenEAI Software Foundation
Who we are
• Tom CervenkaUniversity of Illinois / OpenEAI SF
• Tod JacksonUniversity of Illinois / OpenEAI SF / Open Integration Incorporated
• Steve WheatUniversity of Illinois / OpenEAI SF / Open Integration Incorporated
Copyright © 2007 – The OpenEAI Software Foundation
What is OpenEAI?
The OpenEAI Project endeavors to discover and document the controlling dynamics, principles, and practices of enterprise application integration and service oriented architectures and to present, implement, and promote those findings. The OpenEAI Project presents findings in the form of the OpenEAI methodology and OpenEAI software for implementing integrations.
Copyright © 2007 – The OpenEAI Software Foundation
What we will cover
• Demonstrate the OpenEAI sample enterprise with example integrations and services representative of sites using OpenEAI
• What is OpenEAI?
• Impetus for OpenEAI
• How the OpenEAI project was initiated
• Some benefits of using OpenEAI today
• Some long-term and potential benefits of using OpenEAI and participating in the project
• Commercial implementations of OpenEAI integrations and services
Copyright © 2007 – The OpenEAI Software Foundation
OpenEAI Sample Enterprise OverviewJune, 2007
ENTERPRISE MESSAGE BROKER
Any ERP
Any ERPGateway
Any ERP Details Page
uPortal
uPortal Gateway
Password Synchronization
Service
Password Synchronization
Gateway
CAS
Any ERPGateway
CAS Details Page
Directory Service
Directory Service
Gateway
Directory Service Details PageSakai
Sakai Gateway
Sakai Details Page
Self Service Application
Any ERPGateway
Self Service Application
Details Page
Queue(s) Topic(s)
uPortal Details Page
Password Synchronization Service Details
Page
Self Service Portlet
Any ERPGateway
Warehouse
Warehouse Gateway
Self Service Portlet Page
Warehouse Details Page
REQUEST PROXY | SYNC ROUTER | LOGGING SERVICE
Address Validation Service
Address Validation Gateway
HOSTEDON-DEMAND
SERVICES
Address Validation
Details Page
HODSOverview
Password Validation Service
Password Validation Gateway
Password Validation
Details Page
Copyright © 2007 – The OpenEAI Software Foundation
Hosted On-Demand ServicesOverviewDecember, 2006
ENTERPRISE MESSAGE BROKER
Queue(s) Topic(s)
REQUEST PROXY | SYNC ROUTER | LOGGING SERVICE
Address Validation
Address Validation Gateway
Any OpenEAI Enterprise
Back to Main
Hosted On-Demand Address
Validation Details Page
Validation Data Subscription Service(eg state and postal codes)
Hosted Student Information SystemMaximus SchoolMax
ApplyYourself
Open Integration
Incorporated
Hosted Admissions Application System
Copyright © 2007 – The OpenEAI Software Foundation
What is OpenEAI?
• A methodology for analyzing and defining integrations and enterprise services
• A integration message protocol using XML format that provides the specification for enterprise messages as well as the expected, general behavior for applications that process these messages.
• A suite of standards-based foundational APIs that provide the building blocks for integrations, service implementations and general application development
• An open source project with six departments that focus on documenting OpenEAI technology and concept as well as providing example implementations and production-quality reference implementations
Copyright © 2007 – The OpenEAI Software Foundation
What OpenEAI is NOT• A set of standard message or service definitions
(standards bodies like PESC, IMS, SIF, and others do that work, OpenEAI uses and interfaces with these standards and provides a strategy for implementing any integration where standards do not exist)
• Packaged integrations and services
(the project produces foundation components and reference implementations, and there are many open source, free, proprietary and commercial integration and service implementations using OpenEAI)
Copyright © 2007 – The OpenEAI Software Foundation
OpenEAI Departments
1. Methodology
2. Message Object API
3. Application Foundation APIs
4. Message Definitions
5. Reference Implementations
6. Deployment and Administration
Copyright © 2007 – The OpenEAI Software Foundation
How OpenEAI came to be1. Organizational nature of the University of Illinois
• Large, decentralized organization with three campuses; 66,000 students; 20,000 employees; 964 departments; annual operating budget of $3.5 billion
• Four different departments dedicated solely to IT at the campus and University administration levels and hundreds of active IT groups in the University departments
• Many heterogeneous platforms• Many disparate systems: approximately 130 enterprise-
wide systems; hundreds of campus-specific academic and administrative systems; thousands of academic and administrative systems in University departments
• Business process improvement and cost/risk avoidance• ERP implementation provided an opportunity to rebuild
technology and integration infrastructure• Emphasized dramatic nature of shift from proprietary point-
to-point interfaces to standards-based messaging
Copyright © 2007 – The OpenEAI Software Foundation
2. Why did we build our own?
• Cost savings vs. proprietary approach• Proprietary everything! Terminology, tools
languages…• Much of the same work had to be done even with a
proprietary solution. • UI is a large organization and we couldn’t ask all our
departments to purchase a very expensive license and maintain a very complex integration broker themselves
• Intellectual savings. By developing software and methodologies based on standards, we’re allowing our staff to concentrate on a set of core concepts supported by more than just one company.
How OpenEAI came to be
Copyright © 2007 – The OpenEAI Software Foundation
3. Why and how did it turn into an Open Source initiative?
• After discussing what we had done with our business partners and other interested parties, they expressed interest in using it. An Open Source initiative was the logical way to make this happen
• By making it available to the world, we’re able to leverage input from people way smarter than we are and continuously make OpenEAI better than it is today
• Negotiated an agreement with University of Illinois that led to the intellectual property being gifted to the OpenEAI Software Foundation. This provides the structure to maintain and support the body of work and makes it possible to grow these concepts and technologies even more as time goes by and more people use them
How OpenEAI came to be
Copyright © 2007 – The OpenEAI Software Foundation
• University of Illinois
• SunGard HE and their clients
• Open Integration Incorporated
• MAXIMUS
• Los Angeles Unified School District
• Prince George’s County Public Schools
Implementation Highlights
Copyright © 2007 – The OpenEAI Software Foundation
• 100+ applications integrated using OpenEAI
• New Java applications, legacy mainframe applications, PowerBuilder client/server applications, ColdFusion applications, PERL applications, .Net applications
• Every Java application is OpenEAI based for uniform development, configuration and deployment (using the OpenEAI application configuration foundation and patterns for application development)
• Higher-level enterprise foundation built on OpenEAI (authentication, authorization, session management and directory services)
University of Illinois
Copyright © 2007 – The OpenEAI Software Foundation
• SunGard Banner Gateway
• The Luminis Data Integration for e-Procurement (local SCT Banner Finance with central SciQuest HigherMarkets)
SunGard Higher Education
Copyright © 2007 – The OpenEAI Software Foundation
• OpenII Toolkit Enterprise Service Bus
• Core Services
• General File Connector
• General RDBMS Connector
• ESB Reports
• Numerous connectors both application and site specific
Open Integration Incorporated
Copyright © 2007 – The OpenEAI Software Foundation
• ConnectMAXTM Enterprise Service Bus
• SchoolMAXTM Connector
• Welligent Connector
• Many other application and site specific connectors
MAXIMUS
Copyright © 2007 – The OpenEAI Software Foundation
• Implemented the ConnectMAXTM ESB
• Implementing the Welligent and SchoolMAXTM Connectors
• Developed a connector for their standardized student information system
• Developed connectors for legacy file-based integrations to keep legacy systems up-to-date with the new student information system
Los Angeles Unified School District
Copyright © 2007 – The OpenEAI Software Foundation
• Implemented the ConnectMAXTM ESB
• Deployed the SchoolMAXTM Connector
• Implementing the Active Directory Connector, Oracle ERP Connector to orchestrate account provisioning and maintenance for employees and students
• Implementing a custom connector for their legacy IBM AS/400 SIS to keep it in sync with their new SchoolMAXTM SIS for a period of time
• Planning connectors for lunch and transportation systems
• Analysis on Address Management and Enrollment Validation Services
Prince George’s County Public Schools
Copyright © 2007 – The OpenEAI Software Foundation
Commercially Available ConnectorsGeneral RDBMS Connector
General File ConnectorPassword Validation Service
Password Synchronization ServiceActive Directory Connector
SunGard HE Banner SciQuest e-ProcurementSchoolMAX Connector
Address Validation ServiceOracle ERP Connector
Welligent ConnectorAnd more…
Copyright © 2007 – The OpenEAI Software Foundation
Site Specific ConnectorsEnterprise Application Service
ApplyYourself!Mediease
uPortalSakai
Decision SupportDirectory Service
Institutional Identity ServiceNessie
Legacy Payroll SystemsLegacy Student System
Legacy HR SystemsAnd more…
Copyright © 2007 – The OpenEAI Software Foundation
Benefits of OpenEAI1. Methodology
• Provides an analysis template and analysis process for analyzing and documenting the requirements of integrations, defining enterprise data objects, and specifying enterprise messages without requiring or referencing specific products
• The analysis process ties directly into the implementation process; in other words, the XML and other artifacts produced by following the methodology are actually used to generate and write code that implements integrations and documents their finished state.
NOTE: See the OpenEAI Methodology Document
Copyright © 2007 – The OpenEAI Software Foundation
2. Protocol• Provides a detailed structure for messages in XML format• Defines the message actions that can be performed on
enterprise data objects through messaging• Prescribes general behavior that applications must adhere
to for each message action in order to build reliable integrations and maintain enterprise data integrity
• Provides the format for specifying and talking about enterprise data objects, which are contained within the messages
NOTE: See the OpenEAI Protocol Document
Benefits of OpenEAI
Copyright © 2007 – The OpenEAI Software Foundation
3. Foundational APIs• Provides the set of tools that can be used to implement
defined integrations consistently and reliably
• Not required, but makes much of what has to be implemented much easier
• Key foundation components:
- Gateway pattern- Application foundation- Message objects- JMS foundation objects
Benefits of OpenEAI
NOTE: See the API Introduction and Implementation Strategies documents
Copyright © 2007 – The OpenEAI Software Foundation
OpenEAI Sample Enterprise (1)• Purpose
– To provide an area where we can test changes to core foundation
– To provide an area where we can demonstrate the incorporation of OpenEAI components and strategies with other areas of development and technologies
– To provide a downloadable archive that anyone can download and use to learn more about OpenEAI, with hands-on examples and artifacts that allow people to make changes and see their implications in a “real” enterprise
Copyright © 2007 – The OpenEAI Software Foundation
OpenEAI Sample Enterprise (2)• History
– Initially released in March of 2003
– Included the following components• Request Proxy Service reference implementation
• Sync Router Service reference implementation
• Message Logging Service reference implementation
• Example ERP gateway
• Enterprise Warehouse example gateway
• Self Service Application example (Swing)
Copyright © 2007 – The OpenEAI Software Foundation
OpenEAI Sample Enterprise (3)• Current
– Release July 2007
– Included the following enhancements• Example uPortal, Sakai, and CAS gateways• Self Service Portlet example (uPortal)• Address Validation Service (local and
remote)• Institutional Identity Service
Copyright © 2007 – The OpenEAI Software Foundation
Further Demonstration
(Password Validation Service / ESB Console)