Configuring the HTTPRequest and HTTPAsyncRequest nodes to use SSL (HTTPS)
Configure the HTTPRequest or HTTPAsyncRequest nodes to communicate with other applications that use HTTP over SSL.
Before you begin
About this task
This topic describes the steps that you need to follow when configuring an HTTPRequest node on a Windows system. The steps that you must follow on other operating systems are almost identical.
To enable an HTTPRequest node to communicate using HTTP over SSL, an HTTPS server application is required. The information provided in this topic shows how to use the HTTPInput node for SSL as the server application, but the same details also apply when you are using any other server application. You specify the appropriate SSL client Authentication key alias field (Key Alias) on the HTTPRequest node or HTTPAsyncRequest node when the server key store contains multiple certificates for the server.
Creating a message flow to make HTTPS requests
About this task
The following message flow creates a generic message flow for converting a WebSphere® MQ message into an HTTP Request:
Procedure
What to do next
The message flow is now ready to be deployed to the integration node and tested.
Testing your example
About this task
To test that the example works, complete the following steps:
Procedure
- Follow the instructions in Configuring HTTPInput and HTTPReply nodes to use SSL (HTTPS), including testing the example.
- Deploy the HTTPRequest message flow.
- Put a message to the WebSphere MQ queue
HTTPS.IN1. If successful, a message appears on the output queue. If the process fails, an error appears in the local error log (which is the event log on Windows).