OpenLM Software is delivered with LightTPD: a built-in web server that starts as a service. Users can continue and use the built-in web server or use a standard web server such as Microsoft IIS 7. This guide explains how to configure OpenLM EasyAdmin to work with Microsoft IIS 7 and how to setup SSL on IIS7.
Configure OpenLM EasyAdmin to work with Microsoft IIS 7:
1. Install IIS:
2. Enable CGI in IIS:
Open the Windows’ control panel and select “Programs”
Select “Turn Windows features on or off”
Wait for the window to load (may take a while). Select “World Wide Web Services → Application Development Features → CGI”, and click ‘OK’
3. Create the EasyAdmin site in IIS:
Open Windows’ “Control Panel” → System and Security → Administrative Tools → Internet Information Services (IIS) Manager”
Right-Click “Default Web Site” and select “Add Virtual Directory”:
Set Alias to “easyadmin” and physical path to the EasyAdmin location typically: “C:\Program Files\OpenLM\OpenLM Server\WebApps\EasyAdmin2”:
Right-click on the “easyadmin” site and select “Convert to Application”:
4. Enable EasyAdmin CGI
At easyadmin home double-click “Handler Mappings”:
In the “Executable” test box, type in the “cgi-bin\proxy.exe” path. This is typically
“C:\Program Files\OpenLM\OpenLM Server\WebApps\EasyAdmin2\cgi-bin\proxy.exe”
Press the “Request Restrictions…” button and select “File or Folder”:
Click “OK” twice, and answer “Yes” to this question:
Enable the CGI-exe. Select “Edit Feature Permission”:
Select “Execute” and press “OK”:
5. Configure easy admin to use proxy.exe
Navigate to easyadmin directory, typically:
“C:\Program Files\OpenLM\OpenLM Server\WebApps\EasyAdmin2”
Edit file “Params.js” file; change “proxy.cgi” to “proxy.exe” as seen here:
6. Delete old log files
located in %ALLUSERSPROFILES%\OpenLM\openlm_proxy.log
7. Check that easyadmin is working
Open a web browser and browse to http://<web server>/easyadmin/
Setup SSL on Microsoft IIS 7
Obtain a certificate
Select the server node in the treeview and double-click the Server Certificates feature in the listview:
Click Create Self-Signed Certificate… in the Actions pane.
Enter a friendly name for the new certificate and click OK.
Now you have a self-signed certificate. The certificate is marked for “Server Authentication” use; that is, it is used as a server-side certificate for HTTP SSL encryption and for authenticating the identity of the server.
Create an SSL binding
Select a site in the tree view and click ‘Bindings…’ in the Actions pane. This brings up the bindings editor that lets you create, edit, and delete bindings for your Web site. Click Add… to add your new SSL binding to the site.
The default settings for a new binding are set to HTTP on port 80. Select https in the Type drop-down list. Select the self-signed certificate you created in the previous section from the SSL Certificate drop-down list and then click OK.
Now you have a new SSL binding on your site and all that remains is to verify that it works.
Verify the SSL Binding
In the ‘Actions’ pane, under “Browse Web Site”, click the link associated with the binding you have just created.
Configure SSL Settings
Configure SSL settings if you want your site to require SSL, or to interact in a specific way with client certificates. Click the site node in the treeview to go back to the site’s home page. Double-click the SSL Settings feature in the middle pane, and click apply.