4 Configuring Multiple Location Support

The Multiple Location Support allows configuring a remote site as a DFM site, but uses a central AutoVue installation, or a local AutoVue installation to view replicated files.

Note: For each site that uses an AutoVue server, an Offline Metafile Cache Service is required to be able to replicate files.

4.1 Define Configuration Parameter

Note: For each site, a set of EDB-PVM configuration parameters need to be defined. The complete list of AutoVue configuration parameters can be found in the Online Help > Configuration Parameters.

The following graphic shows the usage of the AutoVue Configuration Parameter:

4.2 Central AutoVue - No DFM

The Central AutoVue integration supports a site specific configuration that uses the environment variable EP_PVM_SITE to choose the configuration of the client location. The stored procedure does not check if the files are available, because DFM is not active.

Note: For detailed information on how to configure the environment variable EP_PVM_SITE for remote sites, refer to the Administration Manual for Agile e6.2.1.0 > Java Client Remote Site Definition. For the Central site, all AutoVue configuration parameters have to be defined. When no File Server is used, the configuration parameter EDB-PVM-AV-DFM-SITE has to remain empty. For the Central site, the configuration parameter EDB-PVM-AV-SITE REF has to remain empty.

Example scenario of network topology:

In this example, the Central site is defined as "de" in Agile e6 and no DFM site is defined.

4.3 Central AutoVue - With DFM

The central Agile e6 AutoVue Integration supports the configuration of a remote location as a DFM location to replicate e.g. CAD files and is using a central AutoVue installation (see example Site A in the graphic below) to view files/assemblies with the Agile e6 AutoVue Integration. The AutoVue server uses the central file server to view the file. If a user changes a file on the remote site, it has to be replicated to the central site to be able to view it with AutoVue. The DFM configuration of the AutoVue server is configured through the AutoVue configuration parameter EDB-PVM-AV-DFM-SITE.

Note: When a File Server is used, the configuration parameter EDB-PVM-AV-DFM-SITE has to be defined.

Example scenario of network topology:

In this example, the Central site is defined as "de" in Agile e6. Although, the DFM site definition can differ from the AutoVue site.

4.4 Decentral AutoVue - With DFM

The decentral Agile e6 AutoVue Integration supports the configuration of a remote location as a DFM location to replicate e.g. CAD files and is using a local AutoVue server installation (see example Site B in the graphic below).

Example scenario of network topology:

In this example, the Decentral site is defined as "cn" in Agile e6. The site reference is defined to point to the Central site.

Note: If any configuration parameter is not defined for the Decentral site, the respective configuration parameter of the Central site will be used. If this configuration parameter is also not defined for the Central site, an error message will be displayed.

The following table explains the components that are installed at the different sites:

Installation	Installed Components
Central	- EDM Workstation to work with Agile EDM - Application Server with WebLogic and the database, and the EDM server - AutoVue server with the integration backbone (VueLink DMS) - File Server to store file based data, e.g. CAD files
Site A	- EDM Workstation to work with Agile EDM - File Server to store file based data, e.g. CAD files
Site B	- EDM Workstation to work with Agile EDM - AutoVue server with the integration backbone (VueLink DMS) - File Server to store file based data like CAD files