Iguana 4.0 and later versions allow you to have multiple copies of Iguana running at the same time. This means that you can install Iguana 4.0 or later on your production machine without affecting your Iguana 3.3 server, which is still processing live production data. To install and configure Iguana 4.0 or any later version on your production machine:

• Using your version control or configuration management system, check out the VMD files and configuration files that you have just checked in from the development server.

• Follow the instructions in Downloading and Configuring the Iguana Server to install a copy of Iguana 4.0 or later on the production machine.

• In the directory in which your new Iguana server is installed, edit iguana_service.hdf to look identical to the copy of this file on the development server. If you are using C:\IguanaConfig as the working directory, iguana_service.hdf will look exactly like the example in Configuring Your Server and VMD Files:

application{
   service_kill_timeout = 500000 
   service_display_name=iNTERFACEWARE Iguana
   service_name=Iguana
   service_description=HL7 Integration Engine
   command_line=iguana.exe --working_dir C:\IguanaConfig\
   path_registry_entry_win32 = SYSTEM\CurrentControlSet\Control\Session Manager\Environment
}

• Open a Command Prompt window and set the current directory to be the directory in which your new Iguana server is installed. Type the following command:

iguana_service --install

Your Iguana service is now started. It will be running on a different web port than your existing Iguana 3.3 service.

• Start the Iguana service by following the instructions in Starting and Stopping the Iguana Service.

• Access the web interface, and log into your new Iguana service. When you are asked for an Iguana license, follow the instructions in Registering and Licensing Iguana Version 4.0 Or Later.

You now have two fully functional servers on your production machine: one running Iguana 3.3 and one running Iguana 4.0 or later. The same channels should be defined on each server.

You can now transfer one channel at a time from your old server to your new one. To do this, simply stop the channel on the old server and start it on the new one. If you want any channels to automatically start when the Iguana 4.0 or later server is restarted, follow the instructions in Displaying Channel Properties that describe how to start a channel automatically.

	Note that some channels may have been defined differently on your new Iguana server. This is because some features, such as message filtering and XML file support, are implemented differently in Iguana 4.0 and later versions. The behavior of the channels should be exactly the same on both machines. For information on the differences between channels in Iguana 3.3 and channels in Iguana 4.0 and later, see the Changes to Channel Configuration subsection of the What's New in Iguana 4.0? section of the manual. For more information on the benefits of using version control with Iguana 4.0 and later versions, see Using Configuration Management and Version Control With Iguana.

	If you install Iguana 4.0 or later manually on a system on which Iguana 3.3.2 is already installed, you may experience problems running plugins on your Iguana 4.0 server. See Problems With Plugins When Installing Iguana 4.0 Or Later Manually in an Iguana 3.3.2 Environment for information on how to resolve this problem.