Unable To Configure O2A 2.0.1.3 For OSM 7.2.4 (Doc ID 2088606.1)

Last updated on DECEMBER 21, 2015

Applies to:

Oracle Communications Order and Service Management - Version 7.2.4 and later
Information in this document applies to any platform.

Symptoms

OSM 7.2.4.1.9 Cluster environment with 4 managed servers.

O2A 2.0.1.3 install on OSM version 7.2.4.1.9 fails when trying to create Weblogic resources for the cluster domain.  

- Design Studio console log showed an error for SAFRemoteContext file when running com_config-cluster-saf.py for SAFRemoteContext as below:


- AdminServer log showed two types of errors:

Error 1. ''weblogic.application.ModuleException: Could not create the JMS descriptor''
Error 2. ''The domain edit lock is owned by another session in non-exclusive mode - this deployment operation requires exclusive access to the edit lock and hence cannot proceed.''
This error is more a consequence of the real issue but not the cause.

Cause

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