Understanding notification profiles
Most InfoPrint objects (the server, actual destinations, logical destinations, queues, jobs, and default jobs) have notification profiles associated with them. A notification profile is composed of one or more notification profile entries. Each notification profile entry has three main components:
- Event Identifiers
- Which events cause messages to be sent. See Event identifiers for more information.
- Delivery method
- How the messages are delivered. See Delivery method and delivery address for more information.
- Delivery address
- Where the messages are sent. See Delivery method and delivery address for more information.
In addition, a notification profile entry can include a comment (text that InfoPrint will add to the general message text) and a locale (to set the language that the message will be sent in). Comments are optional. If you do not specify a locale, InfoPrint delivers messages using the locale (language) that the user is running.
Some objects need only one entry in their notification profiles. For example, when a person submits a job, he is probably the only one who needs to receive information about it, and he will probably be content to have all of the messages about that job delivered the same way.
For other objects, there are very good reasons to have multiple entries. For example:
- If operators manage printers from more than one workstation, you can create an entry for each workstation. That way, all of the messages go to all of the machines.
- If operators can address some messages (like destination-needs-attention), but an administrator needs to address others (like object-deleted), you can create an entry for each operator and one for the administrator. Messages are delivered to the person who can handle them.
- If an administrator likes to use InfoPrint Manager Notifications while he's at work, and wants to keep a more permanent record of how often some events occur, he can set up two entries. One delivers messages to the InfoPrint Manager Notifications client and one writes certain messages into a file that he can check periodically.