This page contains the preparations needed before installing a Lequinox platform on a Red Hat Enterprise Linux or CentOS operating system.
During the preparations you will need a certificate-key-file.
...
Make sure your server environment meets the /wiki/spaces/LPSA510/pages/1671898 system requirements for the version you are about to install.
...
Python is required to run our deployment scripts. Please refer to /wiki/spaces/LPSA510/pages/1671898 system requirements for the latest required version.
When you come across the execution of Python scripts, ‘python’ should be replaced with the path to your Python 3 installation directory.
Provide database access
1. Make sure a database admin user can log on to the database server using username and password.
...
- Xms and Xmx control the JVM memory allocation, and should be tuned based on your need. See the official Oracle documentation on JAVA_OPTS for more information.
- jboss.bind.address configures which IP address the application server will listen on.
- The config.path parameter should point to where the generated configuration file will be placed. The path is generated during the install, and the files are generated based on the profile configuration (see step Generate a new configuration file in the Install section).
- jdk.tls.ephemeralDHKeySize specifies the ephemeral Diffie-Hellman key size. We recommend setting this to matched. See the official Oracle documentation on Java Secure Socket Extension (JSSE) Reference Guide for more information.
For more information on JVM parameters, consult Oracle's documentation.
3. Add your certificate-key-file, for example /etc/pki/wildfly/https/example-keystore.p12, to the server. This keystore needs to contain the certificates used to enable HTTPS. Configuring WildFly to collect the keystore is done in the Deployment profile.
...
| Info |
|---|
| Python may be included in the OS, and psql should be included in the database server. Note that the Python version included might not be the required one. Refer to our /wiki/spaces/LPSA510/pages/1671898 system requirements for information on the correct version. |
...
Prepare the target machine
1. Copy and extract the installation package to the target machine.
2. Set up a directory for the archive_service filestore, and give the WildFly user read and write access.
| Info | ||||||
|---|---|---|---|---|---|---|
A release of the Lequinox platform contains, among other things, deployment scripts and deployment profile files. You will run the /wiki/spaces/SARES/overview during the installation of your Lequinox platform. In order for the scripts to work on your specific system, you need to supply your own details in the files to set up your deployment profile. |
...
| Info |
|---|
| During the installation you will need to add a URL to a National node. A list of public National nodes is found here. |
Your deployment profile
1. Go to the profiles directory in the deployment script directory: <tarball extract directory>/deployment/profiles/
...
| Info |
|---|
| Make a note of where you keep the backup, as having this at hand will save time during future upgrades. Using your previous deployment profile as a starting point, you will not have to make all the changes in step 3 for each upgrade. When upgrading, you will only have to apply any changes mentioned in /wiki/spaces/LPSA510/pages/1672020 deployment profile changes to the files in your own amended profile. |
...
Install your Lequinox platform
You are now ready to run the Lequinox deployment scripts. To do so, follow the instructions to install the Lequinox platform to the point.
...