Skip to content

Commit 3b5d8bc

Browse files
committed
add patching info - monicas review feedback:
1 parent 873e12a commit 3b5d8bc

File tree

1 file changed

+20
-0
lines changed
  • docs-source/content/userguide/managing-domains/fmw-infra

1 file changed

+20
-0
lines changed

docs-source/content/userguide/managing-domains/fmw-infra/_index.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -349,3 +349,23 @@ Now that you have your Docker images and you have created your RCU schemas, you
349349
to create your domain. A [sample]({{< relref "/samples/simple/domains/fmw-domain/_index.md" >}})
350350
is provided that demonstrates how to create a FMW Infrastructure domain.
351351

352+
#### Patching the FMW Infrastructure Image
353+
354+
There are two kind of patches that can be applied to the FMW Infrastructure binaries:
355+
356+
* ZDT compliant, meaning that the patch can be applied in a rolling fashion.
357+
* non-ZDT compliant, meaning that the domain must be shutdown and restarted.
358+
359+
If you wish to apply a ZDT compliant patch which can be applied in a rolling
360+
fashion, after you have patched the domain image as shown in this
361+
[sample](https://github.com/oracle/docker-images/tree/master/OracleFMWInfrastructure/samples/12213-patch),
362+
you can edit the domain custom resource with the name of the new image and
363+
the operator will initiate a rolling restart of the domain.
364+
365+
If you wish to apply a non-ZDT compliant patch to the FMW Infrastructure binary image,
366+
you must shutdown the entire domain before applying the patch. Please see the documentation on
367+
[domain life cycle operations]({{< relref "/userguide/managing-domains/domain-lifecycle/" >}})
368+
for more information.
369+
370+
An example of a non-ZDT compliant patch is one that includes a schema change
371+
that can not be applied dynamically.

0 commit comments

Comments
 (0)