OIC - get ESS JOB Status of a ESS import job

Here, I will show you how to get the ESS job status once the import job completed and you have the ess import request id.

Logic: 

we will create a loop and check the ess job status using the import request id whether the ess import job is successful or not(at each loop it will wait 59 sec). 

Follow the below steps:

Step1: Take an assign activity named like setImportLoopVariable and assign the following 2 variables:

I_inProgress : "true"

I_importRequestStatus : ""

Step2: take a while activity and add the following condition.

$I_inProgress = "true"

Step3: Take a wait activity and assign some time to complete the import ESS process lika value 59sec.

Step4: Drag and drop Erp cloud adapter and configure following:

Provide a name: essJobStatus

Select Query, Create, Update or delete information.

Select service: ErpIntegrationService

Operation: getESSJobStatus

Step5: Map the ess import request id to request id of the getEssJobstatus.

Step6: Take a assign named like updateProgress and do the following:

I_inProgress : returnStatus(result of getESSJobStatusResponse)

I_importRequestStatus: result of getESSJobStatusResponse.

Click here how to convert the status to boolean value:

oic-js-return-boolean-status

OIC - Convert a Scheduled Integration to a REST Adapter-Triggered Orchestration Integration

You can convert a scheduled integration to a REST Adapter-triggered, app driven orchestration integration. This eliminates the need to recreate the integration if you need to change the integration style from scheduled to app driven orchestration.

Restrictions:

• You cannot convert a scheduled integration to a REST Adapter-triggered integration with multiple verbs.
• You cannot convert a scheduled integration with assignments that have the fault data type.

Implementation steps:

Step1: In the left navigation pane, click Home > Integrations > Integrations > de activate and Open the scheduled integration you want to convert.

The integration canvas is displayed.

Right-click the schedule icon and select Convert to REST Trigger.

Menu is displayed with selections for Edit Schedule Definition, Edit Integration Properties, View Integration Properties, and Convert to REST Trigger.

Step2: A list of available REST Adapter triggers is displayed > Select the REST Adapter to use as the trigger connection in this integration. > This invokes the Adapter Endpoint Configuration Wizard. Configure the REST Adapter in the wizard.

When wizard configuration is complete, click Done.

A message is displayed.

Clicking done will perform conversion to REST trigger and will clear tracking information, delete any assignment variables with fault data types and update any impacted actions. Errors and warnings may occur which will require manual correction. Are you sure you want to continue?

Review the message, then click Convert.

Step3: A conversion progress bar is displayed. When complete, the converted integration is displayed in the canvas with the REST Adapter trigger connection.

The integration is displayed horizontally. Conversion errors identified by little red circles are displayed on the impacted actions in the integration.

Step4: Investigate any errors and manually correct the impacted actions or invokes. For example, any scheduled parameters in the scheduled integration are deleted during conversion to an app driven orchestrated integration. This results in errors in any actions that reference those schedule parameters (for example, an assign or logger action).

OIC - Why to avoid creating too many scheduled integrations

When there are too many scheduled integrations configured, instances can get backlogged waiting for resources to become available or previous integration runs to complete. This can cause processing delays where some instances are in a waiting state longer than they should be and schedules may not start at the scheduled time.

Best practice:

• Do not create too many scheduled integrations that are scheduled to run at the same time. 
• Use an asynchronous REST Adapter trigger instead of a scheduled trigger when an active schedule is not absolutely required.
• Do not create any long-running scheduled integrations (a scheduled integration that takes longer than one hour, for example, to complete). This blocks scheduler resources impacting other scheduled runs.
• Spread schedules out over time to avoid schedule clusters.
• You can convert a scheduled integration to an application-driven orchestrated, REST Adapter trigger-based integration. 

OIC - Exception Handling

 OIC provides two out of the box features to handle exceptions.

• Scope Handler:

Scope is one of the out of the box activity allow you to bundle a set of activities which have their own variables, Faults and event handlers. In other words, scope allow you to handle error raised in IC. It is like as try and catch block in other programming languages as java, dotnet etc. every scope activity has their own fault handlers which is treated as catch block.

Click here oic-scope-level-error-handling for POC.

• Global Fault Handler:

The Global fault handler is super catch block which handle all the errors which are not supported by scope handlers. This functionality enables you to direct business faults to the caller or apply business logic before sending faults to the error handling framework. you can add fault handling to any integration type.

Click here oic-global-fault-handling-in-app-driven for POC.

OIC - Connectivity Agent part 2

 This includes:

• Pre-requisites for Connectivity Agent
• Download Connectivity Agent
• Install Connectivity Agent
• Start/Stop Connectivity Agent.
• Log files of Connectivity Agent

Pre-requisites for Connectivity Agent:

Download Connectivity Agent:

Step 1:

Go to the OIC Agents ⇾ Create Agent group ⇾ Provide Agent Group Name ⇾ create

Step2:

Next click the Download button ⇾ Connectivity agent and it will download oic_connectivity-agent.zip

 

Connectivity Agent Installation:

Here showing the installation in Linux system.

Step1: Java jdk 8 version should be installed.

export JAVA_HOME=/home/opc/java/jdk1.8.0_251

export path=$JAVA_HOME/bin:$PATH

java -version

java version "1.8.0_251"

Java (TM) SE Runtime Environment (build 1.8.0_251-b08)

Java HotSpot (TM) 64-bit Server VM (build 25.251-b08, mixed mode)

Step2: unzip zip file

unzip oic_connectivity_agent.zip

ls -ltr

InstallerProfile.cfg

cpi_upgradeutility.jar

coonectivityagent.jar

agenthome

Step3: Provide OIC url and agent group name in InstallerProfile.cfg

vi  InstallerProfile.cfg

Put the following details:

oic_URL:https://host:port

agent_Group_Identifier: AGENT_GROUP

Step4:

java -jar connectivityagent.jar

proceeding to install a new agent

Enter your OIC username:

Enter password for user:

...

Done with Agent installation & Configurations... Starting Agent for message processing.

Agent started successfully...Now available for new message.

Now go to the OIC agents and see 1 connectivity agent is created under Agent_GROUP. If you go to the Monitoring agents, you will see the agent is active in green.

No go the linux page and ctrl +c to shutdown it. and you will see the agent in red monitoring agent.

To run the connectivity in background.

nohup java -jar connectivityagent.jar &

and also add the oic_user and oic_password in the InstallerProfile.cfg file.

oic_user=oicuser

oic password=welcome

Start/Stop Connectivity Agent:

Start:

nohup java -jar connectivityagent.jar &

Stop:

Go to agenthome 

cat pid

5160

kill -9 5160

Log files of Connectivity Agent:

cd agenthome/logs

ls -ltr

OIC - Connectivity Agent part 1

 This includes:

• Connectivity Agent
• Agent types
• Connectivity agent architecture
• Agent in HA Availability
• Agent Group
• Connectivity agent constraints

Connectivity Agent:

• A connectivity agent or on  premise agent is a light weight component which solve the problem of cloud to on premise integration.
• The agent is required to exchange messages with on premises application such as database, Oracle E-Business suite, systems, Applications and SAP products, Ariba etc. 
• This CA can be installed behind the firewall to access on-premises applications.

Agent Types:

• Connectivity agent
• This is the intermediate gateway which provides a connection between SaaS and on-premises application or vice-versa.

• Execution agent
• This is self-managed instance of OIC help to connect applications within the organizations that enable secure integration between these systems residing on premise.

Connectivity Agent Architecture:

• The agent work as a bridge between OIC and On premises applications and without that communication is not possible.
• The OIC does not send any request to CA but CA does this job. Agent sends his heartbeat signals to Oracle Integration regularly to tell that I am live to serve your requests. In addition, to that agent regularly poll for design and run time work on which agent need to act upon.
• Design time work includes set of activities like Test connection, activation or deactivation of integrations.
• Same ways there are run time activities on which agent need to act upon. For any communication between integration cloud and on-premises systems such as Databases, EBS etc.

Agent Group:

• An agent group is a unique identifier which comprises multiple connectivity agents.
• You must create a agent group in OIC before you can run the connectivity agent installer.
• For a single oracle integration instance, you can create up to 5 agent groups. If the limit exceeds, you will get error like "Max limit reached. Maximum 5 Connectivity agents can be added."

Connectivity Agent in HA :

To tackle the high traffic on a single connectivity agent, you can install Connectivity Agent in High Availability mode. you can associate max two agents with a single agent group and both the agents should run on different hosts. The HA mode ensures the transactions will continue if any of the agents goes down or any hosts becomes unavailable.

Connectivity agent constraints:

• 10 MB payload limit
• The OIC agent can handle payload in size which is less than 10 MB in a single transaction.
• 240 sec or 4 mins Timeout
• Every transaction sent out to the on-premises application via agent must be completed within 240 seconds.

OIC - create PGP key to use in FTP connection

Go to pgpkeygen and fill up few details like your name, email id and choose algorithm as RSA , key size as 4096 bits(more secure). expires and passphrase and click generate keys.

Now download the keys.

Downloaded private and public PGP key files: