In this session, we continue with the "We Speak", Mission Critical Series with an episode on how Azure Logic Apps can unlock scenarios that require integration with IBM IMS Systems. This presentation covers a demo of the IBM IMS Built-in (In App) connector in Azure Logic Apps.
Some considerations about IBM IMS:
- IBM IMS performs online transaction processing for applications that access IMS data as well as data stored in Db2 for z/OS.
- IBM IMS (1966) is a system used by 95% of Fortune 1000 and that was built for the Apollo Mission.
- IBM IMS manages over 20 petabytes of production data and serves over 300M users per day.
- IBM IMS, known for its high performance is also known for its complexity as well.
The IBM IMS In-App Connector
Our IMS Azure Integration technologies are based on the IMS Connect programming model that provides access to information management systems (IMS) transactions using TCP/IP. This model uses the IMS message queue for processing data.
If you need APPC support, we provide access to IMS transactions using LU6.2 (available only in Host Integration Server).
To be able to call IMS programs, you need to create a Program definition that can be understood by the Azure Logic Apps Workflow. For this, you will need the Host Integration Server development edition along with Visual Studio 2019. The Program Definition will be created as a Host Integration Designer XML (HIDX) file and will look like this when complete:
Once you create an Azure Logic Apps workflow, you can add the IMS In-App connector. It will load automatically the HIDX files previously uploaded in the Maps artifacts of your Azure Logic App.
To set up the IBM IMS Connector, you will require information from the Mainframe Specialist. You will require at least an IMS System ID, Port Number, ITOC Exit Name and Server Name. For most types of IMS Connect clients, IMS Connect requires the use of a user message exit routine to manage the messages that are received from and sent to the client.
The following video includes a complete demonstration of the IMS connector: