In sps2003, the Reporting Services report is displayed in SPS. You can simply use a web browser or compile a webpart to display the report, basically using an IFRAME. There is also a webpart (rswebparts. cab), which can be found under c: \ Program Files \ Microsoft SQL Server \ [80] [90] \ tools \ Reporting Services \ Sharepoint. Use the SharePoint command line stsadm. exe-O addwppack for installation, and then there will be two webparts in SharePoint that can be used: reportview and report explorer. Both sps2003 and moss2007 use rswebparts, which are not upgraded with the version. I found that the attributes of this webpart are not properly saved or in other situations, in addition, I personally think it is better to use a Web viewer ......
Whether it is a Web page viewer or a reportview, the interface is often ugly, and every time you open the page, You need to log on again to pass the Report Server verification.CodeSimulate or use XMLHTTP to post this problem, but this is not the best method, and the problem can be solved through the integration of SSRS and moss.
In addition, in terms of SSRs security and permissions, although the functions provided by SSRs can basically meet our requirements, before integration with Sharepoint, it is troublesome to closely integrate SharePoint security and permissions. By integrating with Sharepoint, the report service will be taken over by Sharepoint. Naturally, it inherits the Security and permissions of SharePoint, uploads report files to SharePoint libraries, and naturally manages and cooperates with documents, version Control and other functions, at the same time, you can customize applications on the SharePoint siteProgramManage reports, models, data sources, plans, and report history on the page ...... These are all done in Sharepoint. After integration, the component library also has a very useful web component of report Viewer: SQL Server Reporting Services report viewer.
The previous day, we integrated the customer's server farm environment [front-end (NLB) × 2 + backend × 1 + SQL × 2 + SSRs × 1, so the following mainly discusses the general steps and notes for integration in the server farm environment, so that the brothers will be a little loose during integration. ^_^
(For integration of a single server environment, referSharepoint Server and reporting services integrated configurationPart1 Part2, which is detailed here and clear at a glance. )
Conditions required for integration:
- Reporting Services SP2. After SP2 is entered, you can view a Sharepoint integration item in the Configuration Manager of SSRs.
- Reporting Services external program. SSRs communicates with WSS/Moss through external programs. Therefore, if your Report Server is deployed on a separate machine, you also need to install the corresponding WSS Or Moss object model.
- Other patches.
General steps of integration operations if the Report Server is deployed on a separate machine, ensure that the Web Front-end with WSS Or Moss is installed.
- Run the installer, select "advanced" for the installation type, and select "Web Front-end" for "server type"
- In the Configuration Wizard, select "connect to server farm", select "connect to existing server farm", and select "do not use this computer to host the website" for "Advanced Settings ".
- After joining the server farm, you can stop all previous services in the management center.
Open the Reporting Services Configuration Manager to configure SSRs.
- On the "database installation" Page, create an SSRs database or change the mode. Remember to select "Create a Report Server database in SharePoint integration mode"
- You do not need to configure the "Report manager virtual directory". After integration, the "Report manager virtual directory" is unavailable.
- For server farm deployment, we recommend that you use a domain user account for the service identification.
- If you are using the default website configured for a specific port, you need to change the urlroot node in rsreportserver. config.
Install the Reporting Services external program on the SharePoint Web Application
- If the server farm configuration contains multiple SharePoint web applications, the Reporting Services external program must be installed on each computer with a Web Front-end.
After an additional program is installed on all computers, you can see the report services item on the Application Management page.
- "Manage integration Settings", and enter the SSRs URL and Authentication mode. If you configure the SharePoint web application as Windows Authentication and enable the Kerberos protocol, you can select "Windows Authentication". Otherwise, select "trusted authentication. The Dig command line tool sets the SPNs to configure the service subject name for the domain user account. I was afraid to break down the server and did not dare to do it. Then I changed it to "trusted Identity Authentication.
- All accounts that grant database access permissions must be able to access the SSRs database. Otherwise, an error occurs. After the settings are complete, restart the service.
Create a report library in Moss
- Check whether the "Report Server integration function" in "website set function" has been activated. Generally, it is activated after integration is configured.
- Add the "Report Server content type" to the document library or list library ".
At this point, the configuration has been completed.
Deployment of reports
- Upload data one by one.
- Use vs for deployment. For example, the report library path is http: // SPS-server/reports. In this list, create a folder datasource as the data source folder and create a folder rsfiles as the report folder.
The report project attribute is
Enter http: // SPS-server/reports/In targetserverurl/
Targetperformancefolder fill in http: // SPS-server/reports/datasource
Targetreportfolder fill in http: // SPS-server/reports/rsfiles
- The data source must be a valid external data source connection string. If Kerberos authentication is not enabled for the domain, the Windows integrated security credential type cannot be used.
- You must have the "member" or "owner" permission on the SharePoint site to publish a report. Otherwise, the report is denied. The "members" and "owners" of SharePoint match the "content administrator" and "publisher" of reporting services respectively ".
Some shortcomings/problems
- Only one report server can be added to the server farm.
- After integration, the original report manager will be unavailable.
- You cannot use SQL Server Management studio to manage report servers in SharePoint integration mode.
- After integration, some reporting services functions will be unavailable. For example, you cannot deploy or use custom security extensions for reporting services on the Report Server. You cannot use the report manager or manage Report Server instances in SharePoint integration mode. Data-driven subscription is not supported. It does not support linking reports, "My reports", and batch processing methods ..
- After integration, you can view the report in the same domain. Otherwise, the 401 error will occur.
