This is the third in a series of posts on administering SQL Server Report Services. In Part 1 we went over the basic installation of SSRS for native mode. Part 2 went over the components that were installed. This post will discus configuring SSRS using the Reporting Configuration Manager tool, a graphical tool to set up your SSRS instance.
When we installed our new instance we choose the Install and Configure option using the default settings. Let’s take a look to see what they are. Open the Reporting Configuration Manager and connect to your instance. I’m using SQL 2014 Developer, but the tool is similar for other editions and versions.
Once you’re connected you’ll see the status of the service and instance information. You can start SSRS if it isn’t already.
Next, you can set up the account that Reporting Services runs under. Since we chose the default settings during our installation the service is running under the new ReportServer account. You can change to another built-in account or any other domain account.
Configure the Web Service URL on the next screen. Our default settings created a virtual directory called ReportServer; you can create a different one if you want. Also, all IP addresses on the server are assigned using port 80. If you click the Advance button you can set a single address and change the port number. There’s also an option to use a SSL certificate if you’ve installed one.
The screen will display the ReportService URL when you’re finished. Clicking it will open the web service URL. At this point there’s probably nothing much to see. Later you’ll see any folder and reports you’ve deployed.
The next screen is where you set the databases. SSRS requires 2; one to store reports and one for sessions. The defaults are ReportServer and ReportServerTempDB but you can create new ones if you like. This is helpful if you have databases from an existing report server you’ve restored. You can also change the account SSRS uses to connect to the databases. Again the default is the ReportServer account.
Continuing on, the next step is to configure the Report Manager. It’s similar to setting up the web service.
And like the web service, nothing to see until you deploy some reports.
If you’re going to send reports via email subscriptions you need to set up an email account for SSRS first.
Some of your reports may need to open images stored on the network somewhere. Or you may have reports that need to connect to data sources that don’t require authentication. For those cases you’ll need to configure a default Execution Account. Specify a domain account that has the privileges you’ll need. Note that this step is optional.
SSRS uses a symmetric key to encrypt sensitive data, such as passwords used by reports. You should backup the key periodically. One way is through the Report Configuration Manager. You can also use the rskeymgmt command line tool, which I’ll discuss in a later post. I’ll also show you a way to schedule a backup using PowerShell.
I’m not going to discuss Scale-out Deployment here, that’s a much bigger topic.
In the next post I’ll talk about configuring SSRS with through config files.
Reporting Services Configuration Manager (SSRS Native Mode)