IBM BJ0NJML Integration Guide - Page 209
Dedicated Message Processing Servers, Server Cluster Configuration, Global Directory
View all IBM BJ0NJML manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 209 highlights
Dedicated Message Processing Servers run on any server in the cluster. Once messages are in the queue, the application server that is running the JMS consumer cron task processes messages in a sequential order. Unlike the continuous queue, there is no multi-threading of messages by design. A cluster implementation does not significantly impact the processing performance of messages that process through the sequential queue. Dedicated Message Processing Servers High volumes of system inbound messages can cause the application server to run slowly, impacting online application users. One way to improve server efficiency is to move the integration framework inbound message processing to a separate application server or cluster. A separate server or cluster that is dedicated to inbound processing enables the system to process higher volumes of messages without compromising application usability. Server Cluster Configuration To configure a server cluster that is dedicated to processing inbound messages, deploy a separate application EAR file and the target-enabled cron tasks for polling the inbound queues, interface table, and inbound file processing to the server cluster. If applicable, configure the message-driven beans to pull data from the inbound continuous queue. You can run other background processing cron tasks on this server cluster. You can grant user interface access to users who must make use of the integration framework Data Import feature. When you configure separate inbound processing, do not enable message-driven beans for inbound processing within the server or cluster that is dedicated for online users. Global Directory In a cluster environment, the global directory must be accessible to all members of the cluster. To define the global directory, update the mxe.int.globaldir system property in the System Properties application. Inbound Message Receipt All object structure, enterprise, and standard services can be accessed by using the following components: T Java™ remote method invocation (RMI), Internet Inter-ORB Protocol™ (IIOP), and enterprise beans T HTTP and HTTPS Servlet T SOAP, HTTP, and HTTPS Servlet Cluster Configuration 195