Customization management

The following describes the conventions when assembling, installing, or viewing the customization packages (or "patches").

Assemble the customization package

Binary or configuration files in the customization package should keep the same hierarchical structure as it does in the runtime environment. Perform the following to make your customization package compatible with the Platform Analytics patch installer: and add the following text files to this subdirectory:

  1. Create a subdirectory named patch_install in the top-level directory of your package.
  2. Add patch configuration files to the patch_install subdirectory.
    1. Create and add the patchinfo.txt file.

      Specify a semicolon-separated list containing detailed patch information in the following format:

      build_number;build_date;version;dependency;manual_config

      where
      • build_number is the build request number. This is a unique number that distinguishes the patch from other patches. For customizations, specify any unique build number or use a serial number according to the customization naming conventions. For example, 12345.

      • build_date is the build date in UTC/GMT time in the following numerical format: YYYYMMDDhhmmss. For example, 20111015104104.

      • version is the version of your Platform Analytics installation. For example, 8.0.

      • dependency is the build number of a fix or solution that this patch depends on. If there is more than one fix or solution dependency, separate multiple build numbers with a comma. If there are no depencies, use null. For example, 1234,2345.

      • manual_config specifies if the patch has manual configuration steps before starting the Platform Analytics services. If set to Y, the patch installer does not restart Platform Analytics services after deploying the patch; otherwise, the patch installer will restart the Platform Analytics services after deplying the patch. The default value is N.

      For example,

      12345;20111015104104;8.0;1234,2345;Y

    2. Create and add the fixlist.db file.

      Specify a list of bugs fixed in the patch, with each fixed bug on one line in the file. Each line contains the bug tracking number and an optional brief description, ending with a semicolon, as follows:

      bug_number[:description];

      For example,

      148781:Added more columns to pendreasonloader;

    3. Create and add the filelist.db file.

      Specify a list fo files in your customization. Use a slash (/) in the file paths for both Windows and UNIX.

      For example,

      conf/dataloader/pendingreason_148781.xml
      conf/plc/plc_lsf_advanced.xml
      lsf/7.0/lib/pendreason_148781
      lsf/7.0/linux_64-x86/lib/libpendreason_148781.so

Install the customization package

  1. Navigate to the ANALYTICS_TOP/patch_tools directory.
  2. Run the Platform Analytics server patch installer.
    • UNIX: patch_install.sh

    • Windows: patch_install.bat

    Note:
    • The patch installer will prompt you to specify the patch directory, which is the absolute file path to the extracted directory of your patch.

    • The patch installer will restart the services on the Platform Analytics server.

View details on the customization packages

The following commands allow you to view information on the customizations that are applied to the Platform Analytics installation.