Ricoh InfoPrint Pro C900AFP InfoPrint Manager - Page 33
Using InfoPrint Manager notifications, Understanding notification profiles
View all Ricoh InfoPrint Pro C900AFP manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 33 highlights
Chapter 6. Using InfoPrint Manager notifications InfoPrint Manager can detect events (such as job completed or destination needs attention) as they occur, generate messages about those events, and deliver the messages to users who need the information. For example, users can receive messages about jobs they submit, operators can be notified about InfoPrint objects that require their attention, and administrators can be notified if someone makes a configuration change. With notifications, you do not have to query for status of the objects in your system-you just receive messages when specific events occur so that you can take care of them. You can tailor who receives these messages and how they are delivered based on the notification profile that is set for a particular InfoPrint object. 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" on page 16 for more information. Delivery method How the messages are delivered. See "Delivery method and delivery address" on page 16 for more information. Delivery address Where the messages are sent. See "Delivery method and delivery address" on page 16 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: v 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. v 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. 15