WebSphere ESB conversion tool limitations
A number of constraints apply when you convert WebSphere® Enterprise Service Bus resources into IBM® Integration Bus resources by using the WebSphere ESB conversion tool.
For information about the resources that the WebSphere ESB conversion tool supports, see WebSphere ESB conversion tool technical overview. All other WebSphere Enterprise Service Bus resources must be converted manually. Also, be aware of the following specific constraints when you use 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:
- The WebSphere ESB
conversion tool supports
conversions for
Document/literal
andDocument/literal wrapped
WSDL bindings. - 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:
- Mediation module components that do not have an implementation type.
- Stand-alone References.
- A Reference to a target service with a multiplicity setting of 1..1 is converted.
Exports
- WebSphere ESB function selectors, when the WebSphere ESB conversion tool converts a mediation module into an application.
- WebSphere ESB custom function selectors.
- Custom data bindings.
Imports
- Imports with more than one interface.
- Imports with an asynchronous binding, such as MQ, JMS, MQ JMS, or Generic JMS, where the binding interface has one or more request-response operations.
- Imports with an SCA (native) binding, where the binding interface has one or more request-response operations.
- Custom data bindings.
Mediation primitives
- Promoted properties must be manually converted.
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:
- .map files from WebSphere Enterprise Service Bus Version 6.2 are converted to the format used by .map files in WebSphere Enterprise Service Bus Version 7.0 and later, and IBM Integration Bus Version 10.0.
- The following WebSphere Enterprise Service
Bus mapping
transforms are converted to IBM Integration Bus,
but the code might require manual conversion:
- Custom Java
- Custom XPath
- The following WebSphere Enterprise Service
Bus mapping
transforms are not converted to IBM Integration Bus;
you must manually replace these transforms with equivalent IBM Integration Bus transforms:
- Lookup
- Group
- Custom XSLT
- Mapping transforms that are defined on a Service Message Object
(SMO) element are converted to IBM Integration Bus,
except for transforms that are defined on the following elements.
You must manually map these elements to an equivalent part of the IBM Integration Bus message tree:
- Attachment elements
- Header elements
- Context elements (other than transient, shared, or correlation context elements)