Enabling global trust between BPM(SOA) and OSB domains (Doc ID 2512683.1)

Last updated on MAY 15, 2023

Applies to:

Oracle Business Process Management Suite - Version 11.1.1.3.0 and later
Information in this document applies to any platform.

When a BPM(SOA) process calls OSB located on a different domain, several errors or misbehavior occur, including:

- The BPM instances gets stuck on a Human Task without a corresponding entry on the DLV_SUBSCRIPTION table

- There are the following errors on the either OSB or BPM WLS log file:

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Symptoms

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.