Deploying SOA using IBM s Enterprise Integration Messaging Specification (EIMS)

Transcription

1 E-Business On Demand Deploying SOA using IBM s Enterprise Integration Messaging Specification () Architecture and Development Process November, 2005 Copyright

2 Agenda Why deploy a Service Oriented Architecture (SOA)? Why are messaging standards important? What Exactly is? Getting There The Development Process Projects and Lessons Learned 2 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

3 e-business On Demand An enterprise whose business processes integrated end-to-end across the company and with key partners, suppliers and customers can respond with speed to any customer demand, market opportunity or external threat. Sam Palmisano IBM Chief Executive Officer People Process Information 3 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

4 Why SOA? Companies are unable to keep pace with market demand for new business capabilities. Processes are not dynamically adaptable. Architecture is a choke point for business innovation. Monolithic processes and applications can t be reassembled or reused. Ad hoc integration connections are difficult to change and maintain. Lack of standards limits meaningful interoperability. Rigidity of architecture makes small improvements impossible to cost justify. Extracted and transformed segments of legacy/packaged applications SOA is transforming IBM to enable faster solution development and on demand adaptability. Business Units are able to create new services quickly, and to incrementally transform legacy and packaged application functions into Services. Assets (including messaging data) is architected for reuse to support the deployment of service based applications across the enterprise. Compose Modular Process IT Component Web Services IT Component Deploy Workflow IBM On Demand Development Environment Tool Suite (Rational & Websphere) Business analysts compose Plug & Play modular business processes, with pre-associated SOA components, to rapidly implement business rule driven, easily adaptable, operational workflows. 4 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

5 What are the Architectural Objectives of the SOA Messaging Architecture? Loose coupling - Service application interfaces are specified and managed in a manner that will allow service functions to be loosely coupled, location transparent and protocol independent; Application Re-engineering - Will support the evolution of IBM s internal application landscape from one that encompasses a large number of proprietary solutions (4800+), to a more flexible and resilient architecture, with significantly less redundancy; Common business data representation - Existing applications/components can be leveraged to provide their services using a common business data representation. Existing functions can be represented using common data vocabularies, so that the services provided by these functions can be available to the enterprise in a consistent way, regardless of its proprietary interface; Integration simplification - SOA applications are integrated at the service specification point, not at the application interface. This allows application complexities to be isolated from the services interface, and minimizes the impacts of back-end interface and application changes; Responsive to change - Provides an environment whereby business services workflow and business process re-orchestration can be accomplished easily, without the need to go through costly and time consuming software development cycles; 5 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

6 SOA & Concepts.. SOA is more than a technology. It is a management and design philosophy that can be used to bridge the divide that often exists between Business Owners and Technology Developers. - Application integrators will re-engineer the Enterprise by designing application interfaces that provide standardized and re-usable Services, rather than application specific interfaces. - Business Process Owners will define and orchestrate granular Service Components for their Business Domains that can be used to optimize their businesses. The Enterprise Integration Messaging Specification (): OAGIS based integration architecture that has been extended to meet internal application-to-application integration and SOA requirements. An effective SOA messaging architecture will utilize re-usable and standardized message structures and data vocabularies. SOA solutions are typically defined using UML. SOA message payloads are defined using processes. The development process defines tools, governance and design and techniques that facilitate rapid solution development. It is fairly simple to generate web services using programming tools without being concerned about data. However, this approach makes it difficult to re-use common data structures and vocabularies across the enterprise. 6 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

7 End State Vision TRADING PARTNERS IBM Customers Trading Partner External Protocols Ariba Internet Edge Of Enterprise Internal Message Hubs Internal Applications Products & Solutions: Distributors CommerceOne SAP RosettaNet Fulfillment.. Manufacturing Personal Computers Servers Software Manufacturers Oracle Web Browser EDI Web Services (A2A).. Services Storage Services Service based messaging (using ) enables internal and B2B solutions 7 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

8 Why are messaging standards important? Problems: Many legacy applications use proprietary interface data definitions. Why is this a problem? - Application Integration is very expensive Each new interface is a custom solution. - Infrastructures are costly Many point-to-point interfaces exist between IBM s applications. - Business Processes are difficult to modify Every process change requires interface customization. - Application services are difficult to re-use Messages are defined using application specific data semantics. Solution: Develop an enterprise messaging architecture and standardized message vocabulary that can be used across the corporation for application integration, and deployment of IBM s Service Oriented Architecture (SOA). 8 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

9 Benefits of SOA and a Common Messaging Specification The Big Picture Legacy: Many Point-to-Point Interfaces (Required when Interface Data is unique) Service Oriented Topology (Common vocabularies + Reusable Services) A E A E B F B F 2 Common Messages C G C G D H 2*N(N-1) Message Interfaces D 2*N Message Interfaces H Point-to-Point Architecture: Potentially, 56 Unique Messages (112 Message Interfaces/Implementations) Vocabulary Adapters SOA and Common Messaging Specification: 2 Reusable Messages (16 Message Interfaces/Implementations) 9 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

10 Typical B2B Examples Web Interfaces: esites Partners Public Multiple Trading partners, Multiple formats: Ariba/cXML Rosetta Net SAP OAGi C1/xCBL Custom XML Web Services EDI Application(s) that map to/from the Application(s) that map to/from the Create/Extract System Create/Extract System ORDER -BOD ( PBI and variants) Create/Extract System Application(s) that map to/from the IBM s Back End Systems -BOD Canonical Business Messaging Object (Generic Business Object in WBI-ICS) 10 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

11 Supports the Deployment of the WebSphere Business Integration Reference Architecture Model, Design, Development Development, Tools, Services Test Tools Common Runtime Infrastructure Messages Support BPEL Orchestration IT Monitoring Monitoring Services Process Monitoring User Interaction Services Application Services Information Services Process Services Community Integration Services Delivery Services J2EE Extensions Federation Services Choreography Svcs Community Mgmt Experience Services Resource Services J2EE Container Svcs J2EE Base Services Replication Services Transformation Svcs Search Services Business Trans Svcs Process State Mgmt Staff Services Document Mgmt Protocol Services Event Services Enterprise Service Bus Transport Services Mediation Services Data Dictionary Is used for Message Transformation Application Access Services Event Detection Services On-ramp Services Enterprise Applications Data Access Services On-ramp Services Enterprise Data Data vocabulary is used for ESB Mediation 11 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

12 Enterprise Integration Messaging Specification in a Nutshell Architecture The Enterprise Integration Messaging Specification () is the message payload used for A2A within IBM. It expands OAGIS R8 (Open Applications Group Integration Specification) and possesses the following characteristics: Standardized Messaging Interaction Definition Best suited for Enterprise Web Services Standardized Messaging Structure facilitates re-use Guiding Principles and Methodology Canonical Model and Precise Business Interaction (PBI) schemas for transactions Common Building Blocks and Corporate Assets Development Process: Tools, Work Products, Deliverables and Work Flow Governance and Related Standards Development Process Business Transformation Management System (BTMS) Web Standards and Guidelines XML Namespace Standards 12 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

13 What Exactly Is? -BOD IBM Extensions I-N I-V OAGIS V8+ Component Library A library of additions and extensions to the OAGIS V8 specification: Schema components, elements, attributes and enumerations created for IBM s reuse Business objects, actions and messaging objects that meet IBM s business requirements Assembled into Business Object Documents (-BOD) that include business interaction design patterns actions to provide complete interactions (sometimes referred to as BODs in OAGIS) A set of tools and processes that enable the development, use and management of messages Process and tools to create, manage and store and use -BODs and their components 13 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

14 What Exactly Does Provide? A single set of domain based Business Object Documents and message transaction design patterns that supports IBM internal business messaging Provides business vocabulary stability throughout the enterprise Provides a set of standardized message transaction design patterns Similar approach used by industry groups (Automotive, Aerospace, Investing, Real estate ) A single interface development methodology Eases specification of requirements (standard data requirements) Iterative approach speeds development process (enabling automation of interface creation) Reduces specification, design, development & testing reducing project timelines A known form that can be transformed in a predictable way Enables vocabulary & framework specific transforms Empowers applications to control their responsiveness An architecture that ties together business processes, applications and data Service Oriented Architecture (SOA) services enabled using reusable message constructs Business domain vocabularies (data) become the basis for an enterprise data dictionary A focal point to identify common enterprise data requirements 14 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

15 The SOA Rapid Development Process Business Transformation Activities Initiative Definition Project Nominated Evaluate/ Accept/Reject Business Objectives Sponsorship Leadership Concept Project Scope & Requirements Architecture Topology Current State > To Be State Business Scenarios Plan Business Process Modeling BOD Message Design Dictionary Design Test Case Development Develop Detailed Design Domain Test Qualify SIT & Customer Acceptance Test Development Phase Checkpoint ECBA Architecture Review Checkpoint Deploy Deployment Service Registration Deliverables (in yellow) Project Definition Scope & Requirements Interface Context Diagrams Interfacing App. Data Structures Sequence Diagrams APD Arch. Proposal Doc. Data Analysis/ Mappings Draft Schemas ADD Arch. Definition Doc. Final Test Cases/Examples Refined Schemas Message Bindings & Definitions Message schemas with Fixes Deployment Code & schemas UDDI, XSR Artifacts Roles and Responsibilities Service Domain Architect Domain Modeling, UML, Define Message Scenarios & Data Requirements Schema Designer - Designs Transaction Schema (PBI s) CIO Architecture Team Manage/Develop Corporate Canonical Data Models and Development Process Tools: Rational, Websphere, Word, Spreadsheets (for mapping), XMLSPY, EDIFIX, CVS UDDI, XSR 15 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

16 supports the IBM Service-Oriented Development Methodology Monitor & Optimize Business Analysts Operatio nal Model Information Model Entities Messages Service Developer (Canonical and Transaction Business Objects) Process Assembler Integration Specialist Business Operations Enterprise Solution Flow Composition 16 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

17 Customer Management Activity Diagram Purchase Place Sales Supplier Receive Receive Status Change Purchase Status Purchase Sales Status Acknowledge Status Accepted/Rejected Sales Receive Sales/ Status Receive Status Purchase Status Status Sales Status Confirm Change Accepted/Rejected Sales/ Status Fulfillment Cancel Purchase Sales Receive Receive Status Purchase Status Sales Status Confirm Cancel Status Accepted/Rejected Receive Ship Notice Receive Purchase Ship Notice Purchase Status Sales Ship Notice Sales Ship (unless Cancelled) Send 17 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

18 How the Architecture supports SOA and Web Services using Message Design Patterns SOA Component (Information System) Callable Service Service Operation Request/Response Pair Request/Response Data Web Services (optional) service porttype/binding operation input/output message/types Usage of verb, and the values of its attributes (confirm and acknowledge) Business Object Document (BOD) Architecture Service Operation and Example Retrieve Retrieve Show Show Create CreateServiceRequest Change ChangePurchase Process ProcessPurchase Cancel CancelPurchase Validate Synchronize Description Used to retrieve information from an application/service (request-response model). Used to display information. Also used for pubsub subscriptions (push model) Used to start a process, resulting in the creation of an object in an application/service. Used to change an object in an application. Used to initiate Process rules for an existing object. Used to cancel a business operation Used to initiate a validation process. Used to synchronize information between application data stores. Message Interaction Design Pattern Initiator: Get Responder: Show Initiator: Show Responder (optional): Confirm Initiator: CreateServiceRequest Responder: ConfirmServicerequest Initiator: ChangePurchase Responder: ConfirmPurchase Initiator: ProcessPurchase Responder: AcknowledgePurchase Initiator: CancelPurchase Responder: ConfirmPurchase Initiator: ProcessConfigurationValidation Responder: AcknowledgeConfigurationValidation Initiator: SyncCustomerParty Responder: ConfirmCustomerParty 18 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

19 Canonical Model Building Blocks BOD s Development Bill of Materials Bill of Materials Bill of Materials Get Bill of Materials Process Update ElectronicCatalog ElectronicCatalog ElectronicCatalog Show List Electronic Catalog Add Bill of Materials Bill of Materials Bill Document of Materials Reference Parties Payments ElectronicCatalog ElectronicCatalog ElectronicCatalog Tax Header Line/Sub-Line Nouns Contextual Components Data Components 19 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

20 IMS Constructs - Layered/Modular Components Bill of Materials Bill of Materials Bill of Materials Get Bill of Materials Show Update ElectronicCatalog ElectronicCatalog ElectronicCatalog Show List Electronic Catalog Add -BOD Canonical Business Messaging Objects 20 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

21 Constructs Reusable Components Bill of Materials Bill of Materials Bill of Materials Bill of Materials IMS ElectronicCatalog ElectronicCatalog ElectronicCatalog Electronic Catalog Bill of Materials Bill of Materials Bill of Document Materials Reference Parties Payments ElectronicCatalog ElectronicCatalog ElectronicCatalog Tax Header Line/Sub-Line Canonical Business Components 21 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

22 Constructs Contextual Components/Types Bill of Materials Bill of Materials Bill of Document Materials Reference Parties Payments ElectronicCatalog ElectronicCatalog ElectronicCatalog Tax Header Line/Sub-Line Canonical Business Components Contextual Components 22 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

23 Constructs Data Components + Elements Data Components Canonical Business Elements 23 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

24 Example Use of Services in the Same Business Domain Characteristics Requirements are gathered over time. Messages are different (e.g., Japan and ASEAN s are 60% the same) Services are loosely managed, organization-wise. Benefits: Converge to a common structure ( Canonical Schema) simplifies implementation Rapid Interface and message design Examples SAP IDOC E2open, TxHub IGF ESI &GeoHu b FF TxHub e2open RN Business Partners Online (IOL) Japan TDAccess (Gateway) IOL (Direct Insite) Asean Global Image Load (GIL) and Global Contract Preparation System (GCPS) s GCPS GIL Electronic or Paper External Vendors 24 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

25 Global Message Customers and Distributors Using a Browser Customers and Distributors Using B2B Internet On Line (IOL) B2B Gateway Global Message 5 Internal systems now send out invoices in the same format In the future it will be very easy for any of the internal systems to send to both IOL and B2B 25 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

26 Community Governance Process - is a community based development program, (i.e., based on open source architecture development principles), using common architecture principles. - business data vocabularies will be governed/developed by business domain architects based on the process models required for their domains. - As evolves it will contain common, re-usable, business domain based messaging vocabularies required to meet the needs of the IBM enterprise. 26 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

27 Projects Service Domains with proof of concept or deployment projects underway include: Product Availability Credit Management Customer Inventory Management Pricing Contracts Finance Leasing Opportunity Management Entitlement Supply Chain Product Development/Engineering Shipments Sales Management Human Resource Management (Personnel Noun); HR XML tbd? Solution Configuration Exports Management 27 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

28 Major Accomplishments Rapid XML Schema Development Process, Architecture and Tools are in Place Developers and data analysts can quickly create data maps and message solutions. The CIO team trains the Business Unit Architects and programmers when they do their initial SOA/B2B projects IBM s On-line Open Source Library management system is used for Change Control and to manage the artifacts (using CVS). This system can be used by IBM developers anywhere in the world, 24 x 7, to manage their schemas. Supports the Roll-out of IBM s Service Oriented Architecture is the messaging standard for Enterprise Services The concept of common message vocabularies has been incorporated into IBM s SOA methodology. Many internal Application to Application projects are also using. The CIO Architecture team is extending to support UML based development. Important for SOA/ESB deployments. Developers Website Contains all architecture related development documentation, methodologies, governance processes etc. Future: Create an on-line business data dictionary for messaging artifacts. Governance Process is in Place The team has defined a Service Domain Architect (SDA) role for Business Areas. The SDA will own/manage the artifacts required to support their Business Units SOA and B2B deployment projects. This will ensure business knowledge and architectural continuity. 28 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

29 Some extensions and deployment lessons.. from the trenches.. Generic BOD - Used where common schema/class required for Web Service implementations). Many best practices documents created: CS design, SOA message design patterns, Get Verb parameters and examples, App Area and Verb usage specifications/rationale Application Data Exchange metadata - Used in Mediation and gateway environments to facilitate message hand-offs between environments. Service Operation Design Patterns - Used to ensure consistency and decrease implementation costs by re-using similar Service Design Patterns and associated Message patterns. Use of Confirm[ObjectX] message structure as a generic Service Operation Response for Create, Sync, Change and Cancel Operations.. Required for message orchestration and to facilitate error recovery processing.. Rapid development methodology - UML Activity and Message Sequence Diagrams provide context for message object and operation definitions. Governance Model Domain Architects define their Domain vocabularies ; Extend OAGIS artifacts, create new Nouns where there are none etc. Change Management/Certification A hybrid Cathedral and Open Source Bazaar management model.. Federated (Business Domain) teams follow architecture principles to design their solutions. Schemas are certified prior to implementation to architecture is followed; minimizes redundant/overlapping data conflicts. 29 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

30 Something to Think about.. when developing standards -Developers, Business Process Owners, Tools Vendors etc.. All have limited time.. Don t add complexity where it doesn t provide value! -- Standards that are difficult to implement will not be accepted. High Degree of Acceptance/ Buy-in Low Complexity High 30 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

31 Generic Verb This structure promotes consistency within message schemas by maximizing the reuse of each building block. This shortens the development cycle and learning curve required to create messaging solutions. Example: Consider a Purchase, which is a commonly used message in ecommerce transactions. The Purchase message has typical operations ( Actions ) that are performed on it such as Process, Get, Show, and Acknowledge, to name a few. OAGIS currently defines each Verb operation as a separate XML element, which requires a separate message to be created for each Service Operation. That is, although ProcessPurchase and ShowPurchase share the common Noun Purchase, two different XML message schemas are required to implement a typical transaction. Implications of this approach: - For a business interaction that requires two schemas, two separate mapping specifications (used to map the business data for an application to its verb specific XML schema definitions) have to be developed. - When generating Java code, each schema represents a separate group of code, (e.g., Java package). For the request and response message pattern (typical in Web Services), data has to be moved from one package to the other, which increases development activities, and runtime cost. - When a new operation is required for business needs, a new BOD schema has to be constructed, and a new mapping exercise has to be conducted, which is very time consuming. Thus, there is a desire to maintain a common Verb-Noun structure in messages, while avoiding the need to develop separate schemas for each business message. To do this requires that the Operation information for the message be moved out of the XML Verb element definition. 31 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()

32 Summary : Standardizes the Message Payload Structures required for consistent Application to Application Messaging Provides the Message Objects (Data Vocabulary) used to support ESB Mediation and SOA Message Interactions Supports the Deployment of B2B Solutions by standardizing Message Schemas (and therefore the Services) Required for B2B Interactions. Promotes, as a Common Design Practice, the use of Reusable Building Blocks for Constructing Messages. The Development Methodology Simplifies Message Construction and Reduces Development Cost. 32 Implementing SOA using IBM s Enterprise Integration Messaging Specification ()