First ensure that you have an FTR repository.
Against FTR in the SMC, enable your community:
The properties of the FTR will be presented:
There needs to be an Indexing Service catalog on the database server. This will have to be added manually. TheCatalog name must be spelt correctly. Click Apply and you will be given specific instructions as to what you need to do:
The location specified (c:\Bentley\repositories\Generic_FTR) is NOT on the database server, so you will have to share that location out, so you can connect to it using UNC.
So on the database server, expand Indexing service. Right click on Indexing Service, and select New, catalog.
Add the name (eBFTR_Generic_new), and specify the location that the catalog will exist. This is NOT the location of the FTR repository.
The Catalog will remain off-line until Indexing Service is restarted. But please continue and add a directory. Under your new catalog, highlight Directories, right click and select New Directory. For the path, insert your UNC path, and put in a username and password who has access to that location.
Restart the Indexing Service.
The last thing to enable is which files within eB do you want to FTR? FTR is based on the document class, so expand your Community within the SMC, and select FTR.
Select which classes you want to enable.
If you have had eB running for some time, and want to add FTR at a later time, then enabling the document classes will mean that new files added to eB will be FTR'ed. If you want to submit files that had previously been added to eB then you must press the synchronize button.