PATROL KM product file destinations


The installation of a PATROL KM requires that all your KM-related files are placed in the proper place in the PATROL environment.

In the PATROL 3. x architecture, files are installed to the console, agent, or both. With the 7. x three-tier architecture, KM files are installed in different locations. KM files can be installed on one or more of the following locations:

PATROL 3.5 consoles

The following table lists the directories that your KM-related files are placed in during the install process of your PATROL KM for PATROL 3.5 Consoles:

 File destinations for PATROL KM files on 3.5 consoles

File Types

Path

Description

.km
.kml

(UNIX) $PATROL_HOME/lib/knowledge (Windows) %PATROL_HOME%\lib\knowledge

Application class and PATROL KM list files

.ctg

(UNIX) $PATROL_HOME/lib/knowledge (Windows) %PATROL_HOME%\lib\knowledge

KM user-defined event catalog

.bmp
.bmk
.xpm
.msk

(UNIX) $PATROL_HOME/lib/images (Windows) %PATROL_HOME%\lib\images

Icons

.hlp
.cnt
.htm

(UNIX) $PATROL_HOME/lib/help (Windows) %PATROL_HOME%\lib\help\WinHelp

Help files

.psl
.bin
.lib

(UNIX)$PATROL_HOME/lib/psl (Windows) %PATROL_HOME%\lib\psl

PSL scripts and libraries not saved as part of the PATROL KM files This includes any required directories, PATROL Agent configuration files, external scripts, or procedures.

PATROL 3.5 Agents

The following table lists the directories that your KM-related files are placed in during the installation process of your PATROL KM for PATROL 9.0.00 components.

 File destinations for PATROL KM files on 3.5 Agents

File Types

Path

Description and examples

.km
.kml

(UNIX) $PATROL_HOME/lib/knowledge (Windows) %PATROL_HOME%\lib\knowledge

Application class and PATROL KM list files

.ctg

(UNIX) $PATROL_HOME/lib/knowledge (Windows) %PATROL_HOME%\lib\knowledge

KM user-defined event catalog files

.psl
.bin
.lib

(UNIX) $PATROL_HOME/lib/psl (Windows) %PATROL_HOME%\lib\psl

PSL scripts and libraries not saved as part of the PATROL KM files This includes any required directories, PATROL Agent configuration files, external scripts, or procedures.

.sh
.bat
.cmd

(UNIX)$PATROL_HOME/lib/psl (Windows) %PATROL_HOME%\lib\psl

Scripts used at install time to configure KMs like scripts to configure monitoring instances.

.txt

(UNIX)$PATROL_HOME (Windows) %PATROL_HOME

External text files that contain build number and version information used by InfoBox commands

.reg

(Windows) %PATROL_HOME%\lib\psl

PAMO template files for PAMO reports on machines that have Microsoft Office

.bmp
.bmk
.xpm
.msk

(UNIX) $PATROL_HOME/lib/images (Windows) %PATROL_HOME%\lib\images

Icons and icon masks

.bat
.sh
.exe

(UNIX) $PATROL_HOME (Windows) %PATROL_HOME%

Console-side executables for state change actions or #%MODES% menu commands that run on the console computer

PATROL Console Server

The PATROL Console Server provides KM resources for the new PATROL Central consoles.

Note

When you install your icon resource file, you must not install it in the knowledge/default directory, or you will overwrite the default icon resource file, and KMs that depend on this resource for their images will no longer have their icons. You must install your resource file in your knowledge/ prd_KMversion directory.

The following table lists the directories that your KM-related files are installed in during the install of your PATROL KM for PATROL 7. x components:

 PATROL Console Server file usage

File type

Path

Description

.chm

(UNIX) $PATROL_ROOT/lib/knowledge/prd_KMversion/lib/help/LOCALE/prd.chm (Windows) %PATROL_ROOT%\lib\knowledge\prd_KMversion\lib\help\LOCALE\prd.chm

Knowledge module help files for display in PATROL 7. x consoles prd_KMversion is the version-specific directory for the KM package.

resource.mk4

(UNIX) $PATROL_ROOT/lib/knowledge/prd_KMversion (Windows) %PATROL_ROOT%\lib\knowledge\prd_KMversion

Image resource file for the KM prd_KMversion is the version-specific directory for the KM package.

package.mof

(UNIX) $PATROL_ROOT/lib/knowledge/prd_KMversion (Windows) %PATROL_ROOT%\lib\knowledge\prd_KMversion

KM MOF package file for the console server prd_KMversion is the version- specific directory for the KM package.

PATROL Central-Windows Edition console

The only KM files that you need to install on the PATROL Central-Windows Edition computer are the console-side executables for state change actions and #%MODES% local commands.

PATROL Central-Windows Edition file locations

File type

Path (Windows only)

Description

.bat
.sh
.exe

%PATROL_HOME%

Console-side executables used for state change action methods and #%MODES% menu commands

Note

The PATROL Central-Windows Edition files are installed in the PATROL 3.5 %PATROL_HOME% directory structure. This prevents the installation of multiple copies of console-side executables when PATROL 3.5 and PATROL 7. x consoles are installed on the same computer. PATROL Central-Windows Edition can have its own PPF file or you can use the same PPF that is used for the 3.5 Windows console, but you will be installing unneeded files if the 3. x console is not installed on the computer.

PATROL Central-Web Edition Server

The only KM files that you need to install on the PATROL Central-Web Edition Web server are the KM Help files. PATROL Central-Web Edition gets all the KM resources from the console server.

PATROL Central-Web Edition file locations

File type

Path

Description

.jar

Version-specific PATROL Central-Web Edition KM Help (UNIX) KM_WEB_HELP/html/prd_v.r.m_LOCALE.jar (Windows) KM_WEB_HELP\html\prd_v.r.m_LOCALE.jar

KM Help files in .jar archive format

The .jar files are not expanded by the Web server. The Help is served from the .jar file as it is requested by PATROL Central-Web Edition.

The .jar file uses the following values in the naming convention:

  • prd - the KM product code or registered prefix
  • vrm - the KM version number
  • LOCALE - the LOCALE value is formed by concatenating the language code, an underscore, and the country code.

For example, english (EN) and the United States (USA) form the following LOCALE value: EN_USA

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*