How to upgrade the Control-M/Enterprise Manager supplied Web Server (Tomcat 8.5.31) in Control-M 9.0.19?

Version 10
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Control-M/Enterprise Manager


    COMPONENT:

    Control-M/Enterprise Manager


    APPLIES TO:

    Control-M/Enterprise Manager 9.0.19 only



    QUESTION:

    How to upgrade the Control-M/Enterprise Manager supplied Web Server (Tomcat 8.5.31) in Control-M 9.0.19?
     


    ANSWER:

    For Control-M version 9.0.00 or lower please refer to knowledge article 000102371
    For Control-M version 9.0.18 the procedure to upgrade Tomcat is documented in knowledge article 000148756
     

      1)   Download the latest available Tomcat minor version 8.5.xx binaries from https://tomcat.apache.org/download-80.cgi (Binary distribution Core, ZIP or tar.gz file)
             Or Tomcat minor version 9.0.xx binaries from https://tomcat.apache.org/download-90.cgi (Binary distribution Core, ZIP or tar.gz file)

    2)    Extract the new Tomcat package to a newly created temporary source location on the Control-M/Enterprise Manager server:
           a. Windows: %EM_HOME%/Tomcat_Update
           b. UNIX: $EM_HOME/Tomcat_Update
         
    3)    Stop all Control-M/Enterprise Manager components with the following command:
            Unix:  em ctl -mcs -all -C Config_Agent -cmd shutdown
            Windows: ctl -mcs -all -C Config_Agent -cmd shutdown

    4)    Make sure all components were stopped:
                   All GUI Servers
                   GCS
                   Naming Service
                   CMS
                   Configuration Agent (maintag)
                   BIM
                   Forecast
                   Self Service
                   All Gateways
                   Archive Servers
                   Web Servers
                  
             Note: The Enterprise Manager database should remain running
     
    5)    Backup the destination Control-M/Enterprise Manager server “Tomcat” directory (copy to different directory)
           a. Windows: %EM_HOME%/emweb/tomcat
           b. UNIX: $EM_HOME/etc/emweb/tomcat

    6)    Rename the destination Control-M/Enterprise Manager server directory tomcat/bin to tomcat/bin-org.

    7)    Rename the destination Control-M/Enterprise Manager server directory tomcat/lib to tomcat/lib-org.

    8)    Copy the directories “bin” and “lib” from the temporary source location in Step 2 to the destination directory "tomcat".

    9)    Copy the files LICENSE, NOTICE, RELEASE-NOTES and RUNNING from the source location in Step 2 to the "tomcat" destination directories(overwrite the existing files)

    10)   Copy the following .jar files from the destination directory lib-org in Step 7 into the new destination directory emweb/tomcat/lib:
      
       
    • bc-fips-1.0.1.jar
    •  
    • bcmail-fips-1.0.1.jar
    •  
    • bcpg-fips-1.0.1.jar
    •  
    • bcpkix-fips-1.0.1.jar
    •  
    • bmc-data-collection.jar
    •  
    • BMCHeaderSecurityFilter.jar
    •  
    • commons-codec-1.9.jar
    •  
    • CustomAccessLog.jar
    •  
    •  log4j-1.2.8.jar
    •  
    • ojdbc8.jar
    •  
    • postgresql-9.3-1102.jdbc4.jar
    •  
    • security-9.0.jar
    •  
    • slf4j-api-1.6.4.jar
    •  
    • slf4j-jdk14-1.7.6.jar
    •  
    • sqljdbc4.jar
    •  
    • web_connector.jar
        
    11)   Delete all folders under destination directory "webapps" except ROOT folder, but do not delete any of the .war files.
           a. Windows: %EM_HOME%/emweb/tomcat/webapps
           b. UNIX: $EM_HOME/etc/emweb/tomcat/webapps


    12)  Delete the AIRepo directory under tomcat directory is not using Control-M Application Integrator.
     
    13)    Start all EM components
           a. Windows: Start Service "Control-MEM Configuration Agent"
           b. UNIX: em start_config_agent
     
    14)    Only after confirming that the web server starts and Control-M functions properly, delete the destination directories tomcat/bin-org and tomcat/lib-org.

      

     


    Article Number:

    000271725


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles