To install an additional Iguana server, you must first obtain a copy of the zip file that contains Iguana. To do this:

• In your web browser, type the following URL: http://dl.interfaceware.com/iguana/windows/.
• In this directory, select the subdirectory corresponding to the version of Iguana that you want to install.

	While these instructions will work for any version of Iguana starting with 4.0, we recommend that you install the most recent version of Iguana if possible.

• Click the iguana_noinstaller_windows_<version>.zip link (for 32-bit Windows installations) or the iguana_noinstaller_windows_<version>_64.zip link (for 64-bit Windows installations), replacing <version> with the version that you are installing. This will download the zip file onto your system.

Once you have downloaded the zip file, the next step is to configure your Iguana server. To do this:

• Unpack the zip file into the directory into which you want to install the second copy of Iguana. (To unpack a zip file, right-click on it and select WinZip and Extract to here.) When you unpack the zip file, it creates a subdirectory named iNTERFACEWARE-Iguana that contains all of the files needed to create a second copy of Iguana. You can rename or move this directory, if you like.
• From the directory in which you installed your first copy of Iguana, locate IguanaConfiguration.xml. Copy this file to the directory in which you have stored the second copy of Iguana.

The IguanaConfiguration.xml file provides all of the information you need to configure your new Iguana server. Before you can start the new server, you need to edit this file:

• In the web_config section of the file, set the port field to the port you want to use for the new server. This port must not already be in use.

<web_config
    port="8082"
    session_timeout="1200"
    use_https="false"
    https_certificate_key_file=""
    https_private_key_file""
    server_label="server2"/>

• In the log_config section of the file, change the log_directory field to be the logs subdirectory of your second installation. (For example: if your second installation of Iguana is in D:\server2\iNTERFACEWARE-Iguana, the log directory would be D:\server2\iNTERFACEWARE-Iguana\logs\.) This directory can be either an absolute path or relative to the directory in which your Iguana server is installed.

<log_config
    log_purge_time_hour="0"
    log_purge_time_minute="0"
    log_directory="D:\server2\iNTERFACEWARE-Iguana\logs\"

The IguanaConfiguration.xml file also contains information about every channel that has been created for an Iguana server. Because you have copied this file from your other server to this one, you have created copies of the other server's channels as well. To handle this, perform the following steps:

• Ensure that every start_automatically value is set to false. This will ensure that your new server does not try to start channels that are already running on your old server.

<channel_config
    <channel
        name="channel1"
        guid="56237495644B9C43E0C4D323C407F5B6"
        legacy_db_api=""
        legacy_datasource=""
        legacy_username=""
        legacy_password=""
        description=""
        start_automatically="false"
        logging_level="1"
        use_message_filter="false">

	If you want the channel to run on the new server, you can remove it from the old one. (See Removing a Channel for details on how to remove a channel.)

• To remove a channel that you do not want, delete the channel definition in the IguanaConfiguration.xml file. This is everything between the <channel> and </channel> tags.

If you have removed a channel, you must also remove it from the channel groupings section of the IguanaConfiguration.xml file. Entries in this section look like this:

<grouping
    grouping_name="patient data"
    grouping_guid="0F729D2B11C278662EE568D6215B2172"
    description="">
    <channels>
       <channel
          channel_name="patient info 1"/>
       <channel
          channel_name="patient info 2"/>
    </channels>
</grouping>

If, for example, you have deleted a channel named patient info 2, you will need to delete its <channel> entry in this channel grouping. Since all channels are included in the All Channels channel grouping, you will need to remove the deleted channel from this grouping.

	When you log in to your new Iguana server, if you are using a plugin as a source or destination component, you may encounter a plugin communication port conflict. This is because your new server is attempting to use the plugin communication port that another server is using. See Resolving Plugin Communication Port Conflicts for information on what a plugin communication port conflict looks like, and see Plugin Settings for details on how to change the plugin communication port from within the Iguana web interface.