Important:

Back up your database before upgrading.
Review any deployment profile changes before proceeding with the upgrade (see Upgrade to Lequinox platform 5.2.0, step 2). Does this need to be included in this warning? It is in upgrade step 2, which should suffice, ICT agrees, ok to remove, verify with ICT & team. Verified.

Contents

Upgrade to Lequinox platform 5.2.0

For more information on deployment scripts, go to the deployment scripts page.

Steps

Copy and extract the release package to the target machine.
Update the deployment profile that you backed up during your previous install:
1. Locate the deployment profile backup from your previous installation.
2. Copy the contents of your backed up deployment/profiles directory to the newly extracted deployment/profiles/ directory on the target machine for your 5.2.0 install.
3. Apply any changes for your version upgrade mentioned on the deployment profile changes page to the files you just copied from your backup to the deployment/profiles directory.
  
  If you did not back up your deployment profile when you did your previous installation, or if you cannot locate it, you need to go through all the .properties files in your deployment profile directory and set all the UNCONFIGURED values. You also need to change any other default settings where you prefer a different setup or if your environment requires additional adjustments.
Go to the extracted release folder.

Stop any running WildFly instance:

> python deployment/stop_jboss.py -p <profile>

If you are upgrading from version 4.1.0 or earlier, you need to manually remove datasource from standalone.xml in WildFly. The following content shall be removed: Verify with team (ok from ICT) that this entire step can be removed in 5.2.0, since no one is upgrading from 4.1.0 or earlier. Verified with devs as well.

<datasource jndi-name="java:jboss/datasources/DtsEventsDatasource" pool-name="DtsEventsDatasource" use-java-context="true">
    <connection-url>jdbc:postgresql://127.0.0.1:5432/events?useUnicode=true&amp;characterEncoding=UTF-8</connection-url>
    <driver>postgresql-jdbc42</driver>
    <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
	<pool>
       	<min-pool-size>2</min-pool-size>
        <max-pool-size>10</max-pool-size>
        <prefill>true</prefill>
	</pool>
	<security>
         <user-name>events_user</user-name>
         <password><password></password>
	</security>
</datasource>

Remove any previous deployed artifacts, .war- and .ear files, from the WildFly deployment directory <WILDFLY_HOME>/standalone/deployments/.

Generate a new configuration file (config.properties):

> python deployment/generate_configuration.py -p <profile> -d lequinox -f </path/to/config_directory>/config.properties

Run the pre-deploy upgrade script:

> python deployment/upgrade_pre_deploy_config_all.py -p <profile> -d lequinox

Start the WildFly server and wait until all services are started. (If changed since last upgrade: point out your configuration file "-Dconfig.path=<path/to/config_directory>"):
```
> python deployment/start_jboss.py -p <profile>
```
Configure WildFly (the script adds datasources, enables HTTPS etc.):
```
> python deployment/jboss_config_all.py -p <profile> -d lequinox
```
See jboss_config_all.py for limitations.

Deploy new artifacts from current release directory:

> python deployment/deploy_all.py -p <profile> -d lequinox -a .

Run post deploy upgrade script:

> python deployment/upgrade_post_deploy_config_all.py -p <profile> -d lequinox

Check the status of running services on "https://<FQDN>:<PORT>/status".
The upgrade of the Lequinox platform is complete.
Revisit the recommendations regarding backup and security, there might be new information since your first installation.

Upgrade Lequinox platform

Upgrade to Lequinox platform 5.2.0

Steps