As of January 1st 2021, WebLogic is no longer a supported application server for new customers. We will continue to support existing customers who have installed on WebLogic 12.1.3, but recommend that they move to Tomcat. WebLogic 12.1.3 is no longer supported by Oracle and Flexagon has no plans to support newer versions of WebLogic.
Tomcat 9+ (Tomcat 9.0.34 was rigorously tested, and therefore, recommended). If you follow Installing FlexDeploy with Tomcat, you do not have to separately install Tomcat.
You can allocate 4GB space for install of Tomcat with FlexDeploy. This includes space for logs that will be generated during execution of application. See additional disk requirements below.
We recommend approximately 125GB total disk space should be sufficient for application tier.
FlexDeploy uses a working directory for temporary files to be transferred between the server and its endpoints. This directory needs to have at least 10GB of space available on the FlexDeploy Server.
As this file system contains only temporary files, and plugin jars, 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.
Automated purge process for working directory
3 Plugin Jar versions will be kept.
Temporary Files (work folder) in this directory which are older than one day will be purged automatically to help effectively manage the size.
Plugin Jars are stored in this directory @since 5.5.
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.
The Git executable must be installed on the FlexDeploy server & build endpoints, and it must be accessible in its PATH. The Git executable version must be 1.7.9 or higher.
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.
Unix/Linux (and its variants, such as OEL, RedHat, Solaris, AIX, HP-UX etc.)
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.
Make sure that there is no scheduled purge job setup on endpoint working directory. FlexDeploy will automatically manage this folder.
SSH connectivity from FlexDeploy application tier using the following options
User & Password
User & Password with sudo
SSH key with passphrase
Supported web browsers
FlexDeploy supports following web browsers. We recommend use of latest updates to browsers.