Database Tier Requirements

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
• MySQL 8
• Oracle XE, version 11.2, 18
• Oracle Standard, version 11.2, 12.1, 12.2
• Oracle Enterprise, version 11.2, 12.1, 12.2

Requirements

• 4 to 8 GB of RAM for the system.
  • Oracle database - 2GB SGA should be sufficient.
• 1 or 2 CPU
• At least 20 GB of available space, may need additional space based on purge criteria and usage.

Application Tier Requirements

Supported Platforms

• Unix/Linux (and its variants, such as OEL, RedHat, Solaris, AIX, HP-UX etc.)
• Microsoft Windows

Supported Application Servers and Requirements

FlexDeploy is a Java web-based application which runs on the following application servers:

• WebLogic 12.1.3 (license is not included with your FlexDeploy subscription)
  • WebLogic 12.1.3 including JRF (ADF Runtime) 12.1.3 (See WebLogic 12.1.3 Installation Scripts for installation and configuration of WebLogic 12.1.3 domain)
  • 8GB of RAM, consider additional memory for AdminServer if on same host.
  • 1 CPU
  • JDK 1.7.0+ (Use latest patch for JDK 1.7, for additional certifications, see 12.1.3 Certification Matrix)
• Tomcat 8+
  
  • Tomcat 8+ (Tomcat 8.5.x was rigorously tested, and therefore, recommended). If you follow Installing FlexDeploy with included Tomcat, you do not have to separately install Tomcat.
  • 8GB of RAM
  • 1 CPU
  • JDK - refer to http://tomcat.apache.org/whichversion.html for selecting. Tomcat 8.5.x was tested with JDK  1.7_67, 1.8_60 and 1.8_101.
  • When using MySQL database, JDK 8 is required.

Disk Requirements

Working Directory

FlexDeploy uses a working directory for temporary files to be transferred between the server and its endpoints. This directory needs to have at least 4GB of space available on the FlexDeploy Server.

• As this file system contains only temporary files, there is no reason to backup this directory.
• Availability of space within the server working directory is critical to functioning of the FlexDeploy platform. Therefore, the filesystem should be monitored and space should be allocated as necessary. In addition, it is recommended that this be a separate mount point.
• Files in this directory which are older than one day will be purged automatically to help effectively manage the size.

Artifact Directory

The FlexDeploy artifact repository is a directory available on the FlexDeploy server where all build artifacts are stored, and later retrieved for the deployments. This directory needs to have at least 10GB of space available on the FlexDeploy Server.

• Due to the importance of the artifact repository, this file system should be backed up regularly.
• Availability of space within the Artifact Repository is critical to the creation of new build versions. It is highly recommended to have a file system size monitor in place for this directory, and size should be adjusted based on the number of builds created, and the size of the artifacts produced. In addition, it is recommended that this be a separate mount point.

Source Control Requirements

FlexDeploy provides out of the box integration with the following Source Control Management Systems.

• Subversion
• Git
• Microsoft TFS

• Perforce

• CVS

• IBM ClearCase UCM

• PVCS

Endpoint Requirements

An Endpoint is a target server where FlexDeploy can perform build or deploy activities. Endpoints are configured within the FlexDeploy UI. See following requirements for each Endpoint.

Supported Platforms

• Microsoft Windows. For Windows endpoint, CygWin must be installed on target server - see FlexDeploy Cygwin Install Guide.
• Unix/Linux (and its variants, such as OEL, RedHat, Solaris, AIX, HP-UX etc.)

Requirements

• JDK version 1.6 or higher must be installed.
• Some plugins require Java 7 or 8. 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.
• SSH connectivity from FlexDeploy application tier using the following options
  • User & Password
  • User & Password with sudo
  • SSH key
  • SSH key with passphrase