This project has moved. For the latest updates, please go here.

Getting Started

Setting up CrissCross is fairly simple, but does involve some knowledge of IIS and ASP.NET configuration.
So probably best to give it to someone who knows a bit of ASP.NET to set up.

CrissCross is designed to work with a minimum of configuration - basically you just tell it where your SSRS server is and then off it goes. However there is additional optional configuration that can be peformed to control how it behaves.

1a) If you are building from source, open the solution in VS2008 and build.
Then publish the CrissCross Web App project to a temp folder from where you can deploy it.
- choose a folder to publish to
- choose 'Only files needed to run this application'
- check the 'Include files from the App_Data folder' box.

1b) If you downloaded the zipped codeplex download, there is already a built/published version
in the 'PublishedWebApp' folder

2) Find an IIS server and create a CrissCross Virtual Directory on it.
If you use the IIS server on your SSRS server you've got more chance of getting impersonation working (see below) but apart from that, any IIS server will do.

3) Copy the published CrissCross web app into your virtual directory

4) Make sure Windows Authentication is available.
On IIS 6 its always an option, but in IIS 7 you might have to install it as an extra windows feature
http://www.iis.net/ConfigReference/system.webServer/security/authentication/windowsAuthentication

5) Make sure the ReportViewer component is installed on the server
If you're on the SSRS server, it'll be installed already, but if not you can install it using the
ReportViewer 2008 SP1 redistributable installer - which is in Resources/ReportViewerSP1.exe

6) Edit some web.config settings:

In <appSettings> :

crisscross.ReportServerRootUrl
- set this to the url of the root folder of your SSRS reports folders. It will usually be something like
http://your-ssrs-server/reportserver . The ReportViewer component uses this to connect to the
SSRS server

crisscross.ReportServerWebServiceUrl
- set this to the url of the SSRS web service. It is usually something like:
http://your-ssrs-server/ReportServer/ReportService2005.asmx . CrissCross uses this to get the report
catalogue.

crisscross.ImpersonateLoggedOnUser
- CrissCross can either run the reports as the logged in user, or run as a fixed user. Turning off
Impersonation and using a Fixed User is easier to get started with, but turning Impersonation on makes
CrissCross more useful. Note that Impersonation works best when CrissCross is running on the SSRS
server itself. See Impersonation Mode for more details.

crisscross.FixedSsrsUsername
crisscross.FixedSsrsDomain
crisscross.FixedSsrsPassword
- If ImpersonationLoggedOnUser is false, these settings must be set to a valid domain/username/password for running SSRS reports. For best results, set the web app's Application Pool (in IIS) to run under the same account.

crisscross.UseReportHistory
- CrissCross queries information from the SSRS Report Log (see connection strings, below). If you'd rather not do that, set this value to false.

Also, further down in the web config:
<identity impersonate="true/false"/>
- This must be set to the same true/false value as ImpersonateLoggedOnUser

In <ConnectionStrings> :
ReportServerDb
- Set this to point at your SSRS database (the database that holds SSRS settings). It will usually be a database
called ReportServer on the SSRS server. CrissCross uses this to fetch info about previous report runs from the
report log - hence only the datareader role in necessary for the SQL user.

For other options see web.config settings

7) That should be it; use a browser to navigate to the virtual directory and CrissCross should start running.

Last edited Mar 25, 2012 at 1:01 AM by codeulike, version 4

Comments

No comments yet.