| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Designing: IBM WebSphere MQ Server and Queue Manager Limits and Settings |
|
Creating a Runtime Environment
Designing Business Processes in the Sun Business Process Manager
Working with TCP/IP HL7 Collaborations
Developing Sun Master Indexes (Repository)
Developing Sun Master Patient Indexes
Developing OTDs for Application Adapters
Developing OTDs for Communication Adapters
Developing OTDs for Database Adapters
Developing OTDs for Web Server Adapters
Designing with Application Adapters
Building an Oracle Applications Custom Pre-Validation Package
To Build a Custom Pre-Validation Package for a Non-Supported Open Interface
Concurrent Manager Request Function
Naming Conventions for the Oracle Interface
Oracle Applications Manufacturing Module
Oracle Applications Financial Module
Oracle Applications Validation Error Codes
Configuring the PeopleSoft Server for the PeopleSoft Adapter Projects
Configuring PeopleSoft for Enterprise Service Bus Posting
Additional HTTP Configurations
Verifying PeopleSoft Server Logs
Notes on PeopleSoft Server Disconnections for JMS
Creating the PeopleSoft Node to Receive Enterprise Service Bus HTTP Posts
Activating the Message Definition to Receive Enterprise Service Bus Posts
Defining Message Channel Routing Rules
Adding the PeopleSoft Subscription Handler
Creating an HTTP Adapter Message Node
Activating the Message Definition for Subscription
Defining the Message Channel Routing Rules
Adding the HTTP Publication Handler
Accessing Non-Local Queue Managers and Non-Local Queues
To Connect to a Remote WebSphere MQ Queue.
Creating the WebSphere MQ Queue
To Create the WebSphere MQ Queue
Designing with Communication Adapters
Designing with Web Server Adapters
Designing with Sun JCA Adapters
When using the WebSphere MQ queue manager on UNIX, you must be a member of the mqm group to create and start the MQ queue manager.
It is essential that the WebSphere MQ Administrator regularly monitor the number of messages in the queue. Message expiration settings should be set to allow for extended storage.
WebSphere MQ is limited in the number of messages that can be sent before a commit is executed, and the number of physical messages that can exist on the queue at any one time. This can result in exception errors when upper limits for these numbers are exceeded. Memory and performance of the specific server may also effect the results.