Use the following procedures to configure individual Server Monitor test screens.
Composer test
The Composers test checks that all conversion engines for each enabled Composer server are running correctly. If any of the Composers meet the test criteria, the actions defined in the test are triggered. The Composer Verification screen appears.
Click Next to proceed to the Specifying the actions to take for a test screen.
Connector Manager test
The Connector Manager test allows you to test single, multiple, or all connectors for the number of messages in the queue, the rate of messages received from the connector, or the rate of messages sent to the connector. The Connector Manager Verification screen appears and enables you to specify:
- Queue to monitor - Select All or Selected Connectors.
Note: If you select the Selected Connectors option, you must select at least one connector before you can complete the screen.
- What to monitor - Monitor one of the following. You can only select one option per test.
- Number of messages in the queue
- Rate of messages received from the connector
- Rate of sending messages to the connector
If you want to monitor all three options, create three tests.
After you select your monitoring criteria, enter minimum and maximum values between which the action for the test will be triggered. For example, if you are monitoring the Number of messages in the queue, you set the minimum at 10 and the maximum at 100, the specified actions are triggered if the number of messages in the queue is between 10 and 100.
After you configure the test criteria, click Next to proceed to the Specifying the actions to take for a test screen.
Connectors test
The Connectors test allows you to test single, multiple, or all connectors. This test verifies that the selected connectors are enabled. If they are disabled, the specified actions for this test are triggered. The Connector Verification screen appears.
Note: If you select the Selected Connectors option, you must select at least one connector before you can complete the screen.
After you configure the test criteria, click Next to proceed to the Specifying the actions to take for a test screen.
Database Size test
The Database Size test checks to see if the database size falls between a minimum and maximum size (in kilobytes). The Database Size Verification screen appears. Enter minimum and maximum values between which the action for the test will be triggered.
After you configure the test criteria, click Next to proceed to the Specifying the actions to take for a test screen.
Event Log Monitor test
The Event Log Monitor test allows you to configure what information you want to retrieve from the Event Log. You can retrieve information based on the log type, the Event Log status, the source, or the Event ID. You also can specify a wildcard text search on the Message field. The Event Log Monitor screen appears.
Note: This test retrieves information from the Event Log located on the server you are monitoring.
- Log - Select the type of log you wish to retrieve information from: Application, Security, or System.
- Status - Select the type of status message you want to retrieve from the specified log: Any, Information, Warning, or Error.
- Sources - Select to retrieve information for all applications, specify an Application Name, or use a wildcard search.
- Event ID - Select to retrieve all Event IDs, specify a specific ID #, or use a wildcard search.
- Message - Enter an asterisk (*) for a global search, or enter a specific value to narrow the scope of the information you receive. This is a required field. You can use the following variables in the Message body:
- %SERVER% - Maps to the name of the server you are monitoring.
- %CATEGORY% - Maps to the test category (for example: Composers or Connector Manager).
- %TESTDESCRIPTION% - Maps to the test name itself. You define the test name on the final page of the wizard.
- %PROBLEM% - Maps to the list of issues generated during testing.
Note: You must enter a value in the Message field before you can complete this screen.
After you configure the test criteria, click Next to proceed to the Specifying the actions to take for a test screen.
Filescan Folder test
The Filescan Folder test allows you to monitor and verify one of the following:
- Percentage of disk space available
- Age of control files (in minutes) - If you are using virtual control files, the Age of control files (in minutes) option is applied to the scanned files rather than the virtual control files.
- Quantity of bad control files - Server Monitor finds the bad control files, regardless of where they are stored (in the scanned folder or the specified invalid control files folder).
Note: Important! When you create the Filescan connector on the server, you must share the Filescan folder and configure it in UNC format (for example: \\ServerName\Filescan).
The Filescan Folder Verification screen appears. After you select your monitoring criteria, enter minimum and maximum values between which the action for the test will be triggered. For example, if you select to monitor Age of control files (in minutes) and set the minimum at 5 and the maximum at 10, the actions for the test will be triggered when a control file is between 5 and 10 minutes old.
After you configure the test criteria, click Next to proceed to the Specifying the actions to take for a test screen.
Server Disk Space test
The Server Disk Space test allows you to verify if the percentage of free disk space falls between the specified minimum and maximum values. The Server Disk Space Verification screen appears. After you select your monitoring criteria, enter minimum and maximum values between which the action for the test will be triggered.
After you configure the test criteria, click Next to proceed to the Specifying the actions to take for a test screen.
Services test
The Services test verifies that all required services are running properly on the server you are monitoring. The Services Verification screen appears. The required services are:
- Address Book Manager
- Component Manager
- Connector Manager
- Message Server
- Notification Server
Click Next to proceed to the Specifying the actions to take for a test screen.
Telco Folder test
The Telco Folder test allows you to select the folder to monitor (Send or Receive) and then monitor one of the following:
- Percentage of free disk space available
- Oldest item in the queue (in minutes)
- Number of items in the queue
Note: Important! When you create the Telco connector on the server, you must configure the Telco folders to use UNC format by clicking the Advanced button on the General tab of the Telco connector properties (for example: \\ServerName\Genifax).
The Telco Folder Verification screen appears. After you select your monitoring criteria, enter minimum and maximum values between which the action for the test will be triggered.
After you configure the test criteria, click Next to proceed to the Specifying the actions to take for a test screen.
Telco Modem Services test
The Telco Modem Services test verifies if the Modem Service is running on the monitoring server. If it is not running, the actions for this test are triggered. This test also checks one of the following for the RecvLocal folder:
- Percentage of free disk space available
- Oldest item in the queue (in minutes)
- Number of items in the queue
Note: Important! When you create the Telco connector on the server, you must you must configure the Telco folders to use UNC format by clicking the Advanced button on the General tab of the Telco connector properties (for example: \\ServerName\Genifax).
The Telco Modem Services Verification screen appears. After you select your monitoring criteria, enter minimum and maximum values between which the action for the test will be triggered.
After you configure the test criteria, click Next to proceed to the Specifying the actions to take for a test screen.
Workflow Components test
The Workflow components test allows you to verify all or selected components.
Note: If you select the Selected Components option, you must select at least one component before you can complete the screen.
The Workflow Component Verification screen appears. You can select from the following options.
- Queues to monitor - You can select All or Selected Components. Components that you can verify with this test are listed in the table below.
- What to monitor - You can monitor one of the following. You can only select one option per test.
- Number of messages in the queue
- Oldest item in the queue (in minutes)
Note: If you want to monitor both options, create two tests.
Workflow components
|
Variable |
Definition |
|---|---|
| Approval Manager | The Approval Manager component checks messages to determine if they require processing for Fax Review and Approval when the feature has been enabled to function as Fax Approval. A fax requires Fax Approval processing if the sender requested the fax be held for approval or if all faxes sent by the sender require approval (based on settings in the Registered Users database). |
| Approval Pending | The Approval Pending component holds messages that are currently waiting for an approval manager to view and approve. |
| Billing | The Billing component extracts billing information from messages and populates a table in the Genifax database with this information. This feature works in conjunction with CostRecovery. |
| Compose: localhost | The Compose component converts input (source) files from one file type into another file type (the final file format). When the file is part of a fax message, the final file format is TIF. The server supports virtually all file formats for the source files. Compose: localhost is the Compose component that is running on the local server. Any Remote Composers that are running will appear on the Workflow Component test criteria screen as Compose: servername. |
| Compose: Total Documents | The Compose component converts input (source) files from one file type into another file type (the final file format). When the file is part of a fax message, the final file format is TIF. The server supports virtually all file formats for the source files. Total Documents is the counter for the total documents processed by Compose components for all installed composers. |
| Compose: Total Recipients | The Compose component converts input (source) files from one file type into another file type (the final file format). When the file is part of a fax message, the final file format is TIF. The server supports virtually all file formats for the source files. Total Recipients is the counter for the total recipients processed by the Compose component. |
| Dispatch | The Dispatch component determines the final system destination for each message. The final system destination is the part of the server that routes a message to its intended recipient (also known as the recipient destination). The intended recipient is an e-mail address, fax number, folder name, or printer name. The Dispatch component also normalizes the phone number for outbound faxes. |
| Embedded Directive Manager | The Embedded Directive Manager component reads any embedded directive IDs found on inbound fax messages and decodes the information contained in the IDs. This information is used in the routing of returned registration requests for Secure Delivery. |
| FaxCenter Routing | The FaxCenter Routing component holds messages that have been routed to FaxCenter for manual routing by a FaxCenter user. |
| Lookup Manager | Genifax uses the Lookup Manager component to match DID/DTMF extensions to the appropriate Genifax user. This component uses Windows 2000 or 2003 Active Directories to find matches in the recipient's record in the Microsoft Exchange Server Administrator (in the Fax field on the Phone/Notes tab). |
| Maintenance | The Maintenance component removes old fax messages from the History folder. You can set the number of days the component keeps messages before removing them. |
| Notification | The Notification component delivers notification about the status of a message to the person who sent the message. Notification is sent for outbound messages only, or messages that originate within the server. |
| Preview Manager | The Preview Manager component determines if the sender of each message has requested a preview of that message. If the sender has requested a preview, the server holds the message in the Preview Pending component after the message is processed until the sender either approves or declines the message, or until the message expires. |
| Recipient Registration Manager | The Recipient Registration Manager component determines if the sender of each message has requested that the message be sent to secure destinations only. If the sender has requested Secure Delivery, the server holds the message in the Recipient Registration Pending component and faxes the recipient a notification message informing him or her of the need to register with your company. When the recipient registers, you or another administrative person must manually release the fax to that recipient. |
| Recipient Registration Pending | The Recipient Registration Pending component holds faxes that the Recipient Registration Manager component has determined require recipient registration for Secure Delivery. Faxes are held until you or another administrative person manually releases the fax, which should happen only when the recipient has contacted your company to register as a secure destination. |
| Review Manager | The Review Manager component checks messages to determine if they require processing for Fax Review and Approval when the feature has been enabled to function as Fax Review. A fax requires Fax Review processing if the sender requested the fax be held for approval or if all faxes sent by the sender require approval (based on settings in the Registered Users database) |
| Review Pending | The Review Pending component holds messages that are currently waiting for a manager to review. |
After you select your monitoring criteria, enter minimum and maximum values between which the action for the test will be triggered.
After you configure the test criteria, click Next to proceed to the Specifying the actions to take for a test screen.
See also
Optional Server Monitor Configuration