Synchronization of resources in HCL OneTest™ API

You can find information about the synchronization feature in HCL OneTest™ API so that you can model a system for testing with IBM® Integration Bus. After you create a logical integration node for IBM® Integration Bus in HCL OneTest™ API, you can set up the integration node as a synchronization source.

In IBM® Integration Bus, an integration server is a named group of message flows that is assigned to an integration node. HCL OneTest™ API uses integration servers to provide a level of filtering during synchronization. When IBM® Integration Bus is a shared resource used by several teams with each team having a separate integration server, HCL OneTest™ API creates operations for each of the integration servers during synchronization.

A logical integration node becomes the container for many of the resources created during synchronization. For example, operations that are based on the message flows of the selected IBM® Integration Bus integration servers.

Supported message flow nodes and transports in IBM® Integration Bus

When you synchronize HCL OneTest™ API with IBM® Integration Bus, the logical integration node asset is populated with service components and other artifacts in the HCL OneTest™ API project.

During synchronization, HCL OneTest™ API queries the IBM® Integration Bus integration node and retrieves details about applications and message flows deployed on the integration node. After synchronization, the following views of the Architecture School perspective in HCL OneTest™ API are populated:
  • The Logical View is populated with service components that represent the applications and message flows. Within these service components, operations are created to reflect the capabilities of the message flow.

    For example, a message flow that includes a WebSphere® MQ Input node and a WebSphere® MQ Reply node is mapped to a Request-Reply operation bound to a WebSphere® MQ transport.

  • The Physical View is populated with the physical configurations for the logical transports that were created in Logical View.
Note: If the applications and message flows use nodes that are not currently supported by synchronization but HCL OneTest™ API is capable of testing or virtualizing the associated transport, then you must manually create service components and operations to model the system.

Operations

After HCL OneTest™ API is synchronized with IBM® Integration Bus, the logical integration bus is populated with operations that correspond to the message flow nodes within the broker message flows.

Each supported message flow node that exposes a service endpoint or that which consumes another service endpoint is mapped to an operation in the logical model of the HCL OneTest™ API project.

Before you select the tests to create based on the operation created, you must review the message exchange pattern (MEP) for that operation.

Before you select the stubs to create for an operation, you must review the stub settings for the operation.

The following nodes are supported to be created as operations in HCL OneTest™ API:

CICS nodes

When HCL OneTest™ API is synchronized with IBM® Integration Bus, the supported CICS nodes are analyzed and mapped to operations in HCL OneTest™ API.

The CICSRequest node for CICS in IBM® Integration Bus is supported in HCL OneTest™ API.

HTTP nodes

Note: HCL OneTest™ API does not support synchronization of IBM® Integration Bus integration node by using HTTPS.
When HCL OneTest™ API is synchronized with IBM® Integration Bus, the supported HTTP nodes are analyzed and mapped to operations in HCL OneTest™ API.
The following nodes for HTTP in IBM® Integration Bus are supported in HCL OneTest™ API:
  • HTTPAsyncRequest
  • HTTPInput
  • HTTPRequest
  • HTTPReply
  • HTTPHeader
  • HTTPAsynchronousResponse

IMS nodes

When HCL OneTest™ API is synchronized with IBM® Integration Bus, the supported IMS nodes are analyzed and mapped to operations in HCL OneTest™ API.

The IMSRequest node for IMS in IBM® Integration Bus is supported in HCL OneTest™ API.

MQTT nodes

When HCL OneTest™ API is synchronized with IBM® Integration Bus, the supported MQTT nodes are analyzed and mapped to operations in HCL OneTest™ API.

The following nodes for MQTT in IBM® Integration Bus are supported in HCL OneTest™ API:
  • MQTTSubscribe
  • MQTTPublish

Web services nodes

When HCL OneTest™ API is synchronized with IBM® Integration Bus, the HTTP-based supported web services nodes are analyzed and mapped to operations in HCL OneTest™ API.

WebSphere® MQ nodes

When HCL OneTest™ API is synchronized with IBM® Integration Bus, the supported message flow nodes are analyzed and mapped to operations in HCL OneTest™ API.

The following nodes for WebSphere® MQ in IBM® Integration Bus are supported in HCL OneTest™ API:
  • MQInput
  • MQOutput
  • MQReply
  • MQGet
  • MQHeader

You can start the synchronization with IBM® Integration Bus from HCL OneTest™ API. See Synchronizing HCL OneTest API with the IBM Integration Bus integration node.