Artifacts that the WebSphere ESB
conversion tool
produces
The WebSphere® ESB
conversion tool produces the following
IBM® Integration Bus artifacts from WebSphere Enterprise
Service Bus
resources.
The WebSphere ESB
conversion tool converts your WebSphere Enterprise
Service Bus WSDL file and creates a schema (.xsd) file for each inline schema
that is embedded in your WSDL file. The format of the converted WSDL file is different from the
original, but it is logically equivalent. For more information, see Generate WSDL.
One library project is created for each WebSphere Enterprise
Service Bus library.
One application project or one integration service project is
created for each WebSphere Enterprise
Service Bus mediation module.
An integration service project is created for any mediation
module that has a single export with a SOAP/HTTP binding.
An application project is created for all other WebSphere Enterprise
Service Bus
mediation modules.
One message flow is created for a mediation flow component. The message flow is equivalent to the mediation module assembly and all of its
constituent elements, for example, mediation flow component, imports and exports, from the WebSphere Integration Developer or IBM Integration Designer.
One subflow is created for each WebSphere Enterprise
Service Bus service operation. These
subflows are created in an application project or integration service project.
One message flownode is created
for a WebSphere Enterprise
Service Bus export that has an interface with one or more one-way operations.
One SOAPInputnode is
created for an export with a SOAP/HTTP binding or a SOAP/JMS binding.
A Passthroughnode is
created as a placeholder for any other type of export binding.
Two message flownodes are created
for a WebSphere Enterprise
Service Bus export that has an interface with at least one
request-response operation.
One SOAPInputnode and
one SOAPReplynode are
created for an export with a SOAP/HTTP binding or a SOAP/JMS binding.
Two Passthroughnodes
are created as placeholders for an export with any other type of binding.
One message flow node or one subflow is created for each WebSphere Enterprise
Service Bus mediation primitive.
A Mapping node is created for a Mapping mediation
primitive.
A JavaCompute node is created for a Message Element
Setter mediation primitive.
A Route node is created for a Message Filter mediation
primitive.
A subflow is created for all other WebSphere Enterprise
Service Bus mediation
primitives.
One SOAPRequest node, one Passthroughnode, or one
subflow is created for an import.
A SOAPRequestnode is
created for an import with a SOAP/HTTP or SOAP/JMS binding, that is referenced by a WebSphere Enterprise
Service Bus Callout mediation primitive.
A Passthroughnode is
created for an import with any other type of binding, that is referenced by a WebSphere Enterprise
Service Bus Callout mediation primitive.
A subflow is created for an import that is referenced by a WebSphere Enterprise
Service Bus Service Invoke mediation primitive.
Note: Any type of asynchronous WebSphere Enterprise
Service Bus request-response service invocation is converted into a
synchronous request-response service invocation.
Last updated Friday, 21 July 2017
