...
- 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 yuuvis 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 yuuvis (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 yuuvis (dms-service), as well as the credentials of the database user designated for yuuvis into the corresponding fields.
- Under "Enter enaio rendition-plus parameter ", enter the IP address and the port of the server that hosts yuuvis 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.
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'
spring.elasticsearch.rest.uris: '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 Directory:
- 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.
...