Network locations are a basic building block of a single-repository distributed environment for web-based clients. Network locations identify locations on a network, and, optionally, a range of IP addresses, from which users connect to Documentum web clients. For example, a Documentum installation could include network locations called San Francisco, New York, London, Athens, Tokyo, and Sydney, corresponding to users in those cities. A network location can also identify specific offices, network subnets, or even routers.

Network locations are associated with server configuration objects and acs configuration objects. The server configuration objects and acs configuration objects contain information defining the proximity of a Content Server or ACS Server to the network location. Content Server uses the information in the server configuration objects and acs configuration objects and their associated network locations to determine the correct content storage area from which to serve content to a web client end user and to determine the correct server to serve the content.

Creating network locations requires superuser privileges. Network locations can be created only in a repository designated as a global registry, and the name of each location must be unique among the set of network locations in the global registry. Network locations should be created in the global registry repository that is defined when DFC is installed on the Documentum Administrator host. If a network contains multiple global registry repositories, a particular Documentum Administrator instance only recognizes the global registry that was designated during DFC installation on the Documentum Administrator host. You can connect to a global registry repository without being able to create network locations in that global registry.

Use the Administration > Distributed Content Configuration > Network Locations navigation to access the Network Locations list page. From the Network Locations list page, you can create, copy, view, modify, and delete network locations.

For more information about network locations, refer to the Distributed Configuration Guide.