Notification Profile Migration
Once the upgrade is successfully done from 11600 to 12200, you would be seeing more notification profiles than you have actually created. Don't get panic. It is not a bug. It is one of the design changes we have been trying to do it in the past.
Digging into the past
In the past, one of the frequently requested features was to be able to associate the notification profile to the device during discovery of the device. Since the profile and the criteria options were separate, we couldn't achieve this even when we knew it would add lot of value. In the old client, when we edit the Admin-->Notification profile, we wouldn't see previously selected criteria options. Only when we edit it inside the device page, you could see the selected criteria options for the device.
When API client was introduced, we combined the profile and the criteria options but when the user changes the criteria options inside the device, they also had the same profile name. ie A single profile name was having more than one criteria options. This design did not help in achieving that required feature "Automatically assign notification profile to the device during discovery" since there were more than one set of criteria option for the same profile.
So, the only option was to tie a notification profile to one set of criteria option. We introduced that in one of the consolidated API client fix patch in 11600. Those users who have made many changes in criteria options in the device level started seeing hundreds of profiles in the admin page. This was because each set(profilename-critera option) is considered as a separate profile. It was bit tough for them to manage. So we handled this differently in 12200 and it won't list hundreds of profiles in the settings page.
New Design in 12200:
1) If a global notification profile with a single set of criteria options is assigned to one or many devices, it will have only one entry under "Global profiles" after upgrade.
2)In 11600 or before, after assigning a notification profile, if the user had made changes in the criteria options of individual devices, they would be considered as separate profiles. Since that criteria option is specific to that device, it will be listed under "Device Specific profiles".
3)In 11600 or before, if the profile is edited and applied to multiple group of devices with different criteria options, each group will have a separate profile name and they will be listed under global profiles. Names can be manually changed only for these profiles by clicking "Edit Name" option.
Now using Discovery Rule Engine, users can automatically associate a notification profile to the devices during discovery.
New to ADSelfService Plus?
Related Articles
Scenarios in which multiple Notification Profiles need to be created
When a fault is detected in your network, an event occurs and multiple events correlate to trigger an alarm. You can configure OpManager to notify the network administrator or perform automatic actions based on the alarm raised for a device, using ...Email notification does not work
Issue : OpManager is generating alarms but my email notification does not work. Solution: check the following: 1)Mail server settings should be configured correctly and make sure "Test mail" on the same page works fine. (Go to OpManager admin tab > ...Creating custom script template in OpManager
Database Migration - MySQL to PgSQL
The DB migration from MySQL to PgSQL involves taking a PgSQL compatible backup, re-installing the product with PgSQL database and restoring the backup. The procedure for the above is a little tedious and time consuming in version 9 & 10. So, please ...OpManager DB migration from PGSQL to MSSQL in Version 125230
For OpManager version 125230: PGSQL to MSSQL Migration Steps : In the PGSQL setup, go to OpManager home → bin, start Command Prompt with administrator privilege from this path and run DBConfiguration.bat. In the popup shown, please chose MSSQL, check ...