How to improve Teamcenter Rich client login performance ?

              Lets’ discusses how to configure the Teamcenter rich client to improve login performance. While working with my recent client most important enhancement required is reducing the time taken during an initial launch of Teamcenter on a client machine. Here are few steps that you can perform to improve it. 

   o Virus Scanning:  Exclude the entire Teamcenter portal install folder and all of its sub-folders from virus scanning, as well as, the $HOME/Teamcenter/RAC folder, your User folder where the RAC workspace folder is maintained.  One possible approach is to install Teamcenter to a location that is already excluded from virus scanning.

  o Teamcenter Java: If your machine has enough physical memory, adjust the JVM size in the Teamcenter.ini file to a higher value, e.g. 512Mb.  This will avoid memory paging. 

 o Teamcenter Startup: Minimize the size of your system PATH environment variable in the Teamcenter startup script.

      For example, use the following code in your start up portal.bat script:    

                                    o TC_HOME=<your Teamcenter install location>\portal 

                                    o   set FMS_HOME=%TC_HOME%\fcc 

                                    o   set JRE_HOME=%TC_HOME%\portal\jre 

                                    o   set PATH=%FMS_HOME%\bin;%FMS_HOME%\lib; 

                                    o   C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem; 

                                    o   %TC_HOME%\portal\Teamcenter.exe

Sometimes the last used application in Teamcenter requires a signification amount of data to be refreshed on login.  Consider overriding Teamcenter’s default behavior to start the last active application by forcing Teamcenter to start in the Getting Started perspective by adding the following modifier to the Teamcenter call in the above start up script:

%TC_HOME%\portal\Teamcenter.exe -perspective com.teamcenter.rac.gettingstarted.GettingStartedPerspective

Optionally you could also edit the Teamcenter.ini file to set Teamcenter to start in the Getting Started application by adding to the top of the file the following two lines:

       -perspective

       com.teamcenter.rac.gettingstarted.GettingStartedPerspective

        When using the over the web (OTW) install, consider providing two start up scripts, one that checks for updates and one that does not.  You can launch otwportal.bat directly to avoid the OTW check.  Portal.bat checks the OTW configuration, and launches otwportal.bat for startup.  The above script can be used in place of otwportal.bat. 

  o Teamcenter FCC:  Make sure the FCC continues running once launch by setting the FCC timeout to zero.  This approach can be applied for all users by setting the timeout in the fmsmaster.xml on the Teamcenter server or for individual users by setting the timeout in the fcc.xml in FMS_HOME.

<fccdefaults>

<property name=”FCC_IdleTimeoutMinutes” value=”0” overridable=”true”/>

</fccdefaults>