Apache Tomcat Multiple Instances

Learn more about Apache Tomcat that can run multiple instances on a single endpoint. To support accurate detection and seamless patching of all Apache Tomcat installations, BigFix uses the Middleware Scanner. The scanner discovers all installed versions and paths, while the patching process updates outdated versions in a single execution.

Scanner Process

For running the scans on every software versions, refer to BigFix Scanner for Middleware Application. These results are then used by the Apache Tomcat patching tasks to determine which instances require updates.

Note: Before performing any patching activity, it is recommended to create a backup of all custom configurations, instance files, and environment-specific settings. This ensures that you can restore custom configurations if required after the patching process.

Patching Process

The Apache Tomcat patching task uses the scanner results to identify lower versions and update them to the patch version specified in the task.

Select the applicable computer in the BigFix Console to review installed versions.
When you take action on the endpoint, the patching task reads the results.xml and identifies all DB2 instances.
All outdated/lower Apache Tomcat versions are updated in a single execution, including:
Recommended:
If only one instance is found, that specific instance is patched.

If multiple instances (for example, five) are found, the task loops through all five instances and attempts to patch them all in a single execution.
If the installed version is the same or greater, then the patching is skipped.
Note:
- Services must be stopped before starting the patching process and should be restarted once the patching is complete.
- Registry keys are not updated as part of the patching process. Only the bin and lib folders are copied during patching.

Exit codes and their meanings

When performing tasks such as patching or extracting files in Apache Tomcat, certain exit codes may be returned to indicate the outcome of the operation. These codes help to find the issues during the installation or update process. Below is a list of common exit codes, along with their meanings and suggested actions to resolve the issues.

Note: Tomcat checks its version using version.sh or version.bat. Make sure that all required JDK/JRE prerequisites are met before continuing.

Table 1. Exit codes and their meanings
Exit code	Action
Exit Code 11: Patching of one or more instances failed	Run the discovery task again to retrieve the latest versions of the installed Tomcat instances. Ensure that all instances are properly configured and accessible.
Exit Code 12: Archive file not found	Verify that the download link is correct and the file is accessible. Ensure the file exists at the specified location.
Exit Code 13: Extraction of the archive failed	Check if you have the necessary file extraction permissions Ensure that the extraction path is valid and has sufficient space.
Exit Code 14: Extracted folder missing required files	Review the extracted contents and ensure that all required files are present. Refer to the vendor documentation for a list of necessary files and folders that should be included in the archive.