Integrating Reporting Services 2008 with SharePoint 2007 Step 2 - SharePoint Installation
Step 2 - Windows SharePoint Services 3.0 Installation and Configuration
The previous step is:
- Step 3 - Configuring Reporting Services for SharePoint 3.0 Integration - Part 1 : Operations performed with Reporting Services Configuration tool
- Step 4 - Configuring Reporting Services for SharePoint 3.0 Integration - Part 2: Operations performed in SharePoint Central Administration (includes Microsoft SQL Server 2008 Reporting Services Add-in for Microsoft SharePoint Technologies Installation)
- Step 5 - Sample Databases for Microsoft SQL Server 2008 Installation
- Step 6 - Report Creation and Deployment in SharePoint 2007 with Business Intelligence Development Studio (BIDS)
The VM runs Windows 2003 Server OS
The goal is to quickly allow someone to create reports and to discover SharePoint Integrated Mode features: deployment, Web Parts dashboards, subscription, snapshotings, etc.
Even planning for further deployments in a Farm environment with several servers and Active Directory, it may be usefull to have been familiarized with involved products installation, configuration and use, by having tested it in a Simple Farm Topology with one computer and local accounts.
1 - Environment Configuration
|Number of Virtual machines:||1|
|Operating System:||Windows 2003 Server|
|Server Roles:||Application Server|
SQL Server Service Account: Local Administrator
Setup user account: Local Administrator
Server farm account/Database access account: Local Administrator
2 - Referred Documentation
You have installed SQL Server 2008 with reporting services on the virtual machine with a Windows 2003 Server OS.
(if not you can refer to the step 1 of these arcticles group: Step 1 - SQL Server 2008 with reporting Services Installation and Configuration )
- You have downloaded Windows SharePoint Services 3.0 with Service Pack 1
This installation is compliant with both MOSS 2007 and Windows SharePoint Services.
I will deploy Windows SharePoint Services using DBA-Created Databases mode in order to be allowed to choose the name of the SharePoint content database for Central Administration. If you deploy using SharePoint Technology Wizard, you cannot choose this database name and it will be automatically generated by SharePoint with a GUID in a form like
Regarding compatibility of WSS or MOSS and SQL Server 2008, there is only one warning:
SQL Server 2008 requires that Windows SharePoint Services 3.0 SP1 be installed BEFORE installing MOSS or making use of SQL Server 2008 with WSS 3.0
for more information see this TechNet article: Determine hardware and software requirements (Windows SharePoint Services)
This installation includes the following steps:
- Step 1: Create SharePoint Configuration Databases
- Step 2: Create SharePoint Administration Content Database
- Step 3: Launching Windows SharePoint Services 3.0 Installation
- Step 4: "Microsoft Software License Terms" page
- Step 5: "Choose the installation you want" page
- Step 6: "Server Type" Tab
- Step 7: Installation Progress
- Step 8: Close the "Complete the Configuration" dialog box and check Installation
- Step 9: Open a Prompt Command
- Step 10: PSCONFIG.EXE instruction
- Step 11: Run the SharePoint Products and Technologies Configuration Wizard
- Step 12: "services might need to be restarted" dialog box
- Step 13: "Modify Server farm Settings" page
- Step 14: "Configure SharePoint Central Administration Web Application" page
- Step 15: "Completing the SharePoint Products and Technologies Configuration Wizard" page
- Step 16: "Configuring SharePoint Products and Technologies" page
- Step 17: "Configuration Successful" page
- Step 18: Launching SharePoint central administration homepage
- Step 19: Performing optional additional settings
Right click the Database node and select New Database
Type the SharePoint Configuration database name : SharePoint_Config
Click OK. Your database is created.
The next figure shows the state of your database server at the end of this step.
On the Choose the installation you want page, click Advanced in order to access to the Server Type Tab
As it was precised in this document introduction, even if all our deployments (SQL, SharePoint, Add-in, etc.) will be done one a single machine, we can deploy SharePoint in a Simple Farm Topology, that will allow us to configure the Farm, for example choose the SharePoint Configuration database name, and to add more Web Front End Server later if we want to.
On the Server Type Tab choose Web Front End, and click "Install Now".
We don't want to use the wizard because we want to be able to choose the name of the SharePoint Central Administration Content database, and we will do it by a Command Line instruction.
You can check installation by going to the 12 directory.
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12
and check directory was well created : TEMPLATE, LOGS, CONFIG, etc.
Psconfig –cmd configdb –create –server yourMachineName –database SharePoint_Config –user yourMachineName\yourLogin –password yourPassword –admincontentdatabase SharePoint_AdminContent
Wait while SharePoint Products and Technologies Wizard is filling the previously created databases in command line mode.
This operation can last 3 at 10 minutes depending on you system configuration.
While performing configuration, some messages are displayed on the Command Prompt.
At the end of the process you will have a Command Prompt looking like next figure.
On the Welcome to SharePoint Products and Technologies page, click Next.
Notice that the wizard has retrieved your SharePoint configuration database: SharePoint_Config.
I personally use always 55555.
If you want to use Kerberos Security settings, this is the place and moment to choose it. Kerberos authentication requires you to configure your network for Kerberos, so let the default option to NTLM.
Click finish to close the wizard and launch the SharePoint central administration homepage.
You can perform additional configuration tasks like:
- Start the Windows SharePoint Services Search service
- Configure incoming e-mail settings
- Configure outgoing e-mail settings
- Configure diagnostic logging settings
- Configure antivirus protection settings
- Configure workflow settings