Hide Comments
Hide Comments

Comments (0)

If the full-text search is configured correctly in the application configuration, you get in synadmin an overview of the full-text search configuration. 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 index/sub indices (yellow exclamation mark).

SynAdmin full-text search tab

SynAdmin full-text search tab

 

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 layers 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" and the search layers are applied 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.

 

SynAdmin full-text search index creation

SynAdmin full-text search index creation

 

In 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 names, information about lookups and the result weight.

 

icon_comment

If objects are added, edited or deleted using edit functions of WebOffice, the concerning subindex will be updated automatically only if these objects are in the same WebOffice application as the full text search is configured in.

Pay attention to the following scenario: If objects of another WebOffice application (or on desktop) are edited, the subindex will not be updated automatically. In this case, the subindex has to be newly calculated by the administrator.

The calculation of specific (or all) subindices can be done using Batch Administration Request.

 

If a List of Lookup Definitions is configured subsequently on a search or result field that has already been indexed, you have to recreate the subindex so the lookups will be used also for the full-text search. Lookups will also be considered if the project is to be published in more than one language. Therefore, the correspondent tool has to be configured (Change Language) in order to make a language change possible.

If using WebOffice usermanagement you have to mind the following points: Restrictions for layers as well as attributive filters are considered for indexing of the full-text search. After changes in WebOffice usermanagement the affected subindices are marked as "out of date" and have to be recreated.

After an uncontrolled termination of Tomcat, it could happen, that the file which regulates the write access to the search index, is not correctly deleted and so the creation of subindices isn't possible. The error message "Indexing not possible. Delete the file 'write.lock' in the solr/data/index directory of the FTS-Index." will be displayed. After manually deleting the file 'write.lock' (in FTS-Index/solr/data/index) and a restart of Apache Tomcat the problem will be solved.

The amount of needed disk space of a subindex (and therefore the necessary time to create it) is directly coincident with the number of features of a layer. With very large data (approx. 1 million features or more) the creation of a subindex may take some time and requires a large amount of disk space (directory FTS-Index/solr/WebOffice/data).

During creation of a subindex the temporary needed disk space may exceed the finally required disk space by twice. The administrator has to make sure that enough free disk space is available for subindex creation.

 

SynAdmin full-text search subindex details

SynAdmin full-text search subindex details

 

icon_comment

If a conflict with some LOOKUP Definitions within multiple projects exists , a message in the information details of the affected subindex will show up under the main point "Fields with lookup". Therefore the warning will be shown based on the appropriate conflict. If a conflict exists, the project configuration with configured Lookup has priority against the project configuration without the lookup. Additionally to the information in the information details a warning will be shown in the WebOffice 10.9 SP1 logfile of the application.

 

SynAdmin Full-Text search details - LOOKUP conflict

SynAdmin Full-Text search details - LOOKUP conflict

 

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.

 

SynAdmin full-text search detail list

SynAdmin full-text search detail list

 

 

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:

 

Regarding search fields:

GLOBALID

GUID

OID

SINGLE

DOUBLE

DATE

INTEGER

SMALL_INTEGER

STRING

 

Regarding result fields:

GLOBALID

GUID

OID

SINGLE

DOUBLE

DATE

INTEGER

SMALL_INTEGER

STRING

 

icon_comment

Please consider the following points for field values of type GLOBALID, GUID, OID or DATE during the indexing process:

oNo Lookups are dissolved

oNo FTS synonyms are replaced

oNo FTS word delimiters are applied

oNo phonetic alignment is applied

You will be able to search for a GUID (for example "{6D80E51C-EF16-48CB-BCE5-E35ED9A29887}") even if the minus sign is used as a FTS word delimiter. In this case, other search terms like "EF16" can only be found if the search assistant LIKE is activated.

For all other field values of type SINGLE, DOUBLE, INTEGER, SMALL_INTEGER or STRING, all points of the note above (Lookups, FTS synonyms, FTS word delimiters and phonetic alignment) are applied.

The respective settings for the result precision within the Common Settings do not affect the field values of type SINGLE or DOUBLE while executing a full-text search. In this case the settings within the ArcGIS Server are used both for the indexing process as well as for the display of the results.

For field values of type DATE the date format, which is configured within the application configuration, are used both for the indexing process as well as for the display of the results. This date format is also used for searching for date values within the full-text search.

 

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 10.9 SP1. SOLR is used to physically store the index. Solely WebOffice 10.9 SP1 decides whether a subindex is "out of date" because SOLR does not have access to third-party systems (e.g. ArcMap).

Visualisation of the state "out of date" in the SynAdmin

Visualisation of the state "out of date" in the SynAdmin

 

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.

icon_cross-reference

This scenario can be corrected by configuring full-text search status fields in WebOffice author standalone. For details about the configuration of full-text search status fields, see chapter Full-text search status fields

 

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".

icon_cross-reference

By configuring full-text search status fields changes to the status fields are recognized. For details about the configuration of full-text search status fields, see chapter Full-text search status fields.

 

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 Mouse over operation directly on the state of the affected index..

 

Visualisation of the state "no connection" in the SynAdmin

Visualisation of the state "no connection" in the SynAdmin

 

icon_cross-reference

For details about the installation of the full-text search, see chapter WebOffice FTS-Index.

For details about the configuration of the full-text search in the application configuration, see chapter Full-Text Search.

See chapter Full-text search status fields about the configuration of full-text search status fields in WebOffice author standalone.

 

Comments (0)

Ⓒ Copyright 2022 by VertiGIS GmbH