Skip Navigation Links | |
Exit Print View | |
![]() |
Developing OTDs for Oracle Java CAPS Application Adapters Java CAPS Documentation |
Developing OTDs for Application Adapters
Date and Time Stamp Requirements
Installing SAP JCo for SAP BAPI
To Install SAP JCo on Windows 32
SAP JCo and SAP IDoc Class Library Installation
To Download the SAP Java IDoc Class Library
To Create IDoc OTDs Directly From SAP
To Create IDOC OTDs From a Description File
Exporting the IDOC File from SAP
To Download the IDoc Description File From SAP
Saving the IDoc Description File (After 4.6)
To Save the IDoc Description File From SAP
Configuring Your System Before Creating the OTD
Configuring NetBeans to Work with Siebel
Installing seebeyond.sif for Siebel 7.5.x
Installing SiebelMessage XSD Generation Process.xml for Siebel 7.7 and 7.8.x
Encoding Behavior for Redefinitions
enableUnmarshalValidation(boolean enable) Method
marshal(String charset) Method
marshal(OtdOutputStream out) Method
marshal(OtdOutputStream out, String charset) Method
unmarshal(OtdInputStream in) Method
unmarshal(OtdInputStream in, String charset) Method
unmarshal(byte[] in, String charset) Method
unmarshalFromString(String in) Method
useEncoding(String enc) Method
Exposed Oracle Applications OTD Nodes
SWIFT Alliance Gateway Adapter OTD Features
Generating DTDs from PeopleTools 8.13
Generating and Publishing an XML Test Message
To generate a PeopleSoft XML message
Extracting and Viewing the XML Test Message
Generating a DTD for the XML File
The Oracle Applications Adapter uses a wizard-based OTD builder to create OTDs based on your Oracle tables. The wizard queries the Oracle tables to determine the hierarchies of the interface tables for a particular module, and creates a corresponding OTD. It also sets up the necessary staging table and the stored validation procedures to be run against the table.
Figure 18 Oracle Applications OTD
When building an OTD, the wizard calls many JDBC APIs (for example, getProcedureColumns()) which in turn queries the database and returns the resultset. While the Adapter itself doesn’t issue the queries directly, it is the Oracle driver that translates the API into multiple queries. In a situation where there is a lot of data in the database, it may take a while to return all the resultsets to the wizard. The performance of the queries is dependent on the execution path which is formulated when a SQL call is prepared. Not having good statistics in the data dictionary could produce a long running query.
Oracle recommends doing the following to gather vital statistics to improve performance:
Set the following in either the init.ora file or spfile (whichever is appropriate for your installation):
_table_lookup_prefetch_size=0
Analyze the SYS schema for the system as follows:
Start SQL*Plus
Connect as the sys user
exec dbms_stats.gather_schema_stats(’SYS’);
Keep in mind that significant changes to the database would affect the data dictionary (like new tables, indexes, and so on). You should consider running the analysis regularly.
Note - Please consult your Database Administrator or Oracle before taking these steps as it may impact other applications.
The Object Type Definition Wizard appears.
The Specify Database Connection Information page appears.
Host Name - The server where Oracle Applications resides.
Port ID- The port number of Oracle Applications.
SID - The name of the Oracle instance (equivalent to the database name).
User Name - The user name that the Adapter uses to connect to the database.
Password - The password used to access the database.
The Select Oracle Applications Module window appears.
|
Note - A set of stored procedures are installed with the Oracle Applications Adapter. Unless these stored procedures are somehow deleted, the only way to create the OTD is by selecting Replace Existing Stored Procedures, otherwise, the existing stored procedures are not overwritten, an error appears, and the wizard stops.
The Specify the OTD Name window appears.
The Review Your Selections dialog box appears.
![]() | Caution - If the Oracle Applications DDL Scripts have not been properly installed, an error message occurs before the OTD can be successfully generated. |
The resulting OTD appears in the Java CAPS IDE. The time it takes the OTD to generate depends on the module you selected and your system performance.
The generated OTD appears in the OTD Editor. Nodes and methods for your OTD depend on the module you selected and the configuration of your tables.