Hi :) In 8.1 alerts are hijacked to be used for tweets. For exampĺe you can link a twitter account to a people and if he receives a notification of type "alert" it Will send the message to his tweeter account.
I don't know if you can still use alert as it was working in 7.6.04. I just used alerts to create tweets so far Mobilis in Mobile. Le 12 avr. 2013 à 12:04, mkovrizhnykh <mkovrizhn...@gmail.com> a écrit : > Hi All, > > After connection to the ARS 8.1.00 server with Remedy Alert 7.6.04 there are > *no* records in "AR System Alert User Registration" form. > > In aralert.log I see: > <ALRT> <TID: 0000000028> <RPC ID: 0000000057> <Queue: Fast > <Client-RPC: > 390620 > <USER: Demo > /* 12.04.2013 15:34:04.7921 */Received > deregistration request for user Demo at address 192.168.101.94 on port 49179 > <ALRT> <TID: 0000000028> <RPC ID: 0000000057> <Queue: Fast > <Client-RPC: > 390620 > <USER: Demo > /* 12.04.2013 15:34:04.7924 */Registration > entry for user Demo at address 192.168.101.94 on port 49179 was not found > <ALRT> <TID: 0000000027> <RPC ID: 0000000066> <Queue: Fast > <Client-RPC: > 390620 > <USER: Demo > /* 12.04.2013 15:34:05.0126 */Received > registration request for user Demo at address 192.168.101.94 on port 49184 > <ALRT> <TID: 0000000027> <RPC ID: 0000000066> <Queue: Fast > <Client-RPC: > 390620 > <USER: Demo > /* 12.04.2013 15:34:05.0127 */Queued > acknowledgement request for user Demo at address 192.168.101.94 on port > 49184 > <ALRT> <TID: 0000000027> <RPC ID: 0000000066> <Queue: Fast > <Client-RPC: > 390620 > <USER: Demo > /* 12.04.2013 15:34:05.0236 */Preliminary > registration for user Demo at address 192.168.101.94 on port 49184 completed > <ALRT> <TID: 0000000025> <RPC ID: 0000000000> <Queue: Alert > <Client-RPC: > 390601 > <USER: AR_NOTIFIER > /* 12.04.2013 15:34:05.0254 */*Error (22) in > binding send socket for address <:0>* > <ALRT> <TID: 0000000025> <RPC ID: 0000000000> <Queue: Alert > <Client-RPC: > 390601 > <USER: AR_NOTIFIER > /* 12.04.2013 15:34:05.0256 */Pausing for 1 > second(s) before attempting connection retry > <ALRT> <TID: 0000000025> <RPC ID: 0000000000> <Queue: Alert > <Client-RPC: > 390601 > <USER: AR_NOTIFIER > /* 12.04.2013 15:34:06.0309 */*Error (22) in > binding send socket for address <:0>* > <ALRT> <TID: 0000000025> <RPC ID: 0000000000> <Queue: Alert > <Client-RPC: > 390601 > <USER: AR_NOTIFIER > /* 12.04.2013 15:34:06.0315 */Registration > state for user Demo at address 192.168.101.94 on port 49184 updated to DOWN > <ALRT> <TID: 0000000027> <RPC ID: 0000000000> <Queue: Fast > <Client-RPC: > 390620 > <USER: AR_NOTIFIER > /* 12.04.2013 15:34:06.0335 */Cleanup of > registration entry occurred for user Demo at address 192.168.101.94 on port > 49184 > > So, Remedy Alert applcation does not receive alerts. > Does anybody try to use Notify Alerts with new version ARS 8.1? > > > Kind regards, > Mikhail > > > > -- > View this message in context: > http://ars-action-request-system.1.n7.nabble.com/Notify-Alerts-in-ARS-8-1-tp108511.html > Sent from the ARS (Action Request System) mailing list archive at Nabble.com. > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
