Building on top of Oracle Fusion Middleware and service-oriented architecture (SOA) technology, Oracle E-Business Suite Integrated SOA Gateway (ISG) is a complete set of service infrastructure to provide, consume, and administer Oracle E-Business Suite Web services. With service enablement feature, integration interfaces published in the Oracle Integration Repository can be transformed into SOAP and REST based Web services.
...
| Name | Code | Description | Default Value | Supported Values | ||
|---|---|---|---|---|---|---|
| Source | SOURCE | Object Source | SCM | SCM | ||
| Product | PRODUCT | EBS Product Name | Defaults to value provided in @rep:product <product> annotation | Any EBS product name | ||
| Service Alias | SERVICE_ALIAS | Service Alias | Defaults to value provide in @flexdeploy-rep:alias <alias> annotation. If not specified defaults to the name of the PLS/PKH package | Any alias name | ||
| Service Type | SERVICE_TYPE | Service Type | REST Defaults to value provide in @flexdeploy-rep:type <type> annotation. If not specified defaults to the name of the PLS/PKH package. If not specified, the service type defaults to REST. | REST | SOAP | BOTH
|
...
- ILDT
- Deploys the ILDT using FNDLOAD
- Deploys the web service using Ant
- PKH, PLS
- Copies the SQL files to the <Product Top>/patch/115/sql directory
- Generates the ILDT using Perl
- Deploys the ILDT using FNDLOAD
- Deploys the web service (REST) using Oracle supplied Ant script
Limitations
- SOAP services are not currently supported.
- Supported Support for REST services is currently limited to EBS 12.2.x.
- ILDTs can only be generated from PLS or PLH sql files which are annotated appropriately.
- Due to lack of available Oracle APIs, grants performed to the deployed services remains a manual step. Existing grants are preserved across deployments, but new grants and revoked grants must be performed manually.
- When redeploying an existing service, the version number must be incremented. If its not greater than the previous version, no errors occur, but it does not actually get deployed.
- The version number is generated by appending a build sequence number for the project to the Integrated SOA Gateway Version Prefix project property.
- To ensure the version gets auto-incremented with each deployment, all deployments should be initiated through the FlexDeploy project. Otherwise, you run the risk of the generated version being less than the current version.