Beruflich Dokumente
Kultur Dokumente
When you access the INtools application via Citrix, we strongly recommend that you do not perform any INtools administration activities that run automatically for a long time on a client machine. When INtools administration activities are executed via Citrix client, the software actually performs these activities on the server side, while the client remains idle, and the connection to Citrix becomes inactive. This disconnects the INtools session and can even cause INtools to close down on the server. A connection break off during such an activity can cause damage to your INtools database. Examples of such administration activities are: initializing or upgrading a domain, claiming entities, rebuilding stored procedures and triggers, and so forth. Workaround we suggest that you perform this kind of activities either on your database server machine or on a client machine using a configuration other than Citrix.
You can use INtools in thin client mode, which supports Citrix MetaFrame or Microsoft Terminal server. For installation details of Citrix MetaFrame client / server or Microsoft Terminal server, refer to the appropriate software vendors documentation. When starting INtools, the software looks for the INTOOLS.INI in the system path <DRIVE>:\INTOOLS. This path is defined in the Path system variable. To enable INtools to work in thin client mode for multiple users, you must load a separate INTOOLS.INI file for each user who logs on to Citrix. Also, you need to modify the Path system variable to point to the location mapped to each users home folder. For example, you can map this location to U:\INTOOLS, which is actually C:\WTSRV\PROFILES\<USERNAME>\INTOOLS, and then you change the system path parameter accordingly to U:\INTOOLS so that it affects all users. This way, when a user starts INtools, the application uses the individual INTOOLS.INI file in the location specified for that user.
Make sure that the U:\INTOOLS contains the INTOOLS.INI file. You can also use this folder for temporary files.
2. Modify the system path statement on the server (in Control Panel: System: Environment tab: Path system variable) to include the U:\INTOOLS folder in the system path. 3. In the path C:\WTSRV\APPLICATION COMPATIBILITY SCRIPTS, open the file ROOTDRV2.CMD and set the following parameter: SET ROOTDRIVE=U. 4. To ensure that each individual user has a separate folder for storing the temporary files, in the INTOOLS.INI file, do the following: a) In the [Loop] section, change the Pathtemp parameter from the path on the server's shared INtools installation folder to U:\INTOOLS, (or specify some other location if required). b) In the [Project] section, change the Logopath parameter from the path on the server's shared INtools installation folder to U:\INTOOLS, (or specify some other location if required). c) In the [API] section, change the Apitemp parameter from the path on the server's shared INtools installation folder to U:\INTOOLS, (or specify some other location if required). 5. Copy the INTOOLS.INI.ORIG file from the INtools installation folder to each individual user drive in the U:\INTOOLS folder, and rename the INTOOLS.INI.ORIG file to INTOOLS.INI.
Notes This action ensures that each individual user has a separate folder for making individual settings in the INTOOLS.INI file. If required, you can use a script file to automate this step each time a new user logs on to Citrix (see the following procedure for details). In cases where Citrix works with multiple servers, or where users have readonly access to the server registry, to ensure that each user gets a single unique connection ID, check that the INTOOLS.INI file includes the following lines in the [ENVIRONMENT] section ConnIDINI=1 ConnectionID=0 The software replaces the connection ID value with a unique value for each user when the user logs in for the first time. Where this is the first connection, we recommend disconnecting from the program and then reconnecting to ensure that the software updates the new connection ID in the INtools database.
@Echo Off Call RootDrv.Cmd If Not Exist "%RootDrive%\Intools" GoTo NoIn REM Otherwise show message REM Check if INI file is there :NoINI If Not Exist "%RootDrive%\Intools\intools.ini" Copy "C:\Intools\intools.ini.orig" %RootDrive%\Intools\intools.ini GoTo ShowMsg REM echo There is no INTOOLS Sub-Folder in %HomeDrive%%HomePath% :NoIn REM echo INTOOLS Sub-folders do not exist in %RootDrive% md %RootDrive%\Intools GoTo NoINI :ShowMsg MSG %USERNAME% /TIME:1 Your INTOOLS Sub-Folder has been set to %RootDrive%\Intools.
5. Edit the ROOTDRV2.CMD file to specify the home folder drive letter in the statement Set RootDrive = DriveLetter. Note For this installation, you need to change the line Set RootDrive = DriveLetter to Set RootDrive = U. The U drive points to C:\ WTSRV\PROFILES\<USERNAME>.
6. The USRLOGON.CMD file calls the file MKINTOOLS.CMD you have created. 7. The MKINTOOLS.CMD file does the following: a) Calls the ROOTDRV.CMD file to ensure the user has a home folder. b) Checks whether a copy of the INTOOLS.INI file resides in the home folder. If not, it makes a copy of the INTOOLS.INI file (which is located in the actual \INTOOLS folder and was earlier renamed to INTOOLS.INI.ORIG), and places it in the users home folder.