You can send and receive messages in HCL OneTest API by using an EMS server over an SSL connection. You must ensure that the appropriate EMS version is enabled in the Library Manager.

The following procedure is for a sample configuration. Make appropriate changes according to your environment.

  1. Start HCL OneTest API, or restart it if it is already running.
  2. Press F8 to switch to the Logical View in Architecture School.
  3. Create a TIBCO EMS Domain. Right-click and click New > TIBCO > TIBCO EMS Domain.
  4. Enter "ems ssl" as the EMS Domain name.
  5. Switch to the Physical View and add a TIBCO EMS Broker. Right-click the Physical folder and click New > TIBCO > TIBCO EMS Broker.
  6. Double-click to edit the new broker, and enter the following JNDI details:
    Field Value
    Initial Context Factory com.tibco.tibjms.naming.TibjmsInitialContextFactory
    Provider URLs tibjmsnaming://localhost:7243
    Username SSHTest
    Password password
  7. Add the following custom properties to the transport. See step 2 in the topic "Sending EMS messages":
    Name Value
    com.tibco.tibjms.naming.security_protocol ssl
    com.tibco.tibjms.naming.ssl_enable_verify_host true
    com.tibco.tibjms.naming.ssl_expected_hostname server
    com.tibco.tibjms.naming.ssl_identity C:\tibco\ems\samples\certs\client_identity.p12
    com.tibco.tibjms.naming.ssl_password password
    com.tibco.tibjms.naming.ssl_trusted_certs c:\tibco\ems\samples\certs\server_root.cert.pem
    com.tibco.tibjms.naming.ssl_vendor j2se-default
    com.tibco.tibjms.naming.ssl_trace true

    If you want to enable SSL debugging output when diagnosing failed connections, you can add the property com.tibco.tibjms.naming.ssl_trace with the value true.

  8. Click Test Transport to make sure that the configuration is valid. Click Details to see more information about the connection success or failure.
  9. Create a test in the Test Factory. Press F10 and add a Publish action that uses the ems ssl transport. Verify the test.