My Oracle Support Banner

Unable to Create New ADF Connection from Fusion Middleware Control (EM) (Doc ID 2692875.1)

Last updated on JULY 23, 2024

Applies to:

Oracle WebCenter Portal - Version 12.2.1.2.0 and later
Oracle WebCenter Portal for OCI - Version 12.2.1.4_24.2 and later
Information in this document applies to any platform.

Symptoms

Unable to create an ADF Connection using Fusion Middleware Control (EM).

Steps to reproduce the issue:

      1. Connect to Fusion Middleware Control.

      2. From the navigation pane, expand WebCenter > Portal > Server then right-click the on WC_Portal.

      3. Choose ADF > Configure ADF Connections.

The following error message will be returned:

"No ADF Connection configuration is possible. Please ensure the application is running and is deployed with ADF Connection MBean. Refer to your ADF Admin guide for instructions on how to deploy ADF Connection MBean with your app."

The WC_Portal.out log shows:

<DATE> <Warning> <oracle.webcenter.lifecycle.listener.LifecycleServletContextListener> <BEA-000000> <
oracle.webcenter.core.lifecycle.LifecycleException: org.xml.sax.SAXParseException; systemId: /META-INF/mdssys/cust/adfshare/adfshare/connections.xml.xml; lineNumber: 3; columnNumber: 102; No oracle.mds.internal.model.parse.MDSCustNodeParser parser registered for top element;check your namespace declaration.   Namespace:
  Local name: insert)
at oracle.webcenter.core.portlet.lifecycle.PortletLifecycleService.doImportExportSet(PortletLifecycleService.java:395)
at oracle.webcenter.lifecycle.listener.LifecycleServletContextListener.doImportExportSet(LifecycleServletContextListener.java:479)
at oracle.webcenter.lifecycle.listener.LifecycleServletContextListener.contextInitialized(LifecycleServletContextListener.java:106)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:705)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:326)
at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:197)
[...]

Caused By: javax.naming.NamingException: org.xml.sax.SAXParseException; systemId: /META-INF/mdssys/cust/adfshare/adfshare/connections.xml.xml; lineNumber: 3; columnNumber: 102; No oracle.mds.internal.model.parse.MDSCustNodeParser parser registered for top element;check your namespace declaration.   Namespace:
  Local name: insert) [Root exception is oracle.mds.exception.MDSRuntimeException: org.xml.sax.SAXParseException; systemId: /META-INF/mdssys/cust/adfshare/adfshare/connections.xml.xml; lineNumber: 3; columnNumber: 102; No oracle.mds.internal.model.parse.MDSCustNodeParser parser registered for top element;check your namespace declaration.   Namespace:
  Local name: insert)]
at oracle.adf.share.jndi.ContextImpl.throwNamingException(ContextImpl.java:675)
at oracle.adf.share.jndi.ContextImpl.load(ContextImpl.java:923)

 

 

Changes

 

Cause

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
Changes
Cause
Solution


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