Session: J03 SOA Access To and From IMS IBM Advanced Technical Support Suzie Wendler IBM May 19, 2008 • 01:30 p.m. – 02:30 p.m. Platform: IMS Building on decades of innovation and value, mainframe computing with IMS continues to be a significant part of IBM's On Demand and SOA strategy. Customers can rest assured that their investment in existing business logic can be integrated into evolving technologies. This session discusses how new interfaces and architectural frameworks open up and integrate IMS accessibility to and from distributed environments and Web servers. Discussions will position and compare the new IMS technologies that integrate the use of SOAP, XML, EJB's and Web Services. 1 IBM Advanced Technical Support IBM Advanced Technical Support SOA Access to and From IMS • Learn about the different architected interfaces that allow IMS to be integrated into a distributed environment • Solutions to access IMS transactions and how to expose them as web services • Solutions to access IMS data from remote environments • Learn about the capabilities that are available to IMS applications to allow them to consume web services • Understand how IMS can be an integral part of your enterprise solution in answering changing market needs • IMS continues to be a premier server 2 The material presented in this topic is intended to allow attendees to learn about the IMS architected interfaces that have modernized the environment and provide the mechanism to integrate IMS applications and data into the distributed world. 2 IBM Advanced Technical Support IBM Advanced Technical Support Agenda • SOA • Accessing IMS Transactions • Accessing IMS Data • Access from IMS applications • Future directions 3 The agenda begins with an explanation of what SOA (Service Oriented Architecture) means to IMS, followed by an explanation of the IMS solutions. At the end of the session, a brief description will be provided of the IMS future directions in this area. 3 IBM Advanced Technical Support IBM Advanced Technical Support The IMS Evolution UDDI Registry EJB Service IMS IMS Broker Connect find Java publish XML WSDL WSDL SOAP COBOL XML IMS bind, invoke Service DB Service Provider Requester 3270 WWW Client 3270 Web Application Service SOAP IMS EJB Connect COBOL WWW 32703270 Access Enterprise Integration On Demand SOA Optimize operations… Buying, not browsing “ Get on the Net “ … dynamically respond to standards COBOL “ ” Working, not surfing” the needs of customers,” employees, partners. 3270 3270 Integrate Integrate Adopt Access Publish Transact Standardize Internally Externally Dynamically 4 The first message that needs to be emphasized is that IMS continues to be a premier server in today’s world. With new architected interfaces and solutions, the existing IMS environment answers the challenges that are presented by today’s business needs. Existing IMS resources can continue to be accessed, as they have in the past, by simple straight-forward requests such as those that are requested using traditional 3270 interfaces and emulators, or they can participate in distributed requests from a variety of servers using TCP/IP and web-based solutions. As technology has advanced, the On Demand and SOA evolution with IMS continues to support the scalability, security, integrity and performance requirements that IMS has always provided. The main point is that applications that were developed years ago with older communication architectures and technology can continue to be accessed in today’s environment. IMS has always shielded its applications from having to understand changes in communication mechanisms. On the other hand, IMS also provides the ability to modernize its applications to directly participate in enhanced functions. Note that the most recent architecture, as shown on the visual, is SOA (service oriented architecture). A little bit of a background might be helpful in understanding this environment. As the web evolved, its dynamic nature along with continued technological advancements, resulted in increased complexities and challenges for true interoperability. Enterprises that were betting their businesses on these capabilities needed a guarantee of compatibility across platforms, applications and vendors. This set of challenges led to a collaboration in the technical and business community which ultimately defined an architecture specification geared towards standardization. SOA is all about standardization. 4 IBM Advanced Technical Support IBM Advanced Technical Support … To SOA and Web Services UDDI • Definition: Registry Service • Web Service Broker • Software component (callable publish piece of code) that is capable WSDL find of being accessed WSDL (described, published and located) IMS bind, invoke Service Service • via standard network Provider protocols such as SOAP Requester over HTTP Web SOAP Client • independent of platforms or Service Application programming language • Web Services Description Language (WSDL) Industry standards • XML document describing 3 basic components: network services, e.g., what a - Service Provider Web Service can do, where it - Service Broker resides, and how to invoke it - Service Requestor STANDARDIZATION !!! 5 Some basic terminology might be helpful at this point. A service is a callable piece of code (like a web server application) that can be invoked to provide a repeatable function. A web service is a special type of service that adheres to the use of open standards such as XML, SOAP, WSDL and UDDI over a TCP/IP backbone. XML (extensible markup language) is used to tag the data, SOAP (simple object access protocol) is used to transfer the data, WSDL (web services description language) is used to describe the services that are available and UDDI (universal description discovery and integration) is used for listing what services are available. The creation of web services allow organizations to communicate data without knowledge of each other's systems, many of which are behind firewalls. The SOA architecture also includes three basic components. •The service requestor is a client that locates entries in a broker registry and uses the information to bind to the service provider in order to invoke one of its Web services. -The service broker, also known as a service registry, provides the ability to make the web service interface and implementation access information available to any potential service requestor. Service brokers can be public or private. -The service provider creates and provides the runtime environment for a web service and publishes its interface and access information to the service registry. 5 IBM Advanced Technical Support IBM Advanced Technical Support The Challenge - SOA Enablement REQUIREMENTS • Provide access to IMS resources as web services • Provide access from IMS transactions to web services UDDI Registry Service • Figuring out how to access IMS Broker • “Exposing” the IMS resources as web services publish find • Deciding how to create the web service WSDL WSDL ? Service Service bind, invoke Requester IMS Provider Web Client Service Application SOAP • Figuring how to access web services from IMS 6 So what does this all mean for IMS? IMS is not the container for a web service. IMS resources, however, can be “exposed” as web services. What this means is that IMS provides the interfaces so that web services that run in a service provider can be written or generated to access IMS. IMS, therefore, is a resource that can be invoked by a web service and, in terms of this architecture, can be viewed as an extension to the service provider. IMS answers two sets of requirements for SOA enablement. The first is the ability to provide access to IMS resources as web services, and the second is the ability to allow IMS transactions to call out to web services. The challenge for the creator of the web service is to figure out the best way to access IMS resources based on the application, network and business requirements. 6 IBM Advanced Technical Support IBM Advanced Technical Support IMS Solutions Web Solution Solution Direct service s clients s DLI Database WID RAD Model Utility access Developers Java/J2EE IMS WebSphere Client WebSphere Java Java /J2EE dev IMS TM IMS DB Developer Resource Transaction Database Resource Adapter manager manager Adapter ODBA /DRA ODBA IMS Connect IMS Java MFS Web class Services SQL .NET TCP Library SOAP IMS DL/I XQuery CICS Client /IP APP DL/I Developer Client Developer DB2 Direct Java SP/CICS Web Service class Database SOAP Java Library Java class class Library Library IMS SOAP DB2 SAP Gateway Developer Client Application DLI DLI developer WDz Model Model Utility Utility 7 To support the technology explosion, IMS provides a variety of solutions to assist in accessing both IMS transactions and IMS data from remote requestors. This visual provides an overview of the IMS-provided capabilities which will be discussed in more detail in the following visuals. 7 IBM Advanced Technical Support IBM Advanced Technical Support …Provide SOA Enablement • Tooling can be used for the SOA higher layers • Assets projected into the lower layers can be “pulled” higher Monitoring/Event Management Governance Security SOA Process/Orchestration SOAP/J2EE Services SOA enablement J2EE/JCA (EJB) Data Services / Messaging SQL/ Data Abstraction XQuery/XML J2EE/JCA (EJB) IMS IMS Legacy App Data Rep DB Source: Linthicum Group 8 SOA is defined as an architectural style for the creation of business processes which are packaged as services with an accompanying provision for an IT infrastructure