Sie sind auf Seite 1von 2

For AlarmNotifier configurations here are the best practices that I try to use: 1.

Copy the Notifier directory to create a unique AlarmNotifier instance for each application containing the following files: a. .alarmrc b. AlarmNotifier.exe c. ClearScript d. SetScript e. UpdateScript 2. Rename each AlarmNotifier executable to a name with more meaning a. i.e. AlarmNotifier_App1.exe, AlarmNotifier_App2.exe, etc., etc. 3. Edit the .alarmrc file and set the APPLICATION entry to be a unique application name that you will reference in SANM, keeping the APPLICATION name in sync with the AlarmNotifier executable name you defined in step 2. a. i.e. AlarmNotifier_App1, AlarmNotifier_App2, etc., etc. 4. Create a unique processd ticket to autostart and autorestart each instance of the AlarmNotifier app you create. 5. Optionally, you may want to rename each applications Set, Clear, and Update scripts to ensure there is no confusion. a. If you do rename these, be sure to update the values in the .alarmrc file 6. If you decide to keep each Notifier instance in the same directory you must create multiple .alarmrc files a. You would then start each Notifier as: i. AlarmNotifier_App1.exe r .alarmrc_app1 ii. AlarmNotifier_App2.exe r .alarmrc_app2 b. You would also need to create unique Set, Update, and Clear scripts as needed, just ensure you update the appropriate .alarmrc_app files

Hope this helps, Bill


Bill Lavoie
Technology Specialist, Presales Technical Sales Organization (TSO) CA, Inc. Tel: +1 603 334 2141 Cell: +1 603 674 8248 william.lavoie@ca.com

273 Corporate Dr. Portsmouth, NH 03801

Das könnte Ihnen auch gefallen