My Oracle Support Banner

Error WSM-02557 Even Though OWSM Is Not Used (Doc ID 1910685.1)

Last updated on JULY 21, 2023

Applies to:

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

Symptoms

This document does not apply to 11.1.1.6 and earlier.

An 11.1.1.7 domain has been created with OWSM not selected.

From the Fusion Middleware Control's Test Web Service page, a Web Service is tested which does not have any policy applied.

Nevertheless, even though no OWSM policy is used, this fails. Fusion Middleware Control pops up a window with a WSM-02557 error:

java.lang.Exception:
oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException:
oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid:
WSM-02557 oracle.wsm.policymanager.accessor.BeanAccessor The documents required to configure the Oracle Web Services Manager runtime have not been retrieved from the Policy Manager application (wsm-pm), possibly because the application is not running or has not been deployed in the environment. The query "&(policysets:global/%)(@appliesTo~="WS-Client()")" is queued for later retrieval
at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(...)

 

Changes

In 11.1.1.7, even though OWSM itself was not added to the domain, and thus wsm-pm is not deployed, the OWSM agent nevertheless tries to check whether any policies, including global policies, were applied.

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
References


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