What are the patches required for indian Localization in Release 12?
In Release 12, India Localization functionality is included in Base rollup patches itself (For example RUP04, RUP05 etc.,). Hence there is no need to apply separate patches for India Localization as in Release 11i.
Wednesday, August 5, 2009
How to Create a Query-only Responsibility for HR
There is not a delivered responsibility that is query only but you can create one...
1. copy the seeded responsibility you want to use
2. in System Administrator responsibility, go to Profile > System
3. select your newly created responsibility in the Responsibility field
4. Select HR:Query Only Mode in the Profile field
5. set "HR:Query Only Mode" to "Yes" in the responsibility column
6. save
The new responsibility will have access to all the data but the user will not be able to update anything.
Monday, August 3, 2009
How To Change The Standard Oracle Logo in R12 Forms?
1.- Open the file $INST_TOP/ora/10.1.2/forms/server/appsweb.cfg
2.- Check the baseHTML and baseHTMLJInitiator variables inside the file. They point to theappsbase.htm file used in the forms (ussually is the same file for both)
3.- Open the file(s) pointed by those variables
4.- Go to the "// Forms Applet Parameters" section related to the client browser you use
5.- Check if there's a line that references to "PARAM name=logo". An example of how that line mustbe for Internet Explorer is:
IEhtml += '<' + 'PARAM name=logo value="' + xlogo + '">';
add or change that line according to what you have and what you want.
6.- Go to the "// Oracle Applications default Parameters" section in the same file
7.- Add or edit the definition of xlogo variable. It must be:var xlogo = "%logo%"
8.- Save the file(s)
9.- Locate the variable "logo" in $INST_TOP/ora/10.1.2/forms/server/appsweb.cfg file at the ";Forms Server Information: servlet, port, machine name and domain" section. If it's not there thenyou can create the line. The variable must point to the .gif file you want to add on the forms.You must put the .gif file in
$OA_JAVA/oracle/apps/media
and $OA_JAVA paths and point the "logo"variable to your file with:logo=
10.- Bounce Forms and Apache servers for the changes to take effect11.- Open a new browser window on your client desktop and test the forms.
2.- Check the baseHTML and baseHTMLJInitiator variables inside the file. They point to theappsbase.htm file used in the forms (ussually is the same file for both)
3.- Open the file(s) pointed by those variables
4.- Go to the "// Forms Applet Parameters" section related to the client browser you use
5.- Check if there's a line that references to "PARAM name=logo". An example of how that line mustbe for Internet Explorer is:
IEhtml += '<' + 'PARAM name=logo value="' + xlogo + '">';
add or change that line according to what you have and what you want.
6.- Go to the "// Oracle Applications default Parameters" section in the same file
7.- Add or edit the definition of xlogo variable. It must be:var xlogo = "%logo%"
8.- Save the file(s)
9.- Locate the variable "logo" in $INST_TOP/ora/10.1.2/forms/server/appsweb.cfg file at the ";Forms Server Information: servlet, port, machine name and domain" section. If it's not there thenyou can create the line. The variable must point to the .gif file you want to add on the forms.You must put the .gif file in
$OA_JAVA/oracle/apps/media
and $OA_JAVA paths and point the "logo"variable to your file with:logo=
10.- Bounce Forms and Apache servers for the changes to take effect11.- Open a new browser window on your client desktop and test the forms.
IE "Unknown Publisher" Message when Running a Form after Initial 11g Installation
After a new installation of 11g Forms the following url is entered in IE to run the test form:
http://machine.domain:port/forms/frmservlet and the following occurs:
"Unknown Publisher"
This occurs because JRE 1.6.0.12 or higher is not installed on the client machine and because of Bug 8747086 FORMS 11 FORMSWEB.CFG INCORRECTLY CONFIGURED FOR SUN JRE AUTODOWNLOAD
Forms 11.1.1.1.0 is configured to run with Sun JRE 1.6.0.12 or higher. If this is not installed on the client machine it normally should be automatically downloaded when using IE but is not due to this bug.
Steps for IE ->
1. Locate the formsweb.cfg in DOMAIN_HOME\servers\WLS_FORMS\stage\formsapp\11.1.1\formsapp\config
2. Change the following:
jpi_codebase=http://java.sun.com/products/plugin/autodl/jinstall-1_6_0-windows-i586.cab#Version=1,6,0,12
to
jpi_codebase=http://java.sun.com/update/1.6.0/jinstall-6u12-windows-i586.cab#Version=1,6,0,12
3. Rerun the Form and you should be prompted to install the Sun JRE.
http://machine.domain:port/forms/frmservlet and the following occurs:
"Unknown Publisher"
This occurs because JRE 1.6.0.12 or higher is not installed on the client machine and because of Bug 8747086 FORMS 11 FORMSWEB.CFG INCORRECTLY CONFIGURED FOR SUN JRE AUTODOWNLOAD
Forms 11.1.1.1.0 is configured to run with Sun JRE 1.6.0.12 or higher. If this is not installed on the client machine it normally should be automatically downloaded when using IE but is not due to this bug.
Steps for IE ->
1. Locate the formsweb.cfg in DOMAIN_HOME\servers\WLS_FORMS\stage\formsapp\11.1.1\formsapp\config
2. Change the following:
jpi_codebase=http://java.sun.com/products/plugin/autodl/jinstall-1_6_0-windows-i586.cab#Version=1,6,0,12
to
jpi_codebase=http://java.sun.com/update/1.6.0/jinstall-6u12-windows-i586.cab#Version=1,6,0,12
3. Rerun the Form and you should be prompted to install the Sun JRE.
Friday, July 31, 2009
Obtaining Forms Runtime Diagnostics (FRD) In Oracle Applications 11i
1. Set the user value for profile option 'ICX: Forms Launcher' to be
'http://hostname.domain:port/forms/frmservice?record=forms'
2. By default, this will enable tracing for errors only. As an optional step, you can enable different trace options (e.g. user actions, user-exit events, dbsql events, network events) by setting a trace group in file $ORA_CONFIG_HOME/10.1.2/forms/server/ftrace.cfg
3. Login to the Personal Home Page, navigate to the form and perform the steps that you wish to trace.
4. Locate the file in the directory set by variable FORMS_TRACE_DIR. Note: by default, this directory is named forms_.trc, where is the process identifier.Related
Tracing in 11.5.10
1. Make the user value for profile option 'ICX: Forms Launcher' the same as the site value
e.g. copy value of ICX: Forms Launcher for the site Test115 'http://testserver.oracle.com:8005/dev60cgi/f60cgi' to be the value for the user.
2. Append the user value of ICX: Forms Launcher with the Forms parameters for FRD
e.g. update the value of ICX: Forms Launcher for the user to be 'http://testserver.oracle.com:8005/dev60cgi/f60cgi?record=all&log=/tmp/username_frd.log
3. Login to the Personal Home Page, navigate to the form and perform the steps that you wish to trace.
4. Locate the file in the directory set by variable $FORMS60_TRACE_PATH. Note: the default directory for $FORMS60_TRACE_PATH is $ORACLE_HOME/forms60/log.
FRD Tracing in 11.5.x to 11.5.9
This method enables users to run FRD tracing through the Personal Home Page by setting debugging to true using the profile option 'ICX: Forms Launcher'.
When accessing Applications through the Personal Home Page (PHP), there is no way to pass command line parameters such as config=debug and record=all for the duration of a single session.
For example, you cannot add these variables to the PHP connect string
http://testserver.oracle.com/OA_HTML/US/ICXINDEX_test115.htm.
The advantages of using the profile option 'ICX: Forms Launcher' are that you can easily trace the activities of multiple users and assign different log file names.
With Oracle Developer Forms patch 16 and higher, users cannot create adhoc FRD trace files in any directory. The trace files are either created in the directory set by parameter
$FORMS60_TRACE_PATH or they are created in 8.0.6 $ORACLE_HOME/forms60/log directory.
Steps:
To start tracing in this way, modify Profile Option 'ICX: Forms Launcher' at USER level to include the Forms parameters required for FRD logging:
1. Make the user value for profile option 'ICX: Forms Launcher' the same as the site value
e.g. copy value of ICX: Forms Launcher for the site Test115
'http://testserver.oracle.com:8005/dev60cgi/f60cgi'
to be the value for the user.
2. Append the user value of ICX: Forms Launcher with the Forms parameters for FRD
e.g. update the value of ICX: Forms Launcher for the user to be
'http://testserver.oracle.com:8005/dev60cgi/f60cgi?record=all&log=/tmp/username_frd.log
3. Save this change at the USER level, and the next time you access the test115 database through PHP, the Forms variables will be enabled.
Old option: adhoc FRD tracing :
The steps below show how to create an FRD trace file quickly. This is not a supported or preferred method of tracing, however, it may be useful to use this method for adhoc and basic troubleshooting purposes.Note after Oracle Developer Forms patch 16 and higher, users cannot create adhoc FRD trace files in any directory. The trace files are either created in the directory set by parameter
$FORMS60_TRACE_PATH or they are created in 8.0.6 $ORACLE_HOME/forms60/log directory.
1. Logon to Applications 11i and append the following text to the URL: record=all&log=/tmp/username_frd.log
a) Example on Unix:
A typical URL to logon to 11i applications: 'http://testserver.oracle.com:8005/dev60cgi/f60cgi?'
The URL with FRD trace enabled: 'http://testserver.oracle.com:8005/dev60cgi/f60cgi?record= all&log=/tmp/username_frd.log'
b) Example on Windows platforms:
A typical URL to logon to 11i applications: 'http://testserver.oracle.com:8005/dev60cgi/ifcgi60.exe'
The URL with FRD trace enabled: 'http://testserver.oracle.com:8005/dev60cgi/ifcgi60.exe?record= all&log=c:\temp\username_frd.log'
2. Reproduce the steps that you wish to trace in Applications.
3. Exit Applications and logout.
4. Locate the trace file at the server. In the above example, the forms runtime diagnostic trace information will be created to file form1.frd in /tmp or in c:\temp directory depending on the platform on which Applications is installed.
'http://hostname.domain:port/forms/frmservice?record=forms'
2. By default, this will enable tracing for errors only. As an optional step, you can enable different trace options (e.g. user actions, user-exit events, dbsql events, network events) by setting a trace group in file $ORA_CONFIG_HOME/10.1.2/forms/server/ftrace.cfg
3. Login to the Personal Home Page, navigate to the form and perform the steps that you wish to trace.
4. Locate the file in the directory set by variable FORMS_TRACE_DIR. Note: by default, this directory is named forms_
Tracing in 11.5.10
1. Make the user value for profile option 'ICX: Forms Launcher' the same as the site value
e.g. copy value of ICX: Forms Launcher for the site Test115 'http://testserver.oracle.com:8005/dev60cgi/f60cgi' to be the value for the user.
2. Append the user value of ICX: Forms Launcher with the Forms parameters for FRD
e.g. update the value of ICX: Forms Launcher for the user to be 'http://testserver.oracle.com:8005/dev60cgi/f60cgi?record=all&log=/tmp/username_frd.log
3. Login to the Personal Home Page, navigate to the form and perform the steps that you wish to trace.
4. Locate the file in the directory set by variable $FORMS60_TRACE_PATH. Note: the default directory for $FORMS60_TRACE_PATH is $ORACLE_HOME/forms60/log.
FRD Tracing in 11.5.x to 11.5.9
This method enables users to run FRD tracing through the Personal Home Page by setting debugging to true using the profile option 'ICX: Forms Launcher'.
When accessing Applications through the Personal Home Page (PHP), there is no way to pass command line parameters such as config=debug and record=all for the duration of a single session.
For example, you cannot add these variables to the PHP connect string
http://testserver.oracle.com/OA_HTML/US/ICXINDEX_test115.htm.
The advantages of using the profile option 'ICX: Forms Launcher' are that you can easily trace the activities of multiple users and assign different log file names.
With Oracle Developer Forms patch 16 and higher, users cannot create adhoc FRD trace files in any directory. The trace files are either created in the directory set by parameter
$FORMS60_TRACE_PATH or they are created in 8.0.6 $ORACLE_HOME/forms60/log directory.
Steps:
To start tracing in this way, modify Profile Option 'ICX: Forms Launcher' at USER level to include the Forms parameters required for FRD logging:
1. Make the user value for profile option 'ICX: Forms Launcher' the same as the site value
e.g. copy value of ICX: Forms Launcher for the site Test115
'http://testserver.oracle.com:8005/dev60cgi/f60cgi'
to be the value for the user.
2. Append the user value of ICX: Forms Launcher with the Forms parameters for FRD
e.g. update the value of ICX: Forms Launcher for the user to be
'http://testserver.oracle.com:8005/dev60cgi/f60cgi?record=all&log=/tmp/username_frd.log
3. Save this change at the USER level, and the next time you access the test115 database through PHP, the Forms variables will be enabled.
Old option: adhoc FRD tracing :
The steps below show how to create an FRD trace file quickly. This is not a supported or preferred method of tracing, however, it may be useful to use this method for adhoc and basic troubleshooting purposes.Note after Oracle Developer Forms patch 16 and higher, users cannot create adhoc FRD trace files in any directory. The trace files are either created in the directory set by parameter
$FORMS60_TRACE_PATH or they are created in 8.0.6 $ORACLE_HOME/forms60/log directory.
1. Logon to Applications 11i and append the following text to the URL: record=all&log=/tmp/username_frd.log
a) Example on Unix:
A typical URL to logon to 11i applications: 'http://testserver.oracle.com:8005/dev60cgi/f60cgi?'
The URL with FRD trace enabled: 'http://testserver.oracle.com:8005/dev60cgi/f60cgi?record= all&log=/tmp/username_frd.log'
b) Example on Windows platforms:
A typical URL to logon to 11i applications: 'http://testserver.oracle.com:8005/dev60cgi/ifcgi60.exe'
The URL with FRD trace enabled: 'http://testserver.oracle.com:8005/dev60cgi/ifcgi60.exe?record= all&log=c:\temp\username_frd.log'
2. Reproduce the steps that you wish to trace in Applications.
3. Exit Applications and logout.
4. Locate the trace file at the server. In the above example, the forms runtime diagnostic trace information will be created to file form1.frd in /tmp or in c:\temp directory depending on the platform on which Applications is installed.
How to run Forms Runtime Diagnostics (FRD) in 10gR2 Forms.
FRD is a runtime event-based logging system intended to aid in the debugging of Forms
applications. FRD is enabled at runtime on a user by user basis. When a form is run with
FRD enabled, a combination of external user-application interactions and internal Forms
processing events are written in chronological order to a log on the file system. These events
can then be analyzed by both application developers, and Oracle support staff. FRD is not
intended to be used as a performance benchmarking tool or as a mechanism for gauging code
coverage.
FRD generates extensive output useful for analysis and debugging, and it is therefore
recommended FRD be utilized as a logging mechanism only when specific issues are
encountered.
To implement FRD do the following:
In the $ORACLE_HOME/forms/server/default.env (or whatever env file you are using), add the environment variable FORMS_TRACE_DIR specifying a physical directory on the Application Server machine. The FRD log file will be written into the directory specified.
In the formsweb.cfg create a config section something like: [my_frd] otherparams=record=collect log=my_frd.txt form=my_form.fmx
Then call this from a url using the config section.
Example: http://my_machine:my_port/forms/frmservlet?config=my_frd
applications. FRD is enabled at runtime on a user by user basis. When a form is run with
FRD enabled, a combination of external user-application interactions and internal Forms
processing events are written in chronological order to a log on the file system. These events
can then be analyzed by both application developers, and Oracle support staff. FRD is not
intended to be used as a performance benchmarking tool or as a mechanism for gauging code
coverage.
FRD generates extensive output useful for analysis and debugging, and it is therefore
recommended FRD be utilized as a logging mechanism only when specific issues are
encountered.
To implement FRD do the following:
In the $ORACLE_HOME/forms/server/default.env (or whatever env file you are using), add the environment variable FORMS_TRACE_DIR specifying a physical directory on the Application Server machine. The FRD log file will be written into the directory specified.
In the formsweb.cfg create a config section something like: [my_frd] otherparams=record=collect log=my_frd.txt form=my_form.fmx
Then call this from a url using the config section.
Example: http://my_machine:my_port/forms/frmservlet?config=my_frd
Thursday, July 30, 2009
Trace the files loaded in java console while Oracle forms are invoked
1. Enable Java console as follows from Windows client machine,
Run - > Control - > Java - > Advanced Tab - > Java Console - > Click on Java console
2. Whenever the forms get loaded, the java console will be placed in the task bar and we can opne the console and see the files get loaded or trace the debug in case we have any issue with forms load
Eg:
Java Plug-in 1.6.0_12
Using JRE version 1.6.0_12 Java HotSpot(TM) Client VM
User home directory = C:\Users\admin
----------------------------------------------------
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
o: trigger logging
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
x: clear classloader cache
0-5: set trace level to
----------------------------------------------------
Loaded image: http://nglinux04.newgen.com:8099/OA_MEDIA/appslogo_new.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/splash.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndforms.jar!/oracle/forms/icons/oracle_logo.gif
proxyHost=null
proxyPort=0
connectMode=HTTP, native.
Forms Applet version is : 10.1.2.3
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndforms.jar!/oracle/forms/icons/ellipsis.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndforms.jar!/oracle/forms/icons/frame.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afnav.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afinsrw.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/affind.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afnavig.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afsave.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afnxtstp.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afrsp115.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afprint.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afclsfrm.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afcut.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afcopy.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afpaste.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afclrrw.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afclrall.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afdelrw.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afedit.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afzoom.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/aftrans.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afattach.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/affldtls.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afhelp.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/aflleft.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/aflright.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afclps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afclpsa.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afxpnda.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afxpnd.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afxpndc.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Run - > Control - > Java - > Advanced Tab - > Java Console - > Click on Java console
2. Whenever the forms get loaded, the java console will be placed in the task bar and we can opne the console and see the files get loaded or trace the debug in case we have any issue with forms load
Eg:
Java Plug-in 1.6.0_12
Using JRE version 1.6.0_12 Java HotSpot(TM) Client VM
User home directory = C:\Users\admin
----------------------------------------------------
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
o: trigger logging
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
x: clear classloader cache
0-5: set trace level to
----------------------------------------------------
Loaded image: http://nglinux04.newgen.com:8099/OA_MEDIA/appslogo_new.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/splash.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndforms.jar!/oracle/forms/icons/oracle_logo.gif
proxyHost=null
proxyPort=0
connectMode=HTTP, native.
Forms Applet version is : 10.1.2.3
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndforms.jar!/oracle/forms/icons/ellipsis.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndforms.jar!/oracle/forms/icons/frame.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afnav.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afinsrw.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/affind.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afnavig.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afsave.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afnxtstp.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afrsp115.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afprint.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afclsfrm.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afcut.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afcopy.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afpaste.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afclrrw.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afclrall.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afdelrw.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afedit.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afzoom.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/aftrans.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afattach.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/affldtls.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afhelp.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/aflleft.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/aflright.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afclps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afclpsa.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afxpnda.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afxpnd.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afxpndc.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Loaded image: jar:http://nglinux04.newgen.com:8099/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar!/oracle/apps/media/afapps.gif
Subscribe to:
Posts (Atom)