Difference between revisions of "Connection Mapping"

(Added Web Edition category)
Line 3: Line 3:
 
To enable this feature, the {{Code|ConnectionMapping.xml}} file must be created in the {{Code|Xml}} subfolder of the XLCubed Web installation folder. This file can contain one or more {{Code|connectionmap}} nodes, each of which must contain a {{Code|from}} connection definition and a {{Code|to}} connection definition. After modifying this file, IIS must be restarted.
 
To enable this feature, the {{Code|ConnectionMapping.xml}} file must be created in the {{Code|Xml}} subfolder of the XLCubed Web installation folder. This file can contain one or more {{Code|connectionmap}} nodes, each of which must contain a {{Code|from}} connection definition and a {{Code|to}} connection definition. After modifying this file, IIS must be restarted.
  
When a user loads a Report to view, the Web Edition will automatically search for any connections matching a {{Code|from}} definition, and replace them with the corresponding {{Code|to}} definition. The ID number and name for the connection will be left unchanged.
+
When a user loads a Report to view, the Web Edition will automatically search for any connections matching a {{Code|from}} definition, and replace them with the corresponding {{Code|to}} definition.
 +
 
 +
The match is done using the Type, Server, Database and Cube of the from connection.
 +
 
 +
The ID number and name for the connection will be left unchanged.
  
 
==Example XML file==
 
==Example XML file==

Revision as of 10:26, 28 March 2013

XLCubed Web Edition supports the re-targeting of connections for reports published to the web server.

To enable this feature, the ConnectionMapping.xml file must be created in the Xml subfolder of the XLCubed Web installation folder. This file can contain one or more connectionmap nodes, each of which must contain a from connection definition and a to connection definition. After modifying this file, IIS must be restarted.

When a user loads a Report to view, the Web Edition will automatically search for any connections matching a from definition, and replace them with the corresponding to definition.

The match is done using the Type, Server, Database and Cube of the from connection.

The ID number and name for the connection will be left unchanged.

Example XML file

This example matches connections to the DEVELOPMENT server and replaces them with connections to the PRODUCTION server.

<?xml version="1.0" encoding="utf-8"?>
<connectionmapper>
  <connectionmap>
    <from>
      <connection id="0" name="">
        <type>AnalysisServices</type>
        <variable type="String" name="server"><value>DEVELOPMENT</value></variable>
        <variable type="String" name="database"><value>Demo Database</value></variable>
        <variable type="String" name="cube"><value>Demo Cube</value></variable>
        <writebacktype>AnalysisServices</writebacktype>
        <writebacksetting />
        <nodummyrelationalwriteback>0</nodummyrelationalwriteback>
        <variable type="Boolean" name="requirespassword"><value>0</value></variable>
        <lastconnected>0001-01-01T00:00:00</lastconnected>
        <props />
      </connection>
    </from>
    <to>
      <connection id="0" name="">
        <type>AnalysisServices</type>
        <variable type="String" name="server"><value>PRODUCTION</value></variable>
        <variable type="String" name="database"><value>Demo Database</value></variable>
        <variable type="String" name="cube"><value>Demo Cube</value></variable>
        <writebacktype>AnalysisServices</writebacktype>
        <writebacksetting />
        <nodummyrelationalwriteback>0</nodummyrelationalwriteback>
        <variable type="Boolean" name="requirespassword"><value>0</value></variable>
        <lastconnected>0001-01-01T00:00:00</lastconnected>
        <props />
      </connection>
    </to>
  </connectionmap>
</connectionmapper>