Configure TCCS to start when users log on to a Windows operating system

If file warming for the FMS client cache (FCC) is configured, you can also configure a Windows system to launch TCCS each time the system starts and cache rich client files to main memory. Using this functionality in conjunction with FCC file warming improves system startup performance Note If implemented when Kerberos authentication is not configured for zero sign-on, users are prompted to authenticate any proxy servers when TCCS is started. The consequence is that each time users log on to Windows, they are prompted to authenticate any proxy servers. Warning JRE shutdown hooks are not honored, preventing the FCC from closing cleanly. If the TCCS/FCC instance remains running when users log off (or shut down), these operating systems, the FCC segment cache may be corrupted. Siemens Digital Industries Software recommends you add the fccstat -kill command to all user logoff scripts and to any relevant Windows shutdown scripts for Teamcenter clients. Procedure Create a script to automatically start TCCS. Create a batch (.bat) script containing the following instructions: Set the FMS_HOME environment variable. The FMS_HOME environment variable points to the folder where FMS is installed. By default, this location is the tccs directory in the Teamcenter installation folder. For example: Copy set FMS_HOME=C:\Progra1\Siemens\Teamcenterversion-number\tccs C:\Progra1\Siemens\Teamcenterversion-number is the Teamcenter installation folder. The FCC runs as a part of TCCS and is installed in the same folder. Set the JRE_HOME environment variable. The JRE_HOME folder points to the directory where the Java JRE is installed on the system. The Java version must be 1.7 or later. For example: Copy set JRE_HOME=C:\Progra2\Java\jre7 (Optional) Enable startup logging for the FCC. Include this instruction only if the script is being used for debugging purposes. If included, the FCC creates a log for its startup events at the given file path. For example: Copy set FMS_FCCSTARTUPLOG=C:\fccstartup.log Start TCCS. Copy call FMS_HOME\bin\fccstat -start FMS_HOME is the value set in the first step. Set the _EL variable to the correct FCC error level. If the FCC does not start correctly, exiting with an error code, the FCC sets ERRORLEVEL to the correct FCC error code. You can use this value for debugging. For example: Copy set _EL=%ERRORLEVEL% ERRORLEVEL is the level set by the FCC. Exit if startup is successful. If TCCS starts correctly, the script is instructed to close. Copy if "%_EL%" == "0" goto worked Retry TCCS startup. If TCCS did not start correctly in the previous step, instruct the script to retry FCC startup step a few seconds later. The number after -n is the approximate number of seconds to wait. Siemens Digital Industries Software recommends setting this between 10 and 30 seconds. (Accuracy of this timing is not critical to the operation of this script.) For example: Copy @ping 127.0.0.1 -n 30 -w 1000 > nul goto retry Mark the completion of script execution. Instruct the script to print FCC successfully started on the console upon successful completion. Copy :worked echo FCC successfully started. An example of the completed script is: Copy set FMS_HOME=C:\Progra1\Siemens\Teamcenter9\tccs set JRE_HOME=C:\Progra~2\Java\jre7 set FMS_FCCSTARTUPLOG=C:\fccstartup.log :retry call %FMS_HOME%\bin\fccstat -start set _EL=%ERRORLEVEL% if "%_EL%" == "0" goto worked @ping 127.0.0.1 -n 30 -w 1000 > nul goto retry: :worked echo FCC successfully started. Configure TCCS to use the script. Store the script in the appropriate Windows startup directory (Windows 7 or Server2008): Single-user system: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup Multiuser system: C:\Users\user-name\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup Note These directories may be hidden by default. (Optional) Set the TCCS_CONFIG_HOME environment variable to the TCCS home directory. This step is required only when the default home location is not used and a custom TCCS home location is created. (Optional) Set the TCCS_CONFIG environment variable to the TCCS configuration directory containing information about the various TCCS environments. This step is required only when the default TCCS configuration name is not used.