Isight maintenance releases are delivered as .esipatch files and one updates the already installed Isight release using the .esipatch file. However there are situations where one is required to retain the original Isight installation and also have the maintenance release. KB Article QA00000008252 details the procedures to accomplish this. For the sake of viewers who are not able to view the KB article, a copy of the article is attached with this post.
In this post, I am adding some more details to the already published article.
I. Using different libraries for different maintenance releases
If there are multiple maintenance releases ( e.g. 5.6-1 , 5.6-2 etc) on the same machine, one might have issues with the component library database because by default all these releases share the same library folder name. ( e.g. \\\$user.home/locallib_56)
To overcome this problem, one has to change Local Library Directory name in the standalone.cpr of the corresponding installations. One such example is shown below:
#Isight Connection Profile
#Tue Mar 1 16:00:00 EST 2011
Sys_ServerSupportDir=
Sys_LibraryType=local
Sys_ProfileDescription=Standalone
Sys_LocalLibraryDir=\\\$user.home/locallib_5.6-1
Once the .cpr file is modified and Isight is restarted, the library directory will be populated with the new libraries.
II. Results database issues when using Isight 5.7-1 and Isight 5.7-2 together
If Isight 5.7-1 and Isight 5.7-2 are installed in the same machine, one will get database errors the first time one tries to use 5.7-1 after running 5.7-2. To avoid this, do the following:
- In the Gateway, open Edit -> Preferences.
- Go to page “Local Results Database”
- Change {user.home} to {fiper.system.configpath}
- Click OK and restart gateway
This should be done for all the main and maintenance releases of Isight 5.7 and above. Below Isight 5.7 you are not required to do this.
Once the changes are done, the results database will be saved in a place like C:\\SIMULIA\\Isight\\5.7-2\\isightdb-57, depending on the release one installed.
