Tuning considerations for the Active Workspace indexer

In some cases, settings in clients rely on the number of warmed servers. For example, in the Active Workspace, the tc.maxConnections parameter specifies the maximum number of connections between the Teamcenter server and the indexer to be open at a given time. This parameter controls the speed of the indexing process through parallelization of steps. This value should be less than the number of warmed-up Teamcenter servers available in the pool. For example, if you have 100 warmed-up servers in the pool manager, you may want to set the tc.maxConnections value to 50 to provide an adequate number of maximum connections. During a period of heavy indexing, such as when the indexer runs for the first time, ensure that the Teamcenter server pools have sufficient servers to handle the indexing load in addition to other loads such as from interactive user sessions. For example, if the tc.maxConnections parameter is set to 50, the indexer needs 50 available warm servers. This can be achieved by increasing the PROCESS_TARGET parameter of the server pools to prestart an appropriate number of servers. If you use Active Workspace, you can change the value of the tc.maxConnections parameter in Teamcenter Environment Manager (TEM). In the Feature Maintenance panel, select Update Active Workspace Indexer settings, and click Next until you reach the Active Workspace Indexer Settings panel. Click Advanced to set the maximum Teamcenter connections in the Maximum Teamcenter Connections box. You can also change the value of the tc.maxConnections parameter in Deployment Center. In the Indexer component, set the maximum Teamcenter connections allowed between the Teamcenter server and the Active Workspace indexer. To set the maximum connections value dynamically during the indexing run, perform the following command from the FTS_INDEXER_HOME directory (TC_ROOT\TcFTSIndexer\bin): Copy runTcFTSIndexer -maxConnections=connections