skip to main content
Progress Application Server Administration : Administrative scripts
 

Administrative scripts

This topic is a brief overview of some of the administrative utilities for the Progress Application Server, which are implemented as scripts in the Tomcat server's /bin directory. Each script has a UNIX (.sh extension) and a Windows (.bat extension) version.
Notice that the Progress Application Server implements the TCMAN command line utility as an interface to administrative functionality provided by core Tomcat scripts. You will find extended administrative functionality that is easier to find and to use if you run TCMAN rather than running the Tomcat scripts directly.
The following table lists the standard Tomcat utilities in $CATALINA_HOME/bin that were tailored by Progress to set the value of CATALINA_HOME and CATALINA_BASE to values appropriate for the Progress Application Server and its instances.
Table 5. Standard Tomcat utilities modified for Progress Application Server
startup.sh(.bat)
Initiates the start up of the Tomcat server and its web applications.
Functionality of this utility is also available through tcman.sh start
shutdown.sh(.bat)
Initiates the Tomcat server’s shutdown process, beginning with a graceful termination of any running web applications.
Functionality of this utility is also available through tcman.sh stop
version.sh(.bat)
A standard Tomcat script that displays version and system information.
Functionality of this utility is also available through tcman.sh info
configtest.sh(.bat)
Displays the Tomcat server’s configuration and environment information.
Functionality of this utility is also available through tcman.sh test
In addition, there are a number of supporting scripts that are called by Tomcat administrative utilities. Some of these supporting scripts are described in the following table.
Table 6. Supporting administrative scripts for Progress Application Server
catalina.sh(.bat)
Called by administrative utilities on startup or shutdown of the Tomcat server. Calls setenv.sh(.bat) (if it exists) and setclasspath.sh(.bat) to set environment.
setclasspath.sh(.bat)
Called by catalina.sh(.bat) to set JAVA_HOME or JRE_HOME if not already set. If they are set, it validates to ensure that the values are consistent with startup options.
setenv.sh(.bat)
An optional file called by catalina.sh(.bat) on startup. Deploying this file is the standard way to customize the server environment for each running instance.
setenv.sh performs the following operations:
1. Set JVM memory size and the CATALINA environment variables common to all Progress product Web applications.
2. Load Java system properties from conf/server.xml.
3. Find and run any progress_product_setenv.sh(.bat) files.
In addition to the standard Tomcat administrative utilities and supporting scripts described above, Progress Application Server The following table lists the utility scripts in the Progress Application Server /bin directory that were added by Progress to the standard Tomcat server.
Table 7. Progress Application Server scripts
tcman.sh(.bat)
Runs the TCMAN administrative utilities necessary to manage the Progress Application Server. tcman.sh is a command-line wrapper for tools that are implemented in tcmanager.sh and it also manages the instance variables, $CATALINA_HOME and in $CATALINA_BASE.
tcmanager.sh(.bat)
Called by tcman.sh to implement the TCMAN administrative utilities necessary for managing the Progress Application Server. This script is a wrapper for the built-in Tomcat utilities, including startup.sh , shutdown.sh , version.sh, and configtest.sh. In addition, TCMAN adds new administrative functionality specifically for the Progress Application Server.
progress_product_setenv.sh(.bat)
Called by the Tomcat setenv script to set Progress product-specific environment variables and make them available to Java processes.
If this file exists in $CATALINA_HOME/bin and in $CATALINA_BASE/bin, the file in $CATALINA_BASE takes precedence.