Extending AbstractJDBCRiskAnalyzerDataSource Implement RiskAnalyzerDataSource

23 FAQTroubleshooting 23-1 23 FAQTroubleshooting This chapter provides troubleshooting tips and answers to frequently asked questions. It contains the following sections: ■ Techniques for Solving Complex Problems ■ Troubleshooting Tools ■ OAAM UIO Proxy ■ Virtual Authentication Devices ■ Configurable Actions ■ One-Time Password ■ Localization ■ Man-in-the-MiddleMan-in-the-Browser

23.1 Techniques for Solving Complex Problems

This section describe a process to enable you to more easily solve a complex problem. It contains the following topics: ■ Simple Techniques ■ Divide and Conquer ■ Rigorous Analysis ■ Process Flow of Analysis

23.1.1 Simple Techniques

You can work your way through some simple troubleshooting techniques to try to solve a problem. Steps Description Experience You have seen this problem before or it is simply something you know the answer to. Post to the Forum This is not the first step. Only valid once basics have been applied and a second opinion is needed. Appropriate during rigorous analysis, but not before. 23-2 Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager

23.1.2 Divide and Conquer

Steps to reduce the problem to a manageable issue are listed in this section.

23.1.3 Rigorous Analysis

All or part of the process should be applied if: ■ a problem is complex ■ a problem is highly escalated ■ a problem was not solved with the first attempts Intuitive leap or guess The problem just inspires a guess at a cause. You have a feel for the problem or rather its cause. This can be very effective and result in a quick resolution, but without proper confirmation, it often leads to the symptom being fixed and not the real cause being resolved. Review basic diagnostics Check the logs for errors and the flow. Check flow HTTP headers, network packet trace, SQL trace, strace. Run through and document the flow. Cross check with configuration details to ensure flow is expected. Read the error message Reading the error and the flow information will give a big clue. Taken together with some knowledge of the way the component works, this can give a lot of insight. Always check knowledge Oracle and search engine for matches. Perform any diagnostics needed to establish if the error is key. With multiple errors, look to see which is likely the cause and which are just consequences. Compare Compare the logs and flows with a working system. Perform a test case. If it happens only at a certain site, then compare the differences. Divide Break the problem down Process Description Simplify the problem Make a problem as simple as possible. Remove components that are not needed Most problems involve complex components and connections between them. Most involve third party components. So where ever possible, eliminate third party components first and then as many components and custom components as possible for example, command line not application, SQLPLUS is not an application.? Reduce complexity Test to see if a simpler version of the problem exists with the same symptoms. for example, remove components of a complex Select, or a search filter, check if a single request or few requests will suffice?. Like fixing an underground pipe with a leak Imagine a complex configuration as being a underground hose pipe with a leak. You know something is wrong, there is a leak someplace, but not where it is. List the components Draw a box for each components and a line where it is connected to the next. Note the protocols used to join them. Check both ends What goes in should come out the same. If you see data in and out results in a problem then it is one of the ends that is wrong. If the flow is not as expected the problem is in between. Lazy Y Test points in the configuration to find where the deviation occurs. Once established beyond doubt that a piece of the configuration behaves as expected it can be ignored. Repeat Repeat this loop to close in on the problem Help When 3rd party components are involved in the issue, get help from the others and work on the issue together. Steps Description