Article: How to Run FrameFlow on IIS 6.0 (Windows Server 2003/XP) with HTTPS/SSL

Summary

This article explains how to run FrameFlow on IIS 6.0 (Windows Server 2003/XP) with HTTPS/SSL.

By default the user interface is accessed through a web server that is integrated right in FrameFlow and FrameFlow MSP. 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 FrameFlow 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.

1. Stopping the FrameFlow Service

  1. Press Win + R to open the Run dialog
  2. In the "Open:" drop down, type: services.msc
  3. Press Enter or click OK to open the services window
  4. Right click on the "FrameFlow Service" or "FrameFlow MSP Service" service and choose "Stop"

2. Disable the Integrated Web Server

Open the "config.ini" file which is found at "C:\Program Files (x86)\FrameFlow\config.ini" or "C:\Program Files (x86)\FrameFlow\config.ini" using Notepad and look for the section called [WebServer] followed by and entry called "Enabled=1" and change it to "Enabled=0"

3. Starting the FrameFlow Service

  1. Press Win + R to open the Run dialog
  2. In the "Open:" drop down, type: services.msc
  3. Press Enter or click OK to open the services window
  4. Right click on the "FrameFlow Service" or "FrameFlow MSP Service" service and choose "Start"

4. Install IIS

  1. Use the Server Manager to add the "Application Server" role.
  2. After the role installation is complete, open the Internet Information Services (IIS) Manager.
  3. Expand the local computer item and select "Web Service Extensions".
  4. On the righthand side select "Active Server Pages" and select "Allow".
  5. On the righthand side select "Server Side Includes" and select "Allow".

5. Install a Self-Signed Certificate

  1. Download the IIS Resource Kit for Windows Server 2003.
  2. Install the program called "SelfSSL".
  3. Use SelfSSL to install a self-signed certificate.

6. Create a Virtual Directory

  1. Open the Internet Information Services (IIS) Manager.
  2. Expand the "Web Sites" item.
  3. Right-click on "Default Web Site" and select "New Virtual Directory".
  4. Enter "frameflow" for the alias.
  5. Specify "C:\Program Files (x86)\FrameFlow\Html" or "C:\Program Files (x86)\FrameFlow\Html" for the Path.
  6. On the next page allow "Read" and "Run Scripts (such as ASP)" permissions.

7. Require SSL for Communications

  1. Open the Internet Information Services (IIS) Manager.
  2. Expand the "Web Sites" item.
  3. Expand the "Default Web Site" item.
  4. Right-click on "frameflow" virtual directory and select "Properties".
  5. In the "Secure Communications" section at the bottom, press the "Edit" button.
  6. In the window that appears turn on the "Require secure channel (SSL)" option.
  7. Press OK and then press Apply.

8. Verify HTTPS/SSL Access

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

9. Update Remote Node Congifurations (FrameFlow MSP Only)

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