Network directory updates to remote machines

This topic provides an overview of directory updates to Message Networking remote machines. See the Adding and updating subscribers overview for additional information about how subscribers are added and updated on Message Networking remote machines.

The following types of directory updates are supported for N100 remote machines:

Full updates. Full updates include, in the new system's remote subscriber list, every subscriber on every system in the Message Networking network. This option ensures that subscribers on the new system can address by name every subscriber in the network. However, this option can require a large amount of disk space on the new system. Also, remote subscribers who do not send or receive messages will be stored unnecessarily. If you select this option, Message Networking performs a full update when you first administer the new system and run a Demand Remote Push to the new system. Subsequent updates occur in either of the following circumstances:

• When you perform a Demand Remote Push for the remote machine.
• When Message Networking receives a subscriber change from a remote machine.

Caution! If you begin with full updates or later change to dynamic updates, Message Networking removes all subscribers from the remote subscriber directory and begins to repopulate the directory with dynamic updates.

Dynamic updates. With this update option, each time a subscriber on the new system sends a message to a remote subscriber, that remote subscriber is added to the Dynamic Directory List for the new system. Likewise, each time a remote subscriber sends a message to a subscriber on the new system, that remote subscriber is added to the list.

If, typically within the next 90 days (as set on the Dynamic Sub Expiration Days on the General Parameters page), no other messages are sent from the new system to that remote subscriber or vice versa, that remote subscriber is removed from the list. This removal helps save storage space on the new system.

Directory View updates only. With this option, the new system's remote subscriber list includes subscribers within ranges of extensions on the systems you specify. A Directory View list for a system is static and, as with full updates, this option can use a lot of disk space. Additionally, with this option, subscribers who fall outside of the ranges and systems you specify are not addressable by name from the new system.

If you select this option, Message Networking performs a Directory View update when you first administer the new system and perform a Demand Remote Push. Subsequent updates include changes to subscriber lists of remote systems, where subscribers are added or removed. Subsequent updates occur in either of the following ways:

• When you perform a Demand Remote Push for this system
• When Message Networking receives a subscriber change from a remote system.

Combination of dynamic and Directory View updates. You can use dynamic and Directory View updates in combination. In this case, dynamic updates occur as described above, but the Directory Views option also identifies specific ranges of extensions on specific remote machines to ensure that remote subscribers on those systems can be addressed by name on the new system.

This type of setup is useful when you are converting a high-traffic point-to-point system to the Message Networking network or when it is important that all or a subset of remote subscribers on a specific system are addressable by name for subscribers on the new system.

None. With this option, Message Networking does not update the subscriber names list for the new system. This might be a useful option during testing or early during the addition of the new system to discourage subscribers on the system from sending messages through Message Networking.

The following table provides a comparison of the network directory update types supported for each type of remote machine.

Top of page