Enabling SSL 3.0 for App Visibility Manager

Some application servers do not support TLS and therefore require SSL 3.0 communication, which is disabled by default for App Visibility Manager internal communication, to protect against the POODLE vulnerability.

If your system requires SSL 3.0 communication and the POODLE vulnerability is not a concern for your environment, using the following procedure to enable SSL 3.0:

1. On the portal computer, open the portal.properties file, located in the installationDirectory/portal/properties directory.
2. Comment out (add a # character to the beginning of the line) the tomcat.ciphers property.
3. Add SSLv3 to the list of tomcat.ssl.enabled.protocols property and save the file.
4. Open the java.security file, located in the installationDirectory/ADOP_JRE/lib/security directory.
5. Remove SSLv3 from the list of the jdk.tls.disabledAlgorithms property and save the file.
6. Restart the service.
7. Repeat these steps on each collector computer, for the collector.properties, located in the installationDirectory/collector/properties directory, and the java.security file, located in the installationDirectory/ADOP_JRE/lib/security directory.

After a few minutes, the agents can connect to the portal and collector.

Related topics

Enabling communication between App Visibility agents and server components

Changing App Visibility portal settings

Starting and stopping the App Visibility server services