After you install the Integration Service, you can configure it for extended security. This allows the BMC PATROL Agent to connect only to the Integration Service that you specify and not to multiple Integration Services. If you have installed the Integration Service in a clustered setup, to configure for extended security, you must configure both the primary and the secondary Integration Services.
pw remote generateiskey integrationServiceName
command. For example, pw remote generateiskey
IS-1
where IS-1 is the name of the Integration Service connected to the BMC ProactiveNet Server. The key is generated in a .cfg file.After the key is generated, save the .cfg file in your computer.
Export the key to a particular location as follows:
pw remote exportiskey <integrationServiceName> -file <PathOnISMachine>\key1.cfg
HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\Patrol\SecurityPolicy_v3.0\PROXY\client registry entry.
security_mode
and set the value of the key to KNOWN_HOST
.(on UNIX)
[client]
section):security_mode = KNOWN_HOST
Note
On an IPv6 system, restart the primary Integration Service after generating the security key.
In a clustered setup, you must configure the primary and the secondary Integration Services.
to the corresponding location of the secondary Integration Service.
After generating a key to configure the Integration Service for extended security, you must import the key to the BMC PATROL Agent. To import the key:
Installing BMC ProactiveNet Integration Service and BMC ProactiveNet Cell
Managing a BMC ProactiveNet Integration Service cluster through Central Monitoring Administration