[ERROR] AdapterManager - ServletContainerAdapter manager not initialized correctly.
Cause
Potential Cause 1: servers not started up yet
One or more managed servers to which wsm-pm has been targeted have not been started up yet.
Potential Cause 2: misconfigured Policy Accessor URL
Misconfigured Policy Accessor URL in config/fmwconfig/policy-accessor-config.xml.
Potential Cause 3: inconsistent SSL configuration
Any Inconsistent SSL configuration in the Weblogic Domain can break OWSM.
OWSM will, by default, attempt to use SSL for internal connectivity when SSL is configured on any server.
An example of an inconsistent configuration:
Three servers, Admin Server, soa_server1, bam_server1.
No SSL on Admin Server or on soa_server1.
SSL enabled on bam_server1, and bam_server1 is shut down.
Here, when the soa_server1 is started, it will look for policies on bam_server1, as that server is configured for SSL, and SSL takes priority.
This will then prevent soa_server1 from starting even when, apart from the SSL configuration, wsm-pm is correctly configured on soa_server1.
Potential Cause 4: ListenAddress
Misconfigured ListenAddress, or Policy Accessor URL not matching the ListenAddress
<Error> <oracle.wsm.resources.policymanager> <WSM-02120> <Unable to connect to the policy access service.
oracle.wsm.policymanager.PolicyManagerException: WSM-02120 : Unable to connect to the policy access service.Cause
Potential Cause 1: servers not started up yet
One or more managed servers to which wsm-pm has been targeted have not been started up yet.
Potential Cause 2: misconfigured Policy Accessor URL
Misconfigured Policy Accessor URL in config/fmwconfig/policy-accessor-config.xml.
Potential Cause 3: inconsistent SSL configuration
Any Inconsistent SSL configuration in the Weblogic Domain can break OWSM.
OWSM will, by default, attempt to use SSL for internal connectivity when SSL is configured on any server.
An example of an inconsistent configuration:
Three servers, Admin Server, soa_server1, bam_server1.
No SSL on Admin Server or on soa_server1.
SSL enabled on bam_server1, and bam_server1 is shut down.
Here, when the soa_server1 is started, it will look for policies on bam_server1, as that server is configured for SSL, and SSL takes priority.
This will then prevent soa_server1 from starting even when, apart from the SSL configuration, wsm-pm is correctly configured on soa_server1.
Potential Cause 4: ListenAddress
Misconfigured ListenAddress, or Policy Accessor URL not matching the ListenAddress
Solving
Change target WSM_PM from AdminServer to WSM_Cluster
Komentar
Posting Komentar