Upgrade tasks

The sections below describe how to upgrade components from versions 1.x and 2.x of this product.

Web Services Generation Utility

The Web Services Generation Utility is no longer available. Instead, you use System Manager tools to expose collaborations as web services. None of the artifacts generated by the Web Services Generation Utility can be used with this release:

SOAP data handler

You can use the SOAP data handler with the web services connector only. This data handler cannot be used by any other connector nor by Server Access Interface. The sections below discuss additional support issues.

Meta-objects

The top-level SOAP data handler meta-object used with prior releases is no longer supported. Instead you must create a new top-level meta-object for use with the 3.0.x release SOAP data handler. This meta-object must have Classname and SOAPNameHandler attributes only.

The new meta-object no longer requires child meta objects for SOAP message-to-business-object and business-object -to-SOAP-message transformations. Accordingly, make sure that your top-level meta-object does not have SOAPToBOConfigMO and BOToSOAPConfigMO attributes.

The child meta-objects that previously described SOAP message-to-business-object and business-object -to-SOAP-message transformations must now be added as children of the SOAP Request, SOAP Response and SOAP Fault business objects. For further information, see SOAP data handler and Business object requirements.

Application-Specific Information

The new SOAP data handler features new application-specific information (ASI) functionality. You can take advantage of this enhancement by adding specific ASI to SOAP business objects, but doing so is not required. With the exception of adding child SOAP Config MOs to business objects, you can deploy SOAP business objects that you created with prior releases of the connector for use with the 3.0.x version.

Connector compatibility

You can use the new SOAP data handler with the 3.0.x web services connector only. The new SOAP data handler cannot be used with components from prior releases such as the SOAP connector or Server Access Interface.

You cannot use the old SOAP data handler with the 3.0.x web services connector.

SOAP connector

The SOAP connector is not supported with release 3.0.x. Instead, you must use the web services connector to invoke web services.

Web services connector

With release 3.0.x, you use the web services connector for both exposing collaborations as web services and invoking web services. New event notification functionality is used to expose collaborations as web services. New request processing features are now used to invoke web services. The sections below highlight the migration tasks that you must complete to use the web services connector.

Note:
The migration tasks discussed below may not be exhaustive. Also, you can complete the tasks in any order.

Event notification

The 3.0.x connector can invoke collaborations synchronously or asynchronously with no requirement for creating and deploying a proxy class on a web server. The connector now has a listener framework that notifies the connector of events. The listener framework supports SOAP/HTTP, SOAP/HTTPS and SOAP/JMS bindings. If you configure the listeners properly, the connector can detect and respond to web service clients on behalf of collaborations that have been exposed as web services. For further information on the listener framework and how to configure it, see Protocol listeners.

Business objects for event notification

You must create an event notification top-level object (TLO). The TLO is a container for a SOAP Request business object and, optionally (for synchronous request processing), a SOAP Response and SOAP Fault business object. The TLO's structural components anticipate a single web services operation: the SOAP Request business object corresponds to a SOAP request message, the SOAP Response business object corresponds to a SOAP response message, and the SOAP Fault business object corresponds to a SOAP fault message. For further information, see Synchronous event processing TLOs.

Event notification and SOAP business objects

The SOAP business objects used with Server Access Interface in prior releases may be used, with modifications described in SOAP data handler above, with the 3.0.x release. Note that you must specify SOAP business objects as children in the event notification TLO.

Request Processing

Like the SOAP connector in prior releases, the 3.0.x web services connector can invoke web services. In addition, the new connector supports invocation of web services with SOAP/JMS bindings. The sections below discuss further the changes in connector request processing.

Top-level objects request processing

You must create a request processing TLO. The TLO is a container for a SOAP Request business object and, optionally (for synchronous request processing), a SOAP Response and SOAP Fault business object. The TLO's structural components anticipate a single web services operation: the SOAP Request business object corresponds to a SOAP request message, the SOAP Response business object corresponds to a SOAP response message, and the SOAP Fault business object corresponds to a SOAP fault message. In this sense the 3.0.x request processing TLO corresponds to the TLO used with the SOAP connector from prior releases. For further information on request processing TLOs, see Synchronous request processing TLOs.

SOAP business objects

The SOAP business objects used with the SOAP connector of prior releases may be used with modifications as described inSOAP data handler. You must specify these business objects as children of a request processing TLO. Note that in previous releases these business objects were children of a TLO used with SOAP connector.

The 3.0.x web services connector has an additional requirement for SOAP Request business objects. Each SOAP Request business object must have an attribute of type Protocol Config MO (meta-object). The connector uses the Protocol Config MO to determine the destination of the request message. Each Protocol Config MO has a Destination attribute that gives the address of the target web service. If you are using SOAP/HTTP or SOAP/HTTPS to invoke the target web service, then the Destination attribute corresponds to the URL attribute of the TLO used with the SOAP connector from prior releases.For further information, see Protocol Config MO.

Copyright IBM Corp. 1997, 2003