Application Monitoring & Server Maintenance

Prerequisites

• Pulse VPN installed locally

• WinSCP and Putty installed on the system

• Connectivity to AOC (from Adeptia network or through VPN)

Download Links

• Pulse VPN: Download Here

• Zscaler VPN: Instructions and Download

Pulse VPN Credentials:

Zscaler VPN Credentials:

Environments

Maintenance activities will be performed on two servers:

Server Info and URL for PROD Cluster

• 464 server (Primary): appdadc464.na.averydennison.net

• 465 server (Secondary): appdadc465.na.averydennison.net

URLs

• AOC Primary: http://appdadc464.na.averydennison.net/AveryDennison/

• AOC Secondary: http://appdadc465.na.averydennison.net/AveryDennison/

• AIS Primary: http://appdadc464.na.averydennison.net:8080/adeptia/control/

• AIS Secondary: http://appdadc465.na.averydennison.net:8080/adeptia/control/

Steps for Application Monitoring

1. Create Tickets:

   • "AOC PROD Monitoring dd-mm-yyyy"

   • "Avery PROD Solution Health Check dd-mm-yyyy"

2. Check AOC Application:

   • Verify order processing is working and not getting stuck.

3. Check Process Flow Logs in AIS:

   • Verify flows are not getting aborted.

4. Connect to WinSCP and Putty:

   • Check memory usage, hard disk space, and CPU usage.

Steps for Cleanup

WinSCP and Putty

1. Start WinSCP and open both servers using Putty (obtain username and password in advance).

2. Gain Full Privileges:

   • Use the command sudo su.

3. Check RAM Memory Utilization:

   • Use command free -m.

   • Free available RAM must not be less than X%.

4. Check Available Disk Space:

   • Use command df -h.

   • Available disk space must not be less than X%.

Maintenance Activity

1. Shutdown Both Clusters:

   • Shutdown Secondary Cluster (465) first. (Caution: If the primary is shut down accidentally, contact Support Lead immediately).

   • Shutdown Both Clusters:

     • Shutdown Secondary Cluster (465) first. (Caution: If the primary is shut down accidentally, contact Support Lead immediately).

   • Check JAVA Instances:

     • Use the command ps -A | grep java.

1. Verify 5 instances on 464 server and 4 instances on 465 server.

   • Stop JAVA Instances:

     • Navigate to /mnt/AdeptiaData/P2A/AdeptiaSuite-6.5/AdeptiaServer/ServerKernel or /AOC/AdeptiaData/P2A/AdeptiaSuite-6.5/AdeptiaServer/ServerKernel using cd command.

1. Stop Adeptia with command ./stop.sh.

   • Stop 465 cluster first, then 464 cluster.

   • Rename logs before starting servers again.

   • Verify Shutdown:

     • Use command ps -A | grep java.

Renaming Logs

1. Switch to WinSCP:

   • Path: /mnt/AdeptiaData/P2A/AdeptiaSuite-6.5/AdeptiaServer/ServerKernel/logs/applicationlogs or /AOC/AdeptiaData/P2A/AdeptiaSuite-6.5/AdeptiaServer/ServerKernel/logs/applicationlogs.

   • Rename KernelApplication.log and WebrunnerApplication.log using format: KernelApplication.log_15-5-2019.

Tomcat Log Cleanup

1. Shutdown Tomcat:

   • Navigate to /mnt/AdeptiaWeb/apache-tomcat-8.0.28/bin or /AOC/AdeptiaWeb/apache-tomcat-8.0.28/bin.

   • Use command ./shutdown.sh.

2. Delete Tomcat Logs:

   • Navigate to /mnt/AdeptiaWeb/apache-tomcat-8.0.28/logs or /AOC/AdeptiaWeb/apache-tomcat-8.0.28/logs on 464 cluster in WinSCP.

   • Delete Catalina.out.

3. Once the renaming of AIS log and deletion of Tomcat Log is accomplished user must start all instances of JAVA using command ./startup.sh

4. Make sure all 5 instances are running properly (4 AIS+ 1 Tomcat java)

Restart JAVA Instances

1. Start JAVA Instances:

   • Use command ./startup.sh.

   • Verify all 5 instances are running (4 AIS + 1 Tomcat java).

2. Verification:

   • Check java instances with ps -A | grep java.

   • Access Adeptia Suite: http://appdadc464.na.averydennison.net:8080/adeptia/control/

   • Access AOC application: http://appdadc464.na.averydennison.net/AveryDennison/