12c SOA Weblogic console - Database - shared memory realm does not exist IBM AIX RISC System/6000 Error: 2: No such file or directory error

While one of the SOA external DB was upgrading to 19c, I have stumbled with this following error during the datasourse connection testing.

Test of WorkboothDB on server osb_server1 failed, reason:

Error Connection test failed with the following exception: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist IBM AIX RISC System/6000 Error: 2: No such file or directory

Solution:

This is because the Database instance name got changed. I have used the correct instance name and it got resolved.

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:

12c SOA Synchronous BPEL process with a wait activity fails with a timeout

The Wait activity works well with an asynchronous BPEL process but not with a synchronous BPEL process where a transaction is required. The Wait activity involves a dehydration. Dehydration will persist the process and continue the process in a new thread. When the BPEL process is transaction required, the persist will not be complete until the BPEL process completes and transaction commits.

Synchronous BPEL process with a wait activity fails with a timeout

One of the solutions is possible:

Remove the following line from the synchronous BPEL process component:

required

OR

Change bpel.config.transaction to “requiredNew”

requiredNew