Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Yes. Unisys documents several ways for ClearPath MCP systems to connect with Web technologies, but the right option depends on what you need: an MCP program can make an outbound HTTP request, call Windows-hosted .NET code, or provide browser-facing access through a Web server or client. Agile Business Suite (AB Suite) can also generate a Web services interface for an AB Suite solution. These are distinct capabilities—not proof that every existing MCP application automatically becomes a REST or SOAP API.

Choose the integration direction first

“Web services” can describe traffic going out from the mainframe, requests coming in from Web clients, or an interface generated for a particular application framework. Identify the direction and purpose before choosing a product.

Need Documented route What it does What to verify
An MCP program calls an external HTTP endpoint ClearPath MCP HTTP Client The application issues HTTP requests and processes responses. Unisys documents HTTP 1.0 and 1.1 support. Unisys ClearPath Forward Target MCP release, endpoint authentication, TLS policy, payload format, and error handling.
MCP code invokes Windows-hosted .NET logic AIS call-out services ClearPath code calls a public static .NET method hosted in a Windows DLL. Unisys AIS programming guide AIS version, server topology, connectivity services, deployed DLL, and failure behavior.
A browser or Web client accesses MCP content or applications Web Transaction Server or Web Enabler Web Transaction Server serves HTTP content and can act as a gateway to MCP applications; Web Enabler provides browser-based access to MCP server applications. Unisys ClearPath software overview Application compatibility, authentication and authorization, browser support, and current configuration guidance.
A generated business application needs a Web services interface Agile Business Suite interface option The AB Suite catalog lists Web services among interfaces that a generated solution can include. Unisys Agile Business Suite catalog Application framework, generation and runtime versions, interface contract, and release support.

For outbound calls, use the MCP HTTP Client

The ClearPath MCP HTTP Client is the most direct documented route when an MCP application needs to send an HTTP request to an external service and handle its response. Unisys lists COBOL85, ALGOL, NEWP, and AB Suite applications as users of the capability, and identifies the WEBAPPSUPPORT library. It documents HTTP 1.0 and 1.1 support. See Unisys’s MCP HTTP Client information.

This establishes HTTP request capability; it does not establish support for every modern API feature, authentication scheme, TLS configuration, or payload format. Confirm those specifics for the endpoint and the installed MCP release, and design for timeouts, unsuccessful responses, and other errors.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

For Windows-hosted .NET logic, consider AIS call-out

AIS call-out is a different pattern: ClearPath code invokes a public static .NET method running in a Windows DLL rather than simply issuing an HTTP request to an arbitrary endpoint. Unisys describes request creation, response processing, and error handling, and names COBOL85 and ALGOL among MCP languages that can use the capability. The guide characterizes the feature as providing “out bound web access and other .NET capabilities for ClearPath Forward systems.” Read the Unisys AIS programming guide.

Before selecting it, establish how the AIS components, Windows host, connectivity services, and DLL will be deployed together. Do not treat this call-out capability as evidence that MCP itself is hosting a REST service.

For incoming browser access, distinguish the server from the client

Web Transaction Server

Unisys describes Web Transaction Server (WTS) as an HTTP 1.1 server running in an MCP environment. It can serve documents and act as a gateway to MCP applications. That gives Web clients a documented route to MCP-hosted content or applications, but a gateway does not automatically turn every legacy terminal transaction into a secure, well-designed public API. See the Unisys ClearPath software overview.

Web Enabler

Web Enabler is another browser-access approach. Unisys describes it as a Java-based client/server application for accessing MCP server applications over an intranet or the Internet through a capable browser. It is useful to investigate when the goal is browser access to an existing application, rather than an application-to-application API. Check current browser and application compatibility before planning a deployment. See Unisys’s Web Enabler information.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

AB Suite Web services are framework-specific

The Agile Business Suite catalog lists Web services among the interfaces that a generated solution can include. That applies to AB Suite-generated solutions; it is not evidence that an arbitrary existing MCP program can be converted automatically. Verify the interface contract, generation and runtime versions, and support for the target release with Unisys. Review the Unisys AB Suite catalog.

Check release and deployment support before committing

Unisys documentation includes descriptions for MCP 20.0 and an MCP 21.0 catalog dated June 2023, as well as a software overview discussing WTS and Web Enabler. That confirms these capabilities appear in the cited documentation, not that every current installation or server model supports every configuration. The exact compatibility for an unspecified system is not established here.

  1. Record the MCP release, server model, and application language or framework.
  2. Define whether the requirement is outbound HTTP, a call to Windows .NET logic, browser access, or a generated service interface.
  3. Check the applicable release documentation and compatibility matrix for that exact environment; Unisys directs customers to compatibility information and sales representatives for configuration and licensing details. Start with Unisys ClearPath Forward resources.
  4. Confirm security and operational requirements, including authentication, authorization, network connectivity, TLS, logging, error handling, and recovery behavior.
  5. Validate the design against the actual endpoint or client and the deployed application before production use.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.