Login flow in R12.2 and basic troubleshooting

R12.2 is the latest Release of Oracle E-business Suite Products. Here we will be discussing the Login flow in R12.2 and how to troubleshoot login issues in R12.2

Login flow in R12.2

1.  When an HTTP request is made for EBS, the request is received by the Oracle HTTP Server (OHS).
2. When the configuration of OHS is for a resource that needs to be processed by Java, such as logging into EBS, the OHS configuration will redirect the request to the Web Logic Server (WLS) Java process (OACore in this case).
3. WLS determines the J2EE application that should deal with the request, which is called “oacore”.
4. This J2EE application needs to be deployed and available for processing requests in order for the request to succeed.   The J2EE application needs to access a database and does this via a datasource which is configured within WLS.

Here is the processing in terms of URL(Login HTTP headers)

When the EBS login works OK, the browser will be redirected to various different URLs in order for the login page to be displayed.  The page flow below shows the URLs that will be called to display the login page:

/OA_HTML/AppsLogin EBS Login URL /OA_HTML/AppsLocalLogin.jsp Redirects to local login page /OA_HTML/RF.jsp?function_id=1032925&resp_id=-1&resp_appl_id=-1&security_group_id=0&lang_code=US&oas=3TQG_dtTW1oYy7P5_6r9ag..&params=5LEnOA6Dde-bxji7iwlQUg Renders the login page The URLs after the user enters username and password, then clicks the “login” button are shown below/OA_HTML/OA.jsp?page=/oracle/apps/fnd/sso/login/webui/MainLoginPG&_ri=0&_ti=640290175&language_code=US&requestUrl=&oapc=2&oas=4hoZpUbqVSrv9IE0iJdY1g.. /OA_HTML/OA.jsp?OAFunc=OANEWHOMEPAGE /OA_HTML/RF.jsp?function_id=MAINMENUREST&security_group_id=0 Renders user home page Once the users home page is displayed, the logout flow also redirects to several different URLs before returning to the login page: /OA_HTML/OALogout.jsp?menu=Y Logout icon has been clicked /OA_HTML/AppsLogout /OA_HTML/AppsLocalLogin.jsp?langCode=US&_logoutRedirect=y Redirects to the login page /OA_HTML/RF.jsp?function_id=1032925&resp_id=-1&resp_appl_id=-1&security_group_id=0&lang_code=US&oas=r6JPtR7-a4n5U2H3–ytEg..&params=1JU-PCsoyAO7NMAeJQ.9N6auZoBnO8UYYXjUgSPLHdpzU3015KGHA668whNgEIQ4 Renders login page again

Basic Troubleshooting for Login issues in R12.2

Here are some are the common login issues in R12.2 and their solutions

(1)  OHS (apache) failure

If OHS is not running or not responding, one would see a message as below. If OHS is not running then there will not be any messages in any EBS log file for this request.

Firefox: “The connection was reset” or 500 web gateway

Steps to take
Check OHS has started OK

adapcctl.sh status
adapcctl.sh stop
adapcctl.sh start

(2)  OACore JVM process not available (Failure of server APACHE bridge)

If the OACore JVM is not running or not reachable, then one will likely see the following message in the browser:

Failure of server APACHE bridge: No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.

There could be two reason
Steps to take
(a)Make sure the OACore JVM has started correctly

admanagedsrvctl.sh start oacore

(b) Check mod_wl_ohs.conf file is configured correctly

(3) OACore J2EE application not available(Error 404–Not Found)

There may be cases where the OACore JVM is running and reachable but the oacore application is not available.

The browser will report the error:

Error 404–Not Found From RFC 2068 Hypertext Transfer Protocol — HTTP/1.1: 10.4.5 404 Not Found The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

Access_log will show a 404 error:

GET /OA_HTML/AppsLogin HTTP/1.1″ 404

Steps to take

In the FMW Console check the “deployments” to confirm the “oacore” application is at status “Active” and Health is “OK”.

If the status is OK but you are still getting errors, then compiling JSP can be tried

cd $FND_TOP/patch/115/bin
./ojspCompile.pl --compile --flush -p 2
logfile set: ojspc_error.log
starting…(compiling all)
using 10i internal ojsp ver: 10
synchronizing dependency file:
enumerating jsps…8000
parsing jsp…8000
writing deplist…8000
initializing compilation:
eliminating children…5912 (-2088)
translating and compiling:
translating jsps…5912/5912 in 1m40s
compiling jsps…5912/5912 in 4m19s
Finished!

(4) Datasource failure (The system has encountered an error while processing your request)

The oacore logs will show this type of error

<Error> <ServletContext-/OA_HTML> <BEA-000000> <Logging call failed exception:: java.lang.NullPointerException at oracle.apps.fnd.sso.AppsLoginRedirect.logSafe(AppsLoginRedirect.java:639) at oracle.apps.fnd.sso.AppsLoginRedirect.doGet(AppsLoginRedirect.java:1314) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)

The explorer will show

The system has encountered an error while processing your request. Please contact your system administrator

Steps to Take

1. Review the EBS Datasource and make sure it is targeted to the oacore_cluster1 managed server.   Also, use the “Test Datasource” option to confirm database connection can be made
2. If one makes any changes, one will need to restart the managed server, despite FMW Console saying no restart is necessary

(5) The requested resource or page is not allowed in this site

The browser will report the error:

"Requested resource or page is not allowed"

• Make sure you are giving the correct jsp name
• check the “Security: Allowed Resources” (FND_SEC_ALLOWED_RESOURCES) profile.

(6) Users report cache initialization errors in OA Framework-related pages.

oacore logs show the below error

Exception in static block of jtf.cache.CacheManager. Stack trace is: oracle.apps.jtf.base.resources.FrameworkException: IAS Cache initialization failed. The Distributed Caching System failed to initialize on port: 12345. The list of hosts in the distributed caching system

This happens if port 12345 is occupied by any process in all the Middle tiers of the EBS system

netstat -anp | grep 12345 | grep LISTEN

If the process is other than oacore, kill it and try to restart oacore

I hope you like this post on login issues in R12.2. Please do provide feedback

Articles you must read on R12.2

• Important Changes in Autoconfig R12.2
• Service Group changes in R12.2
• adopmon and adopreports utility R12.2.5
• How to re-attach 12.2 E-Business Oracle Homes to the central inventory
• Isolating post-upgrade concurrent programs to a separate manager queue in R12.2