A problem can occur where if you try to log into the OAM console (Example: http://hostname.domain:7003/oamconsole) using the username created during the Domain Configuration (user weblogic for example) if IPv6 is enabled in the Windows server. What will happen is when you try to log into the OAM console for the first time, an error will come up saying that an incorrect username or password was entered. However, the same credentials can be used to access the WebLogic Administration Console.
If you look in the oam_server1_diagnostic.log file located in %OAM_DOMAIN_HOME%\servers\oam_server1\logs, you will see an error such as “OAMSSA-20005: Error initializing User/Role API : null.” in the log. This can happen when IPv6 is enabled in both the Windows server and the network adapter you are using. To fix the problem, you can complete the following steps:
- Open up the Registry Editor (NOTE: Make a backup of the registry first!)
- Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters
- Double-click on DisabledComponents (or create it as a DWORD (32-bit))
- Type in “ffffffff” in the Value. This will disable IPv6 except for the loopback interface.
- Open up setDomainEnv.cmd in a text editor. The file is located in %OAM_DOMAIN_HOME%\bin. (NOTE: Make a backup first!)
- Look for the lines containing “EXTRA_JAVA_PROPERTIES”. Add a new line below each of them:
- set EXTRA_JAVA_PROPERTIES=-Djava.net.preferIPv6Addresses=false –DuseIPv6Address=false –Djava.net.preferIPv6Addresses=false %EXTRA_JAVA_PROPERTIES%
- Save and close the file.
- Restart the Windows server and start up all OID and OAM WebLogic servers.
After applying the steps above, you should be able to log into the OAM Admin Console.
Sources: Oracle Support Notes 1316669.1 and 1311184.1 as well as http://support.microsoft.com/kb/929852 from Microsoft.