Updates for Linux applications - middleware
With Updates for Linux applications - middleware content site, customer can deploy updates to a vast number of third-party middleware applications.
Note: Support for
N,
N-1, and
N-2versions are available for Middleware Patch update fixlets.
Prerequisite of Oracle weblogic
Before running the Fixlet, 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.
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 theORACLE_WEBLOGIC_HOME
key. - Customers can specify the
oraInventory
path for WebLogic by setting theORACLE_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 looks for the
ORACLE_WEBLOGIC_HOME
key within the /etc/environment file. For example, if theoraInventory
path is /Weblogic/Oracle/Middleware/oraInventory, theORACLE_WEBLOGIC_HOME
value would be /WebLogic/Oracle.
Steps to determine RedHat JBoss details on Linux system
These steps 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
andJBOSS_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 keyJBOSS_HOME
.
Steps to determine Apache Tomcat details on Linux (systemd-based)
This step involves locating specific configuration files, extracting information from
them, and filtering based on certain criteria:
- You need to find
.service
files in/etc/systemd/system
that contain theCATALINA_HOME
variable, which specifies the installation location of the software.
Steps to determine MariaDB details on Linux (RPM or Debian packages)
This step involves locating specific configuration files, extracting information from
them, and filtering based on certain criteria:
- For Linux systems, you can use package management tools to check for the
presence and version of
mariadb-server
.
Steps to determine MongoDB details on Linux (RPM or Debian packages)
This step involves locating specific configuration files, extracting information from
them, and filtering based on certain criteria:
- For Linux systems, you can use package management tools to check for the
presence and version of
mongodb-org
.
Steps to determine Postgresql details on Linux (RPM or Debian packages)
This step involves locating specific configuration files, extracting information from
them, and filtering based on certain criteria:
- For Linux systems, you can use package management tools to check for the
presence and version of
postgresql
.
Steps to determine IBM MQ details on Linux (RHEL or AIX packages)
These steps involve locating specific configuration files, extracting information
from them, and filtering based on certain criteria:
- For RHEL systems, check the installed version of the
MQSeriesRuntime
package using the RPM package manager. - For AIX systems, check the installed version of the
mqm.server.rte
using the AIX object repository.
Steps to determine IBM WebSphere details on Linux
This step involves locating specific configuration files, extracting information from
them, and filtering based on certain criteria:
- For Linux and Unix systems, it checks for files named
installed.xml
in the installed folders. For example, /opt/IBM/WebSphere/AppServer/properties/version or /usr/IBM/WebSphere/AppServer/properties/version.
Steps to determine Oracle JDK details on Linux
This step involves locating specific configuration files, extracting information from
them, and filtering based on certain criteria:
- For Linux, it can check the RPM or Debian packages on the machine for
jdk
and its version.
Steps to determine MySQL details on Linux
This step involves locating specific configuration files, extracting information from
them, and filtering based on certain criteria:
- For Linux, it can check the RPM or Debian packages on the machine for
("MySQL-server";"mysql-community-server")
and its version.
Steps to determine IBM DB2 details on Linux
This step involves locating specific configuration files, extracting information from
them, and filtering based on certain criteria:
- It checks for files named
spec
within the.metadata/BASE_DB2_ENGINE
directories located under the installed folder /opt/ibm/db2.
Pre-caching required for Linux applications
Software name | Pre-caching required (Yes/No) |
---|---|
Oracle WebLogic | Yes, needs manual caching. |
RedHat JBoss | Yes, needs manual caching. |
Apache Tomcat | No, files automatically cached to server by fixlets. |
MariaDB | No, files automatically cached to server by fixlets. |
MongoDB | No, files automatically cached to server by fixlets. |
Postgresql | No, files automatically cached to server by fixlets. |
IBM MQ | Yes, needs manual caching. |
IBM WebSphere | Yes, needs manual caching. |
Oracle JDK |
|
MySQL | No, files automatically cached to server by fixlets. |
IBM DB2 | Yes, needs manual caching. |