iWay Application Adapter for Oracle E-Business Suite User's Guide > Introducing the iWay Application Adapter for Oracle E-Business Suite > Limitations and Best Practices

Limitations and Best Practices

This section lists various limitations and best practices for the iWay Application Adapter for Oracle E-Business Suite.

  1. All Oracle packages are supported.
  2. Oracle databases using Real Application Clusters (RAC) are supported.
  3. Oracle functions are not supported.
  4. XML gateway is not supported.
  5. Custom data types of type Object, Table Types, and Nested Objects are supported.
  6. Nested tables and tables comprised of non-scalar objects besides PL/SQL records are not supported, for example, tables comprised of Oracle VARRAYs.
  7. 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.
  8. A package cannot consist of two or more stored procedures with the same name.
  9. 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'
  10. 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.
  11. 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.
  12. The adapter supports custom APIs, but they should conform to all standard Oracle API development methodology.
  13. 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.