SQL 2012 Business Intelligence Automation of Demo Builds Part 2
Reporting Services Installation using a Configuration.ini for use with SQL 2012. Probably next most asked question is how do I setup Report Server in SharePoint Mode. Just like in my last post we have a SQL 2012 Configuration File.ini (RSIntegrated.ConfigurationFile.ini) for the installation. The really cool thing is now SQL 2012 will be configured the same way every time.. The ConfigurationFile will ensure the installation of Reporting Services 2012 and the Reporting Services Add-in are installed.
Just like my Last Post on SQL 2012 Business Intelligence the Automation of Demo Builds I discussed using a ConfigurationFile to configure PowerPivot. There are a couple changes that you will need to make for your environment and on depending how hands on you want to be with the installation.. You can choose to use the file as it is now in Simplified UI mode which is much faster and less tedious than waiting for all of the tests and entering the information by hand, I don’t know about you but whenever I have that many choices to click on I am bound to make a mistake.
However, you can also run it in silent mode by entering your Product Key, Uncommenting the PID parameter.
Then Comment out UIMODE and change either parameter QUITE or QUITESIMPLE value to True
The last change you will need to make unless your installing in the Contoso.com AD Domain is to Change the Service Account Username and Password on Line 93
Then add or remove any additional Administrators on Line 130.
I have included a link to the file on SkyDrive so you can download all of the SQL 2012 Configuration Files.
1. MSSQL.ConfigurationFile – installs the default instance with SQL Server Database Engine, SQL Server Agent, REPLICATION, SQL Server Full Text, Data Quality Server, , Analysis Services Tabular Mode, , Data Quality Client, SQL Server Data Tools (SSDT), connectivity components, Integration Services, backward compatibility components, software development kit, SQL Server Books Online, SQL Server Management Tools Basic& Advanced, SDK for Microsoft SQL Server Native Client, and the Master Data Services
2. MultiDimensional.ConfigurationFile – installs an instance named MultiDimensional with SQL Server Database Engine, SQL Server Agent, REPLICATION, SQL Server Full Tex, Data Quality Server, Analysis Services Multidimensional mode, and Native Reporting Services
3. PowerPivot.ConfigurationFile – installs Analysis Services Power Pivot Mode calculation engine, preconfigured for in-memory data storage and processing. PowerPivot solution packages, SQL Server Books Online, Database Engine, Configuration Tools, SQL Server Management Studio,
4. RSIntegrated.ConfigurationFile – installs Reporting Services for SharePoint Mode and the Reporting Services add-in for SharePoint Products.
The reason behind the configuration files will become more apparent in my next post. Needless to say it allows us to have the 3 Analysis Services Modes, both Reporting Services Mode and the environments are configured exactly the same way every time or perhaps with different UserNames and Passwords but for consistency that doesn't matter. However, between the 4 lines of Code that it takes to configure SQL 2012 and by code I mean Setup /CONFIGURATION=D:\My.ConfigurationFile.ini for Erich of the SQL Instances we are creating then its pretty simple . Since we are calling the 4 lines from PowerShell it looks something like the following: Note: the Configuration Files I use are set with QUITE=”True”
cmd /c "Setup /CONFIGURATION=$Install:\MSSQL.ConfigurationFile.ini"
cmd /c "Setup /CONFIGURATION=$Install:\MultiDimensional.ConfigurationFile.ini"
cmd /c "Setup /CONFIGURATION=$Install:\PowerPivot.ConfigurationFile.ini"
cmd /c "Setup /CONFIGURATION=$Install:\RSIntegrated.ConfigurationFile.ini"
The next command that runs is in the PowerShell Script is cmd /c "AutoSPInstallerLaunch.bat" which I am sure everyone who is reading this post knows what happens next… Anyhow, SharePoint 2010 or SharePoint 2013 is installed by using an answer file (AutoSPInstallerInput.xml) much like the SQL Configuration File Approach…
However, it doesn’t stop there as we still have all of our SharePoint 2013, SQL 2012, and other customizations to work with in a repeatable manner that a SharePoint Admin can handle with having to Open Visual Studio to create WSP / Solutions to be deployed..
I look forward to Sharing the rest with you in my next post…
You can download the 4 SQL 2012 Configuration Files here http://sdrv.ms/RrMBi9