ReportServer - ReportServer Configuration Guide 4.6.1

4.5. Remote RS Server Settings

ReportServer 4.6.0 introduced new ''Remote RS Server'' objects as explained in the Administration Guide. Also, new rpull terminal commands were introduced in order to pull/copy remote entities, e.g. reports from a remote RS installation into the local RS installation, e.g. from PROD to TEST.

In order to be able to import remote reports, their datasources must be able to be mapped to local datasources. This mapping is defined via the /etc/main/mappings.cf configuration file explained next.

The default /etc/main/mappings.cf configuration file is shown below:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
   <datasources>
      <priorities>
         <priority>mapping</priority>
         <priority>same-key</priority>
      </priorities>
      <key-mappings>
      <!--
         <key-mapping>
            <remote>REMOTE_KEY_1</remote>
            <local>LOCAL_KEY_1</local>
         </key-mapping>
         <key-mapping>
            <remote>REMOTE_KEY_2</remote>
            <local>LOCAL_KEY_2</local>
         </key-mapping>
      -->
      </key-mappings>
   </datasources> 
</configuration>

The datasource mapping is performed via datasource keys by the key-mapping elements.

For example, the following configuration maps the remote datasource with key MY_REMOTE_DATASOURCE to the local datasource with key MY_LOCAL_DATASOURCE.

<key-mapping>
   <remote>MY_REMOTE_DATASOURCE</remote>
   <local>MY_LOCAL_DATASOURCE</local>
</key-mapping>

The priorities element defines the mapping priorities. There are currently two types of mappings:

mapping: the explicit mapping defined by the key-mapping elements.
same-key: implicit mapping of datasources with the same key.

For example, in the following configuration, ReportServer tries first to map the datasources via the explicit key-mapping elements. If no mapping is found, it tries to find a local datasource with the same key.

<priorities>
	<priority>mapping</priority>
	<priority>same-key</priority>
</priorities>

On the contrary, in the following configuration, ReportServer tries first to find a local datasource with the same key. If no implicit key mapping could be found, it tries to map the datasources via the explicit key-mapping elements.

<priorities>
    <priority>same-key</priority>
	<priority>mapping</priority>
</priorities>