I have my OrionNPM integrated with Remedy via RPC successfully!
Logic:
- A node with a specific custom property goes down
- Send a special structured syslog message to kiwi
- Kiwi sends the orion message to a VBS script that do a syntactic analysis, format date time, trim and replace text.
- Kiwi send parsed message to a MS-DOS Batch file that assembles command esp-createentry with the relation between remedy Field_ID and our variables
- esp-createentry.exe send to Remedy server via RPC the form information and create the new ticket, it returns the new Ticket ID
Structure (check image attached):
- Install Kiwi syslog server on port UDP 6500
- Create a Custom Property (TK) to select and classify nodes of which we want to create a ticket on remedy
- Create an advanced alert. Trigger alert when node is down and TK contains client. After a delay of 11 min. send a syslog message to our localhost_name:6500 [T#,"${TK}","${State}","${Site} !${Customer_ID}","@${AlertTriggerTime}@","${Caption} ${Status}","-+- ${Customer_ID} ${Caption} ${Status}"]
- On Kiwi syslog create a new rule: [Filter include "T#"], [Actions: 1.Run Script VBScript (Common Fields Read and Write), 2.Run External Program (my_bat.bat %MsgText), 3.Play some sound ]
- Create batch file. In this file we going to build the relation between Remedy field_ID and our variables and send the structure to esp_createentry.exe<Server> <Remedy User> <Password> <Schema> <Field ID>
<Value> [ <Field ID> <Value> ... ]
ESP_CreateEntry: ESP_CreateEntry program is one of the way to make integrations with Remedy ARS server. Following the closure of the company Elegant Software, responsible for this program and no longer make the amendments necessary for adapting to new versions of Remedy ARS. It is not always possible to modify the integration schemes used, and therefore it is necessary to know something more about the operation of this program to carry out proper maintenance of our Remedy ARS server and supporting integrations.