5.3 Installing a Server Patch

The procedure for installing the patch is the same for UNIX and Windows. The type of file for a patch is .jar. If you receive the file with a different extension, rename it to .jar before installing it.

One or more patches can be applied at a time, but patches and rollbacks cannot be applied at the same time with the same command. When a patch has already been applied, but is a older version than what you are installing, it is necessary to rollback the patch before installing the newer version of the patch.

When a patch bundle is applied, all previously applied patches are removed before the patch is applied.

To install the patch:

  1. Verify all clients are logged off.

  2. Shutdown all Operations Center processes.

  3. Copy the patch bundle file to the Operations Center installation root directory.

  4. At the command prompt from within the Operations Center installation directory, enter:

    java -jar patch_filename(s) patch_option(s)

    For example:

    C:/OperationsCenter_install_path>java -jar 500-20110328-NOC.jar --describe

    where C:/OperationsCenter_install_path> is your command prompt. Note that patch files can be listed in any order as the installation process automatically sorts and applies them.

    and where, patch_filename(s) can be a list of one or more patch files separated by a space,

    and where, patch_option(s) are any of the following commands that can be added at the end of the patch command:

    • ‑-help: Displays a list of possible commands including the following options.

    • ‑-describe: Prints patch manifest information

    • ‑-prompt: Displays the Operations Center Configuration Manager after the patch is installed.

    • ‑-verbose: Prints detailed information to the screen as the patch is installed.

    • ‑-force: Forces a patch to install even if it has already been applied. Never use the force command unless instructed to by Technical Support.

    If installing on Windows and User Access Control (UAC) is enabled, you must run the command prompt as the Administrator.

  5. During installation, the following occurs:

    • A back up is automatically created for all files that are overwritten. For more information about rollback files, see Section 5.4, Rolling Back a Patch Installation.

    • Patches (of the same version) that have already been applied are skipped unless the --force option was set.

    • The Operations Center Configuration Manager always runs silently and applies the current settings.

    • The patch does not override the existing Operations Center Configuration Manager settings.

      For more information regarding the Operations Center Configuration Manager, see the Operations Center 5.0 Server Configuration Guide.

    • A Done message displays when the patch install completes and the command prompt displays.

  6. After the installation is complete, do the following:

    1. Implement custom template modifications into the new template files.

      Do NOT overwrite new template files with old template files or modify default properties files. Add custom property modifications into a custom.properties file. For example, any customizations to the Formula.properties file should be added to a Formula.custom.properties file. For more information about the custom properties file, see Making Custom Changes in the Operations Center 5.0 Server Configuration Guide.

    2. Run the Operations Center Configuration Manager and make changes as needed.

    3. Start the Operations Center server.

    4. Log on to the Operations Center server as the Operations Center user.

    5. If running an FX Monitor from another location other than the default /OperationsCenter_install_path/html/classes/ directory, do the following:

      1. Shutdown the FX Monitor.

      2. Copy the /OperationsCenter_install_path/html/classes/fxmonitor.jar file to the alternate FX Monitor location.

      3. Start the FX Monitor.

        For more information about the FX Adapter, see Operations Center 5.0 F/X Adapter Guide.

    6. If running Relay, do the following:

      1. Shutdown Relay.

      2. Copy the relay/bin/relay.jar file into the relay_base_directory/bin directory.

      3. Start Relay.

    7. If running HP Network Node Manager (NNM), do the following:

      1. Shutdown the OvORB service.

      2. Rename the OvORB_base_dir/integrations/nnm.jar file as nnm-ga.old.

      3. Copy the /OperationsCenter_install_path/integrations/nnm.jar file into the OvORB_base_dir/classes directory.

      4. Start the OvORB service.

        For more information about OvORB, see OvORB for HP OpenView Network Node Manager in Operations Center 5.0 Adapter and Integration Guide.

If an Experience Manager patch is supplied, additional steps are required to update Experience Manager (see the Operations Center 5.0 Experience Manager Guide for more information).

After the patch has been installed and a rollback file is created, the patch cannot be installed again. If you attempt to run the patch bundle .jar file again, the following error messages are displayed:

ERROR: Unable to continue since rollback jar already exists

ERROR: unable to create rollback jar