Versions Compared

Key

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

...

Properties sent from FlexDeploy can be overridden by adding a FlexDeployPropertiesOverride.properties override file to the <Agent home>/config folder. There is an example file included with the installation.

Info

The values in a properties file will be encrypted.

The purpose of this file is to not have to store the passwords in FlexDeploy and have them passed over HTTPS. They are only locally on this endpoint.

This properties file uses Java properties file syntax. The key is the code of a property, the value is the value to use when overriding. Take a look at these examples: code

...

FDEBS_APPLICATION_SHORT_NAME=XXHR
FDEBS_SQL_RETRY_COUNT=25

Now when the EBS Plugin is executed against this endpoint, the value of FDEBS_APPLICATION_SHORT_NAME will be XXHR, and the value of FDEBS_SQL_RETRY_COUNT will be 25 no matter what value was set in FlexDeploy itself.

This will work for project properties, but for Target or Integration account properties there is a slightly different syntax. Put the code for that Target (or integration) a dot and then the name of the property. The value is the value that the property should be. See this example:

Code Block
EBS.FDEBS_DB_PASSWORD=databasepassword
MY_GIT_ACCOUNT.FDGIT_PASSWORD=gitpassword

Now the EBS password for the EBS Target and the git password for MY_GIT_ACCOUNT will be overridden.

This file is read in during each plugin execution, so no restart of the agent is required when updating the file.

An encrypted value will look something like this:

Code Block
EBS.FDEBS_DB_PASSWORD=#ENC#aeworuowpitydhnca

To change the value, simply overwrite the encrypted value. The next time a plugin is executed on the endpoint or after a small period of time it will be encrypted automatically.

setenvoverride File

If a setenvoverride.sh (or setenvoverride.bat) file is included in the <Agent home>/config folder, it will be run before tomcat is started in order to configure some environment variables. The following variables are supported.

Variable

Description

JAVA_HOME

The Java path where Tomcat will be run from. This is distinct from the Java path used in the endpoint configuration. The agent will attempt to derive this value from the system path, but sometimes that doesn’t work correctly. You can set it here to override that.

FD_MAX_MEMORY_SIZE

This will set the maximum memory size for the Tomcat server. Will be forwarded as the -Xmx java argument. If none is set defaults to 2048m.

FD_INITIAL_MEMORY_SIZE

This will be set the initial memory size for the Tomcat server. Will be forwarded as the -Xms java argument. If none is set defaults to 512m.

FLEXAGON_FD_JAVA_ARGS

Any extra Java arguments.

FD_AGENT_PROPERTIES_PASSWORD

This property is used to encrypt the properties file. However it is not recommended you set this environment variable here as it will be available in plaintext then.

Examples

Linux

Code Block
JAVA_HOME=/u01/java/jdk1.8.0_361
FD_MAX_MEMORY_SIZE=4096m
FD_INITIAL_MEMORY_SIZE=1024m
FLEXAGON_FD_JAVA_ARGS=-Dthis.is.an.argument=test

...