When Time Matters 9 released the indexer as a standalone program, it created a certain amount of confusion. The Indexer is set to run on the first workstation that logs into TM, and there is no way to control it. If you try starting TM on a separate workstation “first,” that takes up a separate license, which is obviously not a solution. The Indexer, to state the obvious, is responsible for indexing all the Time Matters data and makes searches extremely fast.
It is possible to disable the indexer entirely by creating a simple text file with Notepad named norun.txt. Put this file in the ...\Data\Index\LNDATA folder on the server where the shared Time Matters data is located. While the file is in that folder, the data indexer will not start. But that is not really a solution either.
Ideally, it should be possible to run the indexer as a service, but LexisNexis has not addressed this issue in TM 10.
It is, however, possible to run the indexer with command line switches. Create a one-line text file (call it tmindex.bat or whatever) that looks like this:
Start c:\tmw9e\tmdatndxe.exe /data=c:\tmw9e\data
(obviously the location may change according to the location and version of Time Matters). You can then set this batch file to run on startup. (Thanks to Jeff Stouse). This can be done either on the server, or on a separate PC (perhaps an older PC that is being replaced), a la Worldox Indexer.
Chris Sperry has written a utility that does allow you to run the indexer as a service, but I have not tested it. Contact Chris through Jumpstartsolutions.com
It is possible to disable the indexer entirely by creating a simple text file with Notepad named norun.txt. Put this file in the ...\Data\Index\LNDATA folder on the server where the shared Time Matters data is located. While the file is in that folder, the data indexer will not start. But that is not really a solution either.
Ideally, it should be possible to run the indexer as a service, but LexisNexis has not addressed this issue in TM 10.
It is, however, possible to run the indexer with command line switches. Create a one-line text file (call it tmindex.bat or whatever) that looks like this:
Start c:\tmw9e\tmdatndxe.exe /data=c:\tmw9e\data
(obviously the location may change according to the location and version of Time Matters). You can then set this batch file to run on startup. (Thanks to Jeff Stouse). This can be done either on the server, or on a separate PC (perhaps an older PC that is being replaced), a la Worldox Indexer.
Chris Sperry has written a utility that does allow you to run the indexer as a service, but I have not tested it. Contact Chris through Jumpstartsolutions.com
Great tip!
Posted by: Alex | October 22, 2009 at 03:03 AM
Absolutely FANTASTIC tip.
But, I think the proper syntax is:
Start c:\tmw9e\tmdatndx.exe /data=c:\tmw9e\data
There is no executable file "tmdatndxe.exe" that I could locate.
The indexer has been a nuisance constantly creating problems on the workstation that is unfortunate to have the indexer running. This seems to be a great way to have the indexer running on the server without a license being used. Keep up the good work.
Posted by: Dario | October 24, 2009 at 03:28 PM
New twist on this. If you the indexer on your server as indicated, TimeMatters will automatically end the indexer when you run the utilities (rebuild the data). Apparently, when TimeMatters runs utilities it kills the indexer in order to run the utilities. That means that you have to restart the indexer manually on the server, or it will automatically start on the next workstation to log into TimeMatters, which defeats the purpose of this tip.
Posted by: Dario Diaz | November 01, 2009 at 10:09 AM