Administering the TCCS container

The TCCS container reads TCCS configuration files on startup and launches the container applications enabled in the configuration. Enable each container application to run within TCCS by setting its initialize parameter to true in the tccs.xml file, for example: Consider the following behavior when working with the TCCS container: TcProxyClient component The container initializes the TcProxyClient component that is the forward and reverse proxy support library for TCCS. Idle shutdown TCCS checks each application to determine if it is idle, shutting down when all applications are idle for a configured amount of time. By default, this is set to 240 minutes. If set to zero, TCCS does not automatically shut down. It continues to run until manually shut down. Fatal application errors Each application shuts down the TCCS container if it encounters an unrecoverable fatal error. Restart You must restart TCCS after making changes in TCCS configurations, such as forward proxy, server end points, and HTTP parameters. Note TCCS and all its container applications run simultaneously. Starting, stopping, or reconfiguring TCCS (or any of its applications) propagates the same action to all. TCCS lock file The inappropriate shutdown of TCCS can cause the lock file to become stuck. If the lock file has become stuck, remove the TCCS lock file. It is stored in the %USERPROFILE% .user-name_lock_host-name directory (Windows) or HOME /.user-name_lock_host-name directory (Linux). The file name is TCCS_CONFIG.lck. By default, the TCCS_CONFIG environment variable is set to Teamcenter. For example: Copy C:\Users\smith.smith_lock_host123\Teamcenter.lck