Creating a side-by-side installation of fix packs for WebSphere eXtreme Scale Client for .NET

[Version 8.6.0.2 and later] When you create a side-by-side installation, you can run multiple versions of fix packs for WebSphere® eXtreme Scale Client for .NET on the same server. Your existing .NET applications that were built against the previous version can continue to run against the previous client.

Before you begin

You must have a system that has a previous version of WebSphere eXtreme Scale Client for .NET installed and a separate system to which you install the more recent fix pack.
Install the more recent version of WebSphere eXtreme Scale Client for .NET on a system that is separate from your production systems. For more information, see Installing WebSphere eXtreme Scale Client for .NET.

About this task

When you run a fix pack installation of WebSphere eXtreme Scale Client for .NET, the existing installation is replaced with the new version. Depending on your environment, you might want to test before you upgrade to the new version. You also might want to have some applications use the previous version and some use the more recent version. By manually installing the WebSphere eXtreme Scale Client for .NET, you can use multiple versions side by side.

When you install a new major release of WebSphere eXtreme Scale Client for .NET, the side-by-side installation occurs automatically.

Procedure

From the system that has the most recent installation, copy the entire net_client_home installation directory and all its subfolders. Put these files in a separate directory from the existing installation on the target system that has the previous version installed. This directory is referred to as sidebyside_home.
Manually install the more recent WebSphere eXtreme Scale Client for .NET assemblies from the sidebyside_home/bin directory into the GAC.
After this installation is complete, the GAC contains both the older and newer versions of the WebSphere eXtreme Scale Client for .NET assemblies. How you manually install assemblies into the GAC depends on the version of Windows and .NET framework that are installed.
For example, you might use Windows explorer to copy the assembly files into the %systemroot%\assembly directory. You also might download and use the gacutil.exe utility from Microsoft.
Update WebSphere eXtreme Scale Client for .NET applications to use the new version.
Use one of the following options:
- In each application that you want to update, add an assembly redirect element to the configuration file. This element redirects any reference to the older WebSphere eXtreme Scale Client for .NET assembly to the newer assembly.
```
<runtime>
  <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
     <dependentAssembly>          
        <assemblyIdentity name="IBM.WebSphere.Caching" publicKeyToken="b439a24ee43b0816" />           
        <bindingRedirect oldVersion="8.6.0.0-8.6.0.1" newVersion="8.6.0.2" />         
     </dependentAssembly>      
  </assemblyBinding>     
</runtime>
```
- Rebuild your WebSphere eXtreme Scale Client for .NET application with the newer assembly file in the list of assembly references for your application project.

Results

The applications that you updated use the newer version of WebSphere eXtreme Scale Client for .NET, while the other applications use the previous version.
The log files for the applications that are using the newer version are in the same log directory that is used by the existing applications.
The default client configuration is still obtained from the older WebSphere eXtreme Scale Client for .NET installation in the net_client_home/config directory. To use a different properties file, explicitly pass the path of the new properties file to the Connect() API.

Warning: You must manually uninstall your changes. Manual installations are not upgraded by the WebSphere eXtreme Scale Client for .NET installation program.