Configuring event actions
To configure an event action to interface with FrontRange HEAT, you must write the configuration file for the appropriate interface program. Modify the sample script included in the samples directory, and copy it to the \<instance>\script\. If you cannot find the sample file, try re-running setup
to modify your installation. Sample files are automatically installed only with complete installations. You can select them in custom installations.
When you configure an event, you enter the program name or, as of Bravura Security Fabric version 7.0, the target ID you set up earlier. In both cases, the program looks for the default script with the matching name:
Target type | Interface program | Script file name |
---|---|---|
FrontRange HEAT 6 (Ticket) | pxheat6.exe | pxheat6.cfg |
FrontRange HEAT 7 (Ticket) | pxheat7.exe | pxheat7.cfg |
FrontRange HEAT 8 (Ticket) | pxheat8.exe | pxheat8.cfg |
FrontRange HEAT 9 (Ticket) | pxheat9.exe | pxheat9.cfg |
You can write an alternative .cfg file; for example when you have multiple FrontRange HEAT targets. When you configure an event, you specify the file using the -cfg parameter; for example:
pxheat6.exe -cfg myfile.cfg
or
MYHEAT -cfg myfile.cfg
As of Connector Pack 2.0, pxheat9.exe
interface program has been enhanced with the ability to populate journal and assignment. It also supports getField() operation. See the pxheat.cfg sample file to learn how to use these operations.
Requirements
If you do not use a ticket target to configure events, you must define the variables shown in table below in every FrontRange HEAT script.
Variable | Description of the value |
---|---|
adminid | The user ID of a user with permissions to perform all operations that you require. |
adminpwd | The password for the above user. |
server | The ODBC data source name that points to the database used for the HEAT server. |
Although the HEAT administrator password is blank, ensure that you specify something in the $password field, otherwise the requested operation will not work correctly. The API does not accept blank passwords.