Setting up PSL pre-discovery

This section describes how to set up PSL Pre-discovery for an application class using the PATROL Developer Console for Windows and UNIX. The following topics are covered:

• • Setting up PSL pre-discovery on Windows
  • Setting up PSL pre-discovery on UNIX
  • KM output-application pre-discovery

Setting up PSL pre-discovery on Windows

In this task, you will set up PSL pre-discovery for an application class.

Before setting up PSL pre-discovery, you should have created the application class and set its general properties.

To set the discovery type

1. Choose the Properties option from the popup menu of the application class that you wish the PATROL Agent to detect.
   The Application Properties dialog box for the selected application class appears with the General tab options displayed as shown in Application Properties dialog box, General tab.
2. Click PSL to set the Discovery type to PSL discovery.
   The Pre-Discovery and Discovery tabs appear on the Application Properties dialog box as in the following figure. 
   
   Application Properties dialog box, General tab 
   
   

To define PSL pre-discovery rules

If you create a PSL pre-discovery script, you must provide logic to cause the PSL-pre-discovery script to execute

1. Click the Pre-Discovery tab to access a text box in which to type the PSL script to perform pre-discovery.
   The Pre-Discovery tab appears as shown in the following figure. 
   
   Application Properties dialog box, Pre-Discovery tab
   
   
2. Provide conditional logic to cause the PSL discovery script to execute if the appropriate condition or conditions occur. Provide conditional logic to support all possible initial application class conditions.
   Use the active PATROL Agent namespace variable to control logic flow. Valid values for the active variable lists the valid values for the active variable.
3. Click Save to File to save the PSL pre-discovery script in the PATROL Global PSL directory %HOMEDRIVE%%HOMEPATH%\patrol\psl.
   You will be prompted for the PSL file name.
   In developing PATROL KMs, you can save PSL scripts to a separate file or to the PATROL KM file. Saving your PSL to a separate file allows you to reuse the PSL in other KMs.
4. Click Apply to apply the changes to the dialog box; then, click OK to close the dialog box.
5. Choose File>Save KM from the PATROL Developer Console main menu to save the PATROL KM.
   The PATROL Console for Windows saves the local KM information in the local PATROL KM directory. By default, the local PATROL KM directory is the subdirectory of the local PATROL directory named %HOMEDRIVE%%HOMEPATH%\patrol\knowledge. 
   You can use the PATROL Environmental Probe utility to view the settings of these environment variables on your machine.

Setting up PSL pre-discovery on UNIX

In this task, you will set up PSL pre-discovery for an application class. Before setting up PSL pre-discovery, you should have created the application class and set its general properties.

To set the discovery type

1. Access the application definition dialog box for the appropriate application class. The discovery options for the selected application class appear as shown in the following figure. 
   
   Application Definition dialog box, PSL discovery 
   
2. Click PSL to set the Discovery Rules type to PSL discovery.
   The PSL Pre-Discovery and PSL Discovery buttons appear on the Application Properties dialog box as in the following figure.

To define PSL discovery rules

If you create a PSL pre-discovery script, you must provide logic to cause the PSL discovery script to execute.

1. Click PSL Pre-Discovery to access a window in which to type the PSL script to perform pre-discovery.
   The PSL Pre-Discovery edit window appears as shown in the following figure. 
   
   PSL Pre-Discovery Edit window
   
   
2. Provide conditional logic to cause the PSL discovery script to execute if the appropriate condition or conditions occur. Provide conditional logic to support all possible initial application class conditions.
   Use the active PATROL Agent namespace variable to control logic flow. Valid values for the active variable lists the valid values for the active variable.
3. Choose File >Save from the menu bar to save the PSL pre-discovery script.
   If you are saving the script for the first time, the Editor dialog box appears prompting you to choose where you want the file saved. 
   
   Editor dialog box-PSL pre-discovery
   
   
4. Click Separate File to save the PSL pre-discovery script in the PATROL Global PSL directory. You will be prompted for the PSL file name.
   In developing PATROL KMs, you can save PSL scripts to a separate file or to the PATROL KM file. Saving your PSL to a separate file allows you to reuse the PSL in other KMs.
   The PATROL Console saves the local PATROL KM information in the local KM directory, $HOME/patrol/knowledge and the PSL files in $HOME/patrol/lib/psl.
5. Choose File>Exit from the PSL Editor menu to exit the editor.
6. Click Apply to apply the changes to the Application Definition dialog box; then, click OK to close the dialog box.
7. Choose File>Save KM from the List of Applications menu to save the PATROL KM.

KM output-application pre-discovery

In both Windows ad UNIX you have the ability to save your scripts in an external files instead of in the text of the PATROL KM. External files represent scripted objects that can be reused in other KMs. 

The following figure shows sample output created by the PATROL Developer Console when you add pre-discovery to an application class using an external PSL script. 

KM output-application class pre-discovery