Error : WebLogic User Cannot Log Into Oracle Identity Manager's BI Publisher Native Login Page
Issue :
WebLogic user can not log into OIM's BIP native login page.
When logging in a "Login failed, please retry." error is generated.
Solution :
Follow the steps below for resolution:
1. Log into WebLogic Server Console.
2. From left frame, under Domain Structure, select Services - Messaging - JMS Modules.
3. Select BipJMSResource.
4. Select Targets tab.
5. Under Clusters - bi_cluster select 'All servers in the cluster'.
6. Under Change Center, select Lock & Edit to make the changes from the GUI.
7. After changes are made, select Release Configuration.
8. Save.
9. If making changes from the backend, stop the WebLogic server.
10. Check the system-jazn-data.xml file for the folder location to make sure the credentials are available for reading. Location should be similar to the following:
${domain.home}/servers/${weblogic.Name}/tmp/_WL_user/bipublisher_11.1.1.x.0/-
11. Change the folder location to:
file:${domain.home}/servers/${weblogic.Name}/tmp/_WL_user/bipublisher_11.1.1/-
Note: Please make a backup copy of the system-jazn-data-xml file before modifying it.
12. Restart the WebLogic Server.
Note: It is advised that managed server(s) be stopped before the WebLogic server is stopped and started after the WebLogic server is restarted.
Note : This was very useful information and was very helpful in resolving the issue. It was referred from Oracle Metalink.
Issue :
WebLogic user can not log into OIM's BIP native login page.
When logging in a "Login failed, please retry." error is generated.
Solution :
Follow the steps below for resolution:
1. Log into WebLogic Server Console.
2. From left frame, under Domain Structure, select Services - Messaging - JMS Modules.
3. Select BipJMSResource.
4. Select Targets tab.
5. Under Clusters - bi_cluster select 'All servers in the cluster'.
6. Under Change Center, select Lock & Edit to make the changes from the GUI.
7. After changes are made, select Release Configuration.
8. Save.
9. If making changes from the backend, stop the WebLogic server.
10. Check the system-jazn-data.xml file for the folder location to make sure the credentials are available for reading. Location should be similar to the following:
${domain.home}/servers/${weblogic.Name}/tmp/_WL_user/bipublisher_11.1.1.x.0/-
11. Change the folder location to:
file:${domain.home}/servers/${weblogic.Name}/tmp/_WL_user/bipublisher_11.1.1/-
Note: Please make a backup copy of the system-jazn-data-xml file before modifying it.
12. Restart the WebLogic Server.
Note: It is advised that managed server(s) be stopped before the WebLogic server is stopped and started after the WebLogic server is restarted.
Note : This was very useful information and was very helpful in resolving the issue. It was referred from Oracle Metalink.