OIC Gen3 - How to rename an integration or to change the package name of an integration

Usecase : Here, we will see how to rename an integration or to move an integration from one package to another package and etc.

Step1: for the integration >> click edit

Step2: click primary info >> update the details >>save.

OIC gen3 - Publishing an integration endpoint to OCI api gateway

Usecase: Here, we will see how we can publish our integration endpoint to OCI API gateway.

Steps:

Step1: once your integration is ready, activate and click on action >> publich to api gateway

Step2: select compartment >> selwct api gateway >> select or create new deploymwent.

Step3: view deployment in OCI console >> take api details and test

For more details:

Reference:

https://niallcblogs.blogspot.com/2023/12/999-2312-publishing-oic-endpoints-to.html?m=1

OIC Gen3 - using Recipes and Accelerators

Recipes and accelerators, collectively known as prebuilt integrations, are preassembled integration solutions.

A recipe or accelerator contains all the resources required for a specific integration scenario. The resources include integration flows, connections, lookups, and certificates. Use a recipe or accelerator to quickly get started building an integration.

Recipes types:

they are either project-based or package-based:

• When you install a project-based recipe, you can access it on the Projects page in Oracle Integration.
• When you install a package-based recipe, you can access it on the Packages page in Oracle Integration. 

How to determine whether a recipe in the Integration Store is project-based or package-based:

Before you install it, hover over the recipe card and click Open Details  to expand the information pane. The recipe details show either Project code (for a project-based recipe) or Package name (for a package-based recipe).

Differences Between Recipes and Accelerators

Recipes are sample use cases that give you a head start. Accelerators are run-ready business integrations or technical patterns of larger scale.

Here's a comparison of recipes and accelerators.

Recipes	Accelerators
A recipe is a sample use case that gives you a head start.	A business accelerator provides an end-to-end business process or use case (for example, marketing to lead, hire to retire, or concept to launch). A technical accelerator provides a common technical solution (for example, sending alerts on failures). They are meant to be called by another integration.
Not supported by the producer	Managed and supported by the producer
Fully editable in the Oracle Integration designer	Configurable and extendable
Can't auto-upgrade to new versions	Upgrades provided by producer
Configurator in Oracle Integration	Configurator in Oracle Integration and as native SaaS
Always free	Paid offering (as decided by producer)

How to find a recipe or accelerator:

1. On the Oracle Integration Home page, in the Get started section, click Browse store.
   The Integration Store is displayed. Note that you can toggle the display between a list view and a card view.
   
   
2. Use the Search , Filter , and view tools to narrow your search, filter and sort the list, and change how the list is displayed.

How to install a recipe or accelerator:

1. Find the recipe or accelerator that you want to install.
2. Hover over the recipe or accelerator card and click Install .
   When you install a recipe (or an accelerator), it's installed as a package or project. 

Note:

For project-based accelerators, Oracle periodically releases updates to the Integration Store. You can upgrade an installed accelerator project to a newer version automatically without making manual changes to your existing installation. 

Accelerators extensions and versions:

How to extend an accelerator:

1. First install the accelerator. Go to oracle home page >> view all >> select the version and install.
2. Once installed, for projects , click the action ellipsis(...) of the integration and click extend.
3. Add an extension group before or after the invoke and add a data stitich to enrich data to the invoke or add some fault handling logic after the invoke etc.
4. Save and activate.

How to version an accelerator:

Suppose an accelerator is already installed  and extension logic added and now new upgrade comes, then we can upgrade the version as below:

1. Go to oracle home page >> view all accelerators >> select the acceleraror to upgrade and select latest version and  install.
2. Once installed, for projects , click the ellipsis of the integrations and click refresh enspoints
3. Then marge the extension changes of the previous version to new version.  Click the action ellipsis of the integration >> click extend >> select the previous version to merge to this new version
4. Save it.

Reference

https://docs.oracle.com/en/cloud/paas/application-integration/int-get-started/get-started-integration-recipes-and-accelerators.html

OIC ERP/HCM - How to see or download file from UCM for support.

Usecase: Here we will see how to check or download file from ucm for support help or verification or testing purposes.

Steps: 

Step1: go to content server https://<host instance>/cs and click on search

Step2: search the file with content id and click on info sign

Step3: click the file link below and it will auto download the file. 

This above steps are required to get the file from ucm which we can use or check for support or dev testing verification.

OIC - We need to execute a schedule job in oic that will run only on weekdays excluding public holidays?

To execute a scheduled job in Oracle Integration Cloud (OIC) that runs only on weekdays (Monday to Friday) excluding public holidays, We can follow these steps:

1. Set Up the Weekday Recurrence in OIC:

we can use a recurrence pattern to run the job only on weekdays. choose the iCal format.Set the frequency to DAILY and restrict it to Monday to Friday using the BYDAY parameter.

For example:

FREQ=DAILY;BYDAY=MO,TU,WE,TH,FR

This ensures the job only runs Monday through Friday.

2. Exclude Public Holidays:

OIC doesn't provide a built-in way to exclude public holidays automatically. You'll need to handle this manually or programmatically. Here are some approaches:

Option 1: Manually Disable the Job for Public Holidays

Create a list of public holidays, and manually disable the schedule on those days.You could either:Pause the integration the day before the holiday, orModify the recurrence rules around those dates.

Option 2: Use a Lookup Table for Public Holidays

Create a lookup table that contains the list of public holidays.Modify the integration to check the current date against this list at runtime.If the current date is a public holiday, the job won’t proceed further.

Option 3: Programmatically Handle Holidays in the Integration Flow

In the integration logic, before running the core job, add a step that checks if the current date is a public holiday (by querying a list of holidays stored in a file or a database).If it's a public holiday, you can skip the execution.

You can combine options 1 and 3 for flexibility. Manually manage the public holidays for the current year and set up a query mechanism for holidays that changes each year.

OIC gen3 - Integration patterns and Define schedules

Integration patterns:

1. Application : 
1. Real time call or data feed from the subscriber.
2. Rest client / soap client
3. Oracle fusion application event subscription
4. Oracle CS sales and B2B cloud applocation.
2. Schedule: Runs at specific dates and times defined in a schedule. Mainly used for bulk or batch integration or file processing.
3. Event: starts when an event is published. It is like EDN or even driven Architecture or publish subscribe model.

Creating a schedule: 

There are two ways, we can create or define a schedule of a schuduled integration.

1. On the design canvas , click the ellipsis on schedule node and edit schedule definition.
2. Add a schedule on the integrations page before or after the integration has been activated.

Schedule types:

1. Simple schedule

• We can define only once - hour minutes, days months, weeks
• We can also define recurring schedule - hourly, minutely, daily, monthly, weekly
• Frequency can not be less then 10 mins.
• We can set specific timezone, add a time window to run or never expire mode by default.

1. Advanced schedule or iCal expression

• We use calender expression 
• Frequncy can be set minutely(<10 mins).
• We can also define multiple schedule frequencies together using &.

Examples:

Example 1: This example runs on the 1st, 10th and 15th days of the month at 5:15am, 10:15am , 3:15pm and 8:15 pm.

FREQ=MONTHLY;

BYMONTHDAY=1,10,15;

BYHOUR=5,10,15,20;BYMINUTE=15;

Example 2: multiple schedule frequencies together: The example provided runs every day between 5:30 PM and 7:30 PM, executing every 10 minutes during these hours.

FREQ=DAILY;BYHOUR=17;BYMINUTE=30,40,50;BYSECOND=0;

&FREQ=DAILY;BYHOUR=18;BYMINUTE=0,10,20,30,40,50;BYSECOND=0;

&FREQ=DAILY;BYHOUR=19;BYMINUTE=0,10,20,30;BYSECOND=0;

Note: we can only start the schedule if the integration is activated. Once started, we can see the future runs of the schedule. 

OIC Gen3 - About Tracing Levels while activating integration

OIC has following 3 tracing levels:

1. Production
2. Audit
3. Debug

Production:

• Data is retained for 32 days.
• Log all flow actions
• Log only invoke /logger actions.
• Wihin loops( upto 1000 iterations)

Audit:

• Data is retained for 8 days.
• Logs same as production option
• Also logs external payloads

Debug:

• Data is retained only for 24 hrs.
• Logs same as audit option
• Also logs all actions within the loops.

Can we modify the tracing dynamically?

Yes, We can also dynamically or runtime modify the tracing level without deactivating the integration. 

Steps:

Integration >> "..." actions >> configure activation >> modify the tracing level.

What occurs or observe if we deactivate any integration:

• Activated integrations cannot be edited.
• Stops processing any new messages.
• Pending requests remain unprocessed and are lost.
• Existing history, monitoring, and runtime data are lost.
• In-flight instances will fail, which can be observed.
• You must stop the schedule before deactivation.