Migration Tool : After Altering The JMS Adapter Configuration In JDeveloper, The old values reappear When The JMS Adapter Wizard Is Relaunched (Doc ID 1587693.1)

Last updated on SEPTEMBER 27, 2013

Applies to:

Oracle SOA Suite - Version 11.1.1.5.0 and later
Information in this document applies to any platform.

Goal

On : 11.1.1.5.0 version, SOA Suite Migration Tool

Even after changing and saving JMS Adapter configuration in JDeveloper, the old values reappear once the JMS Adapter wizard is relaunched. 

A Java CAPS (JCAPS) project containing JMS Source Adapter is successfully migrated using the SOA Suite Migration Tool. The migrated project is then opened in JDeveloper and the JMS Source Adapter wizard is run in composite and few values have been changed. But if the JMS Source configuration is again edited, the changed values are not visible and the old values from Java CAPS environment are again seen.

For example:

When migrating a JMS component from JavaCAPS 5.1.3 named "qNotificacaoAlertas_JMSSource_JMSMessageListenerRole" to SOA Suite 11g, the migration tool incorrectly creates a configuration file named "JMSSource_JMSMessageListenerRole_jms.jca". It should be "qNotificacaoAlertas_JMSSource_JMSMessageListenerRole_jms.jca" since SOA11g expects the latter naming convention. As a result when the configuration is again edited, it still loads the information from old file.

One solution is to copy new file's content to the old file but not a good solution.

Is there a Patch for this kind of problem?
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms