Oracle SOA – Integration Artifact Governance

October 17, 2019 Oracle Integration


Structure and the ability to maintain the Integration artifacts in any SOA development are as important as the artifacts itself.  In my projects, I give a reasonable focus on the governance of the Integration artifacts. Technical Artifacts governance is subset of Overall SOA Governance.

  • XML Schema definitions
  • Web Services Definition Language
  • XML Stylesheet
  • XML
  • Policies
  • Cross References & Domain Value Mappings


  • Reusability
  • Abstraction
  • Simplicity
  • Portability


  • How to structure the artifacts?

The following are the key things to consider while creating the integration artifacts.

    • Canonical Model (Customer, Product, Order, Invoice, Address, etc)
    • Application specific folders versus Common folders (EBiz, Siebel, SAP, Common, etc.)
    • Revision Maintainability (V1.0, V1.1 etc)
    • Process Specific Folders (P2P, O2C etc)
    • Type (Application Service, Enterprise Service, Application Objects, Enterprise Objects, Application Message, Enteprise Message)

Typical structure based on the above considerations

  • How to refer to those artifacts in the runtime?

Repository governance choice of tool dictates on how we refer to these artifacts. The following are key things to consider

    • Soft Reference Versus Hard Reference
    • Availability of the Repository to resolve dependencies
    • Single Source of Truth for the Repository
  • What are the Oracle tools available to efficiently perform the technical artifact governance?
    • Oracle Enterprise Repository
    • Oracle Service Registry
    • SOA Metadata Repository