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.
| Tip | |
|---|---|
| title | FlexDeploy Support For ISGFlexDeploy currently supports REST services SOAP Services on EBS 12.1.3 and 12.2.x only. Support for SOAP services and REST services are supported on EBS 12.1.3 will be added in the future2.x only. |
Object Type Identification
Any .pkh or .pls package spec sql files which contain Integrated SOA Gateway annotations (@rep:).
Any .pkh or .pls files with
FDEBS_ISG_ROOT_SOURCE_DIRin the file path.Any .ildt file
| Tip |
|---|
Integrated SOA Gateway Root Source Directory on Project Properties tab defaults to isg, but you can update if you are keeping ISG Files in a different folder. |
File Extensions
.pls
.pkh
.ildt
Object Type Code
ISG
Attributes
Name | Code | Description | Default Value | Supported Values |
|---|---|---|---|---|
Source |
| Object Source | SCM | SCM |
Product |
| EBS Product Name | Defaults to value provided in @rep:product <product> annotation | Any EBS product name |
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 |
names | ||||||
Service Type |
| Service Type | 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
|
Related Project Properties
Name | Code | Description | Default Value | Supported Values |
|---|---|---|---|---|
Integrated SOA Gateway Version Prefix |
| The version number prefix to use when geneting ILDT from source files (e.g. 12.0). At deployment time a build sequence number is added to the prefix. The version number must be incremented |
with each deployment of the service. | 12.0 | Any value of the format #.#. | ||
Integrated SOA Gateway Root Source Directory |
| Source folder for Integrated SOA Gateway (ISG) files. Useful to categorize .pls or .pkh files as ISG objects if those files do not contain ISG annotations. | isg | Any value. |
Sample Build Commands
N/A - Build commands not supported for this type.
...
The EBS deploy operation will generate the necessary commands based on the type of file and the metadata which is captured on the project objects.
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
Creates the package on the target database if it doesn’t exist
Generates the ILDT using Perl
Deploys the ILDT using FNDLOAD
Deploys the web
serverservice (REST
or SOAP) 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
itsit's 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.