Ricoh InfoPrint Pro C900AFP InfoPrint Manager - Page 33

Using InfoPrint Manager notifications, Understanding notification profiles

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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426

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