My Oracle Support Banner

Unable To Integrate OAM11g With OEG11g (Doc ID 1382965.1)

Last updated on DECEMBER 19, 2019

Applies to:

COREid Access - Version 10.1.4.3.0 to 10.1.4.3.0
Oracle API Gateway - Version 11.1.1.4.0 to 11.1.1.6.1 [Release 11gR1]
Information in this document applies to any platform.

Symptoms

OEG 11g integrated with OAM SDK version AccessServerSDK_Ver_10.1.4.3, using the "HTTP Basic" filter of the OEG. Connecting to OAM 11g fails with the following error message:

ERROR <TIMESTAMP> [<THREAD ID>] OAM exception: 205: LANGUAGE_NOT_INITIALIZED
INFO <TIMESTAMP> [<THREAD ID>] OAM SDK version AccessServerSDK_Ver_10.1.4, NetPoint Access Protocol version NAP_Version_3
ERROR<TIMESTAMP> [<THREAD ID>] java exception:
java.lang.RuntimeException: OAM exception: 205: LANGUAGE_NOT_INITIALIZED
at com.vordel.circuit.oracle.OracleAccessManagerInit.obConfigInit(Native Method)
at com.vordel.circuit.oracle.OracleAccessManagerInit.initOracle(OracleAccessManagerInit.java:24)
at com.vordel.security.auth.repository.OracleAccessManagerRepository.checkCredentials(OracleAccessManagerRepository.java:84)
at com.vordel.security.auth.repository.RepositoryBase.checkCredentials(RepositoryBase.java:58)
at com.vordel.security.auth.HttpBasicAuthN.authenticate(HttpBasicAuthN.java:51)


No logfiles are created on the Oracle Access Manager server, not even with trace turned on in OAM.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
 1. Check the ASDK certification Matrix:
 2. Verify that the ASDK is working correctly outside of OEG
 3. Verify that ASDK environment variables have been set correctly
 4. Further debugging instructions:


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.