Internal Errigal Collaboration Wiki

User Tools

Site Tools

Trace:
Writing /app/www/public/data/meta/introduction/appservers/start.meta failed
introduction:appservers:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
introduction:appservers:start [2017/02/02 11:30] – mmccintroduction:appservers:start [2021/06/25 10:09] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== Interacting With Application Servers ======
  
 +Author: Won Lee
 +
 +Updated: Michelle
 +
 +As you become more familiar with the Errigal environments and have begun working on either the operations or development team it is possible that you will be carrying out certain tasks related to application servers. 
 +
 +Examples of these tasks include starting, stopping, and restarting applications, tailing the logs to troubleshoot issues, and or investigating various directories on the servers.
 +
 +This section will describe how to carry out each of these tasks.
 +
 +----
 +
 +===== Starting and Stopping An Application =====
 +
 +There are a number of reasons for stopping and starting applications including troubleshooting an issue or implementing a configuration change.
 +
 +The first time you do this task, be sure to consult with your mentor so you have someone beside you should you have any questions.
 +
 +==== Starting An Application ====
 +
 +  * The **startup.sh** script is responsible for starting up an application
 +  * Each application has its own startup.sh. 
 +  * Note: Only the SnmpManager's startup.sh is required to be run by sudo. Any other applications don't need to be run as sudo.
 +
 +==== Shutting Down An Application ====
 +
 +  * The shutdown.sh script is responsible for shutting down an application
 +  * Like startup.sh, each application has its own one. 
 +  * Note: shutdown.sh for SnmpManager needs to be run by sudo and others don't.
 +
 +==== Tailing the logs ====
 +
 +  * It is very important that you tail the application log and the catalina log when you start up or shutdown application. 
 +  * This allows you to monitor for any issues during the process
 +  * You can tail log file by using the command: ''tail -f //__pathToLogFile__//''
 +
 +For more info on how to start and stop an application please refer to the following wiki entry: [[databaseandnetworkmanagement:restarting_application_container|Restarting An Application Container]]
 +----
 +
 +===== File Directories =====
 +
 +The following section outlines the file directory structure conventions of the most commonly used systems.
 +
 +==== ExteNet ====
 +=== War File ===
 +  * /var/tomcat///__ApplicationName__///webapp///__ApplicationName__//.war
 +=== Start/Stop Script ===
 +  * /var/tomcat///__ApplicationName__///bin/
 +=== AppFile ===
 +  * /home/scotty/appfiles/
 +=== Log Directory ===
 +  * Application Log ... /home/scotty/log/grails///__ApplicationName__//.log
 +  * Catalina Log ... /var/tomcat///__ApplicationName__///log/catalina.out
 +
 +----
 +
 +==== Errigal QA ====
 +=== War File ===
 +  * /var/tomcat///__ApplicationName__///webapp///__ApplicationName__//.war
 +=== Start/Stop Script ===
 +  * /var/tomcat///__ApplicationName__///bin/
 +=== AppFile ===
 +  * /usr/local/appfiles/
 +=== Log Directory ===
 +  * Application Log ... /usr/local/logs///__ApplicationName__//.log
 +  * Catalina Log ... /var/tomcat///__ApplicationName__///log/catalina.out
 +
 +
 +----

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki