Configuring SOAPRequest and SOAPAsyncRequest nodes to use SSL (HTTPS)

On the HTTP Transport page of the properties for the node, set the following properties:

1. In the Web Service URL property, type the URL of the web service you want to call.
2. Optional: Select the Enable certificate revocation list checking property. For more information on Certificate Revocation List (CRL) checking see, Working with certificate revocation lists.
3. Set other SSL properties as appropriate.

1. Import the SOAP Nodes sample.
2. Enable SSL in the SOAPNodesSampleConsumerFlow message flow by completing the following steps:
   1. Open the Invoke_submitPO subflow.
   2. Change the HTTPTransport properties for the SOAPRequest node. In the Web Service URL field, make the following changes:
      • Change http to https
      • Change the port number to the port number of your HTTPSConnector port.
      Note: The default value of the HTTPSConnector port is 7843 but you can use the following command to verify the port number that is configured in your deployment.

      mqsireportproperties broker_name -e integration_server_name -o HTTPSConnector -n port 

      If there are no other HTTPS services in your deployment, the mqsireportproperties command returns a 0 and you should be able to use the default value of 7843 for the value of your HTTPSConnector port.
   3. If you set up your public key infrastructure by following the instructions that are detailed in Setting up a public key infrastructure, all other properties should be correct. Otherwise, you must select the appropriate protocol and change other SSL properties to match your configuration.
3. Enable SSL in the SOAPNodesSampleProvider message flow by opening the properties for the SOAPInput node and selecting Use HTTPS in the HTTP Transport properties panel.
4. If OrderService_SOAPNodesSampleProviderFlow and submitPO_OrderService_SOAPNodesSampleConsumerFlow are not already subflows, you must convert them to subflows. For more information about converting between message flows and subflows, see Converting between message flows and subflows.
5. Refresh the BAR file and deploy.
6. Test the sample. For example, you can test the sample by completing the following steps:
   1. From a web browser, enter the following URL.

      https://localhost:port_number/acmeOrders/WADDR/ProcessOrders

      where port_number is the port number of your HTTPSConnector port.
   2. When you are prompted to accept the certificate, click Yes.

   If you are using a self-signed certificate in your PKI infrastructure, the sample is working correctly if the browser window displays the message There is a problem with this web site's security certificate.

   If you are using a certificate from a certificate authority in your PKI infrastructure, the sample is working correctly if the browser displays a lock symbol next to the URL.

   Note: You can ignore any error messages that are associated with the sample.