June 22, 2007 at 2:07 pm
I'm trying to use the Report View Webpart to host client reports within our extranet environment.
Setup:
As a preliminary test I set up and installed the SSRS Web Services on Server A and the database on Server B. Server A also has SSL. Currently for the test both servers are inside the firewall and within the same domain. The Sharepoint .aspx page containing the Report Viewer Webpart is on a 3rd Server C in a different domain.
Test:
The final test before moving the SSRS Web Services into a server in the Extranet DMZ was to verify (via WireShark) what types of traffic/requests are taking place when the client accesses the SSRS Report Viewer Web part.
Expectations:
Findings:
Apparently, based on the WireShark report, the SSRS Report Viewer has been endowed with the "ability" to not only contact the SSRS Web Service Server but to retrieve information from the Web Service (including .RDL, RDS, etc). With this information: the Report Viewer Webpart attempts to retrieve data from the production databases and render the report on the client.
Well... this may be all well-and-good for internal Sharepoint sites but this won't fly for our Extranet sites.
When I substitute the Report Explorer within a Form View webpart the data retrieveal, rendering, etc all happens as expected. However, I can't use the Report Explorer (as the header provides access to the SSRS environment: folders, report properties, etc).
Stuck again...
Questions:
Thanks
Glenn
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply