After Configuring The WebLogic SSL Protocol For TLS Only (And Disabling SSLv3), The Managed Servers Within The WebLogic Domain Do Not Reflect The Health Status And All Deployments Show A Status Of New (Instead Of Active)
Last updated on DECEMBER 20, 2017
Applies to:Primavera P6 Enterprise Project Portfolio Management - Version 220.127.116.11 and later
Information in this document applies to any platform.
After disabling the SSLv3 protocol by:
- Enabling JSSE under the Managed Server
- Setting the following JVM argument for all managed servers within the WebLogic domain: -Dweblogic.security.SSL.protocolVersion=TLS1
The health of all managed servers and any application deployment on the managed severs do not reflect the proper state/status (the managed servers do not show an OK health (instead the health field was blank within the WebLogic Administration Console) and the deployments show a NEW state (which is a state that reflects the server being offline or the Admin Server not recognizing the state of the servers and any deployments on them).
After disabling SSLv3 and enabling TLS, for the health of all managed servers to reflect accurately in the administration console and any child dependency (like deployments) to reflect the proper state/status.
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