Hi,
a workaround to automatically forward the alarmdata to Remedy is by using Webservices of Remedy.
Last week I have integrated CA Spectrum with Remedy... I had only build the Spectrum-Part.
Mostly there is the problem to get control around the alarms which are send to remedy.
In our case, we used the SetScript and ClearScript of the (Alarm-) Notifier to execute a POST-Request via CURL.
We installed CURL at Spectrum and are able to create and update Tickets.
The Customer has build his own webservice in Remedy with custom variables.
With Setscript we call the webservice and get back the Ticket-ID which we post into the Attribute "TicketID" of Spectrum.
The AlarmID or AID in Spectrum is the Unique variable which we use to identify unique Alarms out of Spectrum.
With Clearscript we use the same AlarmID and the Ticket-ID which helps Remedy to identify the created ticket. Remedy could update the ticket or close it if the Severity is in a specified range.
In the Notifier, we used the Cause_Count-Attribute to identify Root-Cause-Alarms and Symptom-Alarms.
.. and with User-Interaction...
Another way to manually interact between Spectrum and Remedy is to implement a Custom-Context-Menu. ... via Context-Menu we open a URL which includes many variables which we push into a JSP/Webpage. In this webpage the user is able to modify the content.
Finally the user could press a Submit-button in this webpage to reloud the webpage.
The code of the webpage pushes the content into Remedy via a Webservice .... Curl via JAVA....
These are two ways which we used to push the data into Remedy....