'Search' and 'Index' Services
Valid for: enaio version 8.50 SP1
The connection data to Elasticsearch and technical parameters for full-text indexing are specified in the configuration of the 'search' and 'index' services. General service parameters can also be adjusted.
This is configured via enaio services-admin, and can be accessed in the browser at the following URL:
http://<service-manager-admin-IP>:<port>
Default port: 7273
When accessed, enaio services-admin shows all integrated services and their status. The configuration page is opened via the drop-down menu for the 'search' service. The parameters are arranged according to the configuration file in which they are saved. application-blue.yml and application-prod.yml apply to all services. application-es.yml also applies to the 'index' service. The 'index' service also does not have to be configured if you install other 'index' services (see below).
Changes must be confirmed with the Save button on the relevant configuration file.
Configuration
application-blue.yml | |
Technical User |
User name of the technical user for all services. The technical user for the services usually requires access rights to all folder, register, and document types, as well as the system roles 'Server: Switch job context' and 'Server: Execute Ado jobs'. |
Password | Password of the technical user. |
enaio server | IP and port of enaio server with connection probability. Multiple enaio server are specified separated by '#'. |
application-es.yml | |
Elasticsearch – Server |
IP of Elasticsearch.
|
Elasticsearch – Port |
Port of Elasticsearch. Default: 9300 |
enaio server | IP and port of enaio server with connection probability. Multiple enaio server are specified separated by '#'. |
search-prod.yml | |
Maximum number of hits for spell check (suggest minhits) |
The spell check is activated if hit number is less than or equals the value indicated here. Spell check is a feature that suggests other terms in place of possible typing errors. Default: 5 |
Maximum score value for spell check (suggest minscore) |
The spell check will be executed if the maximum score value of hits is between 0 and the value specified here. If the maximum score value of hits is higher than the value entered here, the spell check is not activated assuming that there are not typing errors. Default: 0.6 |
Context size for preview (preview context words) |
Indicate the number of words before and after the search term found in the document. Default: 100 |
Number of text sections for the preview (preview summary fragments) |
Specify the number of text excerpts for preview generation in hit lists. Default: 1 |
Pattern of trusted IPs (trusted IP pattern) |
Pattern of trusted IPs. .* allows all access (default). enaio gateway, enaio server, and enaio service-manager always require access, and potentially also other components that work with full text. In a list of IP addresses, each address must always be placed in brackets. Addresses are separated by the pipe sign '|'. Dots in IP addresses must be preceded by the escape character '\'. However, no escape character is required before colons in IPv6 addresses. |
application-prod.yml | |
Pattern of trusted IPs (trusted IP pattern) |
Pattern of trusted IPs. .* allows all access (default). These IPs apply to all services that cannot be configured via their own parameters. |
If you install additional 'index' services, you must assign unique names to them. The first 'index' service is given the name 'IDXSERVICE'. Each additional 'index' service requires the configuration file index-prod.yml in the directory \services\service-manager\config\ with the following entry for the name:
routing.serviceName: <Bezeichnung>.
Elasticsearch is preconfigured so that access to the microservices 'index' and 'search' is only allowed if they are installed on the same computer as Elasticsearch. If this is not the case, the addresses of these microservices must be entered in the following Elasticsearch configuration file:
…\Elasticsearch\config\elasticsearch.yml
Parameters: intrafind.security.subnet
© Copyright OPTIMAL SYSTEMS 2020. | Legal and Data Privacy