| Oracle® Adaptive Access Manager Administrator's Guide Release 10g (10.1.4.5) Part Number E12055-03 |
|
|
View PDF |
| Oracle® Adaptive Access Manager Administrator's Guide Release 10g (10.1.4.5) Part Number E12055-03 |
|
|
View PDF |
This chapter describes common troubleshooting issues and tips to resolve them.
Common issues in Adaptive Risk Manager are documented in this section.
Oracle Adaptive Access Manager is slow to respond; and diagnostics, logs, and errors—such as "hogging thread counts and a large number of SQL*net and RX errors—indicate a network issue.
If you are experiencing a network performance issue, monitor your network interface using a network utility like Ethtool (for Linux) to help you analyze your network bottleneck.
Check if the remote calls do have DNS lookup or network connectivity. Check the DNS lookup capabilities. Using IP, instead of name may be faster.
Make sure soap time out is not set to too low. Parameter "vcrypt.soap.call.timeout" affects the timeout and default is set to 3000 (3 secs)
Check the port on which the application server is active and serving the Adaptive Risk Manager Online application.
Make sure DNS entry is correct and/or IP Address is accessible.
Rule execution logs are written asynchronously and may not be available immediately. Check back later to see if they are available.
Check that the user id has access and is a member of the predefined roles. The roles are defined in the application server for Adaptive Risk Manager.
Ensure correct database access credentials are used in the sessions.xml. If data source is used, make sure data source is configured correctly.
Check that the TCP/IP port specified on the database server for database access is correct and the database server is listening on the port.
Check the timeout settings for the application server container.
Check that the user ID is a member of the predefined roles, which were defined in the application server for Adaptive Risk Manager.
Problem: While importing the rule conditions using Oracle XE configured through JNDI, a weblogic.jdbc.wrapper.Clob_oracle_sql_CLOB exception occurs. The trace references Oracle8Platform.writeLOB.
Solution: Change the platform class in sessions.xml file to com.bharosa.common.db.wldbutil.Oracle10PlatformLOBUtil and restart WebLogic.
Problem: Adaptive Risk Manager is deployed in WebLogic server. Import fails with following error:
weblogic.jdbc.wrapper.Clob_weblogic_jdbc_base_BaseClob cannot be cast to oracle.sql.CLOB
Solution: There is a known issue with WebLogic JNDI for handling CLOB. The current recommended workaround is to change the platform class in sessions.xml file to the one provided in the Adaptive Risk Manager distribution. Please refer "Configuring Database Connectivity" in the Oracle Adaptive Access Manager Installation and Configuration Guide.
Check that the user id accessing Adaptive Risk Manager Online customer care is a member of the predefined roles, which were defined in the application server for Adaptive Risk Manager. Refer to "Adaptive Risk Manager User Groups" in the Oracle Adaptive Access Manager Installation and Configuration Guide.
The Adaptive Risk Manager Offline application server fails with an OutOfMemory error during data load; the environment uses a SQL Server database.
To load login data from a SQL Server database, the JDBC connection string should be updated to include "selectMethod=cursor".
On the Admin menu, point to DB Configurations and then click List Configurations.
In the Properties tab of your DB Configuration, update "Remote RA DB JDBC URL" to include "selectMethod=cursor", as shown in the example below:
jdbc:sqlserver://localhost:1433;databaseName=oaam_offline;selectMethod=cursor
Common issues in Adaptive Strong Authenticator are documented below.
A large majority of potential problems related to the Adaptive Risk Manager Online system are due to incorrect settings within client-specific properties files.
When troubleshooting a problem relating to an Adaptive Risk Manager Online installation, ensure that the following two general problems have been addressed:
Check that the port settings are correct.
Check the URL to the Web services.
KeyPad does not display.
Check the property:
bharosa.authentipad.image.url=kbimage?action=kbimage&
Make certain that the client application is pointing to the correct server application.
Buttons stop jittering.
Someone has changed the keypad settings. Check with your server personnel regarding property modifications they may have made.
Same image displayed to all users.
Check the properties file to make sure that the backgrounds directory setting is correct.
No image displayed in pad background.
User may have images disabled in the browser.
Users image may have been deleted from the backgrounds directory.
Check the properties file to make sure that the backgrounds directory setting is correct.
Check that Adaptive Risk Manager Online is configured to assign images for personalization.
Oracle Adaptive Access Manager must be integrated with another application in order for the change password feature to work, as Oracle Adaptive Access Manager does not store user passwords. For this reason, when change password is attempted in standalone "test" mode there is no password to update.
If you are unable to access Adaptive Strong Authenticator and an "Authorization Failure" error appears in your client log file, refer to "Configuring SOAP/Web Services Access" in the Oracle Adaptive Access Manager Installation and Configuration Guide for information on setting up SOAP/Web services access.
|
 Copyright © 2008, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
