My previous blog, discussed the approach one could adopt if the organization’s portfolio comprises of CICS applications; now let us discuss the one of the simplest approach to expose IMS application as service.
IMS SOAP Gateway
IMS Enterprise Suite SOAP Gateway is a web services solution that enables IMS applications to interoperate outside of the IMS environment through the SOAP protocol.
The IMS application can be exposed as Web services, by first creating a Web Service Description Language (web service interface) for the IMS application followed by deploying the web service interface to IMS SOAP Gateway and defining the connection and correlation information by using the deployment utility. Once deployed, any client application (Java or Microsoft .NET based) can send a SOAP message to invoke the IMS application. SOAP Gateway is compliant with the industry standards for web services, including SOAP/HTTP 1.1 and Web Services Description Language (WSDL) 1.1
Tools like Rational Developer for System z can be used to generate the WSDL file that is needed to enable the IMS application to run as a Web service provider. All that is required to generate the WSDL file is the COBOL copybook for the IMS application that describes the input and output message format.
Architecture
Note that SOAP Gateway supports various z/OS, other distributed platform like Linux for System, AIX and Windows. This approach requires the following software: IMS and IMS Connect Version 10 or above and IMS SOAP Gateway.
Advantages of this approach
Even though this is an easy way to enable IMS transaction, this approach has many many drawbacks such as no support for MFS-based transactions and two-phase commit. So exploring the options which make use of Enterprise Service Bus is suggested. Will look at the ESB based enablement in a subsequent blog.
IMS SOAP Gateway
IMS Enterprise Suite SOAP Gateway is a web services solution that enables IMS applications to interoperate outside of the IMS environment through the SOAP protocol.
The IMS application can be exposed as Web services, by first creating a Web Service Description Language (web service interface) for the IMS application followed by deploying the web service interface to IMS SOAP Gateway and defining the connection and correlation information by using the deployment utility. Once deployed, any client application (Java or Microsoft .NET based) can send a SOAP message to invoke the IMS application. SOAP Gateway is compliant with the industry standards for web services, including SOAP/HTTP 1.1 and Web Services Description Language (WSDL) 1.1
Tools like Rational Developer for System z can be used to generate the WSDL file that is needed to enable the IMS application to run as a Web service provider. All that is required to generate the WSDL file is the COBOL copybook for the IMS application that describes the input and output message format.
Architecture
Note that SOAP Gateway supports various z/OS, other distributed platform like Linux for System, AIX and Windows. This approach requires the following software: IMS and IMS Connect Version 10 or above and IMS SOAP Gateway.
Advantages of this approach
- Simple and easy way to enable IMS application.
- Existing transactions can be retained with no change.
Even though this is an easy way to enable IMS transaction, this approach has many many drawbacks such as no support for MFS-based transactions and two-phase commit. So exploring the options which make use of Enterprise Service Bus is suggested. Will look at the ESB based enablement in a subsequent blog.
1 comment:
Nice post, thanks for sharing
Web Design Company in Bangalore | web Development Company in Bangalore | Website Design Company in Bangalore
Post a Comment