Use the Global Alarm ID. As you see AlarmID does not have all the fields necessary. Additionally, if you have a distributed SpectroSERVER setup, AlarmID may not be unique. You could have a situation where the same "AlarmID" exists for different alarms on different servers. That is one of the reasons they developed the Global Alarm ID.
Bill > From: Brett Davis <[email protected]> > Reply-To: Brett Davis <[email protected]> > Date: Tue, 13 Oct 2009 19:52:49 -0400 > To: spectrum <[email protected]> > Subject: [spectrum] CORBA app to set status, ticket id, and URL on alarms from > ticketing system > > We are trying to write an application that will sit on our ticketing > system's server and wait for spectrum to send an alarm in the form of an > email in order to generate a ticket. Once the email comes in with the > alarm information, the application should use the alarm_id specified in > the email to connect to the Spectrum server and set the Ticket ID, > Status, and other updateable attributes of the alarm. > > This sounds simple in theory, however the alarm as Spectrum prints it > out is something along the lines of "1586", however this needs to be > converted into a 16 element byte array to be a valid Alarm ID. The API > docs say that the CsCorbaAlarmHelper class is supposed to have a helper > function to do this, but it doesn't exist. > > Anybody have any ideas on how we can take a plain text alarm ID and turn > it into the right kind of byte array? Obviously Spectrum is doing it > somehow when it creates the links that allow you to directly call up an > alarm. > > Thanks for any advice! I'd be happy to provide the code for this > connector to anyone who wants after we get it working. > -- > Brett Davis, CCNA, GSEC > IT Network and Security Operations > Purdue University > YONG 605 > Phone (765) 49-62304 > [email protected] --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
