RServer in 3 tier environment

Can anybody shed some light on this for me?
I have to deploy Reporting Services in what I think is a fairly
typical 3-tier Internet environment.
I have the following
Firewall - 443 only
IIS Server (x2)
Firewall - 443 only
App Server (IIS)(x2)
Firewall - 1433 only
SQL Server
Question. How do I deply Reporting Services in this when the IIS
server can't talk directly to the SQL Server?
Is there some form of proxy I can use to pass through requests, via
the App Servers?
Any ideas appreciated
CliffRS is a webservice
so you can install it on your App server
and you have to create your own front end application for your IIS Server
which talk to RS
"CliffH" <Cliff_Harker@.hotmail.com> a écrit dans le message de news:
c13c8375.0409131514.6969f970@.posting.google.com...
> Can anybody shed some light on this for me?
> I have to deploy Reporting Services in what I think is a fairly
> typical 3-tier Internet environment.
> I have the following
> Firewall - 443 only
> IIS Server (x2)
> Firewall - 443 only
> App Server (IIS)(x2)
> Firewall - 1433 only
> SQL Server
> Question. How do I deply Reporting Services in this when the IIS
> server can't talk directly to the SQL Server?
> Is there some form of proxy I can use to pass through requests, via
> the App Servers?
> Any ideas appreciated
> Cliff|||Cliff
The best solution for this would be to install Reporting Services (IIS) on
your Application Server, this will be able to communicate with your SQL
Server and so deployment would be a simple task using the RS command line
util or ReportingServices() .NET class.
To access the application server ReportingServices from the first (UI?) IIS
server you'll need to create a proxy class to the Application Server
Reporting Services using WSDL. You will be able to reference the proxy class
using code in the UI layer.
Hope this helps
"CliffH" wrote:
> Can anybody shed some light on this for me?
> I have to deploy Reporting Services in what I think is a fairly
> typical 3-tier Internet environment.
> I have the following
> Firewall - 443 only
> IIS Server (x2)
> Firewall - 443 only
> App Server (IIS)(x2)
> Firewall - 1433 only
> SQL Server
> Question. How do I deply Reporting Services in this when the IIS
> server can't talk directly to the SQL Server?
> Is there some form of proxy I can use to pass through requests, via
> the App Servers?
> Any ideas appreciated
> Cliff
>|||Thanks for the replies, I'll get our guys to have a look at creating
this "proxy" on the UI IIS server.
Given this is a fairly typical deployment setup I'm surprised there
isn't something in the package itself to facilitate this
Cliff
"Buzz" <Buzz@.discussions.microsoft.com> wrote in message news:<1BE284C9-C5CB-47E0-AAF3-B07021D3CB79@.microsoft.com>...
> Cliff
> The best solution for this would be to install Reporting Services (IIS) on
> your Application Server, this will be able to communicate with your SQL
> Server and so deployment would be a simple task using the RS command line
> util or ReportingServices() .NET class.
> To access the application server ReportingServices from the first (UI?) IIS
> server you'll need to create a proxy class to the Application Server
> Reporting Services using WSDL. You will be able to reference the proxy class
> using code in the UI layer.
> Hope this helps
>
> "CliffH" wrote:
> > Can anybody shed some light on this for me?
> >
> > I have to deploy Reporting Services in what I think is a fairly
> > typical 3-tier Internet environment.
> >
> > I have the following
> >
> > Firewall - 443 only
> > IIS Server (x2)
> > Firewall - 443 only
> > App Server (IIS)(x2)
> > Firewall - 1433 only
> > SQL Server
> >
> > Question. How do I deply Reporting Services in this when the IIS
> > server can't talk directly to the SQL Server?
> >
> > Is there some form of proxy I can use to pass through requests, via
> > the App Servers?
> >
> > Any ideas appreciated
> >
> > Cliff
> >

RS App tier vs. SQL DB tier, mixing cumulative updates

Does anyone know if it is possible or if any issues will be seen by
updating our RS app tier to a different SQL SP2 cumulative update
level than our SQL DB tier? A higher cumulative update obviously.
Currently our AppTier is SSRS 2005 SP2 and our DB tier is SQL 2005
SP2.
Thanks,
KelI don't see any issue at all. You can have the metadata/object cache on SQL
2000. If RS doesn't care if the database is 2000 it sure wouldn't care if it
a slightly different SQL 2005.
I ran for 6 months with RS 2005 using SQL 2000 so I know this works.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<kelkoenig@.gmail.com> wrote in message
news:5349c98e-88d6-4347-b209-338c246b7597@.e23g2000prf.googlegroups.com...
> Does anyone know if it is possible or if any issues will be seen by
> updating our RS app tier to a different SQL SP2 cumulative update
> level than our SQL DB tier? A higher cumulative update obviously.
> Currently our AppTier is SSRS 2005 SP2 and our DB tier is SQL 2005
> SP2.
> Thanks,
> Kel