Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
http://www.free-online-exams.com
Problem: Forms FRD Trace with New variable FORMS60_TRACE_PATH
Solution:
There has been new added security functionality depending on your Tech Stack Level. This is mainly seen
on the 11.5.10 Tech Stacks. With the Latest Patch Levels or 11.5.10 you are no longer allowed to
enter directly into the Applications Forms via the /dev60cgi/f60cgi URL.
There is a way to directly enter the Applications Forms via /dev60cgi/f60cgi if so desired for Trace purposes.
Note 293609.1 APP-FND-01542 when logging directly into forms via the f60cgi in 11.5.10
Please understand it is UNSUPPORTED to log directly to the Forms via /dev60cgi/f60cgi, but we do allow
it for FRD Traces only.
Starting FRD in Oracle Applications for a user:
Set a profile option "ICX: Forms Launcher" at user level to
http://:/dev60cgi/f60cgi/?&record=collect&log=
e.g. http://hostname.domainname.com:port/dev60cgi/f60cgi/?&record=collect&log=/mgd01/vis510ora/8.0.6/forms60/log
Log in to the Personal Home Page and select a responsibility to start the forms.
Suggestion: Create a user "TRACE" and set above profile for it. When a FRD
is needed ask user to use this username.
This log file will show each keystroke so it will build very fast,
I recommend on intermittent errors that the log file be periodically deleted,
so that the file does not become so massive that it hinders investigation of
the cause of the error.
There is a New twist for where the location of the FRD Trace files.
Found that Forms Patchset 16 introduced a new variable $FORMS60_TRACE_PATH
and it defaults to $ORACLE_HOME/forms60/log.
Forms Server enforces the following conditions after Forms Patchset 16:-
1) Ensures that all files from 'record=xyz', 'record=filename', 'play=xyz',
'log=' etc., are created in either FORMS60_TRACE_PATH or O_H/forms60/log,
and nowhere else.
2) Ensures that any filenames specified in 'log= '/'record= ' params are
stripped of any path information, using only the remaining 'terminal name',
thus making it impossible for users to overwrite any files outside
FORMS60_TRACE_PATH or O_H/forms60/log.
3) Ignores any values specified for FORMS60_TRACE_PATH on the URL or in static
HTML files, making it impossible for users to supply their own value.
Set your $FORMS60_TRACE_PATH variable to a Location from where you would like
your frd trace files to be coppied to or leave as the default.
This was changed for Security reason, so that the Sysadmin's can maintain Security
on the Servers.
References:
Forms FRD Trace with New variable FORMS60_TRACE_PATH [ID 290210.1]
Solution:
There has been new added security functionality depending on your Tech Stack Level. This is mainly seen
on the 11.5.10 Tech Stacks. With the Latest Patch Levels or 11.5.10 you are no longer allowed to
enter directly into the Applications Forms via the /dev60cgi/f60cgi URL.
There is a way to directly enter the Applications Forms via /dev60cgi/f60cgi if so desired for Trace purposes.
Note 293609.1 APP-FND-01542 when logging directly into forms via the f60cgi in 11.5.10
Please understand it is UNSUPPORTED to log directly to the Forms via /dev60cgi/f60cgi, but we do allow
it for FRD Traces only.
Starting FRD in Oracle Applications for a user:
Set a profile option "ICX: Forms Launcher" at user level to
http://
e.g. http://hostname.domainname.com:port/dev60cgi/f60cgi/?&record=collect&log=/mgd01/vis510ora/8.0.6/forms60/log
Log in to the Personal Home Page and select a responsibility to start the forms.
Suggestion: Create a user "TRACE" and set above profile for it. When a FRD
is needed ask user to use this username.
This log file will show each keystroke so it will build very fast,
I recommend on intermittent errors that the log file be periodically deleted,
so that the file does not become so massive that it hinders investigation of
the cause of the error.
There is a New twist for where the location of the FRD Trace files.
Found that Forms Patchset 16 introduced a new variable $FORMS60_TRACE_PATH
and it defaults to $ORACLE_HOME/forms60/log.
Forms Server enforces the following conditions after Forms Patchset 16:-
1) Ensures that all files from 'record=xyz', 'record=filename', 'play=xyz',
'log=' etc., are created in either FORMS60_TRACE_PATH or O_H/forms60/log,
and nowhere else.
2) Ensures that any filenames specified in 'log= '/'record= ' params are
stripped of any path information, using only the remaining 'terminal name',
thus making it impossible for users to overwrite any files outside
FORMS60_TRACE_PATH or O_H/forms60/log.
3) Ignores any values specified for FORMS60_TRACE_PATH on the URL or in static
HTML files, making it impossible for users to supply their own value.
Set your $FORMS60_TRACE_PATH variable to a Location from where you would like
your frd trace files to be coppied to or leave as the default.
This was changed for Security reason, so that the Sysadmin's can maintain Security
on the Servers.
References:
Forms FRD Trace with New variable FORMS60_TRACE_PATH [ID 290210.1]
No comments:
Post a Comment