Friday, 10 March 2017

Oracle SOA suite 12.2.1- Composite Instance Patching

Oracle SOA Suite 12c (12.2.1) supports Composite Instance Patching, which enables you to patch running instances of a composite and recover faulted instances after patching the runtime. You can only include those fixes in the patch that are compatible with Composite Instance Patching. Use the SOA Patch Developer role in Oracle JDeveloper to make the fixes and create the patch.
Composite Instance Patching enables you to deliver urgent composite fixes that can be picked up by long running instances. You can make compatible/allowed changes without aborting in-flight instances. If a patched running instance comes across a business process that has been fixed by the patch, say a BPEL transformation, then it picks up the fixes applied to the business process.

When designing the patch, the SOA Patch Developer mode in JDeveloper automatically disables changes that cannot be made to the patch. Some of the compatible changes that you can make include:
·         Non-schema related XSLT changes, changes to fault policy, sensor data, and analytics data.
·         Compatible BPEL changes such as transformation activity, assign operations, etc.
·         JCA Adapter configuration properties.
You do not specify any composite version during deployment. The composite revision that you create the patch for, in Oracle JDeveloper, is the composite revision to which the patch is deployed.

You can validate the patch before deploying.

SOA Patch Developer Mode in JDeveloper

Use the SOA Patch Developer mode in Oracle JDeveloper to create a patch, containing fixes, for your deployed composite. The patch created in this mode can be applied to the currently deployed composite without changing the version number of the deployed composite. You can apply the patch to runtime even if the composite has running instances.
To use the SOA Patch Developer mode in JDeveloper:
  • If you already have your project open in JDeveloper, you need to switch to the SOA Patch Developer mode. Select Tools > Switch Roles > SOA Patch Developer from the Oracle JDeveloper menu bar



Click OK to restart JDeveloper.
If you do not have Oracle JDeveloper open, start JDeveloper and select the SOA Patch Developer role in the Select Role dialog.



After JDeveloper starts in the SOA Patch Developer mode, you’d notice that the composite editor has the SOA Patch mode label. This reminds you that you can only make edits that are compatible with the patch mode.



Also, when you are editing a BPEL component, for example, the BPEL editor has the Patch mode label.



Only certain activities in the BPEL process are available for editing, the rest of them appear in gray. Also, notice that the Components window shows only those components that are available for use in the SOA Patch Developer mode. A number of properties appear in read-only mode.

Happy Learning...!!!!!!!!!!!! Fun Sharing.........!!!!!!!!!



1 comment:

  1. Thanks for sharing the useful information and good points were mentioned in this post which I found as very informative one and for the further information visit us at
    Oracle Fusion Financials Training

    ReplyDelete