| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Designing: Naming Conventions for the Oracle Interface |
|
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
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
IBM WebSphere MQ Server and Queue Manager Limits and Settings
Designing with Communication Adapters
Designing with Web Server Adapters
Designing with Sun JCA Adapters
The specific name for the Open Interface, which is specified in the XML file.
The name used for the generated utility stored procedures, for each interface table. It is derived from the corresponding Oracle Interface Table name as follows:
If the Oracle Interface Table name is longer than 23 characters, replace INTERFACE or IFACE_ALL with INT to form the short table name.
(Since there is a limitation of 30 characters placed on the function/stored procedure name in Oracle, the Open Interface name specified in the XML file must be no more than 23 characters).
The utility stored procedure names are derived from the Short Table name, according to the following convention:
Sb_XXX_<SHORT_TABLE_NAME>
The name of the staging table node is derived from the corresponding Oracle Interface Table name by adding the prefix SB_ and truncating it to 30 characters, if necessary.
If the SQL file is used to create a packaged stored procedure, the file name must be the same as the package name. The file name is case sensitive and must be less than or equal to 30 character due to the rules of Oracle procedure/function name.
The function name is derived from the Open Interface name specified in the XML, and has the form: FN_REQUEST_<ORACLE_INTERFACE_NAME>.