Chapter 8: Set Up Busy Search

• Busy Search Overview
  
  
• Edit Calendar User IDs
  
  
• Define Post Office Paths

Busy Search Overview

OfficeVision/VM** uses a calendar service machine to extract information from the calendar database. When a user requests a calendar function, such as a busy search (OfficeVision/VM refers to it as a calendar check), the calendar machine performs the operation on the calendar database and then responds to the user by showing the recipient’s calendar.

In many cases, OfficeVision/VM users span several VM nodes. A user on one node may want to use the Busy Search feature to check for an open date and time on another user’s calendar on a different VM node. Remote calendar operations are processed through the REMCAL file. Each calendar machine has a unique machine name in the VM node where it resides. The REMCAL file registers all remote calendar machines by node ID and calendar machine name, as shown below.

GroupWise* users must be able to access data in the REMCAL file. This data is stored in the CALTOHOST.FIL file, which resides in the \WPGATE\OVVM directory. The CALTOHOST.FIL file is automatically created when the gateway receives its first calendar request, and is automatically appended when a calendar request arrives from a new VM node.

You can use the Edit Calendar Users IDs page to incorporate the REMCAL data into the gateway configuration.

Edit Calendar User IDs

OfficeVision/VM uses a calendar service machine to extract information from the calendar database. When a user requests a calendar function, such as a busy search (OfficeVision/VM refers to it as a calendar check), the calendar machine performs the operation on the calendar database and then responds to the user by showing the recipients calendar.

In many cases, OfficeVision/VM users span several VM nodes. A user on one node may want to use the Busy Search feature to check for an open date and time on another users calendar on a different VM node. Remote calendar operations are processed through the REMCAL file. Each calendar machine has a unique machine name in the VM node where it resides. The REMCAL file registers all remote calendar machines by node ID and calendar machine name.

GroupWise users must be able to access data in the REMCAL file. This data is stored in the CALTOHOST.FIL file, which resides in the \WPGATE\OVVM directory on the network. The CALTOHOST.FIL file is automatically created when the gateway receives its first calendar request, and is automatically appended when a calendar request arrives from a new VM node.

To edit the calendar user IDs,

1. From the NetWare* Administrator browser window, double-click the domain where you created the Gateway for OfficeVision/VM.
   
   
2. Right-click the Gateway for OfficeVision/VM  click Details  Edit Calendar Users IDs.
   
   Each post office name that conforms to the VM eight-character restriction is displayed in the Calendar Machine User IDs list. A post office name is not displayed if it does not meet the VM eight-character restriction. If this is the case, you must assign an alias to that post office. For more information, see Conform to GroupWise VM Restrictions in Chapter 6: Send a Message from the Mainframe to GroupWise Users.
   
   
   
   
3. Choose a function to perform:
   
   Edit: To edit an entry, click an entry in the table  click Edit  modify the fields.

   VM Node: Use the name of the VM node where the calendar machine resides.
   
   Calendar Machine ID: Use the name of the calendar machine that resides on the VM node in the above field.

   Delete: To delete an entry, click an entry in the table  click Delete. The item is deleted.
   
   Add VM Node: To add a VM node, click Add VM Node  fill in the fields.

   VM Node: Use the name of the VM node where the calendar machine resides.
   
   Calendar Machine ID: Use the name of the calendar machine that resides on the VM node in the above field.

   Import REMCAL File: The REMCAL file keeps track of the remote calendar machines a VM node can access. This file resides on the mainframe, but the data must be present on the LAN for the gateway to gain access. The Import REMCAL File feature imports the REMCAL file data to the CALTOHOST.FIL file, which enables cross-calendar checking between GroupWise and OfficeVision/VM users. Click the Import REMCAL File button and fill in the field with the name of the REMCAL file.
   
   Number of seconds to wait for busy search to return from OV/VM: To adjust the number of seconds GroupWise should wait for a busy search to be returned from OfficeVision, enter a number in seconds in the Number of seconds to wait for busy search to return from OV/VM. If the busy search is not completed within that time, the user receives an undelivered notification in his or her Out Box. If the interval is too high, a user may have a long wait when there is an unsuccessful busy search.

Define Post Office Paths

Typically, the GroupWise system uses the Message Transfer Agent (MTA) to perform a busy search. The Edit GroupWise Paths feature lets you bypass the Message Transfer Agent by providing the full path-name of the post office. This increases the speed of the busy search. The gateway, instead of the MTA, launches the Busy Search function.

Make sure the gateway station is attached to each file server that includes a post office for which you want to perform a busy search.

To define the post office paths,

1. From the NetWare Administrator browser window, double-click the domain where you created the Gateway for OfficeVision/VM.
   
   
2. Right-click the Gateway for OfficeVision/VM  click Details  Post Office Paths.
   
   
3. Adjust the fields.
   
   
   
   
4. Select a post office in the list  click Edit.
   
   
5. Modify the fields:
   
   Domain: This field displays the domain location of the selected post office entry.
   
   Post Office: This field displays the name of the post office.
   
   Path: Enter the full pathname or the UNC (Universal Naming Convention) path of the post office. The UNC path designates the file's absolute location.

* Novell trademark. ** Third-party trademark. See Trademarks for more information.