WebSphere ESB conversion tool limitations

For information about the resources that the WebSphere ESB conversion tool supports, see Artifacts that the WebSphere ESB conversion tool produces. All other WebSphere Enterprise Service Bus resources must be converted manually. Also, be aware of the following specific constraints when using the WebSphere ESB conversion tool:

Workspace compatibility

You cannot share your workspace for IBM Integration Toolkit and IBM Integration Designer. To make WebSphere Enterprise Service Bus projects available for conversion, export a project interchange (PI) file in WebSphere Integration Developer or IBM Integration Designer, and then import the PI file into IBM Integration Toolkit by using the option WebSphere ESB Project Interchange. For more information, see Preparing WebSphere Enterprise Service Bus resources for conversion.

Project files

Convert your WebSphere Enterprise Service Bus Java™ projects manually.

WSDL files

The following constraints apply to your WebSphere Enterprise Service Bus WSDL files when you use the WebSphere ESB conversion tool:

1. The WebSphere ESB conversion tool supports conversions for Document/literal and Document/literal wrapped WSDL bindings.
2. The WSDL binding style Document/encoded is not supported in IBM Integration Bus.

Services

WebSphere Enterprise Service Bus services that include one or more operations and one or more exports are converted into IBM Integration Bus applications.

Mediation module components

The following constraints apply to your WebSphere Enterprise Service Bus mediation module components when you use the WebSphere ESB conversion tool:

• You must manually convert the following items:
  • WebSphere Enterprise Service Bus mediation modules with more than one export.
  • WebSphere Enterprise Service Bus mediation modules that are implemented with more than one mediation flow component.
  • WebSphere Enterprise Service Bus mediation modules that contain multiple interfaces.
  • Mediation module components that are implemented as a Java component or as a component that does not have an implementation type.
  • Stand-alone References.
  • Components that are not wired to an export.
• A Reference to a target service with a multiplicity setting of 1..1 is converted.

Exports

You must convert WebSphere Enterprise Service Bus exports manually in the following circumstances:

• WebSphere Enterprise Service Bus exports with more than one interface.
• Exports with a non SOAP/HTTP binding.
• WebSphere Enterprise Service Bus function selectors, when the WebSphere ESB conversion tool converts a mediation module into an application.
• WebSphere Enterprise Service Bus custom function selectors.
• Custom data bindings.

Imports

You must convert WebSphere Enterprise Service Bus import bindings manually in the following circumstances:

• Imports with more than one interface.
• Imports with a non SOAP/HTTP binding.
• Custom data bindings.

Mediation primitives

Business Object (BO) maps

BO Maps must be manually converted.

XML maps

The following constraints apply to your WebSphere Enterprise Service Bus XML maps when you use the WebSphere ESB conversion tool:

• The following WebSphere Enterprise Service Bus mapping transforms require manual conversion into IBM Integration Bus:
  • Lookup
  • Submap
  • Group
  • Custom XSLT
  • Custom Java
  • Custom XPath
• IBM Integration Bus does not support the mapping transforms Group and Lookup.
• A transform that is defined on a Service Message Object (SMO) attachment element must be manually converted.
• A transform that is defined on a Service Message Object (SMO) context element must be manually converted.
• A transform that is defined on a Service Message Object (SMO) header element must be manually converted.