Supported Platforms

• Microsoft Windows

• Unix/Linux (and its variants, such as OEL, RedHat, Solaris, AIX, etc.)

Supported Databases

FlexDeploy requires one of the following databases to be installed and running.

• PostgreSQL 11, 12, 13, 14

  • Requires a user with CreateDB privileges or superuser privileges. Prior to FlexDeploy 6.0.0.2, superuser was required.

• Oracle XE, version 18, 19, 21

• Oracle Standard, version 12.1, 12.2, 18, 19, 21

• Oracle Enterprise, version 12.1, 12.2, 18, 19, 21

• JDK version 1.6 or higher must be installed. Java is required for Endpoints. See Plugin Java Requirements for details.

• Typically FlexDeploy references the actual JAVA_HOME folder, or the java version that is used by the technology that is being deployed (if any)

  • The JDK Home can be a symlink if desired to make Java upgrades easier. A symlink is not required or preferred by FlexDeploy, but works.

    • On Windows, a symlink can be created with the mklink /D <target> <source> command where <target> is set as JDK Home in the endpoint settings of FlexDeploy, and <source> is the actual Java install location.

      • If the Java install path is changed, then use rmdir <target> to delete the symlink. Then recreate the symlink with the new <source> folder.

    • On Unix, a symlink can be created with the  ln -sT <source> <target> command where <target> is set as JDK Home in the endpoint settings of FlexDeploy, and <source> is the actual Java install location.

      • If the Java install path is changed, then use rm <target> to delete the symlink. Then recreate the symlink with the new <source> folder.

• Some plugins require newer versions of Java. Please see the plugin guides for this information.

• Disk space on each endpoint of 4GB to be used as temporary working directory. You can start with 1GB space and expand as necessary.

  • There is no need to monitor this file system as FlexDeploy will automatically perform cleanup.

  • Local disk storage is preferable, but a shared file system can be used.

  • As this file system contains only temporary files, there is no reason to backup this directory.

  • Files in the working directory are transient in nature and will be purged by FlexDeploy after one day. The actual size of the directory will depend on the number of projects and deployments, but 1GB is a good starting point.

  • Make sure that there is no scheduled purge job setup on endpoint working directory. FlexDeploy will automatically manage this folder

• Optionally, rsync can be installed on BOTH, the endpoint and the FlexDeploy host and expect can be installed on the FlexDeploy host if you wish to use the rsync protocol to transfer files instead of using scp. SCP is the default transfer method.

• HTTPS or SSH connectivity from FlexDeploy application tier using one of the following options

  • HTTPS

    • User & Password

  • SSH

    • User & Password

    • User & Password with Privilege Escalation (sudo, pbrun etc.)

    • SSH key

    • SSH key with passphrase

    • See Supported

    Algorithms

    • algorithms for SSH

    FlexDeploy supports the following ciphers

    • for SSH connections.  FlexDeploy will automatically negotiate this with the SSH server on the endpoint

    .

    • See Supported algorithms for SSH for information on what SSH algorithms are supported.