Monday, March 12, 2012

How do I get a RS report onto an Internet website?

I've written our first Reporting Services report, using SQL Server 2005. Since we've never used RS before, we may, or may not, have done some things correctly. One of the things is that we only have the Reporting Services, and Report Manager, on our SQL Server 2005 server, which is in our network behind our firewall.

We also have an ASP.NET 1.1 application which is used by external users (other businesses that do business with us). Because of the nature of our business, we don't want people from one agency to access data from another agency. Since calling the report in RS involved passing parameters to the report in the URL, I decided that I would hide those details by putting the web page returned by RS into an IFRAME in an aspx page. It works just fine in our network, but I discovered that it does not work at all outside of our network.

So, my question is how do I make the RS report available to users outside of our network, in such a way that they don't have access to the parameters that I pass to the report? Should I discard the whole IFRAME approach? I have been told that it will likely require doing something about passing credentials to the backend server from the ASP.NET app, but I don't know how to do that, nor do I know what would be involved.

The most straightforward approach is to use the VS reportviewer control & run your report in local mode, e.g., do not rely upon the report server. This approach eliminates the need to create a security extesion for report server. Cheers!|||

I'm sorry to be so obtuse, but what do you mean by, "run [my] report in local mode"?

|||

DoctorWho:

I'm sorry to be so obtuse, but what do you mean by, "run [my] report in local mode"?

Never mind, I've found it (local mode).

No comments:

Post a Comment