IBM Tivoli Composite Application Manager for Application Diagnostics, Version 18.104.22.168
Silent installation and configuration settings for Tomcat - J2EE Agent
Tomcat silent install parameter definitions for UNIX/Linux
Parameter Definition LICENSE_ACCEPT_BUTTON License agreement. You must specify this parameter to begin the product installation. Default setting is true. installLocation The location where you intend to install the product. LAUNCH_CONFIG This parameter launches the Configuration Tool. Specifying this parameter begins the process of configuring the DC to the Managing Server after installation. The default setting is true. LOGSETTING.LOGLEVEL The log level for the installation and configuration process. Possible values are: ALL / DEBUG_MAX / DEBUG_MID / INFO / WARN / ERROR / FATAL / OFF. LOGSETTING.LOGCONSOLEOUT This parameter controls whether the output message is printed to console or not. Possible values are true / false. DC Configuration UNCONFIGURE_SERVERS Specify this parameter will cancel the configuration process after the installation is complete. The default setting is false. J2EE_SELECTED ITCAM for J2EE's Application Monitor interface. Specifying this parameter will configure monitored data to be accessed through ITCAM for J2EE's Application Monitor interface. To use the Application Monitor interface, ITCAM for J2EE and its components must be fully installed. Default true. TEMA_SELECTED ITCAM for J2EE Tivoli Enterprise portal. Specifying this parameter will configure monitored data to be accessed using the ITCAM for J2EE's portal. To use the portal interface, ITCAM for J2EE and its components must be fully installed. Default false. SERVER_HOME Tomcat server directory location. Enter the root directory location in which Tomcat is located on. SERVER_VERSION Tomcat server version number. Enter the version of the Tomcat server that you are currently running. For example, if the Tomcat version is 5.0, SERVER_VERSION should be set as 50; if the version is 5.5, SERVER_VERSION should be set as 55. JAVA_HOME The location of the JDK. Enter the directory location of the JDK supporting Tomcat. IS64UNIXJVM The flag for 64 bit model. The default value is false. If you are running a 64 bit OS using 64 bit JVM on a UNIX or Linux platform, change the parameter to true. Ignore this parameter on Windows. DC_OFFLINE_ALLOW This is for you to decide whether offline configuration is allowed. If you enter "true", the program will skip the verification of the connection to the Managing Server (MS) during configuration, and use the entered value of MS_AM_HOME; if you enter "false", the program will connect to MS and detect the MS home directory on MS server. The default value is false. TEMA_OFFLINE_ALLOW The option indicates whether offline configuration type is allowed during the configuation. The program will skip the monitoring agent connection test if it is set to be true. Set it to false when you don't want to allow the offline configuration for the monitoring agent. AM_SOCKET_BINDIP This is the DC side IP address or full qualified Host name. The IP or Host name will be used by DC to communicate with MS.If there are more then one NIC or multiple IP address configured on DC server, choose one of them. For example: -V AM_SOCKET_BINDIP=22.214.171.124 or -V AM_SOCKET_BINDIP=dc.cn.ibm.com or -V AM_SOCKET_BINDIP=<value> FIREWALL_ENABLED For DC side if the firewall is enabled, set the value to be true; otherwise, set the value to be false. PROBE_RMI_POR If the DC is behind firewall, set this port number.This port number should be configured as allowable in firewall software on which the DC host locates. The legal values are from "8200" to "8299". PROBE_CONTROLLER_RMI_PORT If the DC is behind firewall, set this port number. This port number should be configured as allowable in firewall software on which the DC host locates. The legal values are from "8300" to "8399". Manage-Server Specific Options RECOLLECT_MSINFO Specify this parameter prompts the DC to recollect data from the Managing Server. Default true. MS_AM_HOME The location of the Managing Server. Enter the directory location where the Managing Server was installed. This parameter correlates the DC_OFFLINE_ALLOW. Refer to DC_OFFLINE_ALLOW for more detailed information. KERNEL_HOST01 Primary kernel server name. Enter full-qualified host name of the primary kernel server hosting the Managing Server. PORT_KERNEL_CODEBASE01 Primary kernel codebase port. Default 9122. Application Server Specific Options APPSERVER
Tomcat application server instance. Enter the Tomcat Server instance names that you wish to configure for data collection.
If you are editing the Tomcat Server instance name for the Tomcat configurator, check whether the instance name exists.
- If you are configuring a new Tomcat server, make sure there is no existing instance name. Use a different instance name.
- If you are reconfiguring an existing Tomcat server, you do not need to check the instance name.
The instance name information can be found in the directory, <DC_HOME>/runtime/. If there is an existing Tomcat Server instance name, you can find a child directory under this directory. The child directory takes the form as <Server Name>.<Node Name>.<Instance Name>. For example, tomcat_55_1029_1 is the instance name in the <DC_HOME>/runtime/tomcat55.tiv147.cn.ibm.com.tomcat_55_1029_1 directory.
STARTUP_FILE Server startup script. The startup script is a batch or command file containing the necessary command lines required to startup the application server. Enter the full file path of the startup script here. On UNIX/Linux, the startup script is <Tomcat Home>/bin/catalina.sh. Where <Tomcat Home> is the root directory where you installed the Tomcat server.
Parent topic:Performing a silent installation and configuration