The patch command is the command-line interface to the IBM WebSphere Application Server patcher application.
Installing V5.0.0 Enterprise features can cause related components to regress. The patcher determines regressed components and corrects their history information.
You can prevent component regression when installing V5.0.0 Enterprise features as described in Warning: no string named [rins_installee50] found.. The patcher utility is a work-around for the scenario where you install a V5.0.0 feature without using the InstallEE50 command.
There are three known scenarios for the regression problem:
Scenario 1 - Installing features after installing Fix Pack 1
To correct scenario 1:
./patch.sh install_root -disableFixPack was50_fp1_platform
./patch.sh install_root -apply -disableFixPack was50_fp1_platform
Scenario 2 - Installing features after installing Fix Pack 1 and Fix Pack 2
Scenario 3 - Installing features after installing Fix Pack 2 only
To correct either scenario 2 or scenario 3:
patch.sh install_root -disableFixPack was50_fp1_platform -disableFixPack was50_fp2_platform
patch.sh install_root -apply -disableFixPack was50_fp1_platform -disableFixPack was50_fp2_platform
The platform placeholder in the fix pack name represents the target installation platform:
For example, on a Linux or UNIX-based platform:
./patch.sh /opt/WebSphere/AppServer -apply -disableFixPack was50_fp1_sun -disableFixPack was50_fp2_sun
On a Windows platform:
patch.bat "c:/Program Files/WebSphere/AppServer" -apply -disableFixPack was50_fp1_win -disableFixPack was50_fp2_win
Stop all Java processes on the machine that use the IBM Developer Kit that WebSphere Application Server provides: Before using the patcher, stop all Java processes on the machine that use the IBM Developer Kit that WebSphere Application Server provides to support the Java 2 SDK on your operating system platform, such as the IBM Developer Kit for AIX, Java Technology Edition. Stop all application server processes, the nodeagent process, the deployment manager process, and all server processes, such as the jmsserver process. Features with server processes include the IBM HTTP Server and the embedded messaging feature. Stop all Java processes, if necessary. If you use the patcher while a WebSphere Application Server-related Java process runs, IBM does not guarantee that the product can continue to run successfully or without error.
Remove the WebSphere MQ tray icon if present On a Windows platform, remove the WebSphere MQ tray icon if it is present. The WebSphere MQ tray icon in the lower right corner indicates that a WebSphere MQ process (amqmtbrn.exe) is running. Right click the tray icon and click Hide to remove it.
Do not launch multiple copies of the patcher at one time The patcher cannot be launched concurrently with itself. Performing more than one update at the same time can lead to a failed or faulty installation.
The JAVA_HOME environment setting. Set the environment variable or issue the appropriate command script, from the install_root/bin directory of the installation root:
Windows systems:
Linux and UNIX systems:
Copy the files into the directory containing V5.0.2.x of the update installer program (also known as the updateInstaller program or the update installation wizard). The installer.jar JAR file is required.
Syntax and parameters
Linux and UNIX-based platforms
patch.sh [ install_root ] [ -apply ] [ -verbose ] [ -usage ] [ -help ] [ -revision ] [ -custom propertyFileName ] [ -disableComponents ] [ -enableComponent componentName ] [ -enableComponents ] [ -disableComponent componentName ] [ -disableFixes ] [ -enableFix fixId ] [ -disableFix fixId ] [ -disableFixPacks ] [ -enableFixPack fixPackId ] [ -disableFixPack fixPackId ]
Windows platforms
patch.bat [ install_root ] [ -apply ] [ -verbose ] [ -usage ] [ -help ] [ -revision ] [ -custom propertyFileName ] [ -disableComponents ] [ -enableComponent componentName ] [ -enableComponents ] [ -disableComponent componentName ] [ -disableFixes ] [ -enableFix fixId ] [ -disableFix fixId ] [ -disableFixPacks ] [ -enableFixPack fixPackId ] [ -disableFixPack fixPackId ]
Typically, the patcher utility is invoked once without the -apply argument to display regressions, then, if needed, invoked a second time with -apply to perform corrections on history information.
The patcher utility scans the target installation directories to verify the installation, then scans installed components and installed updates (fix packs and interim fixes) for regressions. An update is regressed when the component build date is earlier than the update build date.
Parameters
Use the following parameters for the patch command:
Specify -custom to use a properties file to force on or off component regressions and to skip particular updates, regardless of actual detected regressions.
The properties file supports these properties:
enableComponents=true componentName=disable disableComponents=true componentName=enable disableFixes=true fixId=enableFix fixId=disableFix disableFixPacks=true fixPackId=enableFixPack fixPackId=disableFixPack
Using the patcher to update components
Use the patcher to enable or disable single components, or all components.
To enable all components but disable those components you specify, use these parameters:
enableComponents=true and componentName=disable
To disable all components but enable those components you specify, use these parameters:
-disableComponents=true and componentName=enable
If you use the disableComponents parameter, you must specify some enablement. Disabling all components halts all processing, and returns a success return code (0).
Specifying both enableComponents and disableComponents produces an error.
Updates for fix packs and interim fixes
You can disable single interim fixes or all interim fixes. You can enable single interim fixes.
Updates for fix packs
You can disable single fix packs or all fix packs. You can enable single fix packs.
Return codes
Patcher return codes are: