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:
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 AK or ICX (in capital letters) and Responsibility Key
should be FWK_TBX_TUTORIAL
To find the correct Application Short Name for the
FWK_TBX_TUTORIAL responsibility you can run the SQL
select resp.application_id, appl.application_short_name
from fnd_responsibility resp, fnd_application appl
where resp.application_id=appl.application_id
and resp.responsibility_key='FWK_TBX_TUTORIAL';
from fnd_responsibility resp, fnd_application appl
where resp.application_id=appl.application_id
and resp.responsibility_key='FWK_TBX_TUTORIAL';
If you have AK *and* ICX returned in above query, then you
need to change the Application Short Name to ICX. If only AK is
returned, then use AK
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
select fnd_web_sec.validate_login('<UserName>','<Password>') from dual;
for example:
select fnd_web_sec.validate_login('FWKTESTER','WELCOME') from dual;
b) Repeat the above test for the GUEST username and
password that is defined in the DBC file you are using. For example:
select
fnd_web_sec.validate_login('GUEST','ORACLE') from dual;
3. Check PC to Database connectivity:
a) Check the RDBMS $TNS_ADMIN/sqlnet.ora file. If "tcp.validnode_checking = yes" then the IP address or hostname of your PC needs to be added to the list of accepted nodes in the "tcp.invited_nodes" entry in sqlnet.ora
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.
a) Check the RDBMS $TNS_ADMIN/sqlnet.ora file. If "tcp.validnode_checking = yes" then the IP address or hostname of your PC needs to be added to the list of accepted nodes in the "tcp.invited_nodes" entry in sqlnet.ora
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.
# Added to increase timeout parameters
# 10 minutes
JRAD.OC4J_TIMEOUT=600000
# 5 minutes
JRAD.JSP_TIMEOUT=300000
# default 30 seconds
JRAD.RUNREG_TIMEOUT=240000
# End of timeout additions
# 10 minutes
JRAD.OC4J_TIMEOUT=600000
# 5 minutes
JRAD.JSP_TIMEOUT=300000
# default 30 seconds
JRAD.RUNREG_TIMEOUT=240000
# End of timeout additions
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.
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)
2. In the "java options" add the following text at the end of the string (case sensitive)
-Duser.language=en -Duser.region=US -Duser.country=US
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)
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)
-Duser.language=en -Duser.region=US -Duser.country=US
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"
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"
SELECT r.application_id APPL_ID,
a.application_name APPL_NAME,
r.responsibility_key,
r.responsibility_id
FROM fnd_user u,
fnd_user_resp_groups ur,
fnd_responsibility r,
fnd_application_tl a
WHERE version =
'W'
AND ur.responsibility_id = r.responsibility_id
AND u.user_id = ur.user_id
AND r.application_id = a.application_id
AND u.user_name = UPPER ('&enter_user_name')
ORDER
BY 1
3. Please provide the output from the following SQL
entering the resp_name of "toolbox" when prompted:
SELECT u.user_name,
SUBSTR (d.responsibility_name, 1, 30) responsibility_name,
r.responsibility_key,
r.application_id APPL_ID,
application_short_name
FROM fnd_user u,
fnd_user_resp_groups ur,
fnd_responsibility r,
fnd_responsibility_tl d,
fnd_application a
WHERE ur.responsibility_id = r.responsibility_id
AND u.user_id = ur.user_id
AND r.responsibility_id = d.responsibility_id
AND UPPER (d.responsibility_name) LIKE UPPER ('%&resp_name%')
AND (r.end_date >= SYSDATE OR r.end_date IS NULL)
AND (ur.end_date >= SYSDATE OR ur.end_date IS NULL)
AND (u.end_date >= SYSDATE OR u.end_date IS NULL)
AND r.application_id = a.application_id
ORDER
BY u.user_name, d.responsibility_name
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)
2. In the "java options" add the following text at the end of the string (case sensitive)
-Djbo.debugoutput=console -Djbo.logging.trace.threshold=9
-Djbo.jdbc.driver.verbose=true -Djbo.jdbc.trace=true
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)
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)
-Djbo.debugoutput=console -Djbo.logging.trace.threshold=9
-Djbo.jdbc.driver.verbose=true -Djbo.jdbc.trace=true
No comments:
Post a Comment