I’ve recently had to set up a local Livelink environment because my system is running too smoothly and I need to throw an enterprise-level content management system at it to remind it that there are things in this world that can take you down in a second.
To minimize the (inevitable) damage, I’ve set up a separate virtual machine for it using a clone of a base Windows 2008 Server image I have. One with IIS7.
I’ve become quite adept at configuring IIS6 for Livelink (versions 9.5 and 9.7). You create a virtual directory against C:opentextcgi (configured as an application) and another for c:opentextsupport. You also need to allow executables. AND Allow Unknown CGI Extensions and Allow Unknown ISAPI Extensions under Web Service Extensions in IIS6. I’ve always been leery about opening it up like this so for IIS7, I was looking for a more restricted way of allowing livelink.exe to run.
IIS7 does things similarly but the options are in a different spot. Essentially, you’re configuring it to run CGI applications.
I’m assuming you’ve run the Livelink install on your machine already. In order to configure IIS7 after it’s done:
- Open IIS
- Click on the server name at the top
- Double-click ISAPI and CGI Restrictions
- Click Add and enter the page to your livelink.exe. Make sure you select Allow extension path to execute
- We’re only partway done. This allows the livelink.exe module to execute when given permission. But by default, IIS7 doesn’t allow CGI applications to execute. In the main IIS window, select the Livelink application and open Handler Mappings
- Next, select cgi-exe at the top of the list in the main panel, then click Edit Feature Permissions… on the right. In the dialogue box, check off Execute and click OK. (In the screenshot, I haven’t checked Execute because as soon as you do, the UI is updated underneath, making the screenshot harder to explain.)
- Finally, reset IIS (i.e. run iisreset from the command prompt or the Run dialog).
After that, you should be able to access your new Livelink installation from Internet Explorer (e.g. http://localhost/livelink/livelink.exe). Firefox is another matter. For whatever reason, it’s not working on my machine. It keeps wanting to download livelink.exe rather than run it as a CGI application. I have reason to believe it is related to content type but I’m nearly positive it worked under IIS6 without any further configuration.
Ah well, a post for another day. If ambition holds, I’ll put something up on configuring a SQL Server database for a local environment too.
Kyle the Livelink’d