Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note

Important: 

Back

Always 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, verify with ICT & team → OK to remove. ICT agrees.
  • Expand
    titleContents
    toc

    , and review the overall upgrade steps and preparations.

    ...

    Upgrade to Lequinox platform 5.2.0

    Info

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

    Steps

    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.

    ...

      1. For your version upgrade

    ...

      1. , apply any deployment profile changes

    ...

      1.  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.
    1. Go to the extracted release folder.

    2. Stop any running WildFly instance:

      Code Block
      languagexml
      > 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 (so far, 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.

    ...

    languagexml

    ...

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

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

      Code Block
      languagexml
      > python deployment/generate_configuration.py -p <profile> -d lequinox -f </path/to/config_directory>/config.properties
    3. Run the pre-deploy upgrade script:

      Code Block
      languagexml
      > python deployment/upgrade_pre_deploy_config_all.py -p <profile> -d lequinox
    4. 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
      languagexml
      > python deployment/start_jboss.py -p <profile>
    5. Configure WildFly (the script adds datasources, enables HTTPS etc.):

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

      See jboss_config_all.py for limitations.

    6. Deploy new artifacts from current release directory:

      Code Block
      languagexml
      > python deployment/deploy_all.py -p <profile> -d lequinox -a .
    7. Run post deploy upgrade script:

      Code Block
      languagexml
      > python deployment/upgrade_post_deploy_config_all.py -p <profile> -d lequinox
    8. Check the status of running services on "https://<FQDN>:<PORT>/status".

    9. The upgrade of the Lequinox platform is complete.

    10. Revisit the recommendations regarding backup and security, there might be new information since your first installation.