Technical Resources

Running on IIS

Running Pimplus on IIS

This article explains how to run Pim+ on IIS. It provides pictorial examples with each step to help you navigate the software's interface. By default, the user interface is accessed through a web server that is integrated right in PimPlus. The integrated web server makes for quick and easy deployment without the need to install and configure IIS.

However, there are certain times when you may prefer to access the PimPlus user interface through IIS and this is fully supported. Reasons to switch to IIS may include corporate policy or the need to use HTTPS/SSL to protect access to the console.

Step 1: Disable the Integrated Web Server

1. Go to the e.g. C:\Program Files\pimplus folder.
2. Edit the file called config.ini using Notepad.
3. Look for the section called [WebServer] followed by an entry called Enabled=1 and change it to Enabled=0.

If the Enabled line is not present in your config.ini file add it manually under the [WebServer] section.

4. Restart the PimPlus service.

Step 2: Install IIS

1. Use the Server Manager to add the "Web Server (IIS)" role.
2. Under the "Web Server (IIS)" item navigate to "Web Server" and then "Application Development".
3. Turn on the options for "ASP" and "Server Side Includes".
4. In the previous step make sure to select just "ASP" and not one of the other options with ASP in their names.

Step 3: Install a Self-Signed Certificate

1. Open the IIS Manager in the Administrative Tools section of the Control Panel.
2. Select the top level item which has the same name as the local system.
3. On the right-hand side double-click on the item called "Server Certificates".

4. In the Actions menu on the very right-hand side select "Create Self-Signed Certificate".

5. Enter a name for the certificate and press OK.
6. Navigate to the "Default Web Site" item in the IIS Manager.
7. Right-click on "Default Web Site" and select "Edit Bindings".
8. Use the Add button to add an HTTPS binding on port 443 with your newly created certificate.
9. Use the Remove button to remove the HTTP binding on port 80 so that HTTPS/SSL is required to access the site.

Step 4 (Optional): Add the Application

This step is only necessary if multiple sites are running in IIS or if the PIM+ API is being used.

1. In the IIS Manager navigate to the "Default Web Site" site under the "Sites" folder.
2. Right-click on "Default Web Site" and select "Add Application".

3. For the alias specify "PimPlus".
4. For the physical path enter e.g. C:\Program Files\pimplus\Html.
   • If you have installed PimPlus in a non-default location use that location instead.

Step 5: Configure Application Pool

1. Right-click on "DefaultAppPool" and choose "Advanced Settings".
2. Verify "Enable 32-bit Applications" is set to "False" and press OK.

Step 6: Configure ASP Limits

1. In the IIS Manager select the "Default Web Site" web site in the tree on the left.
2. On the right-hand side double-click on the item labeled "ASP".

3. Expand the section called "Limits Properties".

4. Change the "Maximum Requesting Entity Body Limit" to 10000000.
5. Change the "Response Buffering Limit" to 50000000.
6. Use the Apply option at the top right to save the changes.

Step 7: Register Components

1. Open a command line window with Administrator access.

2. Navigate to e.g. C:\Program Files\pimplus.
3. Run regsvr32 FrameFlowTokenExpander.dll.
4. Verify that you get a message indicating the operation succeeded.
5. Run the following command: %windir%\system32\inetsrv\appcmd unlock config -section:system.webServer/handlers.

Step 8: Verify HTTPS/SSL Access

1. Verify that you can access the user interface through HTTPS/SSL by visiting https://servername/pim.plus.
2. Your web browser may warn about the self-signed certificate before allowing you to proceed.

Step 9: Update Remote Node Configurations

1. On each remote node, edit the file config.ini in the C:\Program Files\PimPlus folder.
2. Edit the MasterNode value to start with https://.