Business Process/Web Services Integration - eb. XML Himagiri (Hima) Mukkamala Web Services Architect, Sybase e-Business Division
Bio • Web Services Architect for Sybase e. Business Division • Co-author for eb. XML CPPA 2. 0 specification • Co-author for eb. XML BPSS 2. 0 specification • Specification Co-lead for JSR 157 – Java APIs for eb. XML CPPA • Sybase’s representative to W 3 C Web Services Architecture WG
Web Services – Classification • Two categories based on usage patterns – Simple – Collaborative Web Services
Simple Web Services • Basic Web Services. – Stock Quote Service, etc. • Either RPC or Document style • Commonly implemented using SOAP, WSDL & UDDI on a J 2 EE™ App. Server. • Doesn’t provide Business Process Collaboration capabilities natively. • Lacks Trading Partner Agreement, State information
Simple Web Services Request Web Services Provider J 2 EE™ App. Server Internet Web Services Provider Response SOAP Messages . NET
Collaborative Web Services • Complex Web Services. • Either RPC or Document style • Commonly layered on industry standards like eb. XML, Rosetta. Net™, etc. • Business Process Collaboration over the Internet. • Enables Trading Partners to take part in complex business processes. • Provide common services like Exceptions, Security, Non -Repudiation, Notification of Failure, etc. • Larger infrastructure requirements.
Collaborative Web Services(Cont’d) Trading Partner Management Request B 2 B Application Internet Response Request B 2 B Application Response BPM J 2 EE™ App. Server BPM Collaboration . NET ™
eb. XML & Collaborative WS Trading Partner CPP/A Management Core Comp Request B 2 B Application Internet Response Request B 2 B Application Response BPM J 2 EE™ App. Server MSH Collaboration BPSS BPM. NET ™
Business Process Integration • Integrating disparate business processes within and outside the enterprise • Ability to describe business processes in a platform/vendor neutral format • Web Services to integrate diverse architectures and implementations • Different requirements based on integration boundaries. • Business processes could be a choreography of Web Services
Business Process Integration (Cont’d) • Within the enterprise, different systems have to be tied together. • Performance and simplicity becomes a big factor • Automating integration across extended value chain can be delivered using Web Services. • Integration across enterprise can start with simple interactions. • Eventually, for Business Process Integration spanning multiple enterprises, Web Services Integration Architectures have to possess certain functionalities.
Business Process Integration (Cont’d) • Some of the functionality include – – Choreography Transactionality Security Managebility, etc. • These features will let enterprises have flexibility in integrating business partners • Results in automated business collaborations in a standardized format? ?
Business Process Integration (Cont’d) Portal Interface Data Storage Business Process Engine Analysis/Monitoring Application Server Web Services Business Platform Adapters Public Process Integration Transformation/ Routing
What does Sybase provide?
Key Elements of an eb. XML Solution • Modeling tools for BPSS • GUI tools for CPPA creation • Standards adherence • Proven interoperability with solutions from other vendors • Security enhancements like S/MIME • Scalability and High Availability • Integration with security infrastructure • Business Process Management layer
Business Process Integration Solution (Beyond eb. XML) • Adapters to EIS systems like SAP to get to internal processes • Monitoring capabilities to analyze/evaluate business processes – internal & external • Application Server functionality like J 2 EE compliance. • Portal solutions for human interaction across business processes
Sybase eb. XML Solution • Business Process Integrator (BPI) Suite – A comprehensive, modular integration solution for the value chain – eb. XML and Rosetta. Net support – Business process management (public & private) – Business activity monitoring (fat or thin client) – Integration to legacy applications • • EDI (X 12, EDIFACT, HL 7) SAP, Siebel, People. Soft, etc. OS/390 – CICS & IMS Many others
BPI Suite for eb. XML • Web Services Integrator – eb. XML MSH and CPPA support – Tools for CPP and CPA creation and modification. – UCC (Drummond) certified for eb. MS 2. 0 interoperability with 3 other vendors. – Messaging implementation has been open-sourced and is available for public download at www. sybase. com/developer • Power. Designer – Design-time BPSS support – UML Modeling. • Process Server – Run-time eb. XML BPSS support – Additional support for private business processes
BPI Suite for eb. XML(Cont’d) • Biz. Tracker – Monitor status of private or public business processes – Real-time transformation of raw data into meaningful business metrics (real-time BI) • e-Biz Integrator – Message routing – Data transformation • Enterprise Application Server – J 2 EE 1. 3 compliant – Execute CORBA/COM/Java components
eb. XML Specifications • eb. MS 2. 0 & MSH 1. 0 • BPSS 1. 01 • CPPA 1. 0 & CPPA 2. 0 • REGREP using JAXR
Car Parts International • Car Parts International uses the Sybase Business Process Integrator (BPI) Suite to: – Integrate all key touch points in the extended value chain: customers, employees, and business partners in value chain. – Provide valuable services to their customers streamlines integration with existing systems – Automate business processes in an extended enterprise. – Streamline integration with existing systems – Bring news systems on-line
Car Parts International Business Problem Call Center Car Parts International Orders Internet Car Parts Manufacturer • Competitive market place • New channels of delivery needed for customers • Operation systems can’t connect to web applications • Paper intensive manual process • Difficulty bringing new systems on-line quickly
Business Process Engine Start Validate Client Account Exists N Y Check Credit Y Good N Open Send Account Denial Submit Order End External Customer Verification Service
Submit Order Car Parts Manufacturer Order. Reservation. Request Order. Reservation. Response Internet Car Parts International Order. Request Order. Confirmation Public Collaboration Sybase Adapter for SAP R/3 Public Process Interface
The Systems Car Parts International Process Server EAServer J 2 EE 1. 3 Compliant Sybase Adapter for SAP R/3 System Sybase Adapter for Siebel e-Biz Integrator Web Services Integrator Biz. Tracker Siebel System Credit Approval System
Extended Business Process using eb. XML
Public Business Process – Submit Order • “Submit Order” is business process integration across enterprise • This is a two business transaction collaboration • “Car Parts International” will send a “Order Reservation Request” for a particular part ordered by a customer • “Car Parts Manufacturer” will send a “Order Reservation Response” • “Car Parts International” will send a “Order Request” • “Car Parts Manufacturer” will send a “Order Confirmation” • SAP System on the “Car Parts Manufacturer” side will register the order, once PO is received and PO Response is sent.
Description of B 2 B Collaboration using eb. XML • Roles – Seller, Buyer • Transactions – Order Reservation Request, Purchase Order • Business Documents – Order Reservation Request, Order Reservation Response – PO Request, PO Confirmation • • Protocol – HTTP XMLDSIG for Non-Repudiation SSL for Authentication Documents and Capabilities published for Trading Partner access
Scenario Mapped to eb. XML • Business Documents – Order Reservation Request, Order Reservation Response, PO Confirmation – Set of Core Components • Collaboration Description for Purchasing Service Business Process - BPSS • Definition of transport, enveloping, security characteristics, etc. - CPA • Publishing of Document definitions and capabilities - REGREP • Runtime exchange of messages over HTTP – MSH
Sequence of Operations 1. Model the Business Collaboration. 2. Create a BPSS instance document for the collaboration. 3. Choose the Business Documents to take part in the collaboration. 4. Decide on message exchange characteristics 5. Create a CPP for the business process capturing the characteristics decided. 6. Publish the BPSS instance, CPP and the Business Documents to registry under particular category
Sequence of Operations (Cont’d) 7. Trading Partner would query the registry for a particular category. 8. A particular matching partners’ BPSS, CPP and other necessary information are retrieved from the registry. 9. Would create a CPP to match up with their characteristics. 10. Negotiate with the partner chosen to come up with a CPA. 11. Initiate the collaboration by invoking the Business Service Interface provided.
Collaboration Design and Runtime Business Process Model Business Document Core Components BPSS CPP Registry/ Repository CPA Trading Partner Transport & Packaging Trading Partner
Infrastructure Design Document Repository CPA Merge Tool CPA Negotiation CPP Designer BP Modeling Tool Registry Browser Runtime BSI REGREP API CPPA API MSH API App Server
Summary • Things to look for in a Vendors’ offering – – – – Tools, Tools……… GUI tools for CPP/A creation Modeling tools for BPSS Standards adherence Security enhancements like S/MIME Scalability and High Availability Integration capabilities. Business Process Management within and across enterprise.
Information • www. sybase. com/products – Information about Sybase’s BPI Suite • www. sybase. com/developer - Information about Sybase’s opensource eb. XML Messaging implementation.
Скачать презентацию Business Process Web Services Integration — eb XML Himagiri
c4041272580d47b5b814e1dcdce8984f.ppt