OSB Patching by Jon Petter

 

We have some customers which only use OSB – and not SOA Suite. When you want to patch – should you look only at WLS and OSB-patches? The answer is no.

One such reason is documented on MOS: Should the SOA Bundle Patches for 11g and 12c be applied to OSB (Doc ID 2102449.1). It states: In 12c, since OSB services can use JCA technology adapters, there is value in applying the SOA Bundle Patches where fixes to these adapters are included.

The other reason is because JDeveloper has common features in the two products. For example SOA patch 22226040: java.lang.NullPointer for XQuery File ver 1.0 in JDEV 12.2.1 OSB Proj – is one you would like to use for OSB on 12.2.1. The problem is shown in our blog post: OSB Patch. If the patch does not work – remember to do the cleanup-steps mentioned at the end of the blog.

My advise is to create a predefined Patch Search in MOD so you can monitor existing patches. Here are some of my searches.

clip_image002

One good thing you can see is the last time you searched. For example for OSB – then WLS, SOA and OSB are relevant. My advise is to order patches so you see the latest updates first, and that you at least should add the recommended patches. Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Patching SOA Composite Instances in Oracle 12.2.1 by Dennis

clip_image002

 

Introduction

Composite Instance Patching is a new feature introduced in 12.2.1 that allows compatible changes to be made to a SOA composite definition and be applied to long-running active instances. The feature enables you to patch running instances of a composite and recover faulted instances after patching the runtime. You can deliver urgent composite fixes and make compatible/allowed changes that are picked up with long-running instances without aborting them. 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.

Prior to 12.2.1, there was no way to make small changes to a composite and have in-flight instances, which could be long running for days/months, or error hospital instances see those changes. The alternatives were to either redeploy an existing composite revision but that causes long running instances to stop processing, or, to create a new composite revision which does preserve existing running instances but those instances do not see the changes introduced in the new revision. Now, with the new Composite Instance Patching feature in 12.2.1, critical fixes can be applied in a timely fashion and have them take effect immediately which is a unique differentiator for Oracle SOA Suite.

In this article I will (1) highlight some of the compatible changes that can be made to a composite, (2) discuss the enhancements to JDeveloper that allow you to quickly and easily design the patch without worrying about making invalid modifications in the composite patch, and (3) outline the steps used to build, validate, and deploy the composite instance patch to the SOA runtime.

Compatible Composite Changes

As mentioned above, there are only a limited set of modifications that can be made to a composite and deemed compatible with running instances.  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 sync/async invoke, transformation activity, assign operations, etc.
  • JCA Adapter configuration properties
  • Modifications of token values in composite references

while some of the incompatible changes that you cannot make include:

  • Deleting or renaming composite artifacts
  • Updating binding properties
  • Changes to a WSDL and Schema definition
  • Changes to XQuery mappings
  • Changes to BPEL receive inputs, structured activities, assign mapper source/target/skip conditions

Do not worry about knowing exactly what constitutes a compatible or incompatible change since, as we shall see, all those rules are accounted for in a new SOA Patch Developer mode within JDeveloper which automatically disables changes that cannot be made when constructing the patch.

Composite Instance Patch Development in JDeveloper

To simplify the creation of a composite instance patch a number of enhancements have been made to the JDeveloper tooling.  The first change is the introduction of a new new SOA Patch Developer role.  When launching JDeveloper you must first select the role that matches your requirements. Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Patching the Oracle Service Bus 12.1.3 unknown protocol deployment error by Jan van Zoggel

If you (already) created your first Oracle Service Bus 12c application/project with SOAP webservices and tried to deploy it to your IntegratedWeblogic server you might be familiar with this error.

clip_image002

Lucky for us Oracle quickly released a solution on their support website and also various blogs picked it up and posted a solution. The earliest reference I found was posted by Link. The solution to your problem was either:

  • Add felix.service.urlhandlers=false to the Init properties of OSGi frameworks bac-svnserver-osgi-framework factory implementation class
  • Remove the default server as a target for the framework

This worked like a charm and I was able to play around with my 12c Service Bus. However since it was stated that the solution could result into problems with BPM on your domain I reminded myself that I wanted to dive deeper into this when I had the time.

Google helped me out, and I discovered this information on the Apache Felix framework website.

Felix installs the URL Handlers service by default. If you do not want this service you can disable it, by setting the felix.service.urlhandlers property to false in the config.properties file. It is not recommended to disable this, but the main reason for doing so it because the URL Handlers implementation invokes methods to set the singleton factories for URL stream and content handler factories. Assuming that you want to use URL Handlers service, you must configure it if you aren’t running on the standard Sun JRE. Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki