Tutorials: Interface Mapping Toolkit - Mainframe

These tutorials walk you through the process of defining service interfaces in Visual Studio using the Interface Mapping Toolkit feature of Enterprise Developer, deploying them to Enterprise Server, and generating and running clients to access them.
We provide these tutorials:
  • CICS Screen Tutorial - Start with a CICS COBOL application and, using its .bms maps, define a service interface that you deploy to an enterprise server as a Web Services service. Generate a Windows Forms and a console client and access the service with each. This tutorial requires that you have access to TN3270 emulator such as Micro Focus Rumba.
  • CICS Commarea Tutorial - Start with a CICS COBOL application and, using its commarea fields, define a service interface that you deploy to an enterprise server as a Web service. Generate a Windows Forms and a console client and access the service with each.
  • IMS Screen Tutorial - Start with an IMS COBOL application and, using its .mfs maps, define a service interface that you deploy to an enterprise server as a Web Services service. Generate a Windows Forms and a console client and access the service with each. This tutorial requires that you have access to TN3270 emulator such as Micro Focus Rumba.

Before starting any tutorial, you must first create a Visual Studio Solution to contain your service interface projects. Following that, you can do the tutorials in any order, but within each you must complete each topic of instruction in sequence in its entirety to be successful. The bottom of each topic provides Next topic and Previous topic navigational links to help you proceed through the tutorials in their proper sequence.

If you are not familiar with the concept and implementation of a service interface, take some time to review the introductory information and other relevant topics for the IMTK.

Important: If enabled, we highly recommend that you disable User Access Control (UAC) before attempting any IMTK tutorial to avoid possible compile errors. If this is not possible, run Enterprise Developer as an administrator.