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
...
.
Runs adop phase=prepare command.
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
EBS Source Script |
| Yes | Source Script with full path. |
Eg:
|
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 |
Project Properties
Property Name
Required
Description
when performing the deploy operation. All other operations are sourced from run by default. e.g. | |||
EBS Database Password |
| Yes | DB User to connect with privileges. |
System Database Password |
| Yes | SYSTEM Password for AD Online Patching. |
Weblogic Admin Password |
| Yes | The password for the WebLogic admin user. |
Inputs
Input Name | Input Code | Required | Description |
|---|
Outputs
Output Name
Required
Description
ADOP Additional Parameters |
| No | Pass additional parameters to the adop command as key=value pairs with each pair in a new line. Parameters already available as explicit inputs will be ignored. e.g. analytics=yes allowcoredump=yes patchtop=/custom/patch/top |
ADOP Additional Prompt Values |
| No | Pass additional values to prompts that may show up for ADOP phase operations. Each unique prompt value must be separated by a new line. e.g. Y N |
Artifacts
This operation doesn't consume or produce any artifacts.
...
This operation will select all available App Tier (EBS Web Server/EBS Forms Service/ EBS MWA Server) resource type endpoints associated to the environment instanceTarget.
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 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