Prerequisites
The Gibraltar Hub Server requires IIS 7, which is only available on Windows Server 2008 and later.
Desktop operating systems (Windows Vista and Windows 7) also run IIS 7, but we do not recommend
their use as a server.
To install Gibraltar Hub, you need to be sure you've done the following:
- IIS 7 Must already be installed.
- Under Windows Features go into Internet Information Services then Web
Management Tools then IIS 6 Management Compatibility. Make sure that
the IIS Metabase and IIS 6 configuration compatibility box is checked.
- Under World Wide Web Services go into Application Development Features
and make sure ASP.NET is checked.
Hub Server License Key Required
Unlike Gibraltar Analyst, there is no built-in trial for Gibraltar Hub. To use this download you will need
a Gibraltar Hub License Key. Contact Us to arrange
for a trial key for a time-limited trial. You can install and configure the Hub Server without a key but it will not start.
Installation Notes
Create a destination Web Site prior to running the installation
During the installation process you will be asked to select a web site, virtual directory, and app pool to host
the hub. Since the installation does not allow you to create a new site at this point they need to already exist.
Sharing a Web Site
The Gibraltar Hub Server can share a web site with another application, but must be installed in its own virtual directory.
You will be able to specify the virtual directory to use in an existing site during the installation. You are not required
to use a virtual directory, and the installation default is to install in the root of the destination web site.
Anonymous access required
The hub does not use the integrated ASP.NET/IIS authentication. Therefore, the Hub web application must
have anonymous access enabled. This can be done by editing the Web.Config installed with Hub (the relevant
section is present but commented out) or by using the IIS administration tool to enable anonymous access.
This setting is not enabled by default in the Web.Config installed with Hub because if there is an existing
configuration at the web site or web server level they will conflict by default and prevent the site from loading.