FDJDEV_INSTALL_HOME

Yes

The JDeveloper installation directory. You can control Build instance associated with your project, which effectively controls which version of JDeveloper is used for build operations.

FDJDEV_INP_APP_SOURCE_FOLDER

No

The folder where source is checked out. Leave it blank if you did not use any sub-folder to checkout/export source.

If you are using SubVersion and Source is defined on Project configuration, you can use FDBLD_SVN_SOURCE1_CHECKOUT_FOLDER variable.

FDJDEV_INP_APP_DEPLOY_PROFILE

No

The application deployment profile name.

Default is the name of the JDeveloper JWS file in exported or checked out source. So if you keep application profile name same as JDeveloper application name then you can skip this input.

FDJDEV_INP_APP_ARTIFACT_FOLDER

No

Folder name relative to the application where the EAR file will be generated.

Default is the deploy folder, if you do not supply any value here. This is default when you create new Application deployment profile as well.

FDJDEV_INP_APP_SYNC_JDBC_RESOURCES

No

Indicate if the EAR file should have generated WebLogic JDBC xml files.

Default would be false, so by default EAR file will not have any WebLogic JDBC xml files, which allows easy deployment to remote WebLogic server, but you will have to manage the Data Source using WLST or the Administrative console. You can also use the FlexDeploy WebLogic Plugin to manage data sources in automated manner.

FDJDEV_INP_OVERRIDE_FILE_PATTERN

No

Specify {FileName}={OverrideFileName} pattern. Matching files will be replaced by override files and Property replacement logic will be executed as well. For example, web.xml=fd-web.xml.

FDJDEV_INP_SAVE_ARTIFACTS_EXTENSIONS

No

Specify comma separated extensions to be copied to artifacts after build. For example ear, mar etc. (Defaults to ear). You can use mar to capture metadata archive files.