Error WSM-02557 Even Though OWSM Is Not Used
Last updated on FEBRUARY 09, 2018
Applies to:Oracle Web Services Manager - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
An 22.214.171.124 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:
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
In 126.96.36.199, 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.
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