How to Deploy Hotfixes and Track Hotfixes Applied on Data Flow Probe

Starting from version 10.30, packaging of hotfix files is improved to enable easy deployment and management, and a new JMX method showAllBinariesApplied is introduced to enable you to easily view and track all information about the hotfixes you deployed.

Note This hotfix deployment mechanism is applicable for engine hotfixes on probe only, not for content library hotfixes. Therefore the hotfixes for the following paths still follow the old process:

  • DataFlowProbe\runtime\probeManager\discoveryResources
  • DataFlowProbe\runtime\probeGateway\discoveryResources
  • DataFlowProbe\content

Also, invoking the showAllBinariesApplied JMX method will return the result about engine hotfixes only.

When you deploy hotfixes, you are actually deploying each of them separately in a different folder under the classes folder. After deployment, the hotfix path looks like the following:

<DataFlowProbe_install_dir>/classes/HF_QCCR1HXXXXX/com/hp/ucmdb/

The hotfix folder name where the classes are loaded follows the format of HF_QCCR1H<ID>. If the hotfix folder name does not start with the HF_ prefix, the classes for the hotfix will not be loaded.

The hotfix Readme file should be located directly inside the hotfix folder. For example, for HF_QCCR1H101112, the readme file is located in the folder ..\HF_QCCR1H101112/Readme_QCCR1H101112.txt, as shown in the screenshot below. If it has a different name and/or placed in a different location it will not be read.

Note  

  • Hotfixes are loaded at probe startup. If a new hotfix is deployed, it will not be displayed until the probe restarts.

  • Every hotfix has a unique QCCR ID, which will be added to the hotfix folder name after the HF_ prefix.

  • When multiple hotfixes are deployed, class files from hotfixes will be loaded in the sequential order of QCCR IDs of the hotfixes. For example, if hotfixes HF_QCCR1H101112 and HF_QCCR1H123122 are deployed, the class files from HF_QCCR1H101112 will be loaded first. This is important to know in the corner case when a class file is deployed on the server side by two hotfixes.

  • This hotfix deployment mechanism is applicable for engine hotfixes on probe only, not for content library hotfixes. Therefore the hotfixes for the following paths still follow the old process

    • DataFlowProbe\runtime\probeManager\discoveryResources
    • DataFlowProbe\runtime\probeGateway\discoveryResources
    • DataFlowProbe\content

    Also, invoking the showAllBinariesApplied JMX method will return the result about engine hotfixes only.

 

ClosedHow to deploy engine hotfixes on probe
  1. Stop the Data Flow Probe.

  2. Extract classes.zip.

  3. Copy the classes folder of the zip into the following directory: <DataFlowProbe_install_dir>/classes/

    If there already exists a classes folder, back up the folder first, and then copy the classes folder of the zip into the above folder to replace the existing one.

    After deployment, the hotfix path looks like the following: <DataFlowProbe_install_dir>/classes/HF_QCCR1HXXXXX/com/hp/ucmdb/

  4. Restart the probe.

  5. Invoke JMX method showAllBinariesApplied to check and make sure the binary/hotfix was properly deployed.

 

ClosedHow to view and track engine hotfixes applied on probe

To view and track hotfixes deployed on probe,

  1. On the Data Flow Probe machine, launch the Web browser and enter the following address: https://localhost:8453

  2. Enter the JMX console authentication credentials (default login name = sysadmin).

  3. Locate the showAllBinariesApplied operation in the GeneralUtils category:

  4. Click Invoke.

    The result page of the showAllBinariesApplied operation displays detailed information about the hotfixes applied, including hotfix type, readme file, if there're any overlapping files, and if there are any wrongly placed files.