From the General tab in the
Site Settings window, you can
configure:
Collaborations
— Path to your Collaborations directory, by default, Users\Public\Public Documents\Scribe. If
you change the Collaboration Root location:
Move any existing collaboration
files and folders to the new root location before you change the Collaboration
Root location
Restart Scribe services after
changing the Collaboration Root.
Note: When you specify the Collaboration root directory,
use Universal Naming Convention (UNC), such as \\server\share\file_path, if you are referring to a network
folder or a shared local folder. If you select a drive letter and path
instead of a UNC name, the system may be unable to access your Collaborations.
Site
Main Queues — Message queues you can define:
Scribe
Input Queue — Receives all incoming messages, which you can dispatch to any shared, user-created queue. This queue is required when you configure a Queue
Integration Process. The default Scribe Input Queue is SCRIBEIN.
Scribe Retry Queue — Receives messages that fail to process. By default, a
message is retried 120 times at five-second intervals. The number of retries
is controlled by the integration
process settings. The default Scribe Retry Queue is SCRIBERETRY.
Scribe Dead Message Queue — Receives any message that arrives at the Scribe
Input Queue with fatal errors, or that fails to process
after the specified number of retries. The default Scribe Dead Message Queue is SCRIBEDEADMESSAGE.
Alert
Notification — Frequency of alert notifications to be sent to Notification Groups. From this tab, you can resume paused notifications.
Event
Logging — Copy system Alerts to the Console Event
Log. From this tab, you can direct Insight to not copy those alerts to the log.
When you have finished setting these options, click Save,
or click Cancel to discard your
changes.
Note: When the Notification Monitor
encounters an error, it retries indefinitely on the schedule set in
the Alert Notification area.
The Notification Monitor sends
email for alerts that are less than 24 hours old. For example, if the
Notification Monitor is resumed after being off for more than 24 hours,
only alerts that are less than 24 hours old are notified by email.
This reduces the chance of large numbers of email being sent in case the
Notification Monitor was off for an extended period of time.