Web Services Support

Using Enterprise Developer, you can choose from several methods provided to expose COBOL as Web services, and in some cases, deploy and run your Web services on Enterprise Server:

Interface Mapping Toolkit (IMTK)

You can create a Web service interface using the Interface Mapping Toolkit (IMTK) feature in Enterprise Developer, and then deploying the service to Enterprise Server. See Interface Mapping using the IMTK for details.

In addition, you can generate COBOL clients from WSDL files. See Generating a Client from a WSDL File for details.

Note: Enterprise Server supports both document/literal and RPC/encoded encoding styles, but does not support the REST architectural style.

.NET COBOL

Using Enterprise Developer, you can compile your COBOL applications to Microsoft Intermediate Language (MSIL), which uses the Microsoft .NET Framework and includes Windows Communication Foundation (WCF) integration. You can then expose your WCF applications as Web services with the COBOL application running as managed code.

This method requires OO COBOL or C# on the front end to invoke the Web service; however, you can then optionally call procedural COBOL for the back end. See Building Service-Oriented Applications with WCF and COBOL.

Calling COBOL from Another Language

You can call COBOL using any of a wide variety of other programming languages. Some of these languages have direct Web services support through tooling and application server deployment.

CAUTION:

When developing a Web service using this method, be sure to include a failsafe to address the scenario in which the COBOL program crashes or issues a stop run when executed in the same process of an application server. Failure to address this scenario introduces the risk of bringing down the application server.