Targeting a Remedy server
Bravura Security Fabric provides the option of using the ticket target system name in event action fields in the Manage the system (PSA) module or Configure event (ITSM) module, rather than the program name. The security benefit is that all sensitive information (server address, admin credentials) is automatically passed to the program, rather than stored in the .cfg file in plain text.
For each Remedy Action Request System server, add a target system in Bravura Security Fabric (Manage the System > Resources > Target systems).
Remedy Action Request System 7.5+ (Ticket)
If the Remedy AR System is older than version 9.0:
Type is Remedy Action Request System 7.5+ (Ticket)
Ticket targets are grouped under IT Service Management Systems .
Address uses options described in the table below.
Administrator ID and Password identify the target system administrator you configured earlier.
Option | Description |
|---|---|
Options marked with a | |
Server | The name of the AR System server. (key: server) |
Port | If the Remedy server is not configured to use the default port, you can specify the port number in the target system address. If you set the port, the Remedy connector will use the transmission control protocol (TCP) method to connect. If you do not specify the port, the remote procedure calls (RPC) method will be used. (key: port) |
Language | You can specify the language used for various error messages, sorting of strings, and formatting of date and time information, in the format for example ja-JP or fr-CA. If language is not specified, the default is US English. (key: language) |
Form | The AR System form where the interface will look for and update data. (key: form) |
The address is entered in KVGroup format:
{server=<serverName>;port=<portNum>;form=<formName>;[language=<language>-<territory>;]}
Remedy Action Request System 9.0+ (Ticket)
If the Remedy AR system is version 9.0 or newer:
Type is Remedy Action Request System 9.0+ (Ticket)
Ticket targets are grouped under IT Service Management Systems.
Address uses options described in the table below.
Administrator ID and Password identify the target system administrator you configured in earlier.
Option | Description |
|---|---|
Options marked with a | |
Server | The IP address/domain name of the server. (key: server) |
Port | The port number of the server. (key: port) |
Connection over SSL | Select to enforce SSL connections. (key: ssl) |
Validate the server’s certificate when connecting | Determine whether to validate the server’s security certificate for SSL connections. Default is true. (key: checkCert) |
HTTP Network Proxy | Specifies a proxy URL to use for connecting. (key: proxy) |
Advanced | |
Form for creating ticket | The AR System form where the interface will create tickets. (key: createForm) |
Form for searching ticket | The AR System form where the interface will search tickets. (key: createForm) |
Form for updating ticket | The AR System form where the interface will update tickets. (key: updateForm) |
Field holding ticket number | The ticket number field used for the AR System forms. (key: ticketNumber) |
Field holding entry id | The entry ID field used for the AR System forms. (key: entryID) |
The address is entered in the syntax:
{server=<serverName>;port=<portNum>;ssl=true|false;checkCert=true|false;proxy=<proxyServer>;createform=<createFormName>;searchform=<searchFormName>;updateform=<updateFormName>;ticketnumberfield=<ticketNumberID>;entryidfield=<entryID>;}
Once you write a configuration file, you can use the target ID to configure event actions in the Manage the system (PSA) module or Configure event (ITSM) module.