SAMO LIDS 9 Application Server installation
This chapter describes only differences to the version 8 installation. For complete installation guide of version 9 see Installation Guide
Standalone Tomcat installation
Required versions
Eclipse Temurin OpenJDK 17.0.7.7
- JDK is needed
- You no longer need to install a separate JRE if you are already installing the JDK unless a specific tool or configuration explicitly requires the JRE structure or environment. Since JDK 9 and onwards, Oracle and other vendors no longer provide JREs as separate installs
Apache Tomcat 9.0.85
Installation instructions
Installation is the same as for SAMO LIDS 8 Application installation except these differences
Additional Java 9 startup Options
Opening Packages for Deep Reflection:
--add-opens=java.base/java.lang=ALL-UNNAMED\
--add-opens=java.base/java.util=ALL-UNNAMED\
--add-opens=java.base/java.io=ALL-UNNAMED\
--add-opens=java.base/java.lang.reflect=ALL-UNNAMED\
--add-opens=java.base/jdk.internal=ALL-UNNAMED\
--add-opens=java.management/javax.management=ALL-UNNAMED\
--add-opens=java.management/javax.management.openmbean=ALL-UNNAMED\
--add-opens=java.naming/com.sun.jndi.ldap=ALL-UNNAMED\
--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED\
--add-opens=java.xml.crypto/org.jcp.xml.dsig.internal.dom=ALL-UNNAMED\
--add-exports=java.desktop/sun.awt.image=ALL-UNNAMED
Java Endorsed Standards removed
In case there are problems starting Tomcat, check the Java endorsed startup property.
Former property -D**java**.endorsed.dirs=[tomcat root]\endorsed
must be replaced by -D**ignore**.endorsed.dirs=[tomcat root]\endorsed
JavaMail Attachment Filename Support
By default, the JavaMail library used within the SAMO Application Server does not support attachment filenames longer than 60 characters. To enable support for long attachment names, the following Java options must be set when starting the server:
-Dmail.mime.splitlongparameters=false
-Dmail.mime.encodeparameters=true
-Dmail.mime.decodeparameters=true
-Dmail.mime.encodefilename=true
-Dmail.mime.decodefilename=true
-Dmail.mime.decodetext.strict=false
These settings ensure that long filenames in email attachments are properly encoded and decoded in compliance with MIME standards.
Elasticsearch 8 on premise (Windows Server)
ES 8 is deliverd as a .zip file and just needs to be unzipped on desired location. Inlcuded is already the /config subfolder with elasticsearch.yml and jvm.options for further configuration. Data Folder needs to be defined individually and needs referencing in elasticsearch.yml. Also the other configuration parameters like in ES 6 are included there. Memory settings are done in jvm.options.
run ES as a service
you can configure it as a service with the following steps:
- Open a command prompt and go to "ElasticSearch installation directory"/bin.
- Run the following command:
elasticsearch-service.bat install [ServiceID](ServiceID is an optional id that you can specify to identify the service)
configuration of ES 8
the configuration from ES 6 can't be copied 1:1 to the newer version. Some parameters are not supported anymore, some are changed and some are newly required. Here some simplified, running configuration for a single-node, development solution (not recommended for production):
cluster.name: samo_elasticsearch
node.name: <name of the server>
path.data: E:\elasticsearch-8.13.4\data
path.logs: E:\elasticsearch-8.13.4\logs
bootstrap.memory_lock: false
network.host: 0.0.0.0
network.publish_host: <name of the server>
http.port: 9200
transport.port: 9300
discovery.type: single-node
http.max_initial_line_length: 16kb
action.auto_create_index: .security*,.monitoring*,.watches,.triggered_watches,.watcher-history*,.ml*,.kibana*
xpack.license.self_generated.type: basic
xpack.security.enabled: false
Elasticsearch plugin batch analysis-icu must be installed, run elasticsearch-plugin install --batch analysis-icu.
Important change of ES endpoint
Because there is a change in call ES API, LAS doesn't call https port no more. Instead of it uses http port. When you upgrade to ES 8.x, you need to change lids.search.transportAddress property. This manual counts with standard use of ports (9200/9300 and 11920/11930).
For docker installation (LINUX):
lids.search.transportAddress=elasticsearch:9200 for server properties
lids.search.transportAddress=http://server-xxx.domain:11920 for local properties
For native installation (WINDOWS):
lids.search.transportAddress=server-xxx.domain:9200 for server properties
lids.search.transportAddress=server-xxx.domain:9200 for local properties
Localtron
Switch localtron configuration to use LIDS EAR JSE instead of JEE: localtron.json configuration file - property artifacts.lids_ear.classifier
New licenses
Client applications are licensed using specific licenses. New license file must be generated to include the desired licenses:
- SAMOWEBCLIENT.APPRUN .DOCMAN .WORKPLAN - for dashboard or category dashboard modules, for DMS (DOCMAN), for planning-board (WORKPLAN)
- SAMOLIDSBROWSER.APPRUN - for SAMO LIDS Browser
- SAMOMOBILE.APPRUN - for LIDS Mobile (for Android and iOS), Mobile WFM, SAMO Mobile
- LIDSPBS.APPRUN - for LIDS Publishing Server
For LIDS Edit and LIDS Explorer new licenses are not necessary.
New license model version 40 is needed.
License Server 5.0.7 is needed.
Other steps needed
Synchronize database
SYSTEM TABLES - table LIDS_DBCHANGELOG column MD5SUM will be updated from '8:' values to '9:'