This section lists various limitations and best practices
for the iWay Application Adapter for Oracle E-Business Suite.
All Oracle packages are supported.
Oracle databases using Real Application Clusters (RAC) are supported.
Oracle functions are not supported.
XML gateway is not supported.
Custom data types of type Object, Table Types, and Nested Objects
are supported.
Nested tables
and tables comprised of non-scalar objects besides PL/SQL records are
not supported, for example, tables comprised of Oracle VARRAYs.
The schema generated
by the adapter has all Oracle API parameters as optional. There
is no way to determine which parameters are required and which are
optional from the data dictionary.
A package cannot
consist of two or more stored procedures with the same name.
Stored procedures
not within a package are supported. The adapter passes the same
string and API_NAME parameter, and just excludes the package name
while still passing two periods.
API_NAME = 'schema_name..procedure_name'
It is a best
practice to use the ojdbc14.jar thin driver. Other Oracle drivers
provided by various third-party application vendors may cause unexpected
behavior.
On some Oracle
application installations, the sequencing in the data dictionary
can be in reverse order. In these situations, the Oracle API must
be recompiled.
The adapter
supports custom APIs, but they should conform to all standard Oracle API
development methodology.
It is a best
practice to delete and archive the iway_wrapper_log.txt file periodically, as
this file can grow fairly large in size.