Prepares for Online Patch. With EBS 12.2, manual changes can be applied using online patching. FlexDeploy supports both traditional and online patching as a way of deploying your customizations and personalizations. Use this operation to initiate the prepare phase for Online Patching Cycle.
Environment/Instance Properties
| Property Name | Property Code | Required | Description |
|---|---|---|---|
| EBS Source Script |
| Yes | Source Script with full path. If you would like to apply changes directly to run edition for EBS R 12.2+, specify the run param after the script. By default it connects to patch edition. e.g. |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Outputs
Output Name | Required | Description |
|---|---|---|
Artifacts
This operation doesn't consume or produce any artifacts.
Endpoint Selection
This operation will select all available App Tier (EBS Web Server/EBS Forms Service/ EBS MWA Server) resource type endpoints associated to the environment instance.
Endpoint Execution
This operation will run randomly on any App Tier (EBS Web Server/EBS Forms Service/ EBS MWA Server) resource type endpoint.
Special Considerations
See Supported EBS Object Types at the end of this document for supported objects and considerations.
Please note that you need to ensure custom files are defined in the custom synchronization driver. For example, if you have custom java class files under the $JAVA_TOP/{Company identifier}/* directory, and if all the files under this directory need to be synchronized between the patch file system and the run file system, then add the following entry in the custom synchronization driver file: rsync -zr %s_current_base%/EBSapps/comn/java/classes/{Company identifier} %s_other_base%/EBSapps/comn/java/classes