Full Deployment Projects

To create a project for Full Deployment, right-click on the newly created application and select Create Project
 




Enter a name and description for the project. Leave the Partial Deployments checkbox unchecked, and check EBS as the Project Type. Click the OK button to create the project. The newly created project will be opened in the editor.

Click the light-blue Configuration tab to enter the required configuration.

Enter the configuration information as shown in the image above.

  1. Enter the SCM type for your project
  2. Select the build workflow that was created for EBS
  3. Select the build instance on which to run the builds
  4. Select the deploy workflow that was created for EBS
  5. Select the your target EBS instance(s)
  6. Select the SCM instance containing the EBS customizations for this project
  7. Enter the required attributes for your SCM source code. Additional information on the SCM configuration is available in the FlexDeploy User's Guide.

Click Save to save your changes.

Click the purple Properties tab to enter further configuration. 



Enter the Project Properties information as shown in the image above.

  1. Enter values for the project property that are relevant to your EBS Module. Notice the EBS Module Application Short Name property (FDEBS_APPLICAITON_SHORT_NAME), if you are deploying a module. If your folder structure in SCM matches the standard folder structure given in the EBS Plugin guide appendix, you can ignore the properties for *ROOT_SOURCE_DIR and *DESTINATION_SOURCE_DIR. Otherwise specify your folders. For destination folders, you can use environment variables defined in the .env script (e.g. $JAVA_TOP).
  2. Click the Save button to save your changes

For more information regarding Project Properties refer to the EBS Plugin Guide.

Configure EBS Objects and their Attributes

For full EBS deployments, you will have an additional Project Files tab, denoted by the  icon. This tab gives you the ability to define the EBS files (candidates for creating packages) and verify their metadata attributes. You can also edit these attributes and build/deploy commands as required. Typically for full EBS Deployment the Project Files tab is used to override the Deployment Command for specific files, instead of using the Populate from Subversion feature.

Note: You can choose to restrict these configurations to an Apps DBA group (or other) if desired. Review the Security section of the FlexDeploy User's Guide for more information.

For more information on the Populate from Subversion functionality, refer to the Configure EBS Objects for Partial Deployment section.

Source AOL files directly from EBS instance

You can directly create files by clicking on the Create button. This is useful if you would like to download AOL files from the source EBS instance at build time rather than sourcing from the SCM. To create a reference to an AOL file, click on the Create button.


 

The following form will be presented to create the new file. Enter the file name you would like to create (eg: XXHR_MNU_001.ldt – extension is required) and click the Evaluate button. By default, it generates all details for a Concurrent Program. If your AOL is another type, select the type from the Type dropdown and click Evaluate again.



  1. Enter the name of the file with extension
  2. Select the Source from the drop down. Eg: SCM
  3. Click on Evaluate button
  4. Verify all the details (change as needed) and click OK. (you can re-evaluate the calculated fields after modification by selecting the Keep Current Value checkbox, and clicking Evaluate).

Next step      Back