Configuring event actions
pxsvcnow can manage Incident, Problem or Change on ServiceNow systems.
To configure an event action to interface with ServiceNow , you must write a configuration file. Modify the pxsvcnow.cfg sample script included in the samples directory and copy it to the \<instance>\script\ directory. If you cannot find the sample file, try re-running setup to modify your installation. Sample files are automatically installed with complete (typical) 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, pxsvcnow looks for the default script with the matching name.
You can write an alternative .cfg file; for example when you have multiple pxsvcnow targets. When you configure an event, you specify the file using the -cfg parameter; for example:
pxsvcnow.exe -cfg myfile.cfgor
MYTARGET -cfg myfile.cfg
Note
In addition to the Incident—Change—Problem module, pxsvcnow can search for any field from any table in ServiceNow and update that field providing the table ID and the field ID are known. There is an example showing how to do this in the pxsvcnow.cfg sample script.
Requirements
If you do not use a ticket target to configure events, you must define the variables shown in the table below in every ServiceNow script.
Variable | Description of the value |
|---|---|
adminid | is the user ID of a user with permissions to perform all operations that you require. |
adminpwd | is the password for the above user. |
server | is ServiceNow’s host name or IP address. |
port | is port number for ServiceNow web service, default is 443. |
proxy | is the HTTP proxy server. |
ssl | accepts true or false to switch connection SSL protocol on or off. |
checkCert | determines whether to validate the server’s security certificate for SSL connections. |
module | is the module in ServiceNow that you want to access. |