Using Routing Domains

As an alternative to configuring individual links between individual domains throughout your GroupWise system, you can establish a system of one or more routing domains under the following circumstances.

• Domains must connect to the routing domains with TCP/IP links.
• GroupWise 5.5 and 6.x domains can be part of the routing domain system. Domains and MTAs that are still at a 5.2 or earlier version cannot participate and must use links as provided in the Link Configuration Tool.

A routing domain can serve as a hub in the following situations:

• Messages that would otherwise be undeliverable can be automatically sent to a single routing domain. This routing domain could be set up to perform DNS lookups and route messages out across the Internet. See "Using Dynamic Internet Links" in "Connecting to GroupWise 5.x and 6.x Systems" in the GroupWise 6.5 Multi-System Administration Guide.
• All messages from a domain can be automatically routed through another domain, regardless of the final destination of the messages. This provides additional control of message flow through your GroupWise system.

You can set up routing domains on two levels:

• Selecting a System Default Routing Domain
• Selecting a Specific Routing Domain for an Individual Domain

Scheduling Direct Domain Links

When domains link across an expensive medium such as long-distance phone lines, you can reduce the cost of the link by controlling when it is open. You can choose to have some types of messages wait in the message queues for the lowest phone rate. You can collect messages in the message queues until a specified time or size limit is reached, then open the link, rather than opening the link for each message as it arrives in the queue. You can design as many link profiles as you need, to schedule the transfer of various types of GroupWise messages in the most efficient and cost-effective manner.

To create a schedule for a link between domains:

1. In ConsoleOne, click Tools > GroupWise Utilities > Link Configuration.

2. In the drop-down list, select the domain to schedule a link for.

3. Click View > Domain Links to display domain links.

   
   

4. Double-click the domain you want to create a link schedule for.

   Only direct links can be scheduled.

   
   

5. Click Scheduling.

   
   

   The link schedule grid displays the current schedule for the selected direct link. The grid consists of half-hour time slots showing the link profile assigned to each time slot. Available link profiles are listed below the link schedule grid.

   Each link profile defines the following values to set the conditions under which the link opens:

   • Which message queues to monitor
   • Maximum wait time for any message in any monitored queue
   • Maximum number of waiting messages allowed in all monitored queues
   • Maximum total size of waiting messages allowed in all monitored queues

   The default profile shows as white in the link schedule grid. The default profile is in effect at all times when no other profile has been selected. Any other defined profiles show as gray. The currently selected link profile shows as green.

6. To create a new link profile, click Create.

   or

   To edit an existing link profile, select it in the profile list, then click Edit.

   or

   To edit the default link profile, click Default.

   
   

7. If you are creating a new link profile, provide a unique name for the link profile in the Name field.

   If you are editing an existing link profile, you cannot change the name.

8. In the Description field, provide whatever additional information is necessary to describe the purpose of the link profile.

9. Use the scroll bar in the Time Threshold box to select which queues to monitor and process when this link profile is in effect.

   Queue	Purpose
   0	Busy Search requests
   1	Requests from GroupWise Remote users
   2	High priority user messages; administrative messages
   3	High priority status messages
   4	Normal priority user messages
   5	Normal priority status messages
   6	Low priority user messages
   7	Low priority status messages

   The contents of deselected queues are not monitored but are processed when the link opens.

10. For each selected queue, specify the maximum number of minutes a message must wait in each queue before the link opens.

    If you want the link to open immediately when a message arrives in the queue, specify 0 (zero).

11. In the Messages field, specify the total number of messages waiting in all selected queues that will trigger the link to open.

12. In the KBytes field, specify the total size in kilobytes of all messages waiting in all selected queues that will trigger the link to open.

13. Click OK to save the link profile and return to the Link Scheduling dialog box.

14. Select the new or modified link profile in the profile list.

15. Click a time slot or drag to select a range of time slots.

    Time slots assigned to the selected link profile display as green.

16. Select all the time slots you want governed by the selected link profile.

17. Select a different link profile to assign to time slots.

    or

    Create or edit another link profile.

    or

    Click OK to save the schedule for the current link.

18. When the schedule is saved, click OK to close the Edit Domain Link dialog box.

19. To exit the Link Configuration Tool, click File > Exit > Yes.

    ConsoleOne then notifies the MTA to restart using the new link schedule.

Using a Transfer Pull Configuration

Typically for a mapped or UNC link, the MTA for the sending domain writes (or "pushes") message files into the input queue subdirectories of the receiving domain. However, it is possible to change this configuration so the MTA for the receiving domain picks up (or "pulls") message files from the sending domain.

The transfer pull directory is a location in the sending domain where the MTA for the receiving domain can pick up message files (that is, "pull" them from the sending domain). It represents the only configuration where an MTA processes messages outside its own domain directory structure.

NOTE:  The transfer pull configuration does not apply to the Linux MTA because the Linux MTA does not use mapped or UNC links.

To set up a transfer pull configuration between domains:

1. Manually create a transfer directory with input queue subdirectories from which outgoing message files will be pulled.

   The transfer directory must contain a wpcsin subdirectory, with standard priority 0 through 7 subdirectories beneath. For an example, see "Alternate Link Configuration: Transfer Pull" in "Message Delivery to a Different Domain" in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. The transfer directory must be placed where both the sending and receiving MTAs have rights.

2. In ConsoleOne, modify the outgoing link from the sending domain so the MTA for the sending domain writes message files to the transfer directory, rather than directly to the receiving domain. See Modifying the Outgoing Transfer Pull Link.

3. In ConsoleOne, modify the incoming link to the receiving domain so the MTA for the receiving domain actively pulls message files from the transfer directory, rather than waiting for them to be delivered. See Modifying the Incoming Transfer Pull Link.

4. Stop and restart the MTAs for both domains.