John Lewis Partnership
Websphere Application Decommission Document
Technical Information Document (TID):
Decommission of Websphere Application
Version 1.00
Prepared By Reviewed By Approved By
Name Maheshbabu Kamireddy
Role Lead Administrator
Date July 2022
Document Security - Company Confidential
This document is the sole property of the John Lewis Partnership and is for internal use only within
the John Lewis Partnership, John Lewis & Partners, and Waitrose & Partners. No part of this
document, or any document referenced herein in full or in part, may be shared with any individual
or legal entity outside the John Lewis Partnership including, but not limited to, other Companies
incorporated within the UK or internationally.
1 Glossary
Term Description
WAS Websphere Application Server
JVM Java Virtual Machine
IHS IBM Http Server
DB Database
LB Load Balancer
WTR Waitrose
PIT Partnership IT
2 Introduction
This technical information document (TID) contains detailed processes and procedures to
implement decommission of Websphere Applications across the Partnership.
2.1 Technical Information Document Scope
2.1.1 What the TID covers
The purpose of this TID is to provide the comprehensive information to understand the
decommission process flow and to Implement the decommission process and procedures
3 Overview
3.1 Please find the below workflow to understand the Decomm process.
4 Implementation
4.1 Validate the Request
For Non prod servers, requesters should raise RITM requests.
In the case of Prod , it should be through a change request.
Please Validate the Request thoroughly and make sure the Application name, Environment and
JVM details are correct. Reach out to requester in case of any queries
4.2 Application Decommission procedure
1) Stop the application
2) Disable auto restart of the application from WAS Console
3) Stop the JVM also in case if it is a standalone application
4) Stop the IHS if anything is mapped to the application.
We will monitor for a 2 week Cool off period and in case of any issues reported, we will
bring up the IHS, JVM and Application.
###############AFTER 2 WEEKS OF COOL OFF PERIOD############
5) Contact DB team and ask them to proceed with their tasks from DB end(Stopping DB,
removing the configuration etc..,)
6) Contact Network team and ask them to proceed with their tasks from Network
end(disabling LB, removing the configuration etc..,)
7) Uninstall the application and remove application related configuration from Middleware
end
8) Delete the JVM in case of standalone application
9) Make sure the auto start script for nodeagent and JVM auto start after server reboot is
deleted for related JVM instances at OS level (Ex: under /etc/intd).
