SOA Suite 11g to SOA Suite 12c Migration Experience !!!

In this post, I am going to list of some of the problems which I could remember; I have faced during SOA Suite 11g to SOA Suite 12c migration for one the recent project which I have completed.

Problem1: 'jca.retry.count’ error

While running some of the composite, transaction was getting rolled back with below error message –

Cannot parse JCA binding retry property 'jca.retry.count', value '0' due to: Value of JCA binding retry property

'jca.retry.count' must be a positive number: Cannot parse JCA binding retry property 'jca.retry.count', value '0' due to:

Value of JCA binding retry property 'jca.retry.count' must be a positive number</summary>

,code=<code>oracle.fabric.common.FabricException</code>

,detail=<detail>oracle.fabric.common.FabricException: javax.resource.ResourceException: Cannot parse JCA binding

retry property 'jca.retry.count', value '0' due to: Value of JCA binding retry property 'jca.retry.count' must be a positive

number: Cannot parse JCA binding retry property 'jca.retry.count', value '0' due to: Value of JCA binding retry property

'jca.retry.count' must be a positive number

at oracle.integration.platform.blocks.event.jms2.EdnBus12c.publish(EdnBus12c.java:1438

Solution 1:

This error was coming because ‘0’ was set for “NumberofRetry” located at this path

We have modified soainfrastructure>>

SOA Administration>> common properties>> More SOA Advance Configuration Properties >> Application

Defined Beans >> oracle.as.soainfra.config>>EDNConfig>>edn

I believe some internal changes been made for EDN delivery retry mechanism. Earlier as part of 11g, we were able to set “NumberOfRetry=0” but when we carried forward same value for SOA Suite 12c then composite start failing JCA error as listed above.

To fix this error we just change “NumberOfRetry =1” or any positive number up to 5.

Note: Setting number of “NumberOfRetry” =1 does not retry failed JCA transaction automatically.

Refer this document for detailed understanding about different value of NumberOfRetry and its impact.

http://docs.oracle.com/cd/E29542_01/admin.1111/e10226/appx_trouble.htm#SOAAG97758

 

“Test Console” service not running. Contact administrator to start this service

I am sure if you are working as SOA administrator you might have bumped with this error. 

In this blog post I am just trying to highlight few configurations which needs to verified ; if user is not able to launch OSB test console. I have faced this issue couple of time in various environments but fix for that problem was always different, so I just thought to compile some of causes which might help you to fix your environment problem for the same issue. 

Please note: I may be keep adding more causes as I found related to this issue in future assignments.

When OSB console is not accessible then its look like this – 

 

Cause 1:

First and foremost problem, I have noticed that OSB server is not running mode many times. Although user able to access Oracle Service Bus Console which gets deployed on Weblogic Admin Server but if OSB server is not up and running then OSB test console will never work. So make sure Weblogic Admin Server and Weblogic OSB server both must be up and running condition.

Weblogic Users Password Policy Enforcement

Most of clients as part of their security obligation needs to reset weblogic user password frequently and want to adhere strict password policy to avoid any security loophole. Resetting the Weblogic password is very easy but in this simple article I will just explain how to implement strict password policy rule.  Below is one sample password policy requirement given which needs to be implemented.

In order to achieve above password policy, below steps need to be performed-

Navigate to WLS Admin console >> Domain Home >Summary of Security Realms >myrealm >Users and Groups >Providers >SystemPasswordValidator >> Provider Specific tab page >> change highlighted value as per below snap