Contents

Tomcat and Apache Upgrade Checklist

Andrew Dotto Updated by Andrew Dotto

Purpose

This checklist will help you align your tasks with the tasks carried out by the OneAdvanced technical teams, to help you keep track of the step by step tasks required to upgrade your Tomcat and Apache versions within Job Manager.


Preparation Checklist

Checklist

Status

Comments

Send Comms to the Intended recipients

Check the Pre-Image of the Existing system

a) Take a snapshot of running Processes/Services for Kirona

c) Check the version of Java home and Tomcat version that is being currently used

    (i) Check the recent catalina.<date>.log under c:/tpp/tomcat/<<INSTANCE>>/<<Application Version>>/logs

d) Check the Apache running version under services.

Backup Existing Environment's Configuration and Properties file.

a) Copy all the files under c:/app/kirona/admin to the backup location

b) All the files under c:/app/kirona/bin to the backup location

Backup Existing Environment's Tech Stack

a) Take a backup of bin,conf,lib,temp,webapps folders under C:/tpp/tomcat/<<INSTANCE>>/<<Application Version>> to backup location

b) Take a backup of bin,conf,lib,temp,webapps folders under C:/tpp/tomcat/<<INSTANCE>>/integrationTest to backup location

c) Take a backup of bin,conf,lib,temp,webapps folders under C:/tpp/tomcat/<<INSTANCE>>/drsTest to backup location

d) Copy the *.bat files under c:/tpp/tomcat/<<INSTANCE>>/bin/servicescripts to the backup location


Apache Upgrade Checklist

Checklist

Status

Comments

Unzip new version of httpd and copy it under  :/tpp/apache/<Rename_to_New_Version_Name>

Compare c:/tpp/apache/<Current_running_version>/conf/httpd.conf with c:/tpp/apache/<New_version>/conf/httpd.conf and edit the new versoin to match with current one.

Compare c:/tpp/apache/<Current_running_version>/conf/extra/httpd-ssl.conf with c:/tpp/apache/<New_version>/conf/extra/httpd-ssl.conf and edit the new version to match with current one.

Copy the ssl folder from c:/tpp/apache/<current_version>/conf to c:/tpp/apache/<new_version>/conf

Stop Kirona services by running c:/app/kirona/admin/stopall_<<Application Version>>_tomact_services.bat

Stop Apache Service

Open Command Prompt and Navigate to c:/tpp/apache/<current_version>/bin and run

Navigate to c:/tpp/apache/<new_version>/bin and run

Run

Start httpd service

Check if the URL without <<Application Version>> is accessible. If not check for the apache logs for any possible errors, if not bring up the JM app and add <<Application Version>> in the URL and see if this webpage is accessible. If yes, then we are good with this step.


Tomcat Upgrade Checklist

Checklist

Status

Comments

Unzip new version of Apache Tomcat and copy it under c:/tpp/tomcat/<Rename_to_New_Version_Name>

Change the below set of Service scripts to point to new Java/Apache/Tomcat locations  c:/tpp/tomcat/<<INSTANCE>>/bin/servicescripts/*Testservice.bat

run the following in a command prompt: set CATALINA_HOME , set JAVA_HOME, set DISPLAY_NAME=, set JVM=

and --Description lines to point to the newer version(if those lines ate printing to version) and go through the entire script to see if change is needed anywhere else regarding versions.

Make sure JM services are in Stopped state and Open Command Prompt and navigate to the backup folder and uninstall the applications using backup *service.bat files <<Application Version>>service.bat remove

check the services if JM App is removed drsTestservice.bat

remove and check the services if JM DRS is removed integrationTestservice.bat remove and check the services if integration App is removed repairsTestservice.bat remove and check the services if repairs App is removed

Open Command Prompt and navigate to the c:/tpp/tomcat/<<INSTANCE>>/bin/servicescripts/ and install the applications using original *service.bat files and check the output if JAVA and catalina are referring to the new version. <<Application Version>>service.bat install and check the services if JM App is installed drsTestservice.bat install and check the services if JM DRS is installed integrationTestservice.bat install and check the services if integration App is installed repairsTestservice.bat install and check the services if repairs App is installed

Start all the applications by running the start all script under c:\app\kirona\admin and check if the services are running.  Also check for c:\tpp\tomcat\<<INSTANCE>>\<<Application Version>>\logs\catalina_<date>.log for any possible errors annd make sure the start up parameters are referring to the new java and catalina versions. Validate the <<Application Version>> URL accessibility and login.

Under C:\app\kirona\admin modify the below set of files to refer to the new versions. *_installer.properties files Validate Oracle_home, it should match with oracle_home configured under oraclient19.bat file *_tomcat.bat files Change TOMCAT_REL and JAVA_REL to point the new version.

Under C:\app\kirona\bin, make sure all the *installer.bat files are referring to the correct ora*.bat file that matches with the new oracle version

Extract the app software from staging location to c:\app\kirona\admin\upgrades\<particular_app>\

Comment the CHECK_SCHEMAS option in instructions.txt under c:\app\kirona\admin\upgrades\<app>\<New_version>

Run the query within an Oracle console

SELECT GRANTEE, GRANTED_ROLE FROM DBA_ROLE_PRIVS where granted_role = 'KIRONA_APP'; to get the list of usernames to be passed during the installation time.

Open Command prompt and navigate to cd c:\app\kirona\admin\upgrades\<app>\<New_version>

Run /app/kirona/bin/<<Application Version>>_installer.bat install 9.2.2 KJMDEV DEV and pass the parameters during run time and check the run log files for any errors.

Check for any Invalid Objects in the database and recompile the invalid objects to make them valid and still not possible, then run utlrp.sql to recompile invalid objects.

 Run the below query

BEGIN
application_utils.set_organisation(1);
application_utils.set_username('KIRIMP');
END;

/INSERT INTO kir_user_roles
(   kur_org_id,
    kur_usr_username,
    kur_kre_code )
VALUES (1, 'JOBMANAGERIS', 'JM_SW_INTEGRATION')/

Stop all applications including Apache and start all applications manually to make sure everything is working well.

Launch the application and check for the accessibility.

Test the database connectivity of the applications using https://<hostname>/<app_name>/monitor/database.jsp

Check in Server.xml file under all the apps in the container if it holds SecretKey="false" or True according to the entry in httpd-ssl.conf

Was this article useful?

Updating Apache Versions for Job Manager

Contact