My Oracle Support Banner

Oracle WSM Policy Manager Template Deploys To All Managed Servers By Default (Doc ID 2686333.1)

Last updated on JULY 02, 2020

Applies to:

Oracle Web Services Manager - Version 12.2.1.2.0 and later
Information in this document applies to any platform.

Symptoms

A Domain is created with WSM Policy Manager template. It seems to deploy WSM components to all managed servers in the domain. WSM is the only wanted in one of my managed servers.In an attempt to back out WSM deployment from another managed server wsm-pm has been successfully un-deployed from the server, but there appears to still be some residual diagnostic content.

Error are being written to the managed server log:

<Apr 10, 2017, 3:28:36,623 PM PDT> <Warning> <oracle.jps.authorization> <JPS-04155> <Scanning of application policy failed. Reason {0}
oracle.security.jps.service.policystore.PolicyStoreException: JPS-10702: The datasource jdbc/OpssDataSource is not found.
at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.getDataSourceAndSubject(JpsDBDataManager.java:2005)
at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.createEMFAndSubject(JpsDBDataManager.java:1741)
at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.getEMFAndSubject(JpsDBDataManager.java:1714)
at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.init(JpsDBDataManager.java:1384)
at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.jpsObjectListQuery(JpsDBDataManager.java:4096)
Truncated. see log file for complete stacktrace
Caused By: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.OpssDataSource' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/OpssDataSource'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1292)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:349)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:222)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.ServerNamingNode.lookup(ServerNamingNode.java:521)
Truncated. see log file for complete stacktrace
=======

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
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.