Features Flag in Oracle Integration Cloud by Ankur Jain

This article will explain features flag in Oracle Integration Cloud.

Oracle Integration Cloud allows enabling specific functionality to the specific OIC instance as required which is called feature flag model. The codebase will remain the same for all instances but feature flag control the features.

Each new feature is assigned a specific flag that is used to control the feature. For example, if you want to call already activated integration inside another integration, there is a feature flag oic.ics.console.integration.invoke.local.integration assigned to this specific feature. If this flag is enabled in the OIC instance then only this feature can be used. Flags are controlled from a central system and can be updated in real-time by Oracle development and operations. This means that feature flags can be turned on very quickly, and also if a problem occurs they can be disabled.

See one example of feature flag here which calls OIC Integration

The life cycle of Feature Flags

Below diagram depicts the different phases of the Feature Flags. Let’s go ahead and understand the meaning of each phase

Internal Only:

When the specific feature enters to the stage then this feature is available to Oracle only and not available to customers. It is because Oracle trying to test the feature end to end before turning them on for any customers. Once Oracle satisfied with the feature internally then they start releasing the feature to the selected customers and feature move to the Feature Controlled Stage. Please note that this change in stage does not require any code changes, it just requires an approval process to turn on the feature. Read the complete article here.

PaaS Partner Community

For regular information on Oracle PaaS become a member in the PaaS (Integration & Process) Partner Community please register here.

Blog Twitter LinkedIn Facebook Wiki

Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress