Updates for Linux applications

Prerequisite of Oracle weblogic

Before running the Fixlets, make sure that these prerequisites are met on the Linux system:

Ensure you have the recommended version of JDK for Oracle Weblogic installed during installation and for patching Oracle Weblogic 12C and 14C.

Steps to determine Oracle weblogic details on Linux system

These steps involve locating specific configuration files, extracting information from them, and filtering based on certain criteria:

Note: We have customized the WebLogic Fixlet to meet customer needs by modifying its relevance.

The Fixlet retrieves the oraInventory path from the /etc/environment file using the ORACLE_WEBLOGIC_HOME key.
Customers can specify the oraInventory path for WebLogic by setting the ORACLE_WEBLOGIC_HOME key in the /etc/environment file. This enables the Fixlet to use this path for applying the WebLogic patches.
This enhancement serves as an optional feature where the default paths remain functional.
The Fixlet searches for the ORACLE_WEBLOGIC_HOME key within the /etc/environment file. For example, if the oraInventory path is /Weblogic/Oracle/Middleware/oraInventory, the ORACLE_WEBLOGIC_HOME value would be /WebLogic/Oracle.
Note: The folder must be named exactly oraInventory, as the ORACLE_HOME is retrieved from the oraInventory folder.

Steps to determine RedHat JBoss details on Linux system

Make sure that you have the recommended version of Red Hat JBoss installed during installation and configured separately according to the application's requirements.

To retrieve the details of the software version using relevance, follow the steps that involve locating specific configuration files, extracting information from them, and filtering based on certain criteria:

Search in installed folder for version.txt. For example, /opt/jboss.
Check directories specified by environment variables EAP_HOME and JBOSS_HOME.
Search directories containing "eap" or "jboss" at installed folder. For example, /home.
Check /etc/default/jboss-eap.conf and /etc/environment for files containing the key JBOSS_HOME.

Prerequisite of Apache Tomcat details on Linux (systemd-based)

Ensure that a supported Java version is installed and that the JAVA_HOME environment variable is set to the path of the installed JDK on the target endpoint.

Fixlet Action for Apache Tomcat x.x Upgrade

Stops the running Tomcat service using the systemctl stop command.
Creates a backup of the entire Tomcat instance (e.g.,
```
tar
      /usr/local/tomcat9
```
to /usr/local/tomcat9-backup_ActionID.tgz).
Note: The Apache Tomcat x.x version includes versions 9, 10, and 11.
The new version of Tomcat is extracted over the existing instance, excluding the 'conf' directory (the original 'conf' directory is preserved).
The new version's default 'conf' directory is extracted to a default-conf folder, allowing comparison with the original configuration.
The new version's UID and GID are reassigned to match the original instance's UID and GID.
The service is restarted using systemctl start.

If multiple Tomcat x.x instances are detected, the Fixlet will upgrade each instance.

Important:

Only Tomcat instances launched via systemd service are identified and upgraded.
Any changes to the UID and GID beneath the Tomcat instance will not be preserved. The new version will inherit the top-level UID and GID of the original instance.
Any new configuration options required for the upgraded Tomcat instance must be manually applied. The original 'conf' directory is kept for comparison purposes.