In this Document

Applies to:

Goal

The steps below provide instructions on how  to configure JDeveloper for Oracle Applications 11i.   These steps are also relevant for Release 12 version of JDeveloper

Fix

Configuration steps

1.  Verify that the Project Settings are correct in JDeveloper:

a) select the project and then select menu option "Project-->Project Settings"

b) under the "common-->Oracle Applications-->Runtime connection" section, check the settings are all correct:

• DBC filename should point to the explicit path and filename of the DBC file from the Middle Tier server    (that you copied to your PC) 
• The username and password should be correct for an Apps user  (a user who has the FWK_TBX_TUTORIAL responsibility assigned)
• Application Short Name should be ICX (in capital letters) and Responsibility Key should be FWK_TBX_TUTORIAL    
      NOTE - the Application Short Name is shipped as AK by default

2.  Check Applications user connectivity

a) For the username and password from the project settings, run the following SQL.  This needs to return a value of "Y" otherwise your username/password combination is not valid

b) Repeat the above test for the GUEST username and password that is defined in the DBC file you are using.  For example:

3. Check PC to Database connectivity:

a) Check the RDBMS sqlnet.ora file.   Check if "tcp.validnode_checking = yes"   If so, then the IP address or hostname for your needs to be added to the "tcp.invited_nodes"

b) Navigate to "Connections" --> "Database" and select the connection you have created there and click on "Open Connection"   This should display the APPS schema and allow you to navigate to see the DB objects for the APPS user.     This step ensures that there are no basic connectivity issue with JDBC from your PC to the database.

4.  Re-copy the dbc file from the eBiz Web Server

This should have already been done, but if the DBC file has been recreated or the security setting changed then it is possible the file is not synchronized.

Known issues

1. Release 11i only.     If your PC is accessing an Apps Database server across a WAN or if processing time on the PC seems very slow, try adding the following entries to the ide.properties file which will increase the timeout values used by JDeveloper.   This file is located in the  %JDEV_USER_HOME%\system9.0.3.5.1437 directory and should be edited before you launch JDeveloper.

2.  If you are accessing the environment via a secure VPN connection then please set your Embedded OC4J host name (Tools --> Preferences --> Embedded OC4J) to be the dynamically allocated IP address that the VPN server assigns to your machine. If you do not do this then, whenever there is a java exception, the exception details page will be blank and no exception thread dump information will be displayed. 

3. If you are using a non-US English setting in your Control Panel -> Regional Settings, temporarily set Control Panel -> Regional Settings to "English (American)" and re-test after restarting JDeveloper.  This will confirm your issue is not due to issues with language support.  

Alternatively you can set Java Options to explicitly tell JDeveloper to use US English as the language by adding the following entries-

Release 11i

1. Navigate: Project > Project Settings > Configurations > Development > Runner
2. In the "java options" add the following text at the end of the string (case sensitive)

Release 12

1.  Right-click a project in the navigator and choose Project Properties from the context menu. 
2.  Open the Run/Debug page.    
3.  Select a run configuration and click Edit . This opens the Edit Run Configuration dialog. 
4.  On the Launch Settings page, in the "java options" add the following text at the end of the string (case sensitive)

Gathering Troubleshooting data for Oracle Support

If you experience a configuration issue that you are unable to fix, please provide the following data when creating a Service Request: 

1. Please upload the complete output from the "messages" window and "Embedded OC4J Server" window (make sure they are cleared before reproducing the problem.   This will ensure we have the full error stack to investigate

2. Please advise the output from the following SQL.  Please use the username you have setup in the JDev setup.  For example "fwktester"

3. Please provide the output from the following SQL entering the resp_name of "toolbox" when prompted:

4.  To get additional information messages in the JDeveloper console, you can enable JBO and JDBC debug messages

Release 11i

1.  Navigate: Project > Project Settings > Configurations > Development > Runner
2. In the "java options" add the following text at the end of the string (case sensitive)

Release 12

1.  Right-click a project in the navigator and choose Project Properties from the context menu. 
2.  Open the Run/Debug page.    
3.  Select a run configuration and click Edit . This opens the Edit Run Configuration dialog. 
4.  On the Launch Settings page, in the "java options" add the following text at the end of the string (case sensitive)

References