Configuring DevOps Test Integrations and APIs for virtualizing IMS™ Connect traffic

You can set up HCL DevOps Test Integrations and APIs (Test Integrations and APIs) to virtualize IBM® IMS Connect traffic.

Before you begin

You must have completed the following tasks before configuring the relevant operations:

About this task

Configuring Test Integrations and APIs to virtualize IMS™ Connect traffic involves configuring the relevant operations in the Logical View of the Architecture School perspective.

Note: Virtualization of IMS™ Connect traffic is supported in Test Integrations and APIs 8.5.1.1 or later.

Procedure

  1. Double-click the relevant operation in the Logical View of Architecture School perspective.

    The Operation window for the selected operation is displayed.

  2. Click the Stub tab.
  3. Click Browse to select the transport.

    The Select a Resource window is displayed.

  4. Click the relevant IMS™ Connect transport that must be used for the virtual service.
    Note: To display the desired transport, you have to click No, Yes, or Only Direct.
  5. Click OK.

    The fields displayed in the Stub tab and their descriptions are outlined in the following table. The default values displayed in the fields are determined by the configuration of the selected transport.

    Field Description

    Datastore

    The value displayed is the logical name that IMS™ Connect has for an IMS™ instance.

    The datastore is used to route the transaction execution to an IMS™ instance known to IMS™ Connect. There is a many-to-many relationship between IMS™ Connect and IMS™ instances. For example, in a simple configuration, such as one IMS™ instance and one IMS™ Connect, the default value for the datastore name is IMS1.

    Client ID

    The ID used by IMS™ Connect and IMS™ to identify each IMS™ Connect client.

    The ID is also used for the names of asynchronous message queues (OTMA TPipes) and other internal data structures in IMS™ Connect and OTMA.

    Code Page

    The code page number.

    RACF® Identity

    The Resource Access Control Facility (RACF®) can be enabled on a per-transaction basis on the server.

    To support RACF® credentials, an RACF® identity can be created (in the Physical View of Architecture School) and referenced here. The default is None.

    Message-Type

    The IMS™ message structure type.

    Transaction

    The transaction code that enables IMS™ to understand the type of work.
    Note: Test Integrations and APIs routes the virtualized traffic based on the Datastore, the Client ID, the Message-type, and the Transaction Code.

    Ensure that the Datastore and Code Page fields contain the required values.

  6. Click OK.

Results

You can now use Test Integrations and APIs to virtualize the traffic for the selected IMS™ Connect transport.