| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Designing: Template DTD |
|
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
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 Data Type Definition (DTD) associated with the template XML file is shown:
<!ELEMENT OPEN_INTERFACE (Initialize_Script?,
Validation_Script?, Utility_Script, Concurrent_Manager,
Request_Param*, Concurrent_Manager_Status?, Interface_Table+,
Error_Handle?,
Pre_Required_Script*)>
<!-- Open interface name -->
<!ATTLIST OPEN_INTERFACE
Name CDATA #REQUIRED
>
<!-- Oracle Manufacturing Version -->
<!ATTLIST OPEN_INTERFACE
Version CDATA #REQUIRED
>
<!-- Application Suite -->
<!ATTLIST OPEN_INTERFACE
Application-Suite CDATA #REQUIRED
>
<!-- Module Name -->
<!ATTLIST OPEN_INTERFACE
Module CDATA #REQUIRED
>
<!-- utiltiy store procedure name at root level, this attribute is optional
if this attribute is specified, it overrides the default
name convention, which is derived from Name attribute of OPEN_INTERFACE
-->
<!ATTLIST OPEN_INTERFACE
Util_Name CDATA #IMPLIED
>
<!-- relative path to the sql script file for initialize package-->
<!ELEMENT Initialize_Script (#PCDATA)>
<!-- relative path to the sql script file for validation package -->
<!ELEMENT Validation_Script (#PCDATA)>
<!-- relative path to the sql script file for Utility package -->
<!ELEMENT Utility_Script (#PCDATA)>
<!-- relative path to the sql script file for concurrent manager
request function -->
<!ELEMENT Concurrent_Manager (#PCDATA)>
<!-- parameter description for concurrent manager request function -->
<!ELEMENT Request_Param (#PCDATA)>
<!-- relative path to the sql script file for function to retrieve
concurrent manager request status -->
<!ELEMENT Concurrent_Manager_Status (#PCDATA)>
<!-- Oracle Open Interface table definition -->
<!ELEMENT Interface_Table (Validation_Script?, Interface_Table*)>
<!-- name for the oracle open interface table -->
<!ATTLIST Interface_Table
Name CDATA #REQUIRED
>
<!-- name for SB staging table, this attribute is optional
if this attribute is set, the program directly uses
its value as the SB staging table for this specific
interface
-->
<!ATTLIST Interface_Table
SB_Name CDATA #IMPLIED
>
<!-- utility store procedure name at specific interface level,
this attribute is optional
if this attribute is specified, it overrides the default name convention,
which is
derived from the specific interface name
-->
<!ATTLIST Interface_Table
Util_Name CDATA #IMPLIED
>
<!-- Error handling definition -->
<!ELEMENT Error_Handle (Error_Table?, Error_PKG?)>
<!-- relative path to the sql script for creating error table -->
<!ELEMENT Error_Table (#PCDATA)>
<!-- relative path to the sql script for error handling -->
<!ELEMENT Error_PKG (#PCDATA)>
<!-- relative path to the sql script that needs to be compiled in order for
other stored procedure to be compiled successfully -->