Page Comparison

...

Elasticsearch

• Double-click to start the setup
• Follow the dialogs in the setup.
• Under HTTP-Port, you can configure the elasticsearch service port. The preset of 9200 is the typical default. You should only change it if you have a good reason.
• The data directory will contain the indices files, e.g. the fulltext database. We recommend using fast memory, or, ideally, an SSD memory.
• Complete the setup, but do not start the service yet.
• Start the services:
  
  • In the directory <Elasticsearch>\bin, run "elasticsearch-service-x64w.exe".
  • (Optional) In the "Log On" tab, add the technical (Windows) user for the server.
  • (Optional) In the "Logging" tab, modify the log path.
  • (Optional) In the "Java" tab, modify the assigned memory. The start value ("Initial memory pool") and the maximum value ("Maximum memory pool") must always have the same value. We recommend using at least 8192 MB.
  • In the "General" tab, click "Start" to start the server.
  • To activate an automatic restart in case of failure, open the Windows Services manager, then open the elasticsearch service properties and under "Restore" select "Restart service" for each error type.
• Modify the Data Directories:
  • In the directory <Elasticsearch>\config, open the elasticsearch.yml file.
  • Modify the path.data entry to the desired path.
• Modify the Log Directories:
  • In the directory <Elasticsearch>\bin, run the "elasticsearch-service-x64w.exe" file.
  • In the Logging tab, modify the log path and, if desired, set up or change the redirects for Stdout and Stderr.
  • In the directory <Elasticsearch>\config, open the elasticsearch.yml file.
  • Activate the line "#path.logs: /path/to/logs" by removing the #, and enter the desired path to the log file.

...

• Wenn der enaio Service-Manager Dienst auf dem selben Server läuft, muss dieser vor der Installation angehalten werden.
• Das Elasticsearch 5.5 stoppen
• Datenverzeichnis sichern
• Elasticsearch 5.5 deinstallieren
• Elasticsearch 6.3 installieren, dafür elasticsearch-6.3.0.msi starten
• Den Dialogen des Setups folgen und data, log, config- Verzeichnisse konfigurieren
• Elasticsearch als Service installieren
• Den Name vom Cluster (empfohlen „es-red“) konfigurieren 
• ICU-Plugin auswählen und installieren 
• Setup abschließen
• Den Dienst noch nicht starten.
• Pluginverzeichnisse anpassen:
  • Linguistic-Plugin und Security-Plugin in das Plugin-Verzeichis kopieren
    
  • Die Datei java.policy in das Verzeichnis <Elasticsearch>\config kopieren
  • Die Datei intrafind.yml in das Verzeichnis <Elasticsearch>\config kopieren und die IP-Adressen, die das Elasticsearch "sehen" dürfen, eintragen. 
    Es sollte mindestens die IP-Adressen des Service-Manager Servers und des Elasticsearch Servers eingetragen werden. 
  • Im Verzeichnis <Elasticsearch>\config die Datei jvm.options um die folgende Zeile (mit dem Pfad zu java.policy vervollständigen!) erweitern:
    -Djava.security.policy=<Pfad_zu_java.policy>
    Bsp.: -Djava.security.policy=C:\enaio\elastic\config\java.policy
  • Im Verzeichnis <Elasticsearch>\config die Datei elasticsearch.yml um die folgenden Zeilen erweitern:
  • http.type: if-netty4
    network.host: [_site_, _local_]
    script.max_compilations_rate: 300/1m
• Den Dienst starten.

Service-Manager

• Double-click to start the setup.
• Follow the setup dialogs.
• Under HTTP-Port, you can configure the service-manager services port. This port has no special significance but should only be changed if the default port (7281) is already being used.
• Under "Enter enaio dms-service parameter", enter the IP address of the server that hosts the dms-service. (Important: do not use localhost; always use IP-addresses that are externally-visible.) Also enter the credentials of the enaio user (technical user) with whom the service-manager will connect to the dms-service. Usually this is root / optimal.
• Under "Enter database parameter" at "database server" enter the IP address under which the database used for enaio (dms-service) can be reached. You may need to modify the port (1433 is generally correct for MSSQL databases)..
• Enter the database name of the database used for the enaio (dms-service), as well as the credentials of the database user designated for enaio into the corresponding fields.
• Under "Enter enaio rendition-plus parameter ", enter the IP address and the port of the server that hosts enaio rendition-plus. rendition-plus does not yet have to be installed. If a different port is selected during installation of rendition-plus, you must enter it instead of the default 8090.
• Complete the setup but do not start the service yet.
• (Optional) In the file <service-manager>\config\servicewatcher-sw.yml, modify the memory allocation and instances for the individual services. Note: If a service is allocated more than 1.5 GB of memory, you must set the parameter "arch: x64" for this service, to activate the support for 64 bit.

• In the "<service-manager>\config\gateway-prod.yml" file, you can adjust the authentication mechanism for the services. You can also define additional (external) end points as follows:

  routing.endpoints name: 'custom' url: 'http://localhost:4321'

  
  

• If a file with a patch-level version > 0 is in the <enaio_redline_setup>\enaio_redline_client directory (in a client-3.xy.z.zip, the z is the patch-level version), it means a subsequent hotfix for the client exists. You can install it as follows:
  • From the <enaio_redline_setup>\enaio_redline_client folder, copy the client file with the highest patch level to <service-manager>\tools.
  • In the folder <service-manager>\tools\sam, open a command line window and enter the command "sam update..\client-3.xy.z.zip", substituting xy.z with the respective version.
    
  Install the Structure-Service:
  
  • In the <service-manager>\apps folder, create a new folder called "structureservice" and unzip the contents of StructureService.zip there.

  
  

• If the elasticsearch installation is on a different machine than the service-manager installation please edit the <service-manager>\config\application-es.yml file and replace the 127.0.0.1 IP with the IP of the elasticsearch machine in the following lines:

  spring.data.elasticsearch.cluster-nodes: '127.0.0.1:9300' spring.data.elasticsearch.cluster-nodes-rest: '127.0.0.1:9200'

  
  

• Start the services:
  • In the <service-manager>\bin directory, run "enaio_red_service-managerw.exe".
  • (Optional) In the "Log On" tab, enter the technical (Windows) user.
  • (Optional) In the "Logging" tab, modify the log directory.
  • (Optional) In the "Startup" tab, modify the port again. You can also modify the services.log location.
  • In the "General" tab, click "Start" to start the server.
  • You can see an overview of the running services at http://<ip>:7273. This is the Spring Boot Admin service. It can be used to permanently monitor the services.
  • It can take several minutes for all the services to start successfully.
  • "Connection refused" exceptions appearing in the service-manager log file in the first few minutes are nothing to worry about.
• Modify the Data Directories:
  • In the <service-manager>\bin directory, run the enaio_red_service-managerw.exe file.
  • In the "Java" tab, under Java Options, set the temp directory with the JVM option Djava.io.tmpdir. You can use the options –Dcatalina.base and –Dcatalina.home to set the Tomcat work directories.
  • In the directory <service-manager>\config, open the application-prod.yml file and modify enaio.data.path. The relative path to the .jar files is <service-manager>\apps\<*service>. If you use './../..', you end up in the service-manager root directory.
• Modify the Log Directories:
  • In the <service-manager>\bin directory, run the enaio_red_service-managerw.exe file.
  • In the "Logging" tab, modify the log path and, if desired, set up or change the redirects for stdout and stderr.
  • In the "Startup" tab, modify the "--logging.file" argument. The relative path to the .jar files is under <service-manager>\apps\<*service>. Use './../..' to point to the service-manager root directory.
  • In the <service-manager>\config, open the servicewatcher-sw.yml file and in the "logging" section, modify "file". The relative path to the .jar files is under <service-manager>\apps\<*service>. Use './../..' to point to the service-manager root directory.

...