22.13 Verifying Deployment and Troubleshooting

After you deploy your application, test it to ensure that it runs correctly on the target application server. This section provides some common troubleshooting tips.

• Section 22.13.1, "How to Test Run Your Application"

• Section 22.13.2, ""Class Not Found" or "Method Not Found" Errors"

• Section 22.13.3, "Application Is Not Using data-sources.xml File on Target Application Server"

• Section 22.13.4, "Using jazn-data.xml with the Embedded OC4J Server"

22.13.1 How to Test Run Your Application

Once you've deployed the application, you can run it from the application server. To test run your application, open a browser window and enter a URL of the following type:

• For Oracle Application Server: http://<host>:port/<context root>/<page>

• For Faces pages: http://<host>:port/<context root>/faces/<page>

22.13.2 "Class Not Found" or "Method Not Found" Errors

Problem

You get "Class Not Found" or "Method Not Found" errors during runtime.

Solution

Check that ADF runtime libraries are installed on the target application server, and that the libraries are at the correct version.

You can use the ADF Runtime Installer wizard in JDeveloper to check the version of the ADF runtime libraries. To launch the wizard, choose Tools > ADF Runtime Installer > Application_Server_Type. Application_Server_Type is the type of the target application server (for example, WebLogic, JBoss, or standalone OC4J).

22.13.3 Application Is Not Using data-sources.xml File on Target Application Server

Problem

After deploying and running your application, you find that your application is using the data-sources.xml file that is packaged in the application's EAR file, instead of using the data-sources.xml file on the target application server. You want the application to use the data-sources.xml file on the target application server.

Solution

When you create your EAR file in JDeveloper, choose not to include the data-sources.xml file. To do this:

1. Choose Tools > Preferences to display the Preferences dialog.

2. Select Deployment on the left side.

3. Deselect Bundle Default data-sources.xml During Deployment.

4. Click OK.

5. Re-create the EAR file.

Before redeploying your application, undeploy your old application and ensure that the data-sources.xml file on the target application server contains the appropriate entries needed by your application.

22.13.4 Using jazn-data.xml with the Embedded OC4J Server

If your application uses jazn-data.xml, you should be aware of how the embedded OC4J server uses this file: If the embedded OC4J server finds a jazn-data.xml file in the application's META-INF directory, then the embedded OC4J server will use it. The embedded OC4J server will also set the <workspace>-oc4j-app.xml file to point to this jazn-data.xml file. This enables you to edit the jazn-data.xml file using the Embedded OC4J Server Preferences dialog.

If there is no jazn-data.xml file in META-INF, the embedded OC4J server will create a <workspace>-jazn-data.xml file in the workspace root. You would then have to go and edit that file (or use the Embedded OC4J Server Preferences dialog to do so).