How to avoid B2B Instances Getting Deleted When The Configuration is Retired and Purged After Applied B2B 10.1.2.3.0 MLR 9 Patch.

(Doc ID 864593.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Application Server Integration B2B - Version: 10.1.2.3.0 and later   [Release: and later ]
Information in this document applies to any platform.

Goal

After MLR9 was applied in a B2B configuration if is retired and purged a configuration its instances will dissapear. This behavior was not seen before we applied MLR 9 on top of the 10.1.2.3.0 version.

Based on a requirement to create a new configuration based on an already existing TPA. The steps followed earlier (before MLR 9 patch) were as follows:

  1. Quisce the configuration
  2. Retire the configuration
  3. Doing this itself will make the TPA in draft state. Now, update the required change in TPA
  4. Validate the TPA and Create configuration

The new steps followed (after MLR 9) are as follows:

  1. Quisce the configuration
  2. Retire the configuration
  3. DELETE / PURGE THE RETIRED CONFIGURATION FROM "Retired and Discarded Configurations"
  4. After finished step 3, TPA changed to draft state. and it is possible to update the required change in TPA.
  5. Validate the TPA & Create configuration

After made step 3, this action deleted all the existing instances that were created as part of that.
How is possible to avoid the B2B instances removal?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms