...
If necessary to create additional localhost Endpoint, then click the Create button to create a new Endpoint. You can edit an existing localhost Endpoint by clicking on the desired row. Update the required fields as defined in the table below.
...
Field Name | Required | Description |
|---|---|---|
Endpoint Name | Yes | The name of the Endpoint. |
Description | No | An optional description for the Endpoint. |
Active | Yes | Whether or not the endpoint is active in the system. Defaults to "Yes". |
Connection Type | localhost | |
Base Directory | Yes | A working directory on the Endpoint used by FlexDeploy. ~ is not supported here. Working directory under /var/tmp or /tmp folder is not recommended as administrators generally have cron jobs to purge files based on age and that will cause issues when plugin files are deleted. For example, Error: Could not find or load main class flexagon.fd.core.plugin.ExternalPluginServer will be encountered when plugin lib files are deleted. |
JDK Home | Yes | The JDK Home directory on the Endpoint. |
Source Script | No | An optional script executed right before plugins are executed on the endpoint. Some usages of this script include sourcing an environment file (ie: . $HOME/mfile.env) or exporting a variable (ie: export FLEXAGON_FD_PLUGIN_JAVA_ARGS=”-Xmx1024m -Djava.io.tmpdir=/var/tmp”). Variables exported here will become available to plugin executions on this endpoint. |
...
Optionally, click the Test Connection button to validate that the FlexDeploy server can connect to itself properly. This will verify the Base Directory and JDK Home settings.
...