×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
BMC PATROL Agent 11.0 ... Developing Developing a PATROL Knowledge Module KM certification

Additional Requirements

Selecting KM prefixes

Prefixes must be the developed record code for the KM, and the prefix must not begin with a numeric value, a control character (non printable characters), or an underscore.

Note

To be backward compatible, application class names, parameter names, InfoBox items, and menu commands must use a maximum length of thirty characters. Consider this limitation when you request a registered prefix.

The following names use valid prefixes:

  • Abcd_MyProduct
  • ABCD_MyProduct
  • A_MyProduct

The following names use invalid prefixes:

  • MyProduct
  • _MyProduct
  • 123_MyProduct
  • @_MyProduct

Managing multiple application instances

With multiple application instances, a KM maintains a different session for each instance of an application. 

To illustrate concurrent sessions lets use a Web server. When you write your KM to manage a particular Web server, you will offer support for one or more Web servers running on the managed system. 

The customer might expect your KM to run with multiple Web servers on the same computer. Managing concurrent sessions is defined as a KM that supports managing multiple instances of the application. 

It is important not to expect a certain setup at a customer site. For example, look at a cluster KM. Although you might think it is normal that a box would never be part of multiple clusters, the customer might have set it up this way. Your KM needs to handle these types of configurations without interruption of service or failure. 

If the KM does not support multiple instances of an application class, you must indicate this clearly in the end-user documentation.

Reducing the number of discovered instances

When it is reasonable to have a large number of instances to be created for a monitored application such as monitoring webservers from a single PATROL Agent, you must consider using nested instances. If nested instances are not appropriate, the documentation must provide the following information:

  • The performance impact of monitoring a large number of instances (if any)
  • How to limit the number of instances being discovered

The KM must also provide a filtering mechanism. Application class icons designed to appear at the computer class level (known as the root tree of the product) must be limited to only one for a given product to guard against a KM having a large number of application classes in the root tree.

Note

Failure to comply with this requirement might result in a usability issue (opening a container and being confronted by a huge number of icons) and possibly create a performance issue (each instance might potentially have multiple scheduled parameters like standard and collector parameters) when each collecotor or standard parameter is responsible for performing a CPU or memory-extensive operation.

Storing KM configuration information

All KM values must be stored in the PATROL Agent configuration database, and the PATROL Configuration Manger provides users with a standard interface to customize the values.

Formatting error messages

Error messages must be prefix based and must contain an error number. Error messages displayed with the prefix, appearing in the System Output Window, should look similar to the following example. 

PFX_AB011 - The KM is not properly configured 

The user documentation may provide greater detail for each error code. 

If you have to show messages to the user that were not generated by your KM but by the OS or the application you are monitoring, you should make this clear to the end-user by using a specific error prefix for this type of message. For example: 

PFX_OS - File not found

Note

The KM must use its unique prefix for tagging its error messages.

Documenting KM reference information

The KM reference information for all PATROL KM components includes documentation of all application classes, InfoBox items, menus, and parameters (this includes collectors and parameters that have no output). 

The formats and conventions listed in the Help and hard copy models developed by the KM Consistency team must be followed. The following information must be provided for each application

  • Menu Commands
    • Should be documented in the task topic in which the menu is used.
    • Should be indexed in your Help such that all menu commands appear by themselves in the index and under Menus.
  • InfoBoxes
    • InfoBox Name
    • Description
    • For each InfoBox item (command):
      • Name
      • Description
      • Availability (always / offline / online)
      • Security (Inherit / prompt)
      • Value set by (as appropriate)
  • Parameters
    • Parameter Name
    • Description
    • Attributes (as shown in the following figure)
      • Application class
      • Command type
      • Platform
      • Icon style
      • Unit
      • Border range
      • Alarm 1 range
      • Alarm 2 range
      • Scheduling (poll time)
      • Active at installation
      • Parameter type
      • Value set by

Note

Any OS restrictions/exceptions in the preceding list should also be indicated in the Platform field.


Standard parameter attributes

Configuring a KM without a user interface

The KM must provide a non-GUI method of configuration that at a minimum allows the KM to be installed and configured unattended to a point where the KM can begin monitoring. For example, if a KM needs to be told which database instances to monitor and what account to use to connect to the database, then the KM could allow this information to be placed into pconfig or read from a customer-provided configuration file. 

The intent is to support customers that need to mass distribute the KMs to servers and have them automatically configured using a configuration file/script also deployed with the KM without requiring the customer to have to start a GUI and individually configure each instance of the KM.

Creating message catalogs

Each message is uniquely identified by a message ID and is used in conjunction with vendor ID, and tool ID. Keep in mind that due to clients in various countries, everything will have to be translated into multiple languages. Try to use words in your message IDs and catalogs that easily translate into other languages. 

For more information about creating message catalogs, see KM help files.

Installing RuleSets in standard PCM directory

PATROL Configuration Manager RuleSets installed by the KM must be installed in the PCM Shipped RuleSet directory as shown in the following example: 

BMC_BASE /pconfmgr/rulesets/Shipped/ PRD / 

PRD = three letter developed record or product code 

The PRD value is the same as used in the KM directives. For more information about KM directives, see KM directives.

Under this directory, the KM teams can add additional sub-folders to group RuleSets.

Directory folder and RuleSet naming conventions

The PATROL Configuration manager does not support periods or spaces in the directory/folder or RuleSet names. 

All RuleSet names must end with a .cfg extension, similar to other PATROL change files (e.g., abc.cfg). The following example shows the correct directory naming convention: 

Product 

PKM for Event Management (ESG) V2.6.00 

Ruleset Directory 

BMC_BASE /pconfmgr/rulesets/Shipped/ESG/

Supplying a list of files and system values

This section describes and provides an example of the installation information you will provide to BMC Software Customer Support for your KM.

Installed files and system settings

Normally, a PATROL KM installation adds the following information to a system:

  • Installation logs
  • Product files and directories
  • Start Menu entries
  • Security logs
  • Registry entries
  • Service registrations

You will provide a list of the files installed and system settings for the KM for each PATROL infrastructure component:

  • PATROL Consoles
  • PATROL Agent
  • PATROL Console Server
  • PATROL Central-Web Edition Web server (if any)

The following sections show an example of the type of information that you will provide to BMC Customer Support.

Example installation report

The following example includes files and directories added for the PATROL Console and Agent as well as the KM, and this example does not include files installed on the PATROL Console Server or PATROL Central-Web Edition Web server. 

You only need to include the files that are installed and the values set for your KM, but you do not need to include the values for the PATROL infrastructure components.

Note

If the installed files and settings are the same for all Windows versions and all UNIX versions, you only need to provide a list for one Windows and one UNIX version.


The following example contains two sections:

File system additions for the PATROL KM for XYZ

When the PATROL KM for XYZ is installed, the following information is added to the file system:

  • Installation logs
  • PATROL cache
  • PATROL installation directory
  • Entries to the Start Menu for the console, agent, and configuration
  • Updates to the security logs

The following directories and files are added by the PATROL KM for XYZ installation: 

Directory C:\Program Files\BMC Software 

(PATROL installation directory - All files and subdirctories in this directory are added.) 

Directory C:* 

05/14/03 05:47p 48 Agent_200305141743.hst 

05/14/03 05:44p 601 Agent_200305141743.prd 

05/14/03 05:50p 48 Console_200305141747.hst 

05/14/03 05:48p 646 Console_200305141747.prd 

05/14/03 05:50p 135,517 HYNERIAISI.log 

05/14/03 05:50p 4,747 HYNERIAISIdistribute.log 

05/14/03 05:46p 2,309 setupNT05142003174330.log 

05/14/03 05:50p 2,298 setupNT05142003174743.log 

05/14/03 05:43p 311 setupNTError05142003174330.log 

05/14/03 05:47p 311 setupNTError05142003174743.log 

*Directory C:\TEMP 

05/14/03 05:34p <DIR> . 

05/14/03 05:34p <DIR> .. 

05/14/03 05:09p <DIR> patrol 

Directory C:\TEMP\patrol 

05/14/03 05:09p <DIR> . 

05/14/03 05:09p <DIR> .. 

2 File(s) 0 bytes 

Directory C:\WINNT 

05/14/03 05:43p <DIR> . 

05/14/03 05:43p <DIR> .. 

05/14/03 05:43p 299 instx86.ini 

05/14/03 05:50p 477 setupx86.ini 

Directory C:\WINNT\Profiles\All Users\Start Menu\Programs 

05/14/03 05:46p <DIR> . 

05/14/03 05:46p <DIR> .. 

05/14/03 05:50p <DIR> BMC PATROL 

Directory C:\WINNT\Profiles\All Users\Start Menu\Programs\BMC PATROL 

05/14/03 05:50p <DIR> . 

05/14/03 05:50p <DIR> .. 

05/14/03 05:50p 409 Developer Console.lnk 

05/14/03 05:50p 397 Operator Console.lnk 

05/14/03 05:50p 415 PATROL Client 

Configuration.lnk 

05/14/03 05:50p 401 PATROL Environment Probe.lnk 

6 File(s) 1,622 bytes 

Directory C:\WINNT\Profiles\express\Application Data 

01/30/03 03:35p <DIR> . 

01/30/03 03:35p <DIR> .. 

05/14/03 05:35p <DIR> PatrolInstall 

Directory C:\WINNT\Profiles\express\Application Data\PatrolInstall 

05/14/03 05:35p <DIR> . 

05/14/03 05:35p <DIR> .. 

05/14/03 05:34p 59,421 HYNERIAISI.log 

05/14/03 05:32p 0 HYNERIAISIdistribute.log 

05/14/03 05:16p 134 setupNT05142003171609.log 

05/14/03 05:17p 134 setupNT05142003171746.log 

05/14/03 05:18p 134 setupNT05142003171856.log 

05/14/03 05:30p 134 setupNT05142003173029.log 

05/14/03 05:31p 134 setupNT05142003173107.log 

05/14/03 05:34p 1,697 setupNT05142003173145.log 

05/14/03 05:16p 311 setupNTError05142003171609.log 

05/14/03 05:17p 311 setupNTError05142003171746.log 

05/14/03 05:18p 311 setupNTError05142003171856.log 

05/14/03 05:30p 311 setupNTError05142003173029.log 

05/14/03 05:31p 311 setupNTError05142003173107.log 

05/14/03 05:31p 311 setupNTError05142003173145.log 

05/14/03 05:35p 48 Setup_200305141731.hst 

05/14/03 05:35p 2 Setup_200305141731.prd 

18 File(s) 63,704 bytes 

Directory C:\WINNT\Profiles\express\Start Menu\Programs 

05/14/03 05:46p <DIR> . 

05/14/03 05:46p <DIR> .. 

05/14/03 05:46p <DIR> BMC PATROL 

Directory C:\WINNT\Profiles\express\Start Menu\Programs\BMC PATROL 

05/14/03 05:46p <DIR> . 

05/14/03 05:46p <DIR> .. 

05/14/03 05:46p 391 Agent Configure.lnk 

05/14/03 05:46p 391 Agent Manager.lnk 

4 File(s) 782 bytes 

Directory C:\WINNT\system32 

Directory C:\WINNT\system32\config 

08/24/01 02:45p <DIR> . 

08/24/01 02:45p <DIR> .. 

05/14/03 05:48p 524,288 AppEvent.Evt 

05/14/03 05:48p 114,688 default 

05/14/03 05:48p 1,024 default.LOG 

05/14/03 05:48p 20,480 SAM 

05/14/03 05:51p 4,096 SAM.LOG 

05/14/03 05:48p 53,248 SECURITY 

05/14/03 05:48p 1,024 SECURITY.LOG 

05/14/03 05:52p 7,663,616 software 

05/14/03 05:52p 1,024 software.LOG 

05/14/03 05:48p 524,288 SysEvent.Evt 

05/14/03 05:50p 1,564,672 system 

05/14/03 05:50p 1,564,672 SYSTEM.ALT

Windows registry settings for the PATROL KM for XYZ

When the PATROL KM for XYZ is installed, the following information is added to the registry:

  • Registry entry for the XYZ KM v V.R.MM
    [HKLM\SOFTWARE\BMC Software\KM\XYZ]
  • Registry entries for Agent COM server
  • Registry registrations for NTOS
  • Service registrations for the following components:
    • EventLog Monitor
    • Process Monitor 


The following registry information was added by the PATROL KM for XYZ installation: 

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software]

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM]

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT]

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\EventLog]

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\EventLog\Application]

"MaxRecords"=dword:00000032

"BackupDir"="%PATROL_TEMP%\\ntkm\\EventLog\\Application"

"CheckRecord"=dword:00003c7c

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\EventLog\Application\Instances]

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\EventLog\Application\Instances\Summary]

"InstDefinition"="1|7|0|0|0|1|0"



[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\EventLog\Security]

"MaxRecords"=dword:00000032

"BackupDir"="%PATROL_TEMP%\\ntkm\\EventLog\\Security"

"CheckRecord"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\EventLog\Security\Instances]

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\EventLog\Security\Instances\Summary]

"InstDefinition"="1|31|0|0|0|1|0"



[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\EventLog\System]

"MaxRecords"=dword:00000032

"BackupDir"="%PATROL_TEMP%\\ntkm\\EventLog\\System"

"CheckRecord"=dword:00000d36

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\EventLog\System\Instances]

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\EventLog\System\Instances\Summary]

"InstDefinition"="1|7|0|0|0|1|0"



[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\NetProtocols]

"ActiveList"="NETBEUI=1|NETBIOS=1|FTP=0|ICMP=1|IP=1|IPX=1|TCP=1|UDP=1"

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\Printers]

"TimeLimit"="1|1|3|1|1|1|1|5|1|1"

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\Services]

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\Services\CFGlist]

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\Services\CFGlist\List1]

"ServiceList"="Alerter|1|1

EventSystem|0|0

ClipSrv|0|0

Browser|1|1

RelayAgent|1|1

Replicator|0|0

EventLog|1|1

LicenseService|1|1

MSSQLServer|0|0

Messenger|1|1

"

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\Services\CFGlist\List2]

"ServiceList"="NtLmSsp|0|0

Netlogon|1|1

AlertManager|1|1

McShield|1|1

McTaskManager|1|1

NetDDEdsdm|0|0

NetDDE|0|0

PATROLE2E|1|1

PatrolEvMonitor|1|1

PatrolProcessMonitor|1|1

"

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\Services\CFGlist\List3]

"ServiceList"="PatrolAgent|1|1

PlugPlay|1|1

ProtectedStorage|1|1

RPCLOCATOR|0|0

RpcSs|1|1

SQLExecutive|0|0

LanmanServer|1|1

Spooler|1|1

SENS|0|0

LmHosts|1|1

"

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\KM\NT\Services\CFGlist\List4]

"ServiceList"="Schedule|1|1

TapiSrv|0|0

UPS|0|0

MSIServer|0|0

LanmanWorkstation|1|1

"

[HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\PATROL Agent]

"esi_lib"="none"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.hst]

@="hst_auto_file"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.prd]

@="prd_auto_file"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID
{53838040-c039-11d1-ab07-0060970953d5}]

@="BMC PatrolAgent Service COM Server"

"LocalService"="PatrolAgent"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID
{A0DB6FA2-E39B-11D1-AB25-0060970953D5}]

@="psh"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\psh.EXE]

"AppID"="{A0DB6FA2-E39B-11D1-AB25-0060970953D5}"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\BMC.PatrolAgent]

@="BMC PatrolAgent Service COM Server"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\BMC.PatrolAgent\CLSID]

@="{53838040-c039-11d1-ab07-0060970953d5}"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\BMC.PatrolAgent\CurVer]

@="BMC.PatrolAgent.3.3"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\BMC.PatrolAgent.3.3]

@="BMC PatrolAgent Service COM Server"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\BMC.PatrolAgent.3.3\CLSID]

@="{53838040-c039-11d1-ab07-0060970953d5}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\BMC.PatrolAgent.Console]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\BMC.PatrolAgent.Console\CLSID]

@="{26295a90-b2c6-11d1-aaff-0060970953d5}"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\BMC.PatrolAgent.Console\CurVer]

@="BMC.PatrolAgent.Console.3.3"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\BMC.PatrolAgent.Console.3.3]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\BMC.PatrolAgent.Console.3.3\CLSID]

@="{26295a90-b2c6-11d1-aaff-0060970953d5}"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID
{1A9D1F00-E464-11D1-AB25-0060970953D5}]

@="PSFactoryBuffer"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\\{1A9D1F00-E464-11D1-AB25-0060970953D5}\InProcServer32]

@="C:\\PATROL3-3\\bin\\pshps.dll"

"ThreadingModel"="Both"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID
{53838040-c039-11d1-ab07-0060970953d5}]

@="BMC PatrolAgent Service COM Server"

"LocalService"="PatrolAgent"

"AppId"="{53838040-c039-11d1-ab07-0060970953d5}"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\\{53838040-c039-11d1-ab07-0060970953d5}\NotInsertable]

@=""



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\\{53838040-c039-11d1-ab07-0060970953d5}\ProgID]

@="BMC.PatrolAgent.3.3"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\\{53838040-c039-11d1-ab07-0060970953d5}\VersionIndependentProgID]

@="BMC.PatrolAgent"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID
{A0DB6FAF-E39B-11D1-AB25-0060970953D5}]

@="PScriptHost Class"

"AppID"="{A0DB6FA2-E39B-11D1-AB25-0060970953D5}"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\\{A0DB6FAF-E39B-11D1-AB25-0060970953D5}\LocalServer32]

@="C:\\PATROL3-3\\bin\\psh.exe"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\\{A0DB6FAF-E39B-11D1-AB25-0060970953D5}\ProgID]

@="PScriptHost.PScriptHost.1"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\\{A0DB6FAF-E39B-11D1-AB25-0060970953D5}\VersionIndependentProgID]

@="PScriptHost.PScriptHost"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID
{26295a90-b2c6-11d1-aaff-0060970953d5}]

@="BMC PatrolAgent Console COM Server"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\\{26295a90-b2c6-11d1-aaff-0060970953d5}\LocalServer32]

@="C:\\PATROL3-3\\bin\\PatrolAgent.exe"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\\{26295a90-b2c6-11d1-aaff-0060970953d5}\NotInsertable]

@=""



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\\{26295a90-b2c6-11d1-aaff-0060970953d5}\ProgID]

@="BMC.PatrolAgent.Console.3.3"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\\{26295a90-b2c6-11d1-aaff-0060970953d5}\VersionIndependentProgID]

@="BMC.PatrolAgent.Console"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\\{A5177C90-3C79-11D0-B8B2-00A024CDE50F}\LocalServer32]

@="C:\\PATROL~1\\bin\\Patrol.exe"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Console.Document\protocol\StdFileEditing\server]

@="C:\\PATROL~1\\bin\\Patrol.exe"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface
{1A9D1F00-E464-11D1-AB25-0060970953D5}]

@="_IPSHEvent"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\\{1A9D1F00-E464-11D1-AB25-0060970953D5}\NumMethods]

@="4"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\\{1A9D1F00-E464-11D1-AB25-0060970953D5}\ProxyStubClsid32]

@="{1A9D1F00-E464-11D1-AB25-0060970953D5}"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface
{df1e2fc0-afc5-11d1-aafe-0060970953d5}]

@="IPatrolAgent"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\\{df1e2fc0-afc5-11d1-aafe-0060970953d5}\ProxyStubClsid]

@="{00020424-0000-0000-C000-000000000046}"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\\{df1e2fc0-afc5-11d1-aafe-0060970953d5}\ProxyStubClsid32]

@="{00020424-0000-0000-C000-000000000046}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\\{df1e2fc0-afc5-11d1-aafe-0060970953d5}\TypeLib]

@="{B710EE50-B2C6-11D1-AAFF-0060970953D5}"

"Version"="1.0"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib
{A0DB6FA1-E39B-11D1-AB25-0060970953D5}]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\\{A0DB6FA1-E39B-11D1-AB25-0060970953D5}\1.0]

@="psh 1.0 Type Library"

11D1-AB25-0060970953D5}\1.0\FLAGS]

@="0"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\\{A0DB6FA1-E39B-11D1-AB25-0060970953D5}\1.0\HELPDIR]

@="C:\\PATROL3-3\\bin\\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib
{B710EE50-B2C6-11D1-AAFF-0060970953D5}]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\\{B710EE50-B2C6-11D1-AAFF-0060970953D5}\1.0]

@="PatrolAgent 1.0 Type Library"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\\{B710EE50-B2C6-11D1-AAFF-0060970953D5}\1.0\0]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\\{B710EE50-B2C6-11D1-AAFF-0060970953D5}\1.0\0\win32]

@="C:\\PATROL3-3\\bin\\IPA.TLB"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\\{B710EE50-B2C6-11D1-AAFF-0060970953D5}\1.0\FLAGS]

@="0"



[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\\{B710EE50-B2C6-11D1-AAFF-0060970953D5}\1.0\HELPDIR]

@="C:\\PATROL3-3\\bin"



[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Patrol3-3]

"DisplayName"="BMC Software PATROL 3.3"

"UninstallString"="C:\\Program Files\\Common Files\\PatrolUninstall.exe"

"Path"=hex(2):25,53,79,73,74, ....

.....

"PATROL_HOME"="C:\\PATROL3-3\\"

"PATROL_ADMIN"="WIN2K1\\express"

"PATROL_TEMP"="C:\\PATROL3-3\\tmp"

"HOME"="C:\\"



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_PATROLAGENT\0000\Control]

"ActiveService"="PatrolAgent"



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_PATROLEVMONITOR\0000\Control]

"ActiveService"="PatrolEvMonitor"



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_PATROLPROCESSMONITOR\0000\Control]

"ActiveService"="PatrolProcessMonitor"



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\EventLog\Application\PatrolAgent]

"EventMessageFile"=hex(2):43,3a,5c,50,41,54,52,4f,4c,33,2d,33,5c,62,69,6e,5c,\

50,61,74,72,6f,6c,41,67,65,6e,74,2e,65,78,65,00

"TypesSupported"=dword:0000001f



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PatrolAgent]

"Type"=dword:00000010

"Start"=dword:00000002

"ErrorControl"=dword:00000001

"ImagePath"=hex(2):43,3a,5c,50,41,54,52,4f,4c,33,2d,33,5c,62,69,6e,5c,50,61,74,\

72,6f,6c,41,67,65,6e,74,2e,65,78,65,00

"DisplayName"="PatrolAgent"

"ObjectName"="LocalSystem"



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PatrolAgent\Parameters]

"Port"=dword:000007c3

"Security"=hex:01,00,14,80,c0,00,00,00,cc,00,00,00,14,00,00,00,34,00,00,00,02,\

00,20,00,01,00,00,00,02,80,18,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\

00,00,20,02,00,00,02,00,8c,00,05,00,00,00,00,00,18,00,8d,01,02,00,01,01,00,\

00,00,00,00,01,00,00,00,00,67,00,65,00,00,00,1c,00,fd,01,02,00,01,02,00,00,\

00,00,00,05,20,00,00,00,23,02,00,00,72,00,00,00,00,00,1c,00,ff,01,0f,00,01,\

02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,72,00,00,00,00,00,1c,00,ff,01,\

0f,00,01,02,00,00,00,00,00,05,20,00,00,00,25,02,00,00,72,00,00,00,00,00,18,\

00,fd,01,02,00,01,01,00,00,00,00,00,05,12,00,00,00,25,02,00,00,01,01,00,00,\

00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PatrolAgent\Enum]

"0"="Root\\LEGACY_PATROLAGENT\\0000"

"Count"=dword:00000001

"NextInstance"=dword:00000001



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PatrolEvMonitor]

"Type"=dword:00000010

"Start"=dword:00000002

"ErrorControl"=dword:00000001

"ImagePath"=hex(2):43,3a,5c,50,41,54,52,4f,4c,33,2d,33,5c,62,69,6e,5c,70,61,74,\

65,76,6d,6f,6e,2e,65,78,65,00

"DisplayName"="Patrol Event Log Monitor"

"ObjectName"="LocalSystem"



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PatrolEvMonitor\Security]

"Security"=hex:01,00,14,80,c0,00,00,00,cc,00,00,00,14,00,00,00,34,00,00,00,02,\

00,20,00,01,00,00,00,02,80,18,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\

00,00,20,02,00,00,02,00,8c,00,05,00,00,00,00,00,18,00,8d,01,02,00,01,01,00,\

00,00,00,00,01,00,00,00,00,67,00,65,00,00,00,1c,00,fd,01,02,00,01,02,00,00,\

00,00,00,05,20,00,00,00,23,02,00,00,72,00,00,00,00,00,1c,00,ff,01,0f,00,01,\

02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,72,00,00,00,00,00,1c,00,ff,01,\

0f,00,01,02,00,00,00,00,00,05,20,00,00,00,25,02,00,00,72,00,00,00,00,00,18,\

00,fd,01,02,00,01,01,00,00,00,00,00,05,12,00,00,00,25,02,00,00,01,01,00,00,\

00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PatrolEvMonitor\Enum]

"0"="Root\\LEGACY_PATROLEVMONITOR\\0000"

"Count"=dword:00000001

"NextInstance"=dword:00000001



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PatrolProcessMonitor]

"Type"=dword:00000110

"Start"=dword:00000002

"ErrorControl"=dword:00000001

"ImagePath"=hex(2):43,3a,5c,50,41,54,52,4f,4c,33,2d,33,5c,62,69,6e,5c,50,61,74,\

50,72,6f,63,65,73,73,2e,65,78,65,00

"DisplayName"="Patrol Process Monitor"

"ObjectName"="LocalSystem"



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PatrolProcessMonitor\Security]

"Security"=hex:01,00,14,80,c0,00,00,00,cc,00,00,00,14,00,00,00,34,00,00,00,02,\

00,20,00,01,00,00,00,02,80,18,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\

00,00,20,02,00,00,02,00,8c,00,05,00,00,00,00,00,18,00,8d,01,02,00,01,01,00,\

00,00,00,00,01,00,00,00,00,67,00,65,00,00,00,1c,00,fd,01,02,00,01,02,00,00,\

00,00,00,05,20,00,00,00,23,02,00,00,72,00,00,00,00,00,1c,00,ff,01,0f,00,01,\

02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,72,00,00,00,00,00,1c,00,ff,01,\

0f,00,01,02,00,00,00,00,00,05,20,00,00,00,25,02,00,00,72,00,00,00,00,00,18,\

00,fd,01,02,00,01,01,00,00,00,00,00,05,12,00,00,00,25,02,00,00,01,01,00,00,\

00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00



[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PatrolProcessMonitor\Enum]

"0"="Root\\LEGACY_PATROLPROCESSMONITOR\\0000"

"Count"=dword:00000001

"NextInstance"=dword:00000001

Was this page helpful? Yes No Submitting... Thank you
Last modified by Rashmi Gokhale on May 23, 2018

Comments

Log in or register to comment.

Certification Worksheets and checklist
KM certification Best Practices
© Copyright 2014-2017 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.