Known Issues › Known Configuration Issues › Functionality Failures After Configuring the CA SDM Secondary Server with a Different Tomcat Port

Functionality Failures After Configuring the CA SDM Secondary Server with a Different Tomcat Port

Valid on all operating environments

Symptom:

I configured the CA SDM Secondary server with a different Tomcat port than the Primary server port. This configuration causes some functionality to fail when accessed from the Secondary server web URL. For example, attachments, list export, GRLoader, and Process Viewer.

Solution:

Access the functionality from the Primary server URL because they do not work on the Secondary server.