Migrating the IBM Web Service binding (SOAP/HTTP)

The IBM® Web Service binding (SOAP/HTTP) for a BPEL process or other service type can be migrated to the recommended SCA construct.

About this task

In WebSphere® Studio Application Developer Integration Edition, this binding type gave clients the ability to communicate with a BPEL process or other service type by invoking an IBM Web Service, where the communication protocol was HTTP and the message adhered to the SOAP encoding rules.

The following example shows the conventions used when generating an IBM Web Service (SOAP/HTTP) for a 5.1 BPEL service. The JNDI name of the generated IBM Web Service was a combination of the BPEL's name, target namespace, and valid-from timestamp, as well as the name of the interface (WSDL port type that the deployment code was generated for). For example, these attributes can be found by examining the BPEL process' properties in the BPEL editor on the Description and Server content tabs:

Table 1. Generated namespace
Process name	MyService
Target namespace	`http://www.example.com/process87787141/`
Valid From	Jan 01 2003 02:03:04
Interface	ProcessPortType

The generated namespace for this example is then com/example/www/process87787141/MyService20030101T020304_ProcessPortTypePT.

In WebSphere Studio Application Developer Integration Edition when the IBM Web Service binding (SOAP/HTTP) was selected as the deployment type for a BPEL process or other service type, the following options were given:

For Document Style, the default was RPC / other option: DOCUMENT
For Document Use, the default was ENCODED / other option: LITERAL
For Router Address, the default was http://localhost:9080

A WSDL file specifying the IBM Web Service SOAP/HTTP binding and service is created in the generated Web and EJB projects but not in the service project itself. This means that you must manually locate that file and copy it to your business integration module project if it is important that the IBM Web Service client code must not change. By default, this WSDL file was created in the Web project at WebContent/WEB-INF/wsdl/<business process name>_<business process interface port type name>_HTTP.wsdl

The WSDL PortType and Messages of the business process interface are actually copied to this WSDL file as well rather than referencing the existing WSDL PortType and Messages defined in the service project.

If it is important that the IBM Web Service client code remain unchanged after migration, then the information in this file will be needed for the manual migration steps below.

There are two options for migrating the WebSphere Studio Application Developer Integration Edition SOAP/HTTP process binding. The choice will have to be made whether to migrate the client to the SCA programming model or to leave it as a Web services client:

Note: After the manual migration steps have been completed, the client must be migrated to the new programming model as well. See the appropriate topic for the following client types:

Table 2. Further information for migrating clients
Client type	For further information see
IBM Web service client	"Migrating the IBM Web service (SOAP/HTTP) client"