After patching Oracle Integration instances in Oracle Cloud Infrastructure United Kingdom Government Cloud environments, the activity steam is not retained. This is the expected behavior.

An Oracle Integration on Oracle Cloud at Customer instance login to the Oracle WebLogic Service Console shows a double login screen and fails with a 401 error because the Oracle WebLogic Server failed to restart. This error occurs because the identity certificate expired. A review of the Oracle Integration server log provides details.

<98f59cb8-62b7-40db-b6ff-31df720f2eea-00000386> <1622566848703>
<[severity-value: 2] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] >
<BEA-090154> <Identity certificate has expired: [
[
. . .
. . .
 

1. Log in to My Oracle Support and search for Doc ID 2781849.1.
2. Download the following files:
   • rollback.py
   • demo_wlst.py
3. Log in to wls-1.
4. Become the oracle user:

   sudo su - oracle

5. Place both files in the /tmp folder.
6. Execute ls -ltr to confirm you see both files in /tmp.
7. 5. Navigate to /tmp.

   cd /tmp

8. Run the following command:

   python rollback.py

9. Wait for the following message to be displayed:

   Successfully Completed script Run

10. Repeat steps 1 through 9 on wls-2 and the virtual machines (VMs).
11. Restart the servers after the script is run on all VMs.

When creating an integration that includes a Process and an Integration, you cannot expose a WSDL on the Integrations side that is the same WSDL exposed on the Processes start message side. Instead, either use a different WSDL on the Integrations side or expose a REST interface.

1. Ensure that your Oracle Integration instances are running version 18.4.5.181203.1159-20020 or later.

2. Ensure that your user account has the following entitlements:

   Service	Entitlement
   Oracle Identity Cloud Service	Application Administrator
   Oracle Integration	Administrators ServiceAdministrator (to verify that the issue is resolved)

3. Sign into Enterprise Manager for your Oracle Integration Integration and Process instance. Expand WebLogic Domain and Security, and then click System Policies.

4. From the Type list, select Codebase. From the Name list, select Includes. Enter IntegrationSuiteHome into the field, and then click the Search icon.

   
   
   
   Description of the illustration codebase-search.png
   
   

5. Select the result, and then click Edit. Click Add. Select the Select here to enter details for a new permission option, and then enter the following values into the corresponding fields:

   • Permission Class: oracle.security.jps.service.credstore.CredentialAccessPermission

   • Resource Name: context=SYSTEM, mapName=oracle.ics, keyName=OIC_SERVICE_OAUTH_CLIENT

   • Permission Actions: read,write,update,delete

   
   
   Description of the illustration codebase-add.png
   

6. Click OK twice to save your changes.

7. Sign in to the Oracle Integration My Services Console, and then navigate to the Instance Overview page for your Integration and Process instance. Click the IDCS Application link.

   
   
   
   Description of the illustration instance-details-idcs.png
   
   

8. On the Configuration tab, expand the Client Configuration panel. In the Accessing APIs from Other Applications section, set the Trust Scope option to All Resources.

9. If the urn:opc:resource:consumer:all scope is not listed in the Allowed Scopes table: click Add. Enter urn:opc:resource:consumer::all for the scope. The scope should not be protected and does not require consent. Click Save.

   Skip this step if the urn:opc:resource:consumer::all scope is listed in the Allowed Scopes table

10. Restart the managed server(s) for your Oracle Integration Integration and Process instance. In a private browsing session, verify that the authentication pop-up no longer appears.

Applies only to Oracle Integration Classic (user-managed).

On the Services tab of the Oracle Integration My Services console, the Manage this service menu for a provisioned instance contains links to the following consoles. These links do not currently work correctly.

• Open Fusion Middleware Control Console

• Open Weblogic Server Console