ReportServer - ReportServer Configuration Guide 4.7

4.6. Transport settings

As explained in the Administration Guide, in order to allow to use the transport mechanism, you have to configure ReportServer first. There are two relevant files to be configured:

main/mappings.cf. This file is described in Section 4.5. and works analogously for transports for mapping remote datasources to local datasources.
main/transports.cf. This file is described below.

This section explains the configuration options available in the main/transport.cf file, which is used for managing transports within ReportServer.

4.6.1. File Structure

The main/transport.cf file is an XML configuration file containing settings for importing and applying transports. Below is the breakdown of each element within the file:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
   <import>
      <remote>REMOTE_SERVER</remote>
      <target>/transports/import</target>
   </import>
   <apply>
      <!-- the username of the user that applies the transport. Must be a super user. -->
      <user>root</user>
   </apply>
</configuration>

4.6.2. Elements and Their Descriptions

The root element that encapsulates all configuration settings for the transport process.

This section contains settings related to the import of transports from a remote server.

<remote>	Defines the identifier for the remote server from which transports are imported. This should match the key configured for the remote server in ReportServer.
<target>	Specifies the directory path in the ReportServer's file system where the imported transports are stored in the local ReportServer after importing them from the remote server. If the path does not exist, it is created automatically by ReportServer during the import process.

<apply>

<user>

Specifies the username of the user who applies the transport. The user must have superuser privileges in ReportServer to perform this action.

4.6.3. Summary

The transport.cf file is used to configure the import of transports from a remote server and the application of those transports within ReportServer.
Ensure that the <remote> value correctly identifies the remote server, and that the <target> directory is properly set up with the correct permissions.
The <user> applying the transport must be a superuser to ensure successful integration into the target system.