Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

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.

Object Type Identification

  • Any .pkh or .pls package spec sql files which contain Integrated SOA Gateway annotations.
  • Any .ildt file

File Extensions

  • .pls
  • .pkh
  • .ildt

Object Type Code

ISG

Attributes

NameCodeDescriptionDefault ValueSupported Values
SourceSOURCEObject SourceSCMSCM
ProductPRODUCTEBS Product NameDefaults to value provided in @rep:product <product> annotationAny EBS product name
Service AliasSERVICE_ALIASService AliasDefaults to value provide in @flexdeploy-rep:alias <alias> annotation.  If not specified defaults to the name of the PLS/PKH packageAny alias name
Service TypeSERVICE_TYPEService TypeDefaults to value provide in @flexdeploy-rep:type <type> annotation.  If not specified defaults to REST.REST | SOAP

Related Project Properties

NameCodeDescriptionDefault ValueSupported Values
Integrated SOA Gateway Version PrefixFDEBS_ISG_VERSION_PREFIXThe 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 which each deployment of the service.12.0Any value of the format #.#.  

Sample Build Commands 

N/A - Build commands not supported for this type.

Sample Deploy Commands 

N/A - Deploy commands not supported for this type.

Details

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 server (REST or SOAP) 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 server (REST or SOAP) using Ant

Limitations

  • ILDTs can only be generated from PLS or PLH sql files which are annotated appropriately
  • Due to lack of Oracle APIs, grants performed to the deployed services remains a manual step
  • No labels