Dedicated Message Processing Servers; Server Cluster Configuration; Global Directory; Inbound Message Receipt - IBM BJ0NJML - Service And Asset Management Integration Manual

Dedicated Message Processing Servers

Server Cluster Configuration

Global Directory

Inbound Message Receipt

Cluster Configuration
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.
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.
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.
In a cluster environment, the global directory must be accessible to all members of
the cluster. To define the global directory, update the
property in the System Properties application.
All object structure, enterprise, and standard services can be accessed by using
the following components:
Java™ remote method invocation (RMI), Internet Inter-ORB Protocol™
(IIOP), and enterprise beans
HTTP and HTTPS Servlet
SOAP, HTTP, and HTTPS Servlet
Dedicated Message Processing Servers
mxe.int.globaldir system
195