OIC Gen 1 vs Gen 2 | Benefits of OIC Generation 2

Gen1 vs Gen2:

In Oracle Cloud terminology, "Classic" refers to the generation 1 cloud. OCI refers to generation 2 cloud which introduced Bare metal and off-box virtualization.

Oracle Strongly encourages cuatomers ro migrate their existing cloud resources from OCI compute classic regions to OCI GEN2.

OCI is a second generation cloud that provides a better than ever foundation for AI. It offers :

• MULTIPLE layers of  Security for users, data and infrastructures and the oracle autonomous database.
• Lower Compute costs
• Manage new high performance workloads.
• Application development
• Integration of Oracle and Non oracle apps(both on-prem and in the cloud).

Some Benefits of OIC Generation 2:

• Natively integrated with the Oracle Cloud Infrastructure Console : Simplifies creating and managing user accounts, permissions, and Oracle Integration instances

• Integration Insight : Integration Insight in Oracle Integration dramatically simplifies the process of modeling and extracting meaningful business metrics, allowing business executives to understand, monitor, and react quickly to changing demands

• File Server : File Server provides an embedded SFTP server within Oracle Integration, enabling organizations to focus on building integrations without needing to host and maintain a separate SFTP server

• Support for Oracle Cloud Infrastructure (OCI) Compartments : Organize your Oracle Integration instances into OCI compartments (for example, separate dev, test and production compartments). This lets you separate access to instance creation and control instance level management by department.

• Oracle Cloud Infrastructure Identity and Access Management (IAM)

 Provides a rich permission model that gives Oracle Integration users fine-grained access to Oracle Integration instances—for example, manage (create, edit, move, …) or view only.

OIC Retention period | Impact of increasing the retention period | Standard and Warning settings

This feature control how oracle integration retains your historical data. Runtime instance data is purged to free up space for the newer data. 

The default rentention period is 3 days.

What are the impacts of increasing the retention period if the default 3 days are not enough? 

Solution:

Following 3 ways we can do the retention settings:

• Standard
• Warning(Low Space) 
• Manual purge

Standard:

We can adjust the Database retention period for the "Standard Setting" to a higher number (for example, 7 or 10 days), based on your retention requirements. Every day at midnight, data older than this retention period is purged.

Warning(Low Space):
If the database space reaches a warning state, more aggressive settings are used. These settings are configured under "Warning (Low Space) Settings." It is recommended to set the "Warning Settings" lower than "Standard settings". Also, you may want to consider setting the "Keep Faulted Instances" to a higher number of days than the timeframe to retain "Successful Instances".

As for the impact to changing the settings, you will need to monitor your instance to make sure that you are not frequently hitting Warning or Critical states. You can monitor the Data Retention status in the same "Retention Settings" page. If you have Critical Health Alerts configured, you will receive an email notification if the database space reaches a critical state.

Manual Purge:
If the database space reaches a critical state, the system rejects incoming requests and stops all integrations and processes from running until more space becomes available. In these cases, you will need to perform a manual purge.

Steps to configure rentention settings:

Here , we have kept rentention period 30 days for standard , 90 days for Insight . For warning, its 10 days retention.

Setting

Data Retention

Setup 

ERP BI - How to create a simple BI publisher Report | get a sequence number using bip report

Here, we will show you how to create a BI report. Basically we will generate an unique Invoice id based on SQL sequence from dual.

SQL query:

Select AP_INVOICES_S.nextval invoice_id from dual

Steps in detail:

Login to ERP and Navigate to Tools >> Reports & Analytics

Browse Catalog

Create a new folder "Poc" under /Shared Folder /custom/Integration

New >> Data Model

Click "+" sign and Select SQL Query.

Provide Name, select data soirce and SQL query >> ok

Data >> view

Data 》 Save as Sample data

Save Data Model

Go back to Catalog

Now you can see data model is ready.

New 》Report

Select the created data model 》 Next

Select Table 》 Next

Drag and drop field names from data source 》 Next

Finish

Action》Edit Report

View list 

Select output format as Data(csv)

Save Report

Go back to Catalog

Open

You can see its showing the expected invoice id.

OIC | Add Package Name for an Integration

We can put Integrations inside a package using below two methods:

1. At the time of Integration development(For new Integrations)
2. After Integration Developement(for existing integrations)

Steps in detail:

At the time of Integrations development:

Login to console >> Integrations 

Click Create Integration

Select a pattern 

Provide Integration name and a Package name(new or choose existing one). And click create.

After Integration Development:

Login to OIC console >> Choose Integration >> Deactivate

Click Edit

Menu >> Primary info

Change the package name

Save and close

Acrivate the Integration.

Expand and see the package has been changed.