Difference between revisions of "Connection Parameter Web Extension"

(Created page with "The Connection-Parameter mapping XLCubed Web extension allows XLCubed report designers to build Web Parameters into their reports that control certain Managing Connectio...")
 
(Example 1: Simple mapping)
Line 25: Line 25:
  
 
The workbook would then use the connection details as published when loaded normally, but would connect to {{Code|AlternativeServer.example.org}} for its cube connections when loaded with a Web Parameter, for example:
 
The workbook would then use the connection details as published when loaded normally, but would connect to {{Code|AlternativeServer.example.org}} for its cube connections when loaded with a Web Parameter, for example:
     <nowiki>https://MyServer/XLCubedWeb/WebForm/ShowReport.aspx?rep=673dad1d-e406-4493-8ee3-6afdc9ec4f7f.wbsql&connection=mapB</nowiki>
+
     <nowiki>https://MyServer/XLCubedWeb/WebForm/ShowReport.aspx?rep=673dad1d-e406-4493-8ee3-6afdc9ec4f7f.wbsql&connection=mapped</nowiki>
  
 
=== Example 2: Multiple mappings ===
 
=== Example 2: Multiple mappings ===

Revision as of 10:14, 25 October 2018

The Connection-Parameter mapping XLCubed Web extension allows XLCubed report designers to build Web Parameters into their reports that control certain Connection details.

Installation

  • Place the ConnectionParameterExtension.dll file into the Extensions folder of your XLCubed Web installation, usually at C:\inetpub\wwwroot\XLCubedWeb\Extensions.
  • To ask XLCubed Web to load the extension, create the InstalledExtensions.dll file in the same folder, with contents:
   <?xml version="1.0" encoding="utf-8" ?>
   <installation>
     <extensions>
       <extension source="RelativeFile" location="ConnectionParameterExtension.dll" />
     </extensions>
   </installation>
  • Place the mapping.xml configuration file into the same folder (see below for details).
  • Restart IIS or the Application Pool.

Configuration

The mapping.xml file contains the details of which Web Parameters should activate a mapping, and which server, database and cube details to apply to connections in the workbook as a result. Any blank details are left unchanged.

Example 1: Simple mapping

The simplest example would notice when a workbook was loaded with a Web Parameter (here, connection) set to a value (here, mapped):

   <parameterMappings>
     <parameter name="connection">
       <mapping value="mapped" server="AlternativeServer.example.org" database="" cube="" />
     </parameter>
   </parameterMappings>

The workbook would then use the connection details as published when loaded normally, but would connect to AlternativeServer.example.org for its cube connections when loaded with a Web Parameter, for example:

   https://MyServer/XLCubedWeb/WebForm/ShowReport.aspx?rep=673dad1d-e406-4493-8ee3-6afdc9ec4f7f.wbsql&connection=mapped

Example 2: Multiple mappings

You can configure the mapping.xml file to respond to multiple Web Parameter values. In this example, the role parameter can be set to managers to connect to one cube, and users for another:

   <parameterMappings>
     <parameter name="role">
       <mapping value="managers" server="" database="ManagerDatabase" cube="FullCube" />
       <mapping value="users" server="" database="UserDatabase" cube="RestrictedCube" />
     </parameter>
   </parameterMappings>

See Also