"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