Creating the IMS Connect transport

You create an IBM® IMS™ Connect transport when you create a logical IBM IMS Connect resource in HCL OneTest™ API’s Architecture School. Starting in version 9.2, the IBM IMS Connect transport supports forwarding proxy to assist with your testing.

About this task

To create a logical IMS Connect resource, in Architecture School, in the Logical view, select a component in which to create the resource, or create it separately. Then, right-click and select New > IBM > IBM IMS Connect.

To create an IBM IMS Connection transport, do the following steps:

Procedure

Set the binding for the IBM IMS Connection physical resource by using one of these steps:
  • In the Logical view, right click the IBM IMS Connect resource and select Set Binding in > Env > Create new IBM IMS Connect.
  • In the Physical view, click IBM > IBM IMS Connect.

    The New IBM IMS Connect window is displayed.

Field Description

Name

The name of the IMS Connect Transport.

Host

The host name or IP address of the IMS Connect server.

Port The port number where the IMS Connect server is listening (the default is 9941).

Port Forwarding Proxy

The Port Forwarding Proxy settings help you to specify a proxy through which HCL OneTest API will connect to the computer that hosts the IMS Connect transport server. By using a port forwarding configuration in the HCL OneTest API TCP Proxy, you enable the messages sent by HCL OneTest API to pass through the proxy. This allows you to record them for later use (in test and stub resources).

Host The host name or IP address of the proxy through which to connect to the computer that hosts the IMS Connect transport server.
Port The port number of the proxy through which to connect to the computer that hosts the IMS Connect transport server.

Code Page

The code page number.

A suggested value for use when saving events as tests or stubs by using the events generated by a transport monitor (the Save wizard of the Recording Studio). If the events are generated by an Operation monitor, then the value from the Operation editor is used as a "suggestion" when saving tests and stubs. If the generated tests or stubs contain byte arrays or COBOL Copybook data or both in the messages, then the value is used as the encoding value in the schema properties. The code page value is also displayed in the header of IMS messages.

Note: The Code Page field was added to the IMS Connect transport editor to be used when messages are recorded since it is not possible to determine the code page from the raw TCP traffic. When you use a transport monitor to record, the Code Page field of the transport editor is used. When you use an operation monitor to record, the Code Page field from the Operation editor is used.

Encryption Type

The type of ciphers that are allowed.

For details, see SSL encryption type.

The SSL settings are described in the following table:
Table 1. Web server wizard, SSL page fields
Field Description
Use SSL Select this check box to enable security for the transport.

Selecting the check box makes the other controls on the SSL tab available. You can enable security for Testing (Client) or for Virtualization (Server) or both.

Server certificates to trust All available identity stores are displayed in the drop-down menu. Select one of the following menu items:
Trust All
To accept any certificate presented by the server, regardless of its validity. This option is the default, and assumes you are focused on testing an application rather than the security of the server.
New
To define a new identity store.
Identity store
To specify an identity store that contains certificates that the client is to trust.
Client identities to give to server All available identity stores are displayed in the drop-down menu. If you use mutual authentication, a suitable identity is selected from the chosen identity store. Select one of the following menu items:
None
If the server does not request an identity.
New
To define a new identity store.
Identity store
To use an existing identity store. Specify an alias in the Identity field.
Certificate source All available identity stores are displayed in the drop-down menu. You can select one of the following menu items:
Generated
To use a certificate that HCL OneTest API generates for you. The source for that certificate is displayed in the Signed by field.
New
To define a new identity store.
Identity store
To use a certificate from an identity store.
Signed by If you chose Generated in the Certificate source field, this field holds the location of a certificate within the HCL OneTest API installation directory that is used to generate the new certificate. This is a read-only field.
Identity If you specified an identity store in the Certificate source field, use this field to specify the alias of a key in that identity store.
Certificate Authorities a stub will trust All available identity stores are displayed in the drop-down menu. You can select one of the following menu items:
Trust All
To accept any certificate presented by the client.
New
To define a new identity store.
Identity store
To specify an identity store that contains certificates that the stub is to trust.
Override default protocols If you are required to use a specific version of the secure sockets protocol, such as SSLv2 or TLSv1.2, enter that algorithm name here. For a complete list of algorithms, see Standard Algorithm Name Documentation.
Feedback