Szenarios, mit deren Hilfe Sie sich mit der Funktionalität in WebSphere Message
Broker Version 8.0 vertraut machen können.
Scenario: Reusing common application logic in multiple integration solutions
In IBM® WebSphere Message
Broker Version 8.0, you use subflows to group common functionality that you want to
use several times within multiple integration solutions. You can create
subflows as a .subflow file or as a .msgflow file, although creating a .subflow file is the recommended approach for new developments.
Scenario: Transforming SOAP messages by using a message map
In WebSphere Message Broker, you can use message maps to transform SOAP messages. You can set
functions in a graphical data map to transform a SOAP input message
into a required SOAP output message.
Scenario: Converting a message map to a graphical data map
In previous versions of WebSphere Message Broker, you might have created a
message map. To edit your maps in WebSphere Message
Broker Version 8.0 or later, you must convert
message maps to graphical data maps.
Scenario: Updating a WebSphere Message Broker library
You can use libraries to store resources that are shared by multiple WebSphere Message Broker integration solutions (applications
and Message Broker projects). After the applications
and Message Broker projects are deployed, you can
update a library and then manage the deployment of the updated library resources to the applications
and Message Broker projects that reference the
library.