Jboss Multiple Instances

Learn more about Jboss that can run multiple instances on a single endpoint. To support accurate detection and seamless patching of all Jboss 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 Jboss 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 Jboss 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 Jboss 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.

Exit codes and their meanings

When performing tasks such as patching or extracting files in Jboss, 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:

If the JBOSS_HOME is set, it will be automatically unset by the script. Make sure that you add or reset the JBOSS_HOME variable after patching is completed. This behavior applies only to offline patching.

A temporary folder named C:\middleware\patch_tmp_jboss_<version> will be created during patch extraction and automatically deleted after the patching process completes.

Table 1. Exit codes and their meanings
Exit code	Action
Exit Code 12: Patch Failure	Patching for one or more Jboss instances has failed. Refer to the mw_update.log file in the installation directory for complete details. During patching, a new folder is created that stores all JBoss patch logs under: <BES Client>/middleware/Jboss