Creating physical WebSphere® Application Server transports

Before you can synchronize an external logical resource for an IBM® WebSphere® Application Server instance, you must first create a physical connection in your HCL DevOps Test Integrations and APIs (Test Integrations and APIs) project to the WebSphere® Application Server instance.

About this task

If security is enabled in WebSphere® Application Server, you must configure the required SSL settings when creating a physical WebSphere® Application Server resource in Test Integrations and APIs.

As a minimum, you need to choose an identity store to use as the trust store for the connection. This will enable Test Integrations and APIs to validate the identity of the application server before presenting the user name and password to it. If you are connecting to an application server instance that requires client authentication, you must also choose an identity store to use as the keystore.

To set up appropriate identity stores, do these two tasks:
  1. Create a new identity store in your Test Integrations and APIs project.
  2. Import the trust certificates and identity keys from the application server into that store.

Procedure

  1. Open the Physical View of the Architecture School perspective of Test Integrations and APIs .
  2. On the toolbar of the Physical View, click IBM > IBM WebSphere Application Server. The WebSphere® Application Server window is displayed.
  3. Optional: In the Name field, enter the name of the connection to the WebSphere® Application Server instance.
  4. In the Host field, enter the host name or IP address of the computer where the WebSphere® Application Server instance is located.
  5. In the SOAP Connector Port field, modify the port number as required.
  6. If the WebSphere® Application Server instance has security enabled, you must complete the following tasks:
    1. Enter the user name and password required to access the WebSphere® Application Server instance.
    2. From the Trust store list, select an imported trust store file.
      Note: If using default WebSphere® Application Server security settings, importing the certificates from WebSphere Application Server installation directory\AppServer\profiles\Profile name\etc\trust.p12 into the store will be sufficient.
    3. From the Key store list, select an imported key store file if the WebSphere® Application Server instance uses client authentication.
      Note: If client authentication is required, you must also import the certificates and keys from WebSphere Application Server installation directory\AppServer\profiles\Profile name\etc\key.p12.
      Note: Ensure that the Config tab contains connection settings for the relevant deployment manager if the following two conditions are satisfied:
      • If you are using Test Integrations and APIs 8.5.0 or later with WebSphere® Application Server Network Deployment
      • If you are using federated servers and one or more deployment managers
  7. Click Test Transport to verify that the connection works.
  8. Click OK to close the Transport Test Results message window.
  9. Click OK to close the IBM® WebSphere® Application Server window.

Results

The new physical connection is added to your Test Integrations and APIs project.