In the case of Agile 2.3 there are some built in external mashup events that will fire if you have the SBM Integration Settings filled in on the Configuration | Integration Settings screen. Those seem to work fine wether you have Single Sign On (SSO) turned on in SBM or not. These are predefined external notifications with names like AgileWICreate, AgileWIUpdate.
The following change will cause users logged into Agile to be kicked out of their session and be forced to login again so make this change in off hours. Open the web.config file in the following default install folder. C:\Program Files\Serena\Agile Planner\Agile\web.config
Log into Mariner/Agile. Go to Setup | Configuration | Environment Settings | Notification Settings. Set the Notification Queue Server Name to be the name of the Mariner/Agile web server machine (do not use localhost).
The peadmin user (in Mariner/PPM) and the aodadmin user (in Agile Planner) always have full permissions, including Purge Data. Be very careful when logging into the system with this account name.
Data Source: This is case sensitive and must match the name of the connection on the Agile login screen. Location: This is the Agile Server name and Virtual directory name. Note: for Agile on Demand the location will be agile.serena.com/agile
To fix the root cause of the error, we recommend that you take a backup of your database BEFORE clearing the user settings. Then, open a support case ( support@serena.com ). You can send us the backup, and we will work with you on a permanent fix.
Click the Migrate button. If you get any errors, copy them from the bottom half of the migration screen and create a support case for additional help. NOTE
