Change the JNDI name and still wrong JNDI to connect to SAP.

(Doc ID 2298433.1)

Last updated on SEPTEMBER 01, 2017

Applies to:

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


SAP adapter JNDI changes not propagating correctly for all the requests.

JNDI changes should propagate for the entire flow and for all the requests.

The issue can be reproduced at will with the following steps:
1. Service calling SAP using SAP adapter.
2. Service used a wrong JNDI to connect to SAP.
3. Changed the JNDI to the correct one.
4. Redeployed the service.
5. Observed that some requests are using the old JNDI.


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