Migrate Service integration
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.
- Coexistence: Preserve or migrate a Version 5.1 gateway
Web services gateways running on WebSphere Application Server Version 5.1 can, subject to certain restrictions, coexist with gateway instances running on Version 7.0 or later application servers. Alternatively, we can migrate the Version 5.1 gateways and application servers to WAS v7 or later. To help you choose whether to preserve or migrate the Version 5.1 gateways, this topic explains the restrictions to gateway coexistence and the approach taken to gateway migration.
- Preserve a Version 5.1 gateway when migrating a cell
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 the Version 5.1 gateway configurations before you migrate the cell.
- Migrate a Version 5.1 web services gateway configuration
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.
- Add unique names to the bus authorization policy
How to update the authorization policy for the service integration bus with unique name entries.
- Migrate a messaging engine based on a data store
Depending on the existing settings, when migrating a messaging engine from older versions of WAS to Version 7.0 or later, we might have to create or alter database tables.
Administer Service integration
Scripting for Service integration
Establishing high availability for Service integration
Secure Service integration
Develop Service integration
Tune Service integration
Troubleshooting Service integration