Previous PageNext Page

Chapter 10 - StreetTalk Directory Assistance Services

STDA Services

Master Services

The master service visits each target server throughout the day until it collects all group data maintained by the StreetTalk service on that server.
Any changes that have occurred in the targeted StreetTalk databases since the last collection time are added to the master service's database.
At a time specified by the administrator, the master service rebuilds, incorporating the changes into a new database.
Between rebuilds, satellite services downloading information from master services receive the most current version of the master service's database, including any changes collected since the last rebuild.

Satellite Services

Master and Satellite Topology

Figure 10-1. STDA Service Topology

Inclusions, Exclusions, and Exceptions

Note: STDA inclusion names support the same characters in the same way as the StreetTalk Naming service.

Collecting Information

Data Collection by Master Services

Master Service Configuration Guidelines

Data Collection by Satellite Services

Note: For every server you select, you can specify which type of information you want to collect from it by selecting its name spaces; that is: StreetTalk names or inclusions or a combination of both.

Satellite Configuration Guidelines

Displaying Information

StreetTalk and inclusion names
StreetTalk and inclusion attributes

Displaying StreetTalk and Inclusion Names

Displaying StreetTalk and Inclusion Attributes

Collected and displayed for users who want to look up information on StreetTalk resources. These lookup collections are controlled through the Define Attribute Lookup editing screen.
Collected into index lists for users who want to search for StreetTalk resources based on attribute values. These index collections are controlled through the Define Attribute Indices editing screen.

Planning Tasks for STDA Services

Calculating disk space requirements
Locating STDA services on the network
Designating download servers
Scheduling rebuilds
Sorting names
Creating exclusions, exceptions, and inclusions

Calculating Disk Space Requirements

If no attributes are defined for an object, you must reserve 800 bytes of disk space to store each database entry (name).
For each attribute established for a user, allocate an additional 180 bytes of disk space plus the size of the attribute. For instance, if the attribute is 400 bytes, allocate 580 bytes.

Disk Space Requirements for StreetTalk and STDA

Table 10-1. Combined Disk Space Calculations

Locating STDA on the Network

Network Geography and STDA

Organizational Structure and STDA


When to Add a Master Service

Geographical or organizational changes require additional master services to collect or distribute data.
Redundant data collection is required for optimal reconfiguration and limited downtime in the event of a service failure. Establish duplicate master services to collect redundant information for backup in the event of service failure.

Example Sample Master Service Implementation

When to Add a Satellite Service

User requests route through two or more servers residing on different LAN segments to reach an STDA service.
A server accesses the network over a transient link. If an STDA satellite service is added to the network segment where the connecting server is located, users can access the STDA database at any time, whether the link is up or down.
Users who connect to the network through a specific server want or need a customized version of the STDA database. Through the use of exclusions, exceptions, and inclusions used on that server's satellite service, a group of users may use a unique version of the STDA database.

Example STDA Satellite Service Implementation

Each of the three master services collects StreetTalk and inclusion data from StreetTalk services in different countries. Each master service has a backup service collecting duplicate data in the event of failure.
Three concentrator STDA satellite services download a complete view of the network from the three master services. This process ensures an additional layer of data redundancy.
Individual satellites download StreetTalk and inclusions with their attributes from the concentrator satellites.

Figure 10-2. STDA Master and Satellite Service Topology

Restricted Links and STDA

Figure 10-3. STDA Configurations over Restricted Links

Designating Download Servers

Collecting StreetTalk Data with Master Services

Collecting StreetTalk Data with Satellite Services

Scheduling Rebuilds

Figure 10-4. STDA Database Rebuild Order

Sorting Names

Creating Exclusions, Exceptions, and Inclusions

Exclude from master and satellite services all StreetTalk names except those you want to include. Use wildcards (for example, *@*) to exclude any names.
Include on master and satellite services all non-StreetTalk names that users need, such as addresses to mail gateway services.
Let your master service include all StreetTalk names. Define the exclusions on the satellite services. This lets administrators of the satellite services customize the database. The responsibility is removed from the master service.
If you have a common set of exclusions, define them on the master service. Defining the common set reduces the amount of data transferred across the network and eliminates the need to exclude the same names on the individual satellites.

Performance Considerations

Transient links
Network size
Server memory requirements

Transient Links and STDA

Network Size

Place the master STDA service on a server that is not heavily loaded. STDA should be one of the few services running, in addition to the Banyan network services.
In large networks, requests that are not targeted for specific STDA services may cause excessive network traffic. You may want to set specific switches to let users direct STDA requests to specific services, rather than broadcasting requests. However, these connections can only be done with client applications that are designed to respond to profile commands.

Memory Requirements

Previous PageTop Of PageNext Page