Using the HTTP Binding Component

Web Service Client Calling an Operation Using SSL Authentication

In this example, a client invokes a service that requires SSL Authentication. This example assumes that you are running a deployed BPEL project with a WSDL configured for SSL Authentication. This BPEL project invokes a service that is protected by SSL Authentication.

Results

The service receives the expected SOAP Message through HTTP after verifying the security credentials.

Main Scenario

  1. The BPEL process acts as the client to the service implementation. The abstract operation has a concrete HTTP SOAP binding, so the client must use SOAP over HTTP protocol to properly invoke the operation.

  2. The HTTP Binding Component receives the SOAP message, converts it to a normalized message, and forwards the message to the Normalized Message Router to the awaiting BPEL process.

  3. The BPEL Process, acting as the client, receives the abstract operation message and invokes a different in-only abstract operation. This operation has a concrete HTTP SOAP binding that requires SSL Authentication.

  4. When the client BPEL process invokes the abstract operation, a normalized message is generated and sent to the Normalized Message Router.

  5. The binding component picks up the normalized message and converts it to a SOAP message.

  6. The binding component establishes secure communication with the service provider and forwards the request to them.