| Skip Navigation Links | |
| Exit Print View | |
|
Designing with Oracle Java CAPS Application Adapters Java CAPS Documentation |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Designing with Oracle Java CAPS Application Adapters Java CAPS Documentation |
Designing with Application Adapters
Building an Oracle Applications Custom Pre-Validation Package
Oracle Applications Adapter Pre-Validation Scripts
Oracle Application Adapter Pre-Validation Procedures
To Build a Custom Pre-Validation Package for a Non-Supported Open Interface
Oracle Application Adapter Concurrent Manager Request Function
Oracle Applications Adapter Template DTD
Naming Conventions for the Oracle Interface
Concurrent Manager Request Function
Oracle Applications Manufacturing Modules
Oracle Applications Inventory Module
Customer Items Cross-Reference
Oracle Applications Purchase Order Import Module
Oracle Applications Order Entry Module
Oracle Applications Financial Module
Oracle Applications Accounts Payable Module
Oracle Applications Accounts Receivable Module
Oracle Applications Cash Management Module
Oracle Applications Fixed Assets Module
Oracle Applications General Ledger Module
Oracle Applications Validation Error Codes
Oracle Applications Manufacturing Error Codes
Oracle Applications Financial Budget-GL Error Codes
Accounts Receivable Error Codes
Configuring the PeopleSoft Server for the PeopleSoft Adapter Projects
Configuring PeopleSoft for Enterprise Service Bus Posting
Additional HTTP Configurations
Starting and Stopping the JMS Listening Connector
Verifying PeopleSoft Server Logs
Notes on PeopleSoft Server Disconnections for JMS
To Create PeopleSoft Nodes to Receive Enterprise Service Bus HTTP Posts
To Activate 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
The first step in creating the sample Project for the WebSphere MQ Adapter is to install and configure IBM’s WebSphere MQ Server and MQ queue manager on the local host. It is assumed that the reader is experienced in the use of the WebSphere MQ queue manager. For the sample implementation, perform the following:
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.
|