EBS Objects with default source and destination locations.
- Copy Page Tree
- Chandresh Patel
- Rama Rimmalapudi
FlexDeploy provides a platform for building and deploying all common EBS customizations. A key element to the platform is introspecting metadata related to source files, and saving it as project files within the associated project. This reference guide provides details about the metadata, how to influence the metadata generation through project properties, and even how to implement your own generation logic. This reference guide also describes metadata requirements to influence particular behavior within EBS.
When files are populated from a Source Control Management System (SCM), the files are organized into the type of customization they represent. This determination is made, depending on type, based on file extension, file content, or the folder that the source file resides in. This algorithm is implemented by a Groovy script, called a Match Script. FlexDeploy’s default Match Script algorithm is described within the documentation for each type. As an advanced feature, users can override the Match Script to meet unique requirements. However, in a vast majority of cases, customers find the default implementation meets their requirements.
Within each object type, the metadata includes attributes specific to that type. These attributes are ultimately used to generate the deployment command, which is used to load the object into EBS. When files are populated into the project, the default value of each attribute is generated using the algorithm implemented by a Default Script. Each attribute has its own Default Script, with a default implementation provided by FlexDeploy. The default implementation uses Oracle standards and best practices. In many cases, there are project properties which can be used to influence the value generated by the Default Script. It is for this reason that the default implementations of the Default Scripts are generally suitable for most customers. However, there may be unique requirements where overriding the algorithms may be required. Like the Match Script, customers can override the Default Scripts to provide their own implementations if necessary.
About this Reference Guide
This guide is organized by Object Type, and provides the following information for each type.
Section | Overview |
|---|---|
Description | Provides a description of the type of EBS customization the Object Type manages. |
Object Type Identification | Provides details pertaining to how the default Match Script determines that a particular source file is populated into this Object Type. |
File Extensions | Provides a list of file types/extensions which are managed under this Object Type. |
Object Type Code | Provides the Object Type Code, which would be needed to override the default Match Script or Default Script implementations. |
Object Type Attributes | Provides details regarding the attributes for the Object Type, including the defaults values as implemented by default Default Script. |
Related Project Properties | Provides details about any project properties which influence the generation of the default value, as implemented by the default Default Script. |
Sample Commands | Examples of the generated build (where applicable) and deploy commands, as implemented by the default Default Script. |
Considerations | Provides other relevant information specific to a particular Object Type. |
Object Types
- style