Deploying a custom PL/SQL API

This procedure explains the steps for packaging and deploying a Custom PL/SQL API in the Oracle Integration Repository.

Procedure

1. Create the PL/SQL package in the database.

   Annotate the custom PL/SQL API definition based on the Integration Repository annotation standards for the PL/SQL interface type.

2. Create the Integration Repository Loader File (iLDT) file in an SSH environment.

   Validate the annotated custom PL/SQL interface definitions against the annotation standards. The Integration Repository Parser (IREP Parser), a design-time tool, performs this validation by reading the annotated files and generating an iLDT file if no error occurs. For information on how to generate and upload the iLDT files, refer to Generating and Uploading iLDT Files.

3. Upload the generated iLDT file to the Oracle Integration Repository (App Server):

   Upload the iLDT file to the integration repository; it appears under the PL/SQL API interface type in the Integration Repository browser. To differentiate the custom interfaces from Oracle native packaged ones, all custom integration interfaces have Interface Source 'Custom' in contrast to Oracle interfaces with Interface Source 'Oracle' when you view them from the repository. Refer to: Uploading ILDT Files to Integration Repository, Oracle E-Business Suite Integrated SOA Gateway Implementation Guide.

4. Deploy the custom PL/SQL interface as REST services in the Oracle Integration Repository.

   Enter a unique service alias for each selected custom interface before deploying the service. Refer to: Deploying a Custom PL/SQL REST Web Services, Oracle E-Business Suite Integrated SOA Gateway Implementation Guide

5. Create the necessary security grants for the custom integration interfaces.

   Refer to: Creating Security Grants, Oracle E-Business Suite Integrated SOA Gateway Implementation Guide.