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.
...
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 administrator 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.
...
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.
3. Give the WildFly user read and write access to the folder where the Lequinox console will store the secret keys used to secure users' passphrases (parameter consoleplus_secret_keys_path in the <tarball extract directory>/deployment/profiles/default/console_plus.properties file). Verify with devs, OK with ICT.
| Info | ||||||
|---|---|---|---|---|---|---|
A release of the Lequinox platform contains, among other things, deployment scripts and deployment profile files. You will run the deployment scripts 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/
2. Copy and rename* the default profile. That is, copy all the contents of the ‘default’ directory to your own deployment profile directory. Do not remove the default profile from the target directory. Verify wording with devs (ICT says it can be removed, although good to have as a fall-back if you make a typo in some parameter).parameter. Devs have no strong opinion on this. "It depends on how we write that they should do when upgrading. The fallback solution with the default profile, is intended to make it easier since in your own profile, you only need to include the parameters you need to and want to change. So, if we add a new parameter with a default value and if you are content with that value, you don't need to do anything during an upgrade except replacing the default profile. But now that we write that they should copy the entire default profile to their own, it doesn't quite work that way. Also, when we ask them to copy the default profile to their own, parameters that they are not to tamper with are included. For example ”artifact”, which we have for all components. On these we write ”Caution! Do not change.”. And if we do change one of these,, our customers themselves must make the same changes in their profiles, which is something of a hassle. But we probably will not change that recommendation just like that." Should we let them decide, and explain the implications of both alternatives? Decision:
3. Go through all the .properties files in your renamed profile directory, and set all UNCONFIGURED values. Also, change any other default settings if you prefer a different setup or if your environment requires additional adjustments.
...
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.
...