/
Protocol OpenSearch (tC)

Protocol OpenSearch (tC)

OpenSearch logs are written in a single thread. Taking into account that it is not guaranteed that the execution is successful. Filing and further actions are possible independently, even if the ProtocolService is offline.

The configuration of the properties is done via:

<repo>.protocolservice.document.properties <repo>.protocolservice.container.properties

One index must be created per "action", the same index can be used each time:

<repo>.protocolservice.opensearch.index.<action>=<name>

These actions must be configured:

create, read, update, delete, info

The different indexes may have different retention periods.

If you want to ensure that the log is written, a fallback can be enabled. Then all entries are cached locally.

Configuration parameters in repository.cfg

 

Notes for OpenSearch

By default when starting the OpenSearch server Security and HTTPS is enabled. This may be useful, but for local testing it’s rather a hindrance.
It can be deactivated by editing the file: config/opensearch.yml, adding the following entries:

 

Related content

OpenSearch (tC)
OpenSearch (tC)
More like this
Deployment as WAR / in Tomcat (tC)
Deployment as WAR / in Tomcat (tC)
Read with this
Elastic Search (tC)
Elastic Search (tC)
More like this
Protocol (WS)
Protocol (WS)
More like this
ProtocolAccess Service
ProtocolAccess Service
More like this
Protocol Database (tC)
Protocol Database (tC)
More like this