Using OpenJDK with KM repository

Version 1
    Share This:



    TrueSight OM v11.3

    OpenJDK KM repo setup






    Table of Contents

    Table of Contents. 2

    Background: 3

    Getting OpenJDK: 3

    PCIG: 3

    Package creation: 4

    Import into KM repo: 4

    Confirm per agent: 5






    1. Historically Oracle JRE was packaged and delivered with the repo.
      Due to Oracle’s change of LTS and licensing it’s no longer provided within the repo. Some KMs used other types of Java as detailed within documentation.
    2. OpenJDK is now used with multiple KMs and can be provided by the user prior to installing any PATROL components or by importing it into the KM repo on TrueSight OM.
    3. This document explains how to prepare an OpenJDK package to be used with the TrueSight KM repository.
    4. As OpenJDK has rapid release cycle it’s expected users may repeat the process details here few times a year to benefit from latest features/fixes, however usage of the deployed OpenJDK with KMs still require support of the KMs as detailed on


    Getting OpenJDK:

    1. OpenJDK is available from multiple vendors. One of the most commonly used is provided here:
    2. Each package should include one distribution of OpenJDK for one platform e.g.
      provides OpenJDK 13 for Linux x64
    3. You should prepare a copy of the right distribution before building the repo package. Later within the repo you should make sure that ‘km pushing’ an OpenJDK within a silent install bundle is done for each platform separately.
      i.e. don’t create a silent install bundle for both Windows and Linux together.


    PCIG is a utility provided with the PATROL common install package for preparing packages to allow importing into existing repo.

    In this document we will show how to use PCIG running on Windows to create any package of OpenJDK.
    it’s also available as part of the TrueSight PS server installation as follows:

    Linux TSPS file system PATH:  $TRUESIGHTPSERVER_HOME/truesightpserver/modules/cma/pproxy/depot_directory/bmc_products/tools/pcig/ pcig-64.exe
    Windows TSPS file system PATH:



    Notice: as earlier said, packaging in this document is done on Windows, so pcig-64.exe can be take from the path listed here above, whether TSPS is on Windows or Linux.




    Package creation:

    1. Have a windows host available to place OpenJDK package on as well as pcig-64.exe.
      and place it in
    2. Download OpenJDK
      (e.g. or
    3. Extract the downloaded image (.zip or .tar.gz) to the same location.
      it will be placed in
    4. Create directory C:\TEMP\PCIG\Patrol3
    5. Move C:\TEMP\PCIG\jdk-11 into C:\TEMP\PCIG\Patrol3
    6. Run the following command to create a single solution for OpenJDK Windows:
      pcig-64.exe -p openjdk -r 11.0.02 -s C:\temp\OpenJDK\Patrol3 -t “OpenJDK11 for Windows” -l WINDOWS is generated.
    7. Run the following command to create a single solution for OpenJDK Linux:
      pcig-64.exe -p openjdk -r 11.0.02 -s C:\temp\OpenJDK\Patrol3 -t “OpenJDK11 for Linux” -l LINUX is generated.

    Notice: PCIG create packages for the platform provided with ‘-l’ flag the files extracted into
    C:\TEMP\PCIG\Patrol3\jdk-11 need to match that.

    Import into KM repo:

    1. Logon to TrueSight PS.
    2. Under administration à repository import each package
      e.g. or separately as single solution.
    3. Confirm the newly imported images are listed within the repo:




    Confirm per agent:

    Open TSPS UI and select

    1. Configuration à Managed Devices à <selected agent à Query PATROL agent
      type command:
      print(system("%PATROL_HOME%\\jdk-11\\bin\\java -version"));

    Click “Execute” button

    Output should be in the line of the following:

    openjdk version "11" 2018-09-25
    OpenJDK Runtime Environment 18.9 (build 11+28)
    OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode)

    On Linux the command is: print(system("$PATROL_HOME/../jdk-11/bin/java -version"));