X

Announcements and Technical Advice for the Oracle
Utilities product community from the Product Management team

  • July 8, 2019

OUAF Integration Architecture

Anthony Shorten
Senior Principal Product Manager

One of the most important aspects of the Oracle Utilities Application Framework, is the ability to integrate to other technologies and applications using a flexible set of techniques. With each release of the Oracle Utilities Application Framework, the integration architecture is refined to support new and emerging standards for on-premise, hybrid and Oracle Utilities SaaS Cloud implementations of Oracle Utilities products.

The integration architecture is summarized as follows:

  • Screen Pop. The ability to pop into a pre-populated screen of the product from an external product (for example, your IVR/CTI system). This allows a URL to be formulated to jump to the screen and even pre-populate the screen to allow the end user quick access to the information.
  • Client User Exit. This allows the existing user experience to be altered to integrate on the browser to any other browser or other application. For example, integrating to an inline address validation capability at the user experience level.
  • URL Characteristic. This allows integration to other sites or external document control systems from individual objects. This allows sites with content solutions to reuse those solutions from objects.
  • Navigation Keys. This allows sites to add links to internal sites to supplement materials to augment the user experience. For example, link to document repositories for policies etc.
  • Inbound Web Services. One of the major integration points is using SOAP or REST based integration directly or via some software, like middleware, that supports Web Services. The Oracle Utilities Application Framework has been enhancing this capability even before it became popular and continues to enhance this capability to support new and emerging standards.
  • Staging. Utilities require to pass data into the product and also extract data from the product. To protect data integrity, the products provide a set of prebuilt staging tables that can serve as conduits in and out of the product.
  • Outbound Message. The Oracle Utilities Application Framework provides a configurable capability to detect business events and provide payload into a capability that can send that product payload, using various formats and transports, in real time, batch or via middleware to external systems.
  • Algorithm. For on-premise and hybrid implementations, it is possible to integrate third party libraries directly to provide dedicated interfaces at the processing level.
  • SQL, Stored Procedures and Triggers. For on-premise and hybrid implementations, it is possible to use database objects to perform integration at the database level. This is used for reporting tools, database level adapters and database addon products such as Oracle Audit Vault.

A summary of the integration capabilities is shown below:

Integration Architecture

A new version of the Oracle Utilities Application Framework Integration Overview (Doc Id: 789060.1) available from My Oracle Support is now available that covers the aspects of integration described above as well the techniques available for cloud implementations.

Join the discussion

Comments ( 2 )
  • Meghashyam Tuesday, November 19, 2019
    If IWS is deployed on an another dedicated server, will it require both SPL Web and SPL service to work or can it just be deployed alone? If it needs SPL service, is it possible to configure to talk to a remote sever that hosts the spl service?
  • Anthony Shorten Tuesday, November 19, 2019
    Whilst it i possible to set the IWS to reuse a SPL Service component, if you took the time to separate IWS from the online then it makes more sense to also separate the SPL Service component to take full advantage of the separation.

    The configuration is controlled by the BSN* variables.
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.