...

1. Copy and extract the release package to the target machine.
2. 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.

      Note
      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.

      
      

3. Go to the extracted release folder.

4. Stop any running WildFly instance:

   Code Block
   language xml
   > python deployment/stop_jboss.py -p <profile>

   
   

5. 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 that this entire step can be removed in 5.2.0, since no one is upgrading from 4.1.0 or earlier.

   Code Block
   language xml
   <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>

   
   

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

7. Generate a new configuration file (config.properties):

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

   
   

8. Run the pre-deploy upgrade script:

   Code Block
   language xml
   > python deployment/upgrade_pre_deploy_config_all.py -p <profile> -d lequinox

   
   

9. 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>"): 

   Code Block
   language xml
   > python deployment/start_jboss.py -p <profile>

   
   

10. Configure WildFly (the script adds datasources, enables HTTPS etc.):

    Code Block
    language xml
    > python deployment/jboss_config_all.py -p <profile> -d lequinox

    See jboss_config_all.py for limitations.
    
    

11. Deploy new artifacts from current release directory:

    Code Block
    language xml
    > python deployment/deploy_all.py -p <profile> -d lequinox -a .

    
    

12. Run post deploy upgrade script:

    Code Block
    language xml
    > python deployment/upgrade_post_deploy_config_all.py -p <profile> -d lequinox

    
    

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

Post upgrade tasks for users previously on 5.1.0 (Move to internal confluence)

In our continuous work to improve your user experience, we are currently phasing out Lequinox professional ID for platform interaction. Hence, we strongly recommend that for each ‘Professional ID-based’ role account in your organisation, you create a new role account so that they can sign in with name and password instead of Lequinox professional ID.

...

1. Go through your users one by one, and note their registered names and email addresses.
2. Add a new role account for each user. 
3. Verify that they act on the invitation email and activate their new account.
4. Repeat item 1–3 for each Professional ID-based role account.

...