Share via


How to Configure Calendar Connector for Novell GroupWise

 

This topic discusses how to configure Calendar Connector for Novell GroupWise.

Before You Begin

To successfully complete the procedure in this topic, ensure that the server on which you install Calendar Connector meets the following requirements:

  • The server is running Exchange Server 2003.

  • The server running Exchange 2003 has a local replica of the SCHEDULE+ FREE BUSY public folder.

  • The server is part of the same routing group as the server running Connector for Novell GroupWise.

  • You have Exchange Administrator permissions, and you are a member of the Administrators group on the computer on which you install Calendar Connector.

  • You have network connectivity to the Novell NetWare server running the Novell GroupWise API Gateway.

Procedure

To configure Calendar Connector for Novell GroupWise

  1. In Exchange System Manager, expand Administrative Groups, expand the administrative group that contains the server running Exchange with Calendar Connector (for example, First Administrative Group), expand Routing Groups, expand the routing group in which you installed Calendar Connector (for example, First Routing Group), expand Connectors, right-click Calendar Connector, and then click Properties.

  2. On the General tab:

    1. Next to the Connector used to import users into Active Directory box, click Modify.

    2. In the Select Exchange Notes or Groupwise Connector dialog box, select the Connector for Novell GroupWise instance that is used to connect to the Novell GroupWise API Gateway, and then click OK.

    3. In the Number of days of free/busy information to request from foreign calendars box, enter the number of days that users are able to see free/busy information for users on the foreign messaging server. Free/busy information beyond the number of days specified is not retrieved by Calendar Connector and appears as free, even if meetings are scheduled during this time. Remember that the maximum value for GroupWise is 389 days.

    4. In the Maximum age in minutes of foreign free/busy data in Exchange that can be used without querying the foreign calendar box, enter the age limit for free/busy information in minutes. If the free/busy information is beyond the specified number of minutes and a user requests the information, Calendar Connector queries the non-Exchange messaging system for updated data. If the free/busy information is within the specified number of minutes, Calendar Connector uses the current free/busy information.

    5. In the Maximum number of seconds to wait for response from foreign calendars box, enter the number of seconds that you want Calendar Connector to wait for a response after it requests an individual user's free/busy information. Set this to a low number, because each recipient on a meeting request is handled in turn, and a long response interval can cause the mail client to stop responding as it proceeds down the list of recipients.

    Setting the General tab Calendar Connector options

    62699090-eb53-4b67-b01b-3d9e94c09a60

  3. On the Calendar Connections tab:

    1. Click New.

    2. In the Calendar Type dialog box, click Novell GroupWise, and then click OK.

    3. In the GroupWise Calendar Connection dialog box, in the GroupWise API Gateway box, type the domain and gateway name of the Connector for Novell GroupWise that interfaces with the API Gateway. Do not include the certifier information. For example, if your Novell GroupWise domain name is CONTOSO_DOM, and the API gateway name is Exchange Gateway, then type CONTOSO_DOM.Exchange Gateway.

    4. Click OK.

    Configuring the calendar connection to Novell GroupWise

    ba3d0bd3-805d-485e-9a21-dc3d21bfec0f

  4. On the Schedule tab, click Always. This causes Calendar Connector to create a free/busy record for Novell GroupWise recipients in the Exchange public folder. This happens every 15 minutes for new recipients. Alternatively, click Selected times to specify a custom time for the connector to create new records in the server's public folder. Click OK.

For More Information