Skip to content

Replication of changed data

Updating ElasticSearch-Indices can be done in two ways which can be configured in wildfly\standalone\configuration\insight.properties

  1. Via JMS/MessageQueue since insight v2.8

    • indexer.changereader=false

  2. Polling table GISTX before v2.8. Polling is deprecated since v2.8

    • indexer.changereader=true

GISTX table

Data exchange between open-AppServer and Insight Indexer / ElasticSearch works on base of table GISTX:

  • Generate the export-sets and activate the generates.

    • Class/Table GISTX have to exist

  • Deactivate recording changes on table GISTX

    • Start “Objekthistorie: Administration”
    • Add table gis.base.insight.GISTX to “Negativ-Liste”

Polling from Insight

The insight-indexer-application located in Insight-WildFly polls for changes in GISTX periodically.

Sending to Insight

GISTX entries are send to the insight-indexer application in Insight-WildFly.

Configuration:

1) Registry entry for the target-URL to the insight-indexer application in Insight-WildFly:

  • Registry path: /de/ibfs/insight/change/insightChangeUrl (If the target url is empty no changes from GISTX will be send).

Logo

Registry path:

de/ibfs/insight/change/insightLoginUrl
/de/ibfs/insight/change/insightUser Insight login user
/de/ibfs/insight/change/insightPw Insight login password

(If the login url is empty no authentication will be performed).

Logo

2) Registry entry for ObjectLogging:

  • Registry path: /de/ibfs/insight/change/enabled (If enabled expanded change data will be send to the insight-indexer application)

Logo

Without configuration, all changes in open will be transferred to Insight/Elasticsearch. All object types without logging must be written manually into the file "OPEN/etc/insightObjectLoggingType_blacklist.csv" on the open server. You can read all known object types in file "OPEN/etc/insightObjectLogging_all.csv" on the open server. "insightObjectLogging_all.csv" is updated on every start of the extension InsightTransactionService.

IMPORTANT: You have to write the GISTX class to insightObjectLoggingType_blacklist.csv!