This page provides a starting point for finding information about service integration.
Service integration provides asynchronous messaging services. In asynchronous messaging, producing applications do not send messages directly to consuming applications. Instead, they send messages to destinations. Consuming applications receive messages from these destinations. A producing application can send a message and then continue processing without waiting until a consuming application receives the message. If necessary, the destination stores the message until the consuming application is ready to receive it.
When you migrate a cell to a later version, any previously configured gateway on any Version 5.1 application server in the cell is replaced with an empty gateway. Therefore you must preserve your Version 5.1 gateway configurations before you migrate the cell.
In WebSphere® Application Server Version 5.1, the web services gateway was a separable component with its own user interface. In later versions of the product, the gateway is integrated into service integration bus-enabled web services, and re-implemented as a mechanism for extending and linking inbound and outbound services. You use a wsadmin command script to migrate an existing gateway configuration from a Version 5.1 application server to an application server or cluster on a later version.
How to update the authorization policy for the service integration bus with unique name entries.
Depending on your existing settings, when migrating a messaging engine from older versions of WebSphere Application Server to Version 7.0, you might have to create a new data store table.