If the full text search is configured correctly in the application configuration, you get an overview of the full text search configuration in the WebOffice Administration Page (SynAdmin). As you can see there is a new tab called Full text Search. If you made the above mentioned configuration steps for the first time, there won't be any search or sub indices (yellow exclamation mark).

 

 

In SynAdmin, as illustrated above, each configured subindex will be listed with the corresponding layer name and related information. It is important, that all projects (configured for the full text search) are initialized.

The relevancy of each of the subindices and their information regarding their state is illustrated in SynAdmin (Explanations for column State). The blue arrow symbol, which exists for each layer individually, allows the user to generate a subindex. The user can also select the desired indices by ticking them, and create new subindices using the button Recreate checked subindices. If the subindices were successfully created, the information regarding their state will be displayed with created. After that, the different search layers are initialized for the full text search.

The indices can be deleted with the buttons, which are located next to the buttons to create the subindices, or by clicking the Delete checked subindices button. Regardless of the state of the subindex the column Weigh. shows the configured result weight of every subindex of the list.

 

 

Within the WebOffice Administration Page (SynAdmin) there is an info button (yellow symbol on the right hand side) for each subindex concerning details for subindices. The details include (amongst others) the name of the subindex (map service/layer), indexed search fields, indexed result attributes, information about lookups and the result weight.

 

 

 

 

 

In the tabular list of the subindex details the queries which use a specified subindex are displayed. If there are queries in different projects, which use the same layers (feature classes), you can see here the aggregation of the configurations. Also consider the notes below the subindex details, explaining the various meanings of different types of brackets.

 

 

All indexed search fields and result fields of a query, which was indexed for the full text search, are listed within the details for the selected subindex.

The following data types are supported in course of the indexing process in WebOffice 10.9 R4:

 

 

If there are problems with the creation of indexes during the full text search in the SynAdmin this is indicated by a red cross at the beginning of the line. Additionally, the user can get more information about the specific error by displaying it via a tooltip at the column State or by using the red cross icon. The mouse must be moved over these columns. The error information provides additional hints about problems with the initialization of the index.

 

 

If data is changed that is related to a subindex, the state of the subindex is displayed as out of date in SynAdmin. Please note, that the data for the index is prepared WebOffice. SOLR is used to physically store the index. Solely WebOffice decides whether a subindex is out of date because SOLR does not have access to third-party systems (e.g. ArcMap).

 

 

The following scenarios lead to the status out of date:

•The logfile describing the configuration of the subindices in the current FTS index is missing (see C:\Tomcat\webapps\<WebOffice application>\WEB-INF\work\fulltextsearch\fts_admin_log.xml).

•A change to the application configuration or a project configuration has changed a subindex relevant configuration value (e.g. weighting, searchfields, resultfields, filterfields, definitionQuery, objectnameConcatenator, wordDelimiters, ftsSynonyms, phoneticLocale, phoneticAlignment, dateFormat; see C:\Tomcat\webapps\<WebOffice application>\WEB-INF\work\fulltextsearch\fts_admin_log.xml).

•Editing a feature in WebOffice could not be synchronized to FTS index (e.g. because it was temporarily unavailable).

•Editing a feature using a WebOffice External Call could not be synchronized to FTS index (e.g. because it was temporarily unavailable).

•The number of features in the subindex does not match the current number of features of the layer.

•The largest and smallest OBJECTID in the subindex does not match the largest and smallest OBJECTID of the layer.

 

If one or more features are changed by a third system (e.g. ArcMap) without changing the number of features or the smallest or largest OBJECTID (e.g. editing an attribute in ArcMap, neither deleting or nor adding), this is not recognized, although the subindex is functionally out of date.

 

If the request of the current state of the index failed, because of unavailability of the service, the state of the index will turn to no connection in the SynAdmin. The state no connection is colored in orange. An additional explanation of that state is also visible directly in the SynAdmin. A tooltip with detailed information about the connection problems will be visible by a mouseover operation directly on the state of the affected index.