The current versions of the Attunity BizTalk Gateway (up to v1.3.3) dont support Upgrade Insallation.

At some sites where there are several Adapters and complicated projects, it could be near to impossible to upgrade to a newer version of the attunity BizTalk Gateway using the traditional method described in the following article.


The solution is to manually upgrade the installation. The process is very delicate and should be done carefully.

In these steps we will assume that the customer is currently running v1.2 of the Gateway and wants to upgrade to the latest v1.3.2:
1. Shutdown the different BizTalk Hosts, and stop all related processes.

2. Backup the current installation directory of the Attunity BizTalk Gateway (assuming default installation):
C:\Program Files\Attunity\Attunity Adapter Suite for BizTalk Server 2004 1.2.0
3. Install the Attunity BizTalk Gateway v1.3.2 on a DIFFERENT MACHINE, and ZIP the files from the installation directory to be copied to the BizTalk machine.

The purpose of this step is to get the files from the installation, and not to install v1.3.2 on the BizTalk machine we want to manually upgrade.

4. Copy the files from the v1.3.2 installation to the v1.2.0 directory from STEP 2.

In this step we will have the v1.3.2 binaries in the v1.2.0 directory, this will let BizTalk load and use the newer version DLLs.

5. Use the RegEdit utility and navigate to the following key:
6. Create the following key under the Attunity section:
Attunity Adapter Suite for BizTalk Server 2004 1.3.2
This is the version which we are installing (upgrading to).

7. Click on the newly created key, and create a STRING Value called "Path", and the value should be the installation of the BizTalk Adapter you are upgrading, for example:
C:\Program Files\Attunity\Attunity Adapter Suite for BizTalk Server 2004 1.2.0\
This is the case if you are upgrading from a machine which contained v1.2.0. This directory would contain your assemblies.

Attachment 103
8. Restart the BizTalk Hosts.
The process should be carried out carefully, please consult R&D support for more information.