If you want to access Smarts SolutionPack in the HTTP mode, perform the following steps:

  1. Add the parameter, SM_CAS_SERVER, to the runcmd_env.sh file in the Presentation SAM server. SM_CAS_SERVER is the URL that identifies the M&R Tomcat server host, and it has to specify the protocol and port used to log into M&R. Example: SM_CAS_SERVER=http://M&R IP:58080. You must use the SM_CAS_SERVER entry to connect to the M&R server. IF M&R was upgraded and was not changed to run on HTTPS, then SM_CAS_SERVER=http://M&R IP:58080.
    Note: The entries in the Reports configuration screen of the SolutionPack for Smarts must match the values in SM_CAS_SERVER. In the example above:
    • Set M&R tomcat hostname or IP address to mnrhost.domain.com
    • Ensure M&R tomcat port number matches the port specified in SM_CAS_SERVER (58080 in the example)
    • Ensure the Frontend server in the Physical Overview uses the same naming convention (You must use the FQDN across all field entries.)
    • Use the FQDN, not the IP address, for hostnames; otherwise CAS (Central Authentication Service) will not work properly.
  2. Set the SM_TOMCAT_SERVER parameter in the runcmd_env.sh file of the Presentation SAM server to specify the Fully Qualified Domain Name (FQDN) of the SAM Tomcat server. Example: the value for HTTP mode is SM_TOMCAT_SERVER=http://<hostname.com>:8080. This SM_TOMCAT_SERVER entry must match the name and port values in the Smarts EDAA host name or IP address and Smarts EDAA port number fields of the Reports configuration block in the SolutionPack for Smarts.
  3. In the /opt/APG/Web-Servers/Tomcat/Default/conf/server.xml file:
    1. Locate and remove the entry redirectPort="58443"
      Before removing the entry redirectPort="58443", it appear as follows:
      <Connector port="58080" protocol="HTTP/1.1"
      redirectPort="58443" URIEncoding="UTF-8" />
      After removing the entry redirectPort="58443", it must appear as follows:
      <Connector port="58080" protocol="HTTP/1.1"
      URIEncoding="UTF-8" />
    2. Comment out the following line:
      <Valve className="com.watch4net.apg.v2.gui.tomcat.ForceSSL" />
  4. Restart the Tomcat service.
  5. Clear the browser cache, and then log in using HTTP.