Each instance of StarTeam Notification Agent can monitor only one server configuration. That means that you must run StarTeam Notification Agent once for each server configuration to be monitored.
Before you can run an instance of StarTeam Notification Agent, you must:
The user must have an email address listed in the server’s User Manager. StarTeam Notification Agent does not have to use that user’s email address, but the user must have one.
If the user name to be used by StarTeam Notification Agent is that of a team member and you plan to send email notification messages that require a response, StarTeam Notification Agent must use a different email address. You will not want to fill the team member’s mailbox with email from the StarTeam Notification Agent.
For details about adding users, see the StarTeam Administrator’s Guide.
This type of notification is either on for all users or off for all users.
This type of notification can be redundant or conflict with StarTeam Notification Agent email messages.
This type of notification is turned on and off per component and per user. There are personal options for system tray notification in the Microsoft Windows client. The StarTeam Cross-Platform Client does not have this functionality.
Run StarTeam Notification Agent setup to identify each server configuration to be monitored by StarTeam Notification Agent and to set notification properties for that configuration.
As part of this process, a StarTeam Notification Agent folder will be added to the server configuration’s StarFlow Extensions project. StarTeam Notification Agent uses this folder to
store the setup information for the server configuration in a file named NotificationAgent.conf.xml.This process also creates a serveraddress_port.nac file (for example, orion_49201.nac) for each server configuration. The .nac file contains the mailbox password but in an encrypted format. The file is stored in StarTeam Notification Agent’s installation folder.