Before you start
Configuring a Secure Sockets Layer (SSL) is important to implement security during Web service calls. The SSL is used to transport SOAP messages between a client and a Web service over HTTP.
This tutorial provides steps to configure an SSL for a Web service request from WebSphere Process Server (hereafter called Process Server) to a Web service running outside the WebSphere environment. In many scenarios, during the development of Process Server and WebSphere Enterprise Service Bus (ESB) modules, a developer is dependent on the external systems or Web services to be available to configure and test the SSL. This tutorial isolates the need of having the endpoint available and running by generating the sample server keys and mocking the Web services by using the SOAP UI to test and configure the SSL.
Consider the Process Server module as a client and the endpoint outside the WebSphere environment as the server. Since the client connects to the server, the client has to import the server's public key into its truststore, and the server decrypts the data using its private key as shown in Figure 1.
Figure 1. Client server key and trust stores
In the above scenario, the SSL is configured for server authentication. However, if the SSL is configured for client authentication, it will fail because the server does not have the client's public key in its truststore.
This tutorial covers the following steps:
- Generating the client and sample server keystore and truststore using the ikeyman tool
- Importing the server certificate into the Process Server trust store
- Mocking the Web services using the SOAP UI
- Testing the SSL connection
Note: The SOAP UI is the world's leading Open Source Functional Testing tool for Web service testing. It is the leading desktop application for inspecting, invoking, monitoring, simulating or mocking, as well as functional testing, security testing, and so on.
- You must be familiar with the SOAP UI.
- You need to have good hands-on experience in configuring Process Server and performing administrative activities.
- You need to have an understanding of Web services.
- You must be familiar with WebSphere Integration Developer (hereafter called Integration Developer) and using it as a development tool.
- Microsoft® Windows® machine
- SOAP UI
- IBM® WebSphere Integration Developer V7 installed with a WebSphere Process Server V7 test environment
In this tutorial, the following directories are used as the installation paths for the components:
- WebSphere Integration Developer root:
- WebSphere Process Server root:
This tutorial will take about 2 to 3 hours to complete.