E152 Leveraging Web Services for Integration

1. E152Leveraging Web Services for Integration • Michael Gordon • Sr. Manager, Integration Product Mgmt • e-Business Division • mgordon@sybase.com

2. Sybase e-Business PlatformComprehensive,Modular, Integrated and Open Enabling Your Customers Empowering Your Enterprise Enriching B2B Interactions Trding Partners Customers Enterprise Access Power Designer Enterprise Portal - Web & Mobile Access Integrate Process Server Biz Tracker Integration Server Application Adapters Web Services Develop Transact Java IDE Application Server Business Intelligence Replication Database Metadata Repository - Configuration Security - Install - Management SYBASE e-Business Platform

3. Power Designer Enterprise Portal - Web & Mobile Access, Openbiz Process Server Biz Tracker Integration Server Application Adapters Web Services Java IDE Application Server Business Intelligence Replication Database Metadata Repository - Configuration Security - Install - Management SYBASE e-Business Platform Sybase e-Business PlatformSupport for Web Services • Simple Web Services • Defined as: UDDI, WSDL, SOAP • Supported through • EAServer • PowerDesigner • Collaborative Web Services • Defined as: B2B, RosettaNet, ebXML • Supported through: • Web Services Integrator • OpenBiz

4. Sybase e-Business Platform Access Power Designer Enterprise Portal - Web & Mobile Access Integrate Process Server Biz Tracker Integration Server Application Adapters Web Services Develop Transact Java IDE Application Server Business Intelligence Replication Database Metadata Repository - Configuration Security - Install - Management SYBASE e-Business Platform

5. Agenda • Overview of Web Services • Web Services Value Proposition • Future: Adoption and Evolution of Web Services • Sybase Web Services Solutions for Integration • Demos

6. Overview of Web Services

7. Web Services Definition • Web Services are XML-based standards for deploying highly distributed, componentized applications that transcend server, firewall, and enterprise boundaries.

8. Web Services Characteristics • Platform Independent • Standards-based • Secure • Reusable • Distributed • Scalable

9. Web ServicesA new paradigm • Service Oriented Architectures consist of: • Distributed & process centric application deployment • Loosely coupled (XML based) interfaces • Publish and discovery capabilities • Web Services are a set of standards that define how to achieve a loosely coupled framework for communication and application development and deployment • In that regard, Web Services are a standards based instance of a Service Oriented Architecture • Web Services allow business processes to be abstracted into ‘services’ that can then be easily linked together

10. Web Services Dissected • Simple Web Services – Component level building blocks for constructing highly distributed, network based applications. Can be constructed either at design-time (per traditional application development paradigm), or at run-time (concept of the “virtual application”). • Collaborative Web Services – Complex protocols governing the interaction between applications and enterprises. Address additional requirements for security, non-repudiation, business process management, and long-running transactions.

11. Simple Web Services

12. Mainframe (components) Conceptual Diagram Exposed Service Trading Partner ApplicationServer (components) Web Services basedapplication Exposed Service My Enterprise Financial Entity

13. Simple Web Services • WSDL (Web Services Description Language) • SOAP (Simple Object Access Protocol) • UDDI (Universal Description, Discovery, and Integration)

14. WSDL • WSDL • WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. • A Web Service represents a unit of business, application, or system functionality that can be accessed over the Web. • WSDL describes the interface for a Web Service.

15. SOAP • SOAP • SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment. • SOAP messages can call a procedure on a server across a network. • SOAP-compliant procedures can be called from across a network. • Firewall friendly – messages can easily transverse firewalls.

16. UDDI • UDDI • UDDI is a specification for a Web-based business registry that can be used to describe and discover Web Services. (There are both public and private registries.) • WSDL documents (or links to WSDL documents) are posted to a UDDI repository. • A UDDI repository can be searched for exposed Web Services at design-time and run-time.

17. Now What? • WSDL defines the interface • SOAP defines the messaging service • UDDI defines the repository • Need to orchestrate interaction between Web Services to create an application • Enter WSFL (Web Services Flow Language) and XLANG

18. WSFL & XLANG • WSFL • Designed by IBM • XML language for the description of Web Services compositions as part of a business process definition • XLANG • Designed by Microsoft • Provides the model of an orchestration of services as well as collaboration contracts between orchestrations

19. Which Orchestration Spec Will Become Standard? • Not clear whether XLANG or WSFL will dominate • Potential for new XLANG/WSFL hybrid backed by IBM and Microsoft • New standards emerging such as WSCI • Can’t predict future at this point

20. Collaborative Web Services

21. Collaborative Web Services • Collaborative Web Services “live higher on the stack” than simple Web Services. • Can be viewed as B2B integration protocols that are built upon Web Services standards. • Address additional requirements for security, non-repudiation, business process management, and long-running transactions.

22. ebXML • ebXML • ebXML is a complete B2Bi XML framework that enables business collaboration through the sharing of Web-based business services. • ebXML supports the definition and execution of B2Bi business processes expressed as choreographed sequences of business service exchanges. • ebXML expands upon first generation B2B solutions (such as EDI) by standardizing business process, trading partner profiles & agreements, message transports, and security. • ebXML is payload independent.

23. Key Areas of ebXML Specification • BPSS (Business Process Specification Schema) • Registry • CPPA (Collaboration Protocol Profile & Agreement) • Message Service

24. RosettaNet • RosettaNet • RosettaNet specifications allow manufacturers, distributors, resellers, and end-users to leverage the Internet to exchange business documents across the entire supply chain. • The RosettaNet Implementation Framework (RNIF) specification provides XML-based standards for business documents and specifies common business processes between trading partners (known as PIPs). • RosettaNet standardizes both process and data aspects of B2B collaboration. • RNIF 3.0 will incorporate ebXML standards for trading partner management and message transport/security.

25. Web Services Value Proposition

26. I.T. Benefits of Web Services • XML standards-based – relatively low cost to develop and deploy • Legacy components can be wrapped instead of re-built • Application components can be “outsourced” • Flexibility in solution architecture • Dynamic application-to-application integration • More rapid application development • Developers can focus on “core” business applications

27. Business Benefits of Web Services • Opportunity to develop new business relationships • On sell-side – Opportunity to compete and sell into a larger market • On buy-side – Opportunity to identify new vendors and better terms & prices • Faster, more flexible e-business

28. 2 ERP application searches for vendor Web Services that provides product availability and price info 3 Two product query services are found. Descriptions of these services are returned to the ERP application 1 Manufacturer’s ERP system determines need for 1000 5mm steel ball bearings to fulfill customer order 4 ERP application submits order to vendor with best terms and price Simple Web Services Example UDDI Repository

29. Complex Web Services Example Companies publish descriptive information about themselves (CPP) and required business process (BPSS) in a repository Design Time ebXML Repository CPP CPP BPSS BPSS Run Time ebXML Repository CPP BPSS Buyer discovers seller, electronically defines partner agreement (CPA) based on buyer’s andseller’s CPP, then initiates BPSScollaboration using ebXML messaging

30. Future: Adoption and Evolution of Web Services

31. Adoption of Web Services • Hype around Web Services continuing to grow • Standards expected to evolve and mature over coming years – increased focus on security and transactionality required • Organizations will begin to experiment with Web Services internally at first, then “test the waters” outside the firewall with simple components

32. Adoption of Web Services (cont’d) • Widespread adoption/implementation of Web Services not anticipated until 2004 and beyond • Early applications likely to support transportation, commodity goods & services, and complex calculations • Potentially as revolutionary as the “web browser”, but adoption will be key measure of success

33. Sybase Web Services Solutions for Integration

34. Web Services Benefits: Sybase is accelerating the adoption rate of Web Services by enabling developers to expose their existing components, data and applications as enterprise-class Web Services Sybase delivers a comprehensive framework to develop, provide, orchestrate and access enterprise-class Web Services

35. Web Services Framework • Develop: software that helps develop the Web Services Provide: software that hosts a Web service • Orchestrate: assemble and orchestrateaset of software service(s) that are designed to help coordinate the activities while they are being used (service-broker) • Access: software that connects to a service and delivers the value of that service on to its intended user(s)

36. Sybase Web Services Framework • CICS • Stored Procedures • *Applications • Mobile messaging • services • Vertical component • applications(EBA) • *IWS Java EJB .Net *C++ *NVO Access Enterprise Portal m-Business Studio EAServer Web Services Integrator BPI Suite Develop PowerDesigner PowerBuilder Web Services Toolkit Orchestrate Open Biz Interchange Biz Tracker Process Server Provide EAServer BPI Suite Web Services Integrator Adapters Database(s) Enterprise Portal

37. Enterprise-class Web Services Role-based security Single-sign on / SBOs Failover / Fault tolerance Guaranteed delivery Authentication Sybase is a member of WSI (Web Services Interoperability Organization), as well as OASIS

38. Multi-channel Services Architecture Smart-client Web Mobile Portal Automated Design, Modeling and Development Service-Broker Self-hosted Sybase-hosted Business Services Business Services

39. Web Services Solutions for Integration • Create, deploy, and access simple Web Services on a J2EE development platform via EAServer’s Web Services Toolkit • WSDL - ability to describe exposed services in WSDL format, automatically generate WSDL via GUI • SOAP – client and servlette support for SOAP, GUI-based template tool • UDDI – ability to publish to and retrieve from UDDI repositories

40. Web Services Solutions for Integration (cont’d) • Business Process Integrator (BPI) Suite - Enterprise class integration, inside and outside the firewall • e-Biz Integrator • Process Server • Web Services Integrator • EAServer w/Web Services Toolkit • BizTracker • Adapter for XML • Many pre-built adapters available for packaged applications, legacy systems, and “technology targets”

41. BPI Suite • Comprehensive process and data integration solution across the value chain • Leverages New Era of Networks’ strength and experience in integration technology, extending these capabilities across the boundaries of the enterprise • Synergy between integrated New Era of Networks and Sybase technology delivers an integration solution for the value chain, supporting EAI, Web Services, J2EE, and collaborative Web Services protocols like ebXML and RosettaNet

42. BPI Suite Overview • BPI Suite enables Web Services based integration via the following features • Invoke a Web Service from within a business process involving other Web Services or “traditional” application end points • Expose a private business process as a Web Service • Monitor Web Services activity • ebXML support • RosettaNet support

43. Sybase EAServer EJB Adaptors SAP R3 Database New Era e-Biz Integrator People Soft Flat File Siebel BPI Suite Scenario XML Message Bridge Business Transaction Firewall XML Adaptor New Era Process Server Process Flow

44. Web Services Solutions for Integration (cont’d) • Adapters for Application Servers • Expose packaged application interfaces as Web Services • Deploy on EAServer, WebLogic, or WebSphere • Connect to SAP, Siebel, or PeopleSoft

45. WEB AAS for SAP Scenario ECP CPI Adapter forSAP R/3 End User EA Server Messaging JSPs Business EJBs WebSphere App Server EA Server Business EJBs

46. Demos