This chapter provides suggestions for resolving problems that may arise when installing the Oracle Configurator Servlet. This installation is described in Oracle Configurator Servlet Considerations.
This chapter covers the following topics:
Oracle Configurator Developer and Oracle Configurator use the standard Oracle Applications methods of logging to analyze and debug both development and runtime issues. These methods include setting various profile options and Java system properties to enable logging and specify the desired level of detail you want to record.
For more information about logging, see:
The Oracle E-Business Suite System Administrator’s Guide. This document provides descriptions of the Oracle Applications Manager UI screens that allow System Administrators to set up logging profiles, review Java system properties, search for log messages, and so on.
The Oracle E-Business Suite Developer's Guide. This document includes logging guidelines for both System Administrators and developers, and related topics.
Oracle Application Framework Documentation Resources, Release 12, on MetaLink. This document provides troubleshooting information that is specific to the OA Framework.
Before troubleshooting OC Servlet installation, be sure that:
The Oracle Applications profile option BOM: Configurator URL of UI Manager points to the location of the Oracle Configurator Servlet.
Your executable path includes the Shared Object files (.so or .dll). A symptom of this problem might be an error message starting with a line similar to the following:
java.lang.UnsatisfiedLinkError: no czjni in shared library path
Does the UI Servlet respond to a test message?
Invoke the following URL in a Web browser:
http://hostname:portnum/OA_HTML/configurator/UiServlet?test=version
where hostname is the name of your internet server and portnum is the port number for your Web listener. If the servlet is installed correctly and running, it should produce an HTML page that prints the current build version of Oracle Configurator and the expected version for the CZ schema.
For example:
http://www.mysite.com:8802/OA_HTML/configurator/UiServlet?test=version
If the UI servlet is running and installed correctly, entering this URL should produce a result similar to the following:
Using configuration software build: 12.0.27.2 Expecting schema: 27b
Note: The property cz.uiservlet.versionfuncsavail determines whether you can test the response of the servlet using the test=veresion string. For details, see cz.uiservlet.versionfuncsavail.
Enable logging, or increase the level of detail that Configurator Developer records by changing settings available by clicking the Diagnostics global link. Look in the log file to see which classes it loads, and from which JAR files. There may be a message indicating that some classes failed to load. It is probably the case that there is a JAR file in the list that is not in the path specified or that there was an error in specifying its name.
For details about the logging options that are available via the Diagnostics global link, see the Oracle Application Framework Documentation Resources, Release 12, on MetaLink.
There may be a basic problem with your Apache configuration. Refer to Oracle Application Server documentation for troubleshooting information.
Does your configuration model behave as you expect in the runtime Oracle Configurator?
You can launch a generated User Interface from Oracle Configurator Developer by clicking the Test Model button in the Structure, Rules, or User Interface area of the Workbench. For more information, see the chapter on unit testing in the Oracle Configurator Developer User’s Guide.
Alternatively, you can test the behavior of the runtime Oracle Configurator by creating a test page that substitutes for your host application.
To do this:
Create an HTML test page that posts an initialization message to the UI Servlet.
See the chapter on session initialization in the Oracle Configurator Implementation Guide for an explanation of the OC initialization message.
See Test Page for Invoking the JRAD Runtime Oracle Configurator, and the Oracle Configurator Implementation Guide for examples of simple test pages.
Test Page for Invoking the JRAD Runtime Oracle Configurator
<html> <head> <title>Minimal Configurator Test</title> </head> <body> <form action="http://www.mysite.com:8802/OA_HTML/CZInitialize.jsp" method="post"> <input type="hidden" name="XMLmsg" value= '<initialize> <param name="database_id">serv01_sid02</param> <param name="user">operations</param> <param name="pwd">welcome</param> <param name="calling_application_id">708</param> <param name="responsibility_id">22713</param> <param name="ui_type">JRAD</param> <param name="ui_def_id">3120</param> </initialize>'> <p>Click the button to configure the model... <input type="submit" value="Configure"> </form> </body> </html>
Ensure that you have the necessary database connectivity, and that your UI Servlet is installed and configured correctly.
For details, see Verifying Apache and OC4J Setup.
Test the runtime Oracle Configurator by opening the test page.
Your default Web browser should open and contain the specified configuration model and User Interface. If you used Test Page for Invoking the JRAD Runtime Oracle Configurator, click the button to display the specified User Interface.