How to create a custom integration interface in SOA Gateway. This example will illustrate on how to develop a simple interface using PLSQL. The Integration Repository will recognize integrations through annotations in the code details about annotations can be found in the Integrated SOA Gateway Developers Guide, Appendix A. You can annotate. For PLSQL packages, only the package spec should be annotated. Do not annotate the body. Example of a annotated package spec CREATE OR REPLACE PACKAGE xxtestsoagway AS. Header. This package returns different data from Financials GL. S. rep category BUSINESSENTITY GLACCOUNTCOMBINATION. PSEGMENT1 varchar. Multitenant/opatch_02.png' alt='How To Rollback A Failed Patch In Oracle' title='How To Rollback A Failed Patch In Oracle' />Background Overview. The following documentation provides instructions for upgrading an Oracle 10. Oracle 11. 2 database residing on Sun Solaris 10. Segment 1. param PSEGMENT2 varchar. Segment 2. param PSEGMENT3 varchar. Segment 3. param PSEGMENT4 varchar. Segment 4. param PSEGMENT5 varchar. Segment 5. rep scope public. Return CCID. FUNCTION getccid PSEGMENT1 IN VARCHAR2. PSEGMENT2 IN VARCHAR2. PSEGMENT3 IN VARCHAR2. PSEGMENT4 IN VARCHAR2. PSEGMENT5 IN VARCHAR2 RETURN NUMBER. END xxtestsoagway Note The annotation BUSINESSENTITY is where in the Integration Repository your custom integration will be found. The below queries will help you find the correct BUSINESSENTITY. Its not possible to add your own BUSINESSENTITYs in the current version. SELECT FROM fndlookupassignments WHERE lookuptype BUSINESSENTITYSELECT FROM fndlookups WHERE lookuptype BUSINESSENTITYIn the example above a package called xxtestsoagway is created with one function called getccid. The function will return a code combination id for the segment parameters that we are using in the request. The package body is saved on the local hard drive as xxtestsoagway. The next step is to create an i. LDT file Integration Repository loader file that we should use to upload to the Integration Repository. Application using JDBC 10. Oracle 9i to 10g. JDBC Version 10. 1. The file is created with a tool called Integration Repository Parser IREP Parser, the tool will validate the file against the annotation standards. Before the i. LDT file can be created xxtestsoagway. In this case we will put the file in GLTOPpatch1. Run the command to generate the i. LDT file IASORACLEHOMEperlbinperl FNDTOPbinirepparser. Note If you are generating a new i. LDT file for an already uploaded interface you need to add a higher version number then the last uploaded. IASORACLEHOMEperlbinperl FNDTOPbinirepparser. When the i. LDT file is successfully created we can upload it to the Integration Repository using FNDTOPbinFNDLOAD appsapps 0 Y UPLOAD FNDTOPpatch1. Successfully uploaded to the Integration Repository. Now the package needs to be created in the database. CREATE OR REPLACE PACKAGE xxtestsoagway AS. Header. This package returns different data from Financials GL. To manually repair your Windows registry, first you need to create a backup by exporting a portion of the registry related to oci. Oracle 8i Enterprise. S. rep category BUSINESSENTITY GLACCOUNTCOMBINATION. PSEGMENT1 varchar. Segment 1. param PSEGMENT2 varchar. Segment 2. param PSEGMENT3 varchar. Segment 3. param PSEGMENT4 varchar. Segment 4. param PSEGMENT5 varchar. Segment 5. rep scope public. Return CCID. FUNCTION getccid PSEGMENT1 IN VARCHAR2. PSEGMENT2 IN VARCHAR2. PSEGMENT3 IN VARCHAR2. PSEGMENT4 IN VARCHAR2. PSEGMENT5 IN VARCHAR2 RETURN NUMBER. END xxtestsoagway. PACKAGE BODY xxtestsoagway AS. FUNCTION getccid PSEGMENT1 IN VARCHAR2. PSEGMENT2 IN VARCHAR2. PSEGMENT3 IN VARCHAR2. PSEGMENT4 IN VARCHAR2. PSEGMENT5 IN VARCHAR2 RETURN NUMBER AS. NUMBER. SELECT codecombinationid INTO vccid. FROM glcodecombinations. WHERE NVLsegment. NVLPSEGMENT1,. AND NVLsegment. NVLPSEGMENT2,. AND NVLsegment. NVLPSEGMENT3,. AND NVLsegment. NVLPSEGMENT4,. AND NVLsegment. NVLPSEGMENT5,. AND enabledflag Y. Frisco Texas Drivers License Renewal more. RETURN vccid. WHEN nodatafound THEN. RETURN 9. 9. WHEN toomanyrows THEN. RETURN 9. 0. END getccid. END xxtestsoagway. When the code have been successfully compiled we need to service enable the new integration interface. Go back to the xxtestsoagway PLSQL interface and click on the button Generate WSDL. After the generation of the WSDL a link will appear in the interface page. The next step is to deploy the web service and is simply done by clicking the Deploy button. When the web service is deployed it is possible to Redploy and Undeploy the service. The last thing before we can invoke the web service is to set the Grant, this is done by clicking the Create Grant button. In this example set the Grantee Type to All users. Before the web service can be invoked we need to restart the Application server and clear the cache. Restartcd INSTTOPadminscripts. Clear cache. Use responsibility Functional Administrator and go to Core Services Caching Framework Global Configuration Clear all cache. Now the web service is deployed and ready to be invoked. By using the tool soap. UI it is easy to unit test the newly created service download from www. Open soap. UI and create a new project. Paste the WSDL link from the E Business Suite Integration Repository and select some options in the SOAP UI new project dialog. Add username and password enduser in E Business Suite, encrypted password not supported at the moment and add parameters for segment 1 5. Then click the submit request top left corner in Request 1 window to invoke the web service. The response will be shown in the right side of the window.