Question about programming reporting services

Hi there,
We have ASP.NET application and we want to use SQL Server Reporting Services
to display the report links to the end user. Report Server however won't be
accessible from the internet for security reasons. The server side code in
ASP.NET pages on the IIS server can access this report server on intranet. I
was exploring the choices I have to build this functionality.
I think the obvious choice of using URL addressability of SQL RS won't work
because it would mean report server can be accessed from internet. For the
same reason I think ReportServer ASP.NET control that Microsoft ships as
samples also won't work because it uses IFRAME which in turn depends on URL
addressability. So it seems programming using Report Server web service is
the only choice. This means writing code for pagination, laying out report in
landscape/portrait manner as defined in RDL, ability to export the report
etc. Is there a better alternative that anyone can suggest?
Thanks
YogeshYou are understanding it correctly. One point though, are you aware that
Report Server and SQL Server can be on different boxes, so your SQL Server
can be behind the firewall and RS can be accessed from the internet, then
URL integration will work. You would need another license though. Otherwise
until V2 comes out with the web controls your only other option is web
services.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"yogeshprabhu" <yogeshprabhu@.discussions.microsoft.com> wrote in message
news:BE238509-4BBC-46E6-B4FC-6765C4A114F0@.microsoft.com...
> Hi there,
> We have ASP.NET application and we want to use SQL Server Reporting
Services
> to display the report links to the end user. Report Server however won't
be
> accessible from the internet for security reasons. The server side code in
> ASP.NET pages on the IIS server can access this report server on intranet.
I
> was exploring the choices I have to build this functionality.
> I think the obvious choice of using URL addressability of SQL RS won't
work
> because it would mean report server can be accessed from internet. For the
> same reason I think ReportServer ASP.NET control that Microsoft ships as
> samples also won't work because it uses IFRAME which in turn depends on
URL
> addressability. So it seems programming using Report Server web service is
> the only choice. This means writing code for pagination, laying out report
in
> landscape/portrait manner as defined in RDL, ability to export the report
> etc. Is there a better alternative that anyone can suggest?
> Thanks
> Yogesh|||Thanks Bruce. I was aware that Report Server and SQL Server can be on
different boxes, but our organization has decided that they don't want report
server available over internet. Do you know of any books or articles that
explain handling pagination or ability to export the report using web
services?
Yogesh
"Bruce L-C [MVP]" wrote:
> You are understanding it correctly. One point though, are you aware that
> Report Server and SQL Server can be on different boxes, so your SQL Server
> can be behind the firewall and RS can be accessed from the internet, then
> URL integration will work. You would need another license though. Otherwise
> until V2 comes out with the web controls your only other option is web
> services.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>|||I have a couple at work and on Monday will give you the titles to them.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"yogeshprabhu" <yogeshprabhu@.discussions.microsoft.com> wrote in message
news:7246EF1E-0174-4CFA-A7AC-478ADF0AAEEC@.microsoft.com...
> Thanks Bruce. I was aware that Report Server and SQL Server can be on
> different boxes, but our organization has decided that they don't want
> report
> server available over internet. Do you know of any books or articles that
> explain handling pagination or ability to export the report using web
> services?
> Yogesh
>
> "Bruce L-C [MVP]" wrote:
>> You are understanding it correctly. One point though, are you aware that
>> Report Server and SQL Server can be on different boxes, so your SQL
>> Server
>> can be behind the firewall and RS can be accessed from the internet, then
>> URL integration will work. You would need another license though.
>> Otherwise
>> until V2 comes out with the web controls your only other option is web
>> services.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>|||Besides web services you will also need to be implementing your own
authentication too. Two books I use (both have some on Web services, enough
to get you going but are also good for other topics as well) are: Microsoft
Reporting Services in Action by Teo Lachev and Hitchhiker's Guide to SQL
Server 2000 Reporting Services by Peter Blackburn and William Vaughn.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"yogeshprabhu" <yogeshprabhu@.discussions.microsoft.com> wrote in message
news:7246EF1E-0174-4CFA-A7AC-478ADF0AAEEC@.microsoft.com...
> Thanks Bruce. I was aware that Report Server and SQL Server can be on
> different boxes, but our organization has decided that they don't want
report
> server available over internet. Do you know of any books or articles that
> explain handling pagination or ability to export the report using web
> services?
> Yogesh
>
> "Bruce L-C [MVP]" wrote:
> > You are understanding it correctly. One point though, are you aware that
> > Report Server and SQL Server can be on different boxes, so your SQL
Server
> > can be behind the firewall and RS can be accessed from the internet,
then
> > URL integration will work. You would need another license though.
Otherwise
> > until V2 comes out with the web controls your only other option is web
> > services.
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
>