XLCubed is now FluenceXL. The new wiki can be found here: https://help.fluencexl.com/

Difference between revisions of "XLCubed Web Edition Installation Guide/Version 6.1"

(→‎Analysis Services Security Setup and Options)
(→‎External Links)
 
(46 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
= Overview =
+
== Overview ==
  
 
To install XLCubed Web:  
 
To install XLCubed Web:  
Line 8: Line 8:
 
* Please note version 6 will not upgrade existing version 5 installations: it will install as a separate product
 
* Please note version 6 will not upgrade existing version 5 installations: it will install as a separate product
  
−
= Installation Prerequisites =
+
== Installation Pre-requisites ==
  
 
Server Requirements:  
 
Server Requirements:  
Line 22: Line 22:
 
The installation will automatically download and install any required Microsoft redistributables. If desired or if Internet access is restricted, these can be downloaded and installed manually before running the XLCubed setup process. A list is available [[XLCubed_Web_Edition_Prerequisites/Version_6.1|here]].
 
The installation will automatically download and install any required Microsoft redistributables. If desired or if Internet access is restricted, these can be downloaded and installed manually before running the XLCubed setup process. A list is available [[XLCubed_Web_Edition_Prerequisites/Version_6.1|here]].
  
−
= Analysis Services Security Setup and Options =
+
== Setting up the XLCubed Web Edition application manually ==
  
−
== Cube-based security options ==
+
This step is usually not required, as the setup program will create the web application for you. It may be necessary if:
 +
* During the setup process, the {{Code|Add XLCubed Web Edition to IIS}} checkbox was unselected
 +
* Your web server is set up in a non-standard configuration, especially where the Default Web Site has been modified
 +
* You wish to create the web application yourself for whatever reason
 +
 
 +
Note that in the non-standard configuration, you may receive the following error message from the setup program: {{Code|Failed while processing WebVirtualDirs. (-2147024894)}}
 +
 
 +
In any of these cases, the setup program will have copied the application files to the web server, but you will have to create the site yourself. To do this:
 +
# Open Internet Information Services Manager ({{Code|inetmgr.exe}})
 +
# Under the {{Code|Application Pools}} node, ensure that the XLCubed application pool has been set up. It must be configured to use v4.0 of the .NET Framework and use the Classic pipeline mode.
 +
# Under the {{Code|Sites}} node, open the website in which XLCubed Web Edition should be made available (usually the Default Web Site).
 +
# Usually the {{Code|XLCubedWeb}} Virtual Directory will already exist within the website. If this is the case, then right-click on it and select {{Code|Convert to Application}}. If not, right-click on the website instead and select {{Code|Add Application...}}
 +
# In the {{Code|Add Application}} dialog, ensure that the {{Code|XLCubed}} application pool is selected and, if necessary, choose the correct path.
 +
 
 +
This will set up the application's web site. Further security setup and other configuration will likely be necessary. Information can be found below.
 +
 
 +
== Analysis Services Security Setup and Options ==
 +
 
 +
=== Cube-based security options ===
 
=== XLCubed Web Edition and Analysis Services on same server ===
 
=== XLCubed Web Edition and Analysis Services on same server ===
  
 
Either basic authentication or integrated security may be enforced by IIS.  
 
Either basic authentication or integrated security may be enforced by IIS.  
−
== Windows Authentication ==
+
==== Windows Authentication ====
  
−
=== IIS Settings ===
+
===== IIS Settings =====
  
 
Depending on your IIS version, take the following steps:
 
Depending on your IIS version, take the following steps:
  
−
==== IIS 5 ====
+
====== IIS 5/6 ======
  
 
Right click the XLCubedWeb directory and select "Properties"
 
Right click the XLCubedWeb directory and select "Properties"
Line 42: Line 60:
 
[[File:XLCubedWebConfigIIS5AuthenticationWindows.png|200px|center]]
 
[[File:XLCubedWebConfigIIS5AuthenticationWindows.png|200px|center]]
  
−
==== IIS 6 ====
+
====== IIS 7/7.5 ======
  
 
Select the XLCubedWeb directory and open the "Authentication" section.
 
Select the XLCubedWeb directory and open the "Authentication" section.
Line 55: Line 73:
 
Control Panel -> Programs -> Turn Windows features on or off
 
Control Panel -> Programs -> Turn Windows features on or off
  
 +
===== Web.config =====
 +
You will need to change the web.config file to include entries for all bindings.
 +
These entries are dependent on the authentication mode (Basic, Windows or Anonymous) and whether or not you are using HTTPS.
 +
 +
Please note that when using HTTPS the security mode should be equal to Transport.
  
−
=== web.config Settings ===
+
{| class="wikitable"
 +
! scope="col" width="100" | Authentication
 +
! scope="col" width="100" | Using HTTPS
 +
! scope="col" width="700" | web.config: on all bindings
 +
|-
 +
|Windows
 +
|Yes
 +
|<security mode="Transport"> <transport clientCredentialType="Windows"/> </security>
  
−
In the bindings section the security should be as follows for ''all'' bindings.
+
|-
 +
|Windows
 +
|No
 +
|<security mode="TransportCredentialOnly"> <transport clientCredentialType="Windows"/> </security>
  
−
    <security mode="TransportCredentialOnly">
+
|}
−
        <transport clientCredentialType="Windows"/>
 
−
    </security>
 
  
−
== Basic Authentication ==
+
=====Multiple IIS sites=====
  
−
=== IIS Settings ===
+
If you are using multiple sites in IIS you need to add the following to web.config in section <serviceHostingEnvironment>
 +
 
 +
multipleSiteBindingsEnabled="true"
 +
 
 +
==== Basic Authentication ====
 +
 
 +
===== IIS Settings =====
  
 
Depending on your IIS version, take the following steps:
 
Depending on your IIS version, take the following steps:
  
−
==== IIS 5 ====
+
====== IIS 5/6 ======
  
 
Right click the XLCubedWeb directory and select "Properties"
 
Right click the XLCubedWeb directory and select "Properties"
Line 78: Line 115:
 
[[File:XLCubedWebConfigIIS5AuthenticationBasic.png|200px|center]]
 
[[File:XLCubedWebConfigIIS5AuthenticationBasic.png|200px|center]]
  
−
==== IIS 6 ====
+
====== IIS 7/7.5 ======
  
 
Select the XLCubedWeb directory and open the "Authentication" section.
 
Select the XLCubedWeb directory and open the "Authentication" section.
Line 88: Line 125:
 
[[File:XLCubedWebConfigIIS6AuthenticationBasic.png|200px|center]]
 
[[File:XLCubedWebConfigIIS6AuthenticationBasic.png|200px|center]]
  
−
=== web.config Settings ===
+
===== Web.config =====
 +
You will need to change the web.config file to include entries for all bindings.
 +
These entries are dependent on the authentication mode (Basic, Windows or Anonymous) and whether or not you are using HTTPS.
  
−
In the bindings section the security should be as follows for ''all'' bindings.
+
Please note that when using HTTPS the security mode should be equal to Transport.
  
−
    <security mode="TransportCredentialOnly">
+
{| class="wikitable"
−
        <transport clientCredentialType="Basic"/>
+
! scope="col" width="100" | Authentication
−
    </security>
+
! scope="col" width="100" | Using HTTPS?
 +
! scope="col" width="700" | web.config – on all bindings
 +
|-
 +
|Basic
 +
|Yes
 +
|<security mode="Transport"> <transport clientCredentialType="Basic"/> </security>
  
−
== Anonymous Authentication ==
+
|-
 +
|Basic
 +
|No
 +
|<security mode="TransportCredentialOnly"> <transport clientCredentialType="Basic"/> </security>
  
−
=== IIS Settings ===
+
|}
 +
 
 +
=====Multiple IIS sites=====
 +
 
 +
If you are using multiple sites in IIS you need to add the following to web.config in section <serviceHostingEnvironment>
 +
 
 +
multipleSiteBindingsEnabled="true"
 +
 
 +
==== Anonymous Authentication ====
 +
 
 +
===== IIS Settings =====
  
 
Depending on your IIS version, take the following steps:
 
Depending on your IIS version, take the following steps:
  
−
==== IIS 5 ====
+
====== IIS 5/6 ======
  
 
Right click the XLCubedWeb directory and select "Properties"
 
Right click the XLCubedWeb directory and select "Properties"
Line 110: Line 167:
 
[[File:XLCubedWebConfigIIS5AuthenticationAnon.png|200px|center]]
 
[[File:XLCubedWebConfigIIS5AuthenticationAnon.png|200px|center]]
  
−
==== IIS 6 ====
+
====== IIS 7/7.5 ======
  
 
Select the XLCubedWeb directory and open the "Authentication" section.
 
Select the XLCubedWeb directory and open the "Authentication" section.
Line 123: Line 180:
 
Control Panel -> Programs -> Turn Windows features on or off
 
Control Panel -> Programs -> Turn Windows features on or off
  
−
=== web.config Settings ===
+
===== Web.config =====
 +
You will need to change the web.config file to include entries for all bindings.
 +
These entries are dependent on the authentication mode (Basic, Windows or Anonymous) and whether or not you are using HTTPS.
  
−
In the bindings section the security should be as follows for ''all'' bindings.
+
Please note that when using HTTPS the security mode should be equal to Transport.
  
−
    <security mode="TransportCredentialOnly">
+
{| class="wikitable"
−
        <transport clientCredentialType="None"/>
+
! scope="col" width="100" | Authentication
−
    </security>
+
! scope="col" width="100" | Using HTTPS
 +
! scope="col" width="700" | web.config: on all bindings
 +
|-
 +
|Anonymous
 +
|Yes
 +
|<security mode="Transport"> <transport clientCredentialType="None"/> </security>
  
 +
|-
 +
|Anonymous
 +
|No
 +
|<security mode="TransportCredentialOnly"> <transport clientCredentialType="None"/> </security>
  
−
==== Basic authentication ====
+
|}
−
 
 
−
An authentication dialog will prompt the user on their initial connection to the cube through the web application. This can be set up through http or https. To enable basic authentication, a change is also required in the web.config file: In the {{Code|<system.serviceModel>}} section, under {{Code|<bindings>}} change it to:
 
  
−
<transport clientCredentialType="Basic" />
+
=====Multiple IIS sites=====
  
−
==== Integrated security ====
+
If you are using multiple sites in IIS you need to add the following to web.config in section <serviceHostingEnvironment>
  
−
The user's windows network credentials are passed through in a trusted connection.
+
multipleSiteBindingsEnabled="true"
  
 
=== XLCubed Web Edition and Analysis Services on separate servers ===
 
=== XLCubed Web Edition and Analysis Services on separate servers ===
Line 148: Line 214:
 
==== Basic authentication ====
 
==== Basic authentication ====
  
−
An authentication dialog will prompt the user on their initial connection to the cube through the web application, as [[#XLCubed Web Edition and Analysis Services on same server|above]]. This can be set up through http or https. To enable basic authentication, a change is also required in the web.config file: In the {{Code|<system.serviceModel>}} section, under {{Code|<bindings>}} change it to:
+
Make same changes as for XLCubed Web Edition and Analysis Services are on same server.
−
 
 
−
<transport clientCredentialType="Basic" />
 
−
 
 
−
Note: both occurrences must be changed.  
 
  
 
==== Integrated Security ====
 
==== Integrated Security ====
  
−
To enable integrated security in this situation, the network must be set up to support the [http://technet.microsoft.com/en-us/library/bb742516.aspx Kerberos authentication protocol] to enable the security credentials to be passed on from the web server (where they were received from the originating client) to the OLAP server. This is due to a limitation in the NTLM (LanManager) protocol which does not support the delegation of security credentials further than one-hop.  
+
Make same changes as for XLCubed Web Edition and Analysis Services are on same server.
  
−
== No requirement for cube-based security ==
+
In addition to enable integrated security in this situation, the network must be set up to support the [http://support.microsoft.com/kb/917409 Kerberos authentication protocol] to enable the security credentials to be passed on from the web server (where they were received from the originating client) to the OLAP server. This is due to a limitation in the NTLM (LanManager) protocol which does not support the delegation of security credentials further than one-hop.
  
−
Where cube-based security is not implemented at a user or user group level, the simplest model is to ensure that the IIS account that the web application is running under has the required access to the cube. In this case it is effectively the web application that is accessing the cube, not the end-user who originated the request. To enable anonymous authentication, a change is also required in the web.config file, as below: In the {{Code|<system.serviceModel>}} section, under {{Code|<bindings>}} change it to:
+
==== Anonymous authentication ====
  
−
<transport clientCredentialType="none" />
+
Make same changes as for XLCubed Web Edition and Analysis Services are on same server.
  
−
= XLCubed Web Security =
+
== XLCubed Web Security ==
  
 
During the installation XLCubedWeb sets up Read/Write permissions on the following folders.  
 
During the installation XLCubedWeb sets up Read/Write permissions on the following folders.  
 
* {{Code|XLCubedWeb\Repository}} (handles repository and publish / preview)  
 
* {{Code|XLCubedWeb\Repository}} (handles repository and publish / preview)  
−
* {{Code|XLCubedWeb\Temp}} (handles save to excel)  
+
* {{Code|XLCubedWeb\Temp}} (handles save to excel and save to repository)  
  
−
== Functional User Permissions ==
+
=== Functional User Permissions ===
  
 
Access to the application, and the type of access is controlled by two files located in:  
 
Access to the application, and the type of access is controlled by two files located in:  
Line 181: Line 243:
 
  adhoc.xml
 
  adhoc.xml
  
−
== Repository Management and Security – User Folders ==
+
=== Repository Management and Security – User Folders ===
  
 
The repository, visible in the left hand pane of the web application, is simply a folder on the Web Server within which additional subfolders can be added. All published reports are held within the repository folder, or subfolders within it. The folder location will by default be:  
 
The repository, visible in the left hand pane of the web application, is simply a folder on the Web Server within which additional subfolders can be added. All published reports are held within the repository folder, or subfolders within it. The folder location will by default be:  
Line 193: Line 255:
 
  C:\Inetpub\wwwroot\XLCubedWeb\Repository\__userfolders__
 
  C:\Inetpub\wwwroot\XLCubedWeb\Repository\__userfolders__
  
−
== Published Connections ==
+
=== Published Connections ===
  
 
When a user publishes a connection to XLCubed Web, which may contain custom calculations, etc, they are published to:  
 
When a user publishes a connection to XLCubed Web, which may contain custom calculations, etc, they are published to:  
Line 203: Line 265:
 
  C:\inetpub\wwwroot\XLCubedWebv6\Repository\__xlcubed__\__grids__\Published Favourites
 
  C:\inetpub\wwwroot\XLCubedWebv6\Repository\__xlcubed__\__grids__\Published Favourites
  
−
= Accessing XLCubed Web reports from SharePoint and other portals =
+
== Accessing XLCubed Web reports from SharePoint and other portals ==
  
 
XLCubed Web reports can be accessed either through the Web Edition homepage, or accessed directly by URL within other portals.  
 
XLCubed Web reports can be accessed either through the Web Edition homepage, or accessed directly by URL within other portals.  
Line 231: Line 293:
 
  http&#58;//localhost/XLCubedWeb/WebForm/ShowReport.aspx?rep=XLCubed/Management Book.xml&dpi=96&Toolbar=True
 
  http&#58;//localhost/XLCubedWeb/WebForm/ShowReport.aspx?rep=XLCubed/Management Book.xml&dpi=96&Toolbar=True
  
−
= System Configuration Settings =
+
== System Configuration Settings ==
−
== Behavioural Configuration ==
+
=== Behavioural Configuration ===
  
 
The web.config file held within the XLCubedWeb folder determines various behavioural aspects of the product. The following settings are held within the {{Code|<appSettings>}} section.
 
The web.config file held within the XLCubedWeb folder determines various behavioural aspects of the product. The following settings are held within the {{Code|<appSettings>}} section.
Line 253: Line 315:
 
|{{Code|DrillthroughAbsoluteMaxRows}}||maximum permitted rows on a drillthrough
 
|{{Code|DrillthroughAbsoluteMaxRows}}||maximum permitted rows on a drillthrough
 
|-
 
|-
−
|{{Code|RepositioryRootUNC}}||UNC path to a share containing the repository so that users can edit it. For example, {{Code|\\XL3WebServer\Repository}}
+
|{{Code|RepositioryRootUNC}}||No longer supported - listed for compatibility reasons. To create a shared repository, use MKLink [http://en.wikipedia.org/wiki/NTFS_symbolic_link] to replace the folder with a Symbolic Link to a network share.
 
|-
 
|-
 
|{{Code|ClearLevelsMovedToFilters}}||Where an entire level is selected on an axis (potentially a large number of members), and is dragged onto the slicer, the selection is changed to the default member (Typically 'All'). This is to prevent users accidentally creating a very slow running query by individually aggregating all the members dragged to the slicer
 
|{{Code|ClearLevelsMovedToFilters}}||Where an entire level is selected on an axis (potentially a large number of members), and is dragged onto the slicer, the selection is changed to the default member (Typically 'All'). This is to prevent users accidentally creating a very slow running query by individually aggregating all the members dragged to the slicer
Line 270: Line 332:
 
{{TableFooter}}
 
{{TableFooter}}
  
−
== PDF Printing - Configuration ==
+
=== PDF Printing Configuration ===
 +
 
 +
For PDF printing you need to:
  
−
XLCubed Web incorporates PDF printing. To enable this, a user id and password must be specified in the web.config file located in the website folder. The settings which need to be edited are:  
+
1. Edit '''web.config''' and change '''PDFRenderer''' value to '''SpreadsheetGear:'''
−
<add key="PdfConverterUserName" value="servername\username"/>
 
−
<add key="PdfConverterPassword" value="password"/>
 
  
−
Note the user name should contain the machine name also. The specified user only requires read access to the XLCubed Web website itself. It is suggested that a specific local id is set up on the server, with low level access specifically for this purpose.
+
'''<add key="PdfRenderer" value="SpreadsheetGear"/>'''
  
−
The print process also requires end user read access to the temporary internet files folder on the web server. This is needed because CSS files needed to render the PDF are stored here. To enable that:
+
2. In a 64-bit environment you will also need to change an application pool setting in IIS.  
−
* Open {{Code|C:\Windows\Temp}}
 
−
* There should be a folder called {{Code|Temporary Internet Files}}. If not, open the {{Menu|Tools|Folder options|View options}} dialog, and unselect the {{Menu|Hide protected operating system files}} option
 
−
* Right click the {{Code|Temporary Internet Files}} folder and give the end users read access to it
 
  
−
The PDF print process uses a server-based process to re-open the HTML from the current webpage, so doesn't re-query the cube. This requires that the Web server can access the website using the identical URL to an end user. Where the web site uses integrated Authentication and has a name that is mapped to the local loopback address, you can receive a 401.1 error on trying to print.  Microsoft has released an article, which outlines how to resolve this: [http://support.microsoft.com/kb/896861 Microsoft Knowledge Base article 896861].
+
[[Image:PDF1.png|350px|centre]]
 +
 +
Select View Application Pools and select the XLCubed application pool.
  
−
= Server specification =
+
[[Image:PDF2.png|350px|centre]]
  
−
Recommended specification is dependant on the cube size and design, the number of users, and the pattern of usage. Having Analysis Services on the same machine will also have an impact.  
+
Select Advanced Settings and set '''Enable 32-bit Applications''' to '''False'''
 +
 
 +
[[Image:PDF3.png|350px|centre]]
 +
 
 +
== Server specification ==
 +
 
 +
Recommended specification is dependent on the cube size and design, the number of users, and the pattern of usage. Having Analysis Services on the same machine will also have an impact.  
  
 
As an absolute minimum we recommend:  
 
As an absolute minimum we recommend:  
 
* Memory: 2GB  
 
* Memory: 2GB  
−
* Processor: Dual Core 2.2 GHz  
+
* Processor: Dual Core 2.2 GHz
  
−
= Application Usage =
+
== Application Usage ==
 
* Please refer to the help menu within the product for an overview of all functionality.  
 
* Please refer to the help menu within the product for an overview of all functionality.  
  
−
= See Also =
+
== See Also ==
 
* [[XLCubed Web Edition Prerequisites/Version 6.1|XLCubed Web Edition Prerequisites]]
 
* [[XLCubed Web Edition Prerequisites/Version 6.1|XLCubed Web Edition Prerequisites]]
  
−
= External Links =
+
== External Links ==
 
* [http://technet.microsoft.com/en-us/library/bb742516.aspx Kerberos Explained]
 
* [http://technet.microsoft.com/en-us/library/bb742516.aspx Kerberos Explained]
 
* [http://support.microsoft.com/kb/896861 Resolving a 401.1 error when PDF printing]
 
* [http://support.microsoft.com/kb/896861 Resolving a 401.1 error when PDF printing]
 +
 +
[[Category:Installation]]
 +
[[Category:Web Edition]]

Latest revision as of 11:05, 17 June 2015

Overview

To install XLCubed Web:

  • Run the setup program while logged onto the server as a user with administrator permissions
  • Once installed, copy the provided license key (xl3web.license) into the website folder, which is by default: C:\Inetpub\wwwroot\XLCubedWeb
  • When installed, the application is accessed by navigating to http://<yourservername>/XLCubedWeb
  • XLCubedWeb is the default website name during installation, but can be changed as required during the installation process
  • Please note version 6 will not upgrade existing version 5 installations: it will install as a separate product

Installation Pre-requisites

Server Requirements:

  • Windows 2000 Server or above
  • Internet Information Services (IIS) 5.1 or above
  • Microsoft .NET Framework version 4.0

Client Requirements:

  • Internet Explorer 7.0 or above
  • Google Chrome 5.0 or above
  • Mozilla Firefox 3.6 or above

The installation will automatically download and install any required Microsoft redistributables. If desired or if Internet access is restricted, these can be downloaded and installed manually before running the XLCubed setup process. A list is available here.

Setting up the XLCubed Web Edition application manually

This step is usually not required, as the setup program will create the web application for you. It may be necessary if:

  • During the setup process, the Add XLCubed Web Edition to IIS checkbox was unselected
  • Your web server is set up in a non-standard configuration, especially where the Default Web Site has been modified
  • You wish to create the web application yourself for whatever reason

Note that in the non-standard configuration, you may receive the following error message from the setup program: Failed while processing WebVirtualDirs. (-2147024894)

In any of these cases, the setup program will have copied the application files to the web server, but you will have to create the site yourself. To do this:

  1. Open Internet Information Services Manager (inetmgr.exe)
  2. Under the Application Pools node, ensure that the XLCubed application pool has been set up. It must be configured to use v4.0 of the .NET Framework and use the Classic pipeline mode.
  3. Under the Sites node, open the website in which XLCubed Web Edition should be made available (usually the Default Web Site).
  4. Usually the XLCubedWeb Virtual Directory will already exist within the website. If this is the case, then right-click on it and select Convert to Application. If not, right-click on the website instead and select Add Application...
  5. In the Add Application dialog, ensure that the XLCubed application pool is selected and, if necessary, choose the correct path.

This will set up the application's web site. Further security setup and other configuration will likely be necessary. Information can be found below.

Analysis Services Security Setup and Options

Cube-based security options

XLCubed Web Edition and Analysis Services on same server

Either basic authentication or integrated security may be enforced by IIS.

Windows Authentication

IIS Settings

Depending on your IIS version, take the following steps:

IIS 5/6

Right click the XLCubedWeb directory and select "Properties" Select the "Directory Security" tab Ensure that "Integrated Windows authentication" is checked and all others are not.

XLCubedWebConfigIIS5AuthenticationWindows.png
IIS 7/7.5

Select the XLCubedWeb directory and open the "Authentication" section.

XLCubedWebConfigIIS6Authentication.png

Ensure "ASP.NET Impersonation" and "Windows Authentication" are enabled, and others are disabled.

XLCubedWebConfigIIS6AuthenticationWindows.png

If you do not have these options you must add them from Control Panel -> Programs -> Turn Windows features on or off

Web.config

You will need to change the web.config file to include entries for all bindings. These entries are dependent on the authentication mode (Basic, Windows or Anonymous) and whether or not you are using HTTPS.

Please note that when using HTTPS the security mode should be equal to Transport.

Authentication Using HTTPS web.config: on all bindings
Windows Yes <security mode="Transport"> <transport clientCredentialType="Windows"/> </security>
Windows No <security mode="TransportCredentialOnly"> <transport clientCredentialType="Windows"/> </security>
Multiple IIS sites

If you are using multiple sites in IIS you need to add the following to web.config in section <serviceHostingEnvironment>

multipleSiteBindingsEnabled="true"

Basic Authentication

IIS Settings

Depending on your IIS version, take the following steps:

IIS 5/6

Right click the XLCubedWeb directory and select "Properties" Select the "Directory Security" tab Ensure that "Basic authentication" is checked and all others are not.

XLCubedWebConfigIIS5AuthenticationBasic.png
IIS 7/7.5

Select the XLCubedWeb directory and open the "Authentication" section.

XLCubedWebConfigIIS6Authentication.png

Ensure "ASP.NET Impersonation" and "Basic Authentication" are enabled, and others are disabled.

XLCubedWebConfigIIS6AuthenticationBasic.png
Web.config

You will need to change the web.config file to include entries for all bindings. These entries are dependent on the authentication mode (Basic, Windows or Anonymous) and whether or not you are using HTTPS.

Please note that when using HTTPS the security mode should be equal to Transport.

Authentication Using HTTPS? web.config – on all bindings
Basic Yes <security mode="Transport"> <transport clientCredentialType="Basic"/> </security>
Basic No <security mode="TransportCredentialOnly"> <transport clientCredentialType="Basic"/> </security>
Multiple IIS sites

If you are using multiple sites in IIS you need to add the following to web.config in section <serviceHostingEnvironment>

multipleSiteBindingsEnabled="true"

Anonymous Authentication

IIS Settings

Depending on your IIS version, take the following steps:

IIS 5/6

Right click the XLCubedWeb directory and select "Properties" Select the "Directory Security" tab Ensure that "Enable anonymous access" is checked and all others are not.

XLCubedWebConfigIIS5AuthenticationAnon.png
IIS 7/7.5

Select the XLCubedWeb directory and open the "Authentication" section.

XLCubedWebConfigIIS6Authentication.png

Ensure "ASP.NET Impersonation" and "Anonymous Authentication" are enabled, and others are disabled.

XLCubedWebConfigIIS6AuthenticationAnon.png

If you do not have these options you must add them from Control Panel -> Programs -> Turn Windows features on or off

Web.config

You will need to change the web.config file to include entries for all bindings. These entries are dependent on the authentication mode (Basic, Windows or Anonymous) and whether or not you are using HTTPS.

Please note that when using HTTPS the security mode should be equal to Transport.

Authentication Using HTTPS web.config: on all bindings
Anonymous Yes <security mode="Transport"> <transport clientCredentialType="None"/> </security>
Anonymous No <security mode="TransportCredentialOnly"> <transport clientCredentialType="None"/> </security>
Multiple IIS sites

If you are using multiple sites in IIS you need to add the following to web.config in section <serviceHostingEnvironment>

multipleSiteBindingsEnabled="true"

XLCubed Web Edition and Analysis Services on separate servers

Either basic authentication or integrated security may be enforced by IIS.

Basic authentication

Make same changes as for XLCubed Web Edition and Analysis Services are on same server.

Integrated Security

Make same changes as for XLCubed Web Edition and Analysis Services are on same server.

In addition to enable integrated security in this situation, the network must be set up to support the Kerberos authentication protocol to enable the security credentials to be passed on from the web server (where they were received from the originating client) to the OLAP server. This is due to a limitation in the NTLM (LanManager) protocol which does not support the delegation of security credentials further than one-hop.

Anonymous authentication

Make same changes as for XLCubed Web Edition and Analysis Services are on same server.

XLCubed Web Security

During the installation XLCubedWeb sets up Read/Write permissions on the following folders.

  • XLCubedWeb\Repository (handles repository and publish / preview)
  • XLCubedWeb\Temp (handles save to excel and save to repository)

Functional User Permissions

Access to the application, and the type of access is controlled by two files located in: 

C:\Inetpub\wwwroot\XLCubedWeb\Xml\Security

To enable or disable user or group access to the Web Edition, enable or disable read access for the relevant user or group to: 

system.xml

'Ad hoc' access gives users the ability to build their own report from scratch. This access is controlled via the adhoc.xml file. To restrict users to be able to view only pre-published reports, revoke access to: 

adhoc.xml

Repository Management and Security – User Folders

The repository, visible in the left hand pane of the web application, is simply a folder on the Web Server within which additional subfolders can be added. All published reports are held within the repository folder, or subfolders within it. The folder location will by default be: 

C:\Inetpub\wwwroot\XLCubedWeb\Repository

Additional folders can be added as required, at the level immediately beneath the Repository folder itself, for example one folder per user group. These are added on the server itself, thus lending itself to maintenance of the structure by the IT function, or a designated user(s).

Windows permissions determine which folders are visible within the web application to any given user, e.g. can be configured such that the 'Sales' function cannot see the 'Finance' function folder and vice versa. This is all handled transparently by the application, and set at the Windows folder level permissions level. The same logic is true of read/write vs. a read-only split between user groups.

Note that every user has a 'My Reports' folder, which is the equivalent of 'My Documents' in Windows, and is only accessible by the individual user. These are held in the location below: 

C:\Inetpub\wwwroot\XLCubedWeb\Repository\__userfolders__

Published Connections

When a user publishes a connection to XLCubed Web, which may contain custom calculations, etc, they are published to: 

C:\Inetpub\wwwroot\XLCubedWebv6\Repository\__xlcubed__\__connections__\Published Connections

or to subfolders which have been created within this.

Published Favourites When a user published a report favourite to the web, they are published to: 

C:\inetpub\wwwroot\XLCubedWebv6\Repository\__xlcubed__\__grids__\Published Favourites

Accessing XLCubed Web reports from SharePoint and other portals

XLCubed Web reports can be accessed either through the Web Edition homepage, or accessed directly by URL within other portals.

To get the URL for a specific report, in the homepage of XLCubed Web:

  • Click on the View parameters icon:
    GetUrl1.png
  • Then press the Get Url button:
    GetUrl2.png

The provided URL can be used to embed the report within other portals and frames as required. In the case of SharePoint, the URL is used within a sitelink web part.

Additional configuration options accessible as suffixes on the URL are:

HorizontalScrollbar true/false
VerticalScrollbar true/false
SheetTabs true/false
Toolbar true/false
DefaultTargetFrame text

For example, for the report above, to include the toolbar in the rendered version, the URL would become: 

http://localhost/XLCubedWeb/WebForm/ShowReport.aspx?rep=XLCubed/Management Book.xml&dpi=96&Toolbar=True

System Configuration Settings

Behavioural Configuration

The web.config file held within the XLCubedWeb folder determines various behavioural aspects of the product. The following settings are held within the <appSettings> section.

LogErrors write errors to Error.log file
LogPerformance for debug only
ShowErrorMessages show detailed error messages or just a reference to the log file
DefaultChartSeries default number of series to chart on an ad-hoc report
MaxChartSeries maximum number of series to chart on an ad-hoc report
DisplaySystemMemProps show system member properties available for selection
DrillthroughDefaultMaxRows default maximum rows on a drillthrough
DrillthroughAbsoluteMaxRows maximum permitted rows on a drillthrough
RepositioryRootUNC No longer supported - listed for compatibility reasons. To create a shared repository, use MKLink [1] to replace the folder with a Symbolic Link to a network share.
ClearLevelsMovedToFilters Where an entire level is selected on an axis (potentially a large number of members), and is dragged onto the slicer, the selection is changed to the default member (Typically 'All'). This is to prevent users accidentally creating a very slow running query by individually aggregating all the members dragged to the slicer
DefaultCulture Backup culture where it cannot be retrieved from the browser
QueryActiveDirectory Used to display the user name on homepage
WritebackTimeout Writeback timeout in milliseconds
PdfConverterUserName see PDF Printing - Configuration
PdfConverterPassword see PDF Printing - Configuration
DocumentDomain Used when embedding XLCubed within an iframe on a different server

PDF Printing Configuration

For PDF printing you need to:

1. Edit web.config and change PDFRenderer value to SpreadsheetGear:

<add key="PdfRenderer" value="SpreadsheetGear"/>

2. In a 64-bit environment you will also need to change an application pool setting in IIS.

PDF1.png

Select View Application Pools and select the XLCubed application pool.

PDF2.png

Select Advanced Settings and set Enable 32-bit Applications to False

PDF3.png

Server specification

Recommended specification is dependent on the cube size and design, the number of users, and the pattern of usage. Having Analysis Services on the same machine will also have an impact.

As an absolute minimum we recommend:

  • Memory: 2GB
  • Processor: Dual Core 2.2 GHz

Application Usage

  • Please refer to the help menu within the product for an overview of all functionality.

See Also

External Links

Retrieved from ‘https://help.xlcubed.com/index.php?title=XLCubed_Web_Edition_Installation_Guide/Version_6.1&oldid=386’