About the automated Install/Migration tool

The flexdeployerinstaller.sh script is an automated process that reduces efforts for installing or upgrading FlexDeploy. There is a configuration file which will need to be configured for your installation, and then the installer can take over.  There are three basic modes to the installer: 1) prerequisite checking with no installation or upgrade, 2) first time installation of FlexDeploy and 3) upgrading a current installation of FlexDeploy. You choose prereqs mode with the -p argument. Upgrade or install is selected by the presence of the FlexDeploy war in the webapps folder. If you are upgrading Weblogic, use the -w argument.

The apache-tomcat-flexdeploy folder will be cleaned up with each upgrade, so it is important not to place any supporting files in the apache-tomcat-flexdeploy folder. Place them in the FLEXDEPLOY_HOME folder or another subfolder instead. Example of such files may include the SSO configuration file, Keystore and/or Wallet files.

Versions / Release Notes

The current version is 1.0.1718. You should always download the latest version before running another install or upgrade. See the Installer Release Notes for more information.

This automated installer will handle

• executing prerequisite checks to ensure the installation/upgrade will be successful

• downloads of FlexDeploy software and influx database software if the server has access to the Internet

• installation of FlexDeploy 5.7.0.12+

• upgrading from version 5.1.0.0+

• upgrading to FlexDeploy 5.7.0.12+

• backing up the current FlexDeploy installation, plugins, and optionally artifacts before upgrading

• backing up the database before upgrading (optional)

• creating or migrating the FlexDeploy database schemas

• installation or configuration of the influx database which is used for reporting and dashboard data for FlexDeploy version 6.0 and higher.

This automated installer will not handle

• downloads of software if the server has no access to the Internet. In this case, the files need to be placed on the FlexDeploy server in locations specified by the installer

• download of security wallets

• upgrading a Kubernetes installation

• install or upgrade on Windows

Installer arguments

The following arguments are available to be used:

• -p run the installer in the prerequisite checking mode. There will be no installation/upgrade performed when using this flag, so it can be run anytime.  If the installer detects any issue(s), those will be reported to the logs and displayed on the screen.  The prerequisites will also be run during the installation or upgrade process and may stop the process, which is why it is recommended to run this mode until there are no issues being reported.  Each issue that is reported will have a possible resolution to the issue to assist you in resolving it.  Some of the checks are: verify file system sizes to make sure all required directories have at least the minimum amount, flexdeployinstaller_config.txt file properties are set, java is at the right level, etc. Removing this argument will execute the install/upgrade.

• -v version Tells the installer what version to install. You can specify versions as 4 numbers separated by periods, or the word latest. (Required argument)

  • See http://support.flexagon.com or http://wiki.flexagon.com to find details on latest or specific version. Few examples of specific versions are 7.0.0.5, 6.0.0.0 etc.

  • If you are planning to upgrade or install more than one FlexDeploy instances, then make sure to use specific version instead of word latest as meaning of latest will change over time.

• -c <path to>/flexdeployinstaller_config.txt points the installer to the flexdeployinstaller_config.txt file that contains the user configurations. (Required argument)

• -s there are several passwords in the flexdeployinstaller_config.txt file and if a password field is left blank, in this scenario, a prompt for the password will happen (nothing will be stored) and the password is not shown on the screen, similar to other Linux password prompts.  The -s option will show the password on the screen as you type.

• -i skip the database backup. This can be done if you have an existing database backup.

• -a skip the artifacts backup. This can be done if you have an existing backup of the artifacts folder or a snapshot of the VM.

• -d Install as a docker container.

• -w Specify that you are upgrading from a WebLogic install to a Tomcat install. Not compatible with the -d option.

Step by Step Guide to Using the installer

Step 0: System Requirements

See FlexDeploy System Requirements for details on software and hardware requirements. See FlexDeploy Architecture for architecture details.