Divide and Conquer Techniques for Solving Complex Problems

FAQTroubleshooting 23-9

23.3 OAAM UIO Proxy

UIO ISA Proxy To troubleshoot the OAAM UIO Proxy Web publishing issues: ■ Ensure that the .NET2.0 framework is installed and enabled to successfully register the Bharosa Proxy DLL. ■ Ensure the database access credentials are correct when the firewall logging properties in Microsoft ISA use the SQL Database as the log storage format. ■ IP exceptions are defined for trusted IPs like Router IP when flood mitigation settings are enabled to mitigate flood attacks and worm propagation. ■ Ensure that the default inbound and outbound rules allow HTTPHTTPS traffic to be forwarded tofrom OAAM Server. ■ Check the order precedence of the rules to ensure that the default rule, deny, is not at a higher order; otherwise, it blocks all rules. If the rule is last in precedence, all rules are executed. ■ In the OAAM Server rule you must ensure that: – The external IPname is mapped to the internal IPname OAAM CLI Script Issues ■ Make sure the JAVA_HOME environment variable is set to the JDK certified for the Identity Management Suite for 11g ■ Make sure CLI related properties are set in the oaam_cli.properties file. SOAP Call Issues ■ Known issues exist with time-outs in SOAPGenericImpl ■ OWSM is enabled by default, so you need to set OWSM policy before using SOAP ■ Make sure the SOAP server URL including the port number is valid Native Integration Issues ■ Make sure the appropriate version of the OAAM Extensions Shared Library is used the WAR should use the war version and EAR should use the ear version ■ Make sure the OAAM data source is created and the JNDI name is correct it should match the JNDI name of the OAAM Server ■ Make sure the native application is using the same keys that are used by the OAAM Admin and OAAM server ■ Issues with the encryption keys – Make sure all the managed servers are on the same WebLogic domain or copy the keys across the domains – If using non-11g servers, use the Java keystores ■ Shared library usage by many applications on the same server Currently the OAAM Extensions Shared Library cannot be used by more than one application on the same managed server Table 23–3 Cont. Problems and Tips Problem Checks You Can Perform