After the customer disabled their AT-TLS rule, the problem was eliminated. They had the AT-TLS rule encrypting all ports AND they had configured Tomcat to secure ports ( HTTPS ), so it appears that their issue was caused by double encryption.
4. Edit the SBM links in the zmfalf_resource.properties file (..\common\ tomcat \8.0\webapps\almzmfalf\WEB-INF\conf) to receive ALF Events on the secure SBM port, such as https ://<sbmhostname>:8443.
/eventmanager/services/ALFEventManager Restart Micro Focus Common Tomcat To verify ZMF Connector's Tomcat setup, open a browser and go to https ://myConnectorServer:8443/
3. When configured for SSL, the application is referenced using the following port: https ://serverName:8443/almsernet....... (Default for Tomcat ) ChangeMan ZMF Plugin Quick Reference 17
Customer is on ZMF 8.2 Patch 3 and has the REST Services Tomcat server up. They noticed in the Tomcat log the SEVERE error message listed below. The customer confirmed the file does exist using ISPF option 3.17.
