Executes the adpatch command line interface to perform 12.1.3 EBS patches.
As all workflow operations, if this fails, the server will remain in its current state, which may mean that some services will not be running.
A webhook may be advisable to notify a team if it fails if automating adpatching.
Target Properties
Property Name | Property Code | Required | Description | ||
|---|---|---|---|---|---|
EBS Source Script |
| Yes | Source Script with full path.
| ||
EBS Database Password |
| Yes | Password to connect for EBS Database User. | ||
EBS System Password |
| Yes | SYSTEM Password for running adpatch. | ||
EBS Database SID |
| Yes | Database SID for the EBS install. |
...
Input Name | Input Code | Required | Description |
|---|---|---|---|
Patch Top |
| Yes | Patch top to be used when applying a patch via adpatch. This should be the parent folder of the driver file. e.g. Use groovy and set to “/path/to/patches/” + PATCH_NUMBER Make a workflow input or get the PATCH_NUMBER from an artifact (echo > file in build, cat file in deploy) |
Driver Name |
| Yes | The driver to execute as part of the patch. This must only be the driver file, specifying a relative path to the driver will not work. e.g. Use groovy and set to “u” + PATCH_NUMBER + “.drv” |
Number of Workers |
| Yes | The number of workers to use when applying the patch. The default is 8 but it should be configured based on the number of servers in your cluster. |
Abandon Session |
| No | If the previous session failed or was interrupted should this execution resume where the previously halted session stopped? |
Test Mode |
| No | Setting this to true will only output the steps that would be applied if applying the patch outside of Test Mode. You can run this first to verify the patch steps. When running in test mode it is recommended to run in Hot Patch as well. |
Hot Patch |
| No | Setting this to true will result in a hot patch being applied. When hot patching, the EBS server will not be put in maintenance mode. If unchecked, the server will enter maintenance mode (adsetmmd.sql ENABLE) before and exit it after applying the patch. |
EBS Patch Notification |
| No | Should a notification email be sent on failure? |
EBS Patch Notification Email |
| No | Email to use in the case of FDEBS_INP_PATCH_NOTIFICATION being true. |
Defaults Override |
| No | This plugin makes use of a defaults file to provide silent input to the adpatch command. If you wish to use your own defaults file to apply the patch you can specify that here. |
...
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.
Special Considerations
Running in
...
Test Mode
Before applying a patch, it is recommended to run with HotPatch and TestMode enabled. This behavior will test the patch application whilst without not putting the server in maintenance mode.
...
This operation makes use of a defaults file to pass parameters to the adpatch command. This file is only here for reference if you wish to specify the path to your own defaults file via the FDEBS_INP_ADPATCH_DEFAULTS_FILE input. All defaults files will have FlexDeploy property replacement performed on them.
...