Pistachio Installer

March 15, 2014 , by

So, you decided to install Pistachio. That's wonderful! We have a nifty installer to help you setup your admin portal, prepare the Powershell Script to install the web part, and most importantly get you on your way to a truly great Pistachio experience.

First, you need to get your hands on the pistachio_installer.zip. If you don't have that please contact your sales or client service representative over at LimeLeap they would love to help you get moving with your installation.

System Requirements

Before proceeding, please make sure that all the necessary system requirements are met.
Please visit System Requirements for more information.

Unpacking the Installer

Once you have downloaded pistachio_installer.zip you will need unzip the files to a drive accessible to the server you are installing the Admin Portal (i.e. C:\pistachio_installer).

Now let's take a quick second and make sure you got all the important stuff. Check out the directory you specified and make sure you have all of the following:

  • C:\pistachio_installer\Resources
  • C:\pistachio_installer\T-SQL
  • C:\pistachio_installer\Webpart
  • C:\pistachio_installer\Setup.exe

So now it looks like you're ready to install this thing. Navigate to the Setup.exe and execute it! Don't be alarmed - we wired it up to require administrative privileges on purpose. Make sure you have the appropriate admin rights and continue.

Accept

Please accept our terms real quick and continue. It's standard stuff.

Admin Portal Settings

The installer is going to attempt to setup your Admin Portal website in IIS and wire up the application pool. A few things need your attention before you proceed. We have defaulted some values for you but feel free to customize those items.

Host Name and Port Number

Even though the Host Name is optional, you need to make sure that there is no other site without a host name that is running under the port you specified in the IIS. If there is another site running under the same port and host name, the admin site will be created in IIS, but won't start automatically and will become inaccessible. You'll have to start it manually once you update the configuration.

If you provided a host name, the site still might be inaccessible if the host name you provided is not registered in your network. If that is the case, you'll need to contact your network administrator to setup the domain for you.

Database Settings

Next up is your configuration database. This is where Pistachio stores all the settings and meta data for the applications you configure. Pistachio requires a SQL Server database for this - it can be a full blown SQL Server or SQL Sever Express. Check out our system requirements article if you are not sure you've got what it takes (System Requirements).

Oh great, you've got SQL Server! Our installer will create the configuration database for you. A bunch of tables, views, and stored procedures will automagically be setup. In addition, we'll populate some configuration data.

Integrated Security

With integrated security, the account currently logged in to Windows will be used to create the database in SQL Server and later on will be used by the application to retrieve configuration settings. This will work if SQL Server and SharePoint are hosted on the same server. If they are not, you need to configure Active Directory services to pass the login credentials to the database server (double hop authentication).

Also note that with integrated authentication, you might need to add/update the database permissions for the user associated with the website's Application pool once the site is setup. Use the IIS website application pool user for authentication purposes.

If you do not use integrated security, you have to specify a user account that has full administrative access to SQL Server (equivalent to the sa account). You can create a dedicated Pistachio account in SQL Server for this purpose. Once the installation routine is completed and the database is created, you can downgrade the security of the dedicated account so it only has access to the Pistachio configuration database.


SharePoint Settings

You may or may not be the SharePoint guru who is going to install the web part but we wanted to make sure you get what you need to deploy the solution. Not to worry, we've got that covered.

SharePoint URL

There can be multiple SharePoint sites running under same URL, but different ports. No port specified means the site is running under default port of 80. For example, you might have 2 SharePoint sites running as:
http://mysharepointurl.com and http://mysharepointurl.com:90

Please provide the website URL with the port number as well, if its running on other port than 80.

After the install the you'll have a single PowerShell script that is loaded up with some key values to store in the SharePoint Property Bags, and the script to deploy the web part to SharePoint. So at this time we need the URL of the SharePoint farm you will be installing Pistachio.

Install/Next Steps

If this is a new installation, and you want a demo configuration and some demo data? No problem... check the box and we'll wire up a configuration and create a cool little demo to boot!

Almoshttp://pistachioapps.com/help/post/web-part-installer.aspxt done. Go ahead and click next, next, next, and finally install! If all is well you'll have a brand new IIS site running on a brand new App Pool, a configuration database ready for your configurations, and maybe some demo data to play with.

At this point you need to give that SharePoint guru at your organization the Pistachio.WebPart.wsp, and the Pistachio.Installer.ps1 files. You can find those in the .\WebPart\ directory where you unpacked the installer files earlier in the process.

Check out our So you want to install Pistachio in SharePoint to walk you through that process.

If for some reason things did not go as planned check out the error messages, we tried to think of all possible things that could go wrong and give you helpful tips to resolve them.