Deployment Administration / Maintenance

Post date: Oct 6, 2017 5:23:27 AM

Restart Triniti Applications Server

The following are the different scenarios where restarting Triniti Applications Server is required with proper stop and start of the application server:

• 1. Whenever Database is bounced

  2. Whenever High CPU usage is identified for long time

  3. Whenever Server is not responding with Busy database connections

Use the below sequence of step to proper shutdown and start the Tomcat application server:

• 1. Open Linux server VNC session

  2. Navigate to Tomcat HOME directory path - cd $CATALINA_HOME

  3. Change to bin directory - cd bin

  4. Execute Tomcat shutdown shell script - sh shutdown.sh

  5. Kill all java processes if any

  6. Change to Triniti HOME directory path - cd $TRINITI_HOME

  7. Change to MigBuild directory - cd MigBuild

  8. Execute logs files copy and remove shell script - sh CopyRemoveLogs.sh

  9. Start Tomcat

     1. Start the tomcat using below commands in the same VNC session

     2. $ cd $CATALINA_HOME/bin

     3. $ sh startup.sh

     4. Verify tomcat startup log

     5. Go to tomcat logs folder and check for catalina.out file content

     6. $ cd $CATALINA_HOME/logs

     7. $ tail -f catalina.out

     8. Wait for server to start completely (log file shows “server started in <n> seconds).

     9. You will see prints something like below

Run Triniti Custom Schemas Gathering Optimizer Statistics

Gathering Optimizer Statistics for TDM Framework schemas - STATEGPS, SCH, TAS., and other Triniti Application specific schemas need to be scheduled on weekly basis.