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.
Use this task to set tuning properties for the service integration environment.
To help optimize performance, you can set tuning properties that control the performance of message-driven beans and other messaging applications deployed to use service integration technologies.
Use this task to configure the throttling of messages for message-driven beans that you have deployed as JCA 1.5 resources on the default messaging provider.
Obtain an overview of improving the performance of messaging engine data stores.
Use this task to tune a mediation for performance by using the administrative console.
Use this task to enable container-managed persistence (CMP) entity beans to share the database connections used by the data store of a messaging engine. Performing this task has been estimated to provide a potential performance improvement of 15% for overall message throughput, but can only be used for entity beans connected to the application server that contains the messaging engine.