WebSphere MQ for ClearPath MCP

Product Overview

WebSphere MQ for ClearPath MCP is message-oriented middleware that allows Transaction Server programs and other application programs on ClearPath MCP servers to participate in message-oriented processing applications. WebSphere MQ for ClearPath MCP can communicate with platforms on which IBM WebSphere MQ is available.

WebSphere MQ for ClearPath MCP offers the two paths that provide WebSphere MQ functionality to applications running in the MCP Environment:

  • A WebSphere MQ bridge to Transaction Server direct-windows applications. The bridge enables unmodified, existing Transaction Server direct windows programs to exchange messages with WebSphere MQ applications on other platforms. The two portion of this data path are

    • Custom Connect Facility protocol-specific handler (CCF PSH)

    • Connector protocol-specific handler (Connector PSH)

  • The Message Queuing Interface (MQI)—the IBM standard WebSphere MQ API—is available to programs written in COBOL74, COBOL85, ALGOL, NEWP, and C.

WebSphere MQ for ClearPath MCP uses the IBM MQSeries product or the IBM WebSphere MQ product running in the Windows environment to manage message queues and facilitate message exchange between applications.

General Features

WebSphere MQ for ClearPath MCP is ideal for integrating applications that have the following characteristics:

  • Run on several different platforms, such as IBM i, Sun Solaris, Microsoft Windows, HP-UX, and Unisys ClearPath OS 2200.

  • Demand reliable, secure, and recoverable message delivery.

  • Can run independently, with or without an active network connection, depending on business requirements.

  • Need to be able to trigger application initiation to process messages.

WebSphere MQ for ClearPath MCP minimizes the impact on existing MCP workloads by offloading queues and the queue manager’s workload to Windows.

If you run WebSphere MQ for ClearPath MCP on the internal Intel processor of your ClearPath server, you can potentially achieve performance benefits. However, you can also use the WebSphere MQ for Windows on a stand-alone Intel server.

You can also use any systems management tool that supports WebSphere MQ for Windows. This versatility gives you automated management of WebSphere MQ across the enterprise. Examples of suitable systems management tools include BMC PATROL for WebSphere MQ and Tivoli Monitoring for Business Integration: WebSphere MQ.

Remote Control of WebSphere MQ for ClearPath MCP

The WebSphere MQ for ClearPath MCP Explorer enables you to manage and control the WebSphere MQ for ClearPath MCP service running on a remote computer. A site can administer multiple installations of the WebSphere MQ for ClearPath MCP service from a single, centralized location.

User Exit

A user exit is a dynamic link library (DLL) exporting several functions that the Custom Connect Facility (CCF) protocol-specific handler (PSH) routers can call before forwarding a message to the Transaction Server and after receiving a response from the Transaction Server. The router passes certain configuration information to the user exit during initialization. WebSphere MQ for ClearPath MCP provides the names of the queue manager and the input queue being used by the router. It also provides the IP address and port number of the ClearPath MCP server, the name of the invoking router, and a reference to the router copy of the XlateEBCDIC control.

Security Exit

A security exit is a DLL enforcing security on a message-by-message basis that the Connector PSH routers can call before forwarding a message to the Transaction Server. The router passes certain configuration information to the security exit during initialization. WebSphere MQ for ClearPath MCP provides the names of the queue manager and the input queue being used by the router. It also provides the IP address and port number of the ClearPath MCP server, the name of the invoking router, the name of the Transaction Server window, and a reference to the router copy of the XlateEBCDIC control.

MQAPI RPC Server Kerberos Security

The MQAPI remote procedure call (RPC) interface to WebSphere MQ for ClearPath MCP can be configured to require ClearPath MCP client applications to provide Kerberos credentials at the time of connection. This configuration enables system administrators to control access to WebSphere MQ that is provided to the ClearPath MCP application.

Configuration Requirements

Windows Environment

  • Windows operating system

    See the compatibility matrices at URL below.

  • IBM WebSphere MQ

Compatibility Matrices at

https://www.support.unisys.com/common/matrices/matrixTOC.aspx?pla=MCP&nav=MCP

MCP Software

  • Custom Connect Facility (CCF) must be installed if you plan to use CCF PSH routers.

  • Connector PSH (CONNPSH) must be installed if you plan to use Connector PSH routers.

  • Unisys TCP/IP implementation.

  • WIN RPC must be installed if you plan to use the API feature.

  • MCP Transaction manager must be installed if transaction semantics are to be supported.

Ordering Information

Platform

Style

ClearPath

The group style for WebSphere MQ for ClearPath MCP is CSP 10nn-MQ, where nn represents performance groups 10 through 160 (in increments of 10).

Product Information

Refer to the following documents for more information:

  • WebSphere MQ for ClearPath MCP User’s Guide (8999 8983)

  • WebSphere MQ for ClearPath MCP Help (8999 9585)

Prev  Up  Next
Web Transaction Server for ClearPath MCP  Home   Systems Management