1. Verify Maintenance Mode is disabled (applicable to 11.5.

10 and customers with AD I patchset level (Patch 3180816(AD I) or Patch 4038964 (AD I1))). For more i nformation about the maintenance mode check metalink Note 291901.1 and Note 2897 91.1 2. Personal Home Page: Use http://<hostname.domain>:port 2.1. Login into Personal Home page as Sysadmin User 2.2. Choose Application Adminsitrator Responsibility to log into core app lications. 2.3. Check whether User/Responsibility Administrator Screen is coming up without errors. 2.4. Submit "Generate Concurrent Processing Environment Information" Conc urrent Request and "Active Users" report. Once completed normally then use expor t function (MainMenu/File/Export). If errors check your APPS_LISTENER is up and running else further debugging is needed. 2.5 Select Concurrent Manager Administer and check the status of Service Mana Service Manager is not running, Shutdown concurrent managers, run cmclean.sql an d restart concurrent managers. 3. SSP Products: Login to applications using step 1 and select Sales Online, iEx penses or iProcurement responsibility. Check whether pages are coming up or not, If customer is licensed for it. 4. Reports Server and Discoverer: To be tested only in the case the customer is licensed for any Business Intelligence Modules 4.1. Report Server: Login to applications using step 1 and select respons ibility like Financial Intelligence. Run report Earnings per Share and ensure th at graphs are displayed without any errors. 4.2. Discoverer Viewer:http://<hostname.domain>:<port>/discoverer4i/viewer (in case of failure, run $ORACLE_HOME/discwb4/util/checkdiscoverer.sh t o check status of each component) 4.3. Discoverer Plus: http://<hostname.domain>:<port>/discwb4/html/english /welcome.htm (in case of failure, run $ORACLE_HOME/discwb4/util/checkdiscoverer.sh to check s tatus of each component) 5. Check Jserv is Up and running : 5.1. http://<hostname.domain>:port/servlets/Hello 5.2 For Multi-MT instances, perform the following check using machine name URL for each MT and make sure the page comes uphttp://<hostname:domain>:port/OA _HTML/AppsLocalLogin.jsp 6. JTF Login Page for customers using CRM (Check for each MT using real host nam es) http://<hostname.domain>:port/OA_HTML/jtflogin.jsp

7. Workflow: Login to OAM. Navigate to Workflow Manager and make sure Notification M s and Agent Listeners are up. 8. Ensure Database is in archive log mode ( If it was disabled for patching/upgr ade) $sqlplus " / as sysdba" SQL>archive log list 9. Optional: Check multiple JVM's have come up if configured. Only if autoconfig was run, check that number of JVMs configured is same as it was before change. 10. Check the invalid object count and make sure that there is no additional inv alid objects after the maintanence 11.Run apps diagnostics tests: Login to Personal Home Page using http://<>:port Click on System Administration responsibility and run the tests under the Diagno

stics page: a) b) c) d) PL/SQL ping JSP Ping AOL/J Database Connection Pool Status Servlet ping

These checks will make sure all necessary components of oracle applications func tioning well. Troubleshooting AOLJTEST.jsp Errors ================================================================================ This document contains solutions to typical errors encountered when using the AOL/J Setup Test suite. The suite is made up of Java Server Pages (JSPs) designed to trouble-shoot AOL/J setup problems. These JSPs exercise various features of AOL/J and provide feedback on the results. The test suite is accessed from the URL: http://<host_name>:<port_number>/OA_HTML/jsp/fnd/aoljtest.jsp where host_name and port_number correspond to the host name and port number of your instance's Apache listener. The host name and port number values are normally found in the APPS_SERVLET_AGENT profile option. The tests must be performed in sequence starting at the top in order to avoid unnecessary errors. Benefits of using aoljtest.jsp: 1. Tests ModJserv. 2. Displays JDK version and jserv.properties classpath information. 3. Displays dbc file being used for by Apache Jserv (JVM) for connecting to the database. 4. Displays dbc file content and its location. 5. Tests ability to login as an Applications User. 6. Verifies all Apache aliases/virtual directories are configured correctly in apps.conf. 7. Displays the Applications Web Agent setting. 8. Tests Applications Web Agent/ModPlsql connection to the database. 9. Tests that ModPlsql custom authentication has been enabled. 10. Tests the Generic File Manager (GFM)which is used to upload, store and download documents from the database. 11. Displays the setting for the Applications Servlet Agent. 12. Tests servlet connectivity. 13. Displays the setting for the Framework Agent. 14. Tests OA_HTML cabo style sheet pages access. 15. Tests X Server access which is used by Framework for dynamic gif file genera tion. 16. Displays OA Framework System Information including current Framework version . 17. Displays the current version of all loaded java classes. 18. Displays and tests the Help Web Agent URL. 19. Tests the configuration of TCF. 20. Displays and tests ICX_FORMS_LAUNCHER, ICX_REPORT_LAUNCHER, and ICX_DISCOVER ER_LAUNCHER URLs. Problem: http://<host.domain:port>/OA_HTML/jsp/fnd/aoljtest.jsp seems to be using a

cached copy of aoljtest.jsp. Solution: Delete all the directories and files from OA_HTML/_pages. When aoljtest.jsp is run the first time it creates class files are sometimes not overwritten with the latest classes which should be generated from the newer jsp files. Problem: Netscape hangs and displays "Document contains no data. Try again later or contact the server's Administrator.", after filling in aoljtest.jsp's five (5) parameters: IE hangs and displays "Page cannot be displayed.", after filling in aoljtest.jsp's five (5) parameters: Apps Schema Name: Apps Schema Password: Two Task: Host Name: Port Number: Solution: The typical reason for this error is that the Apache Port Number is being used instead of the RDBMS Port Number. Problem: Verifying APPS_WEB_AGENT (http://<host.domain:port>/pls/VIS)... Error: Different than profile value retrieved earlier. Solution: Add a / to the end of the Applications Web Agent profile URL. http://<host.domain:port>/pls/VIS/ Problem: Trying to locate DBC file: /home/applmgr/visappl/fnd/11.5.0/gggrant2_vis.dbc .dbc FND_TOP defined in system properties. FND_TOP=/home/applmgr/visappl/fnd/11.5.0 ==>Trying to locate /home/applmgr/visappl/fnd/11.5.0/secure/home/applmgr/ visappl/fnd/11.5.0/gggrant2_vis.dbc.dbc on gggrant2.us.oracle.com... ERROR: java.io.FileNotFoundException: /home/applmgr/visappl/fnd/11.5.0/ secure/home/applmgr/visappl/fnd/11.5.0/gggrant2_vis.dbc.dbc (No such file or directory) Please carefully read AOL/J's dbc setup guideline and check to see if everything is in place. Solution: 1. Workaround: Edit the Jserv.properties DJTFDBCFILE to contain only the name of the dbc fi le

with any path or extention. You will need to stop and restart Apache. wrapper.bin.parameters=-DJTFDBCFILE=<host_sid> OR 2. Apply patch 2209062 AOL/J SETUP TEST FAILS TO READ DBC FILE WHEN JTFDBCFILE SET TO FULL PATH Problem: Checking DB_HOST... ERROR:DB_HOST value set in dbc file is: <host>.<domain> the host value you input in Step 1 was: <host> Please correct the dbc file or restart the test with the correct host value. Solution: The DB_HOST parameter is stored in the <host>.dbc file which is obtained from the jserv.properties: wrapper.bin.parameters=-DJTFDBCFILE=<Absolute FND_TOP Path>/secure/<host_sid>.db c Problem: Checking guest user/password... ...verified:GUEST/ORACLE WARNING: GUEST_USER_PWD specified differently in profile store (OPERATIONS/WELCOME). Solution: This profile option is used by CRM so only users of CRM modules need to set this Guest User Password profile. Problem: Using Custom Authentication: Testing http://gggrant2.us.oracle.com:8002/pls/VIS/HTP.HR... java.io.IOException: Server returned HTTP response code: 401 for URL: http://gggrant2.us.oracle.com:8002/pls/VIS/HTP.HR Error: Unable to get response message from URL http://gggrant2.us.oracle.com:8002/pls/VIS/HTP.HR Solution: The error can be ignored as this URL should always fail unless HTP.HR is registered in the FND_ENABLED_PLSQL table Problem: Applications Framework Errors. Solutions: All tests will fail in this section unless Framework Agent profile is set correctly. APPS_FRAMEWORK_AGENT = http://<host.domain:port/

Problem: 1. General HELP_WEB_AGENT errors. 2. ===== Start Message ==== JSP Error: Request URI:/OA_HTML/jsp/fnd/fndhelp.jsp Exception: Java.lang.NoSuchMethodError Solution: 1. The Applications Help Web Agent profile should be set to NULL ie. Left blank as the URL is built as a servlets based on the proper setting of Applications Servlet Agent APPS_SERVLET_AGENT = http://<host.domain:port/oa_servlets 2. Delete all the directories and files from OA_HTML/_pages. When fndhelp.jsp is run the first time, it creates class files are sometimes not overwritten with the latest classes which should be generated from the newer jsp files. Problem: TCF connection errors or TCF connection hangs. Solution: 1. Add to your iAS/Apache/Jserv/zone.properties file: a. # Startup Servlets ####################### servlets.startup=oracle.apps.fnd.tcf.SocketServer 2. Add to your APPL_TOP/admin/adovars.(env/cmd): a. Add 'jsdk.jar' to your $CLASSPATH. The path to jsdk.jar is located in your jserv.properties file. 3. Apply patch 2090381 4. On Windows machines set the TCF Socket Server service to manual/disabled. 5. On Unix do not run adtcfctl.sh 6. Shutdown and restart Apache