guidelines to run oracle forms 11g application in client
TRANSCRIPT
Guidelines to run Oracle Forms 11g Application in Client
CSC 3 December 2012
This report contains 10 pagesAuthor: Documentation Team
www.csc.com/globalhealthcare
document.docx | created 03/12/2012 16:34 Windows SOE ManagerUpdated 05/12/2012 05:24 Windows SOE Manager
Guidelines to run Oracle Forms 11g Application in Client
Contents
1 Introduction 3
2 Guidelines to Run Oracle Forms 11g Application 4
3 Revision History 9
INTERNAL - This document is for INTERNAL purposes only and must not be reproduced or distributed outside of the organisation without prior written permission Page 2 of 10
Guidelines to Run Oracle Forms 11g Application
1 IntroductionThis document covers the guidelines to run Oracle Forms 11g application in client.
INTERNAL - This document is for INTERNAL purposes only and must not be reproduced or distributed outside of the organisation without prior written permission Page 3 of 10
Guidelines to Run Oracle Forms 11g Application
2 Guidelines to Run Oracle Forms 11g ApplicationBefore running the application, check whether Java is installed in your system.
Note:
If Java is installed in your system, you can view the Java icon in the Control Panel Programs.
If not, install JRE 1.6 update 33.
If you have Java installed in your system, check its Version as described below.
1. Go to Control Panel Programs click Java icon. The Java Control Panel screen is displayed.
Figure 1
2. Click About to view the Java version installed in your system. Oracle suggests Java 1.6.0_33 version, as this is certified with Oracle 11g Forms R1 or R2.
INTERNAL - This document is for INTERNAL purposes only and must not be reproduced or distributed outside of the organisation without prior written permission Page 4 of 10
Guidelines to Run Oracle Forms 11g Application
Once you have Java in the system, do the below set up in the Java Control Panel to avoid the below pop-up
Cause:-
Signed Java Web Start applications and applets that contain signed and unsigned components could potentially be unsafe unless the mixed code was intended by the application vendor. As of the Java SE 6 Update 19 release, when a program contains both signed and unsigned components, a warning dialog is raised.
Solution:-
In the security dialog, if the user clicks yes, it blocks potentially unsafe components from running, and the program may terminate. If the user clicks the No button, the application or applet continues execution.Raising a warning is the default behavior, but there are options available for users to manage this situation.
You can manage how mixed code programs are handled through the Java Control Panel.
INTERNAL - This document is for INTERNAL purposes only and must not be reproduced or distributed outside of the organisation without prior written permission Page 5 of 10
Guidelines to Run Oracle Forms 11g Application
1. Go to Control Panel Programs click Java icon. The Java Control Panel screen is displayed.
Figure 2
2. Click Advanced tab.
INTERNAL - This document is for INTERNAL purposes only and must not be reproduced or distributed outside of the organisation without prior written permission Page 6 of 10
Guidelines to Run Oracle Forms 11g Application
3. Click ‘+’ sign near Security to view the options.
Figure 3
INTERNAL - This document is for INTERNAL purposes only and must not be reproduced or distributed outside of the organisation without prior written permission Page 7 of 10
Guidelines to Run Oracle Forms 11g Application
4. Click ‘+’ sign near Mixed code under Security.
Figure 4
INTERNAL - This document is for INTERNAL purposes only and must not be reproduced or distributed outside of the organisation without prior written permission Page 8 of 10
Guidelines to Run Oracle Forms 11g Application
5. Select the Disable verification (not recommended) option as shown below.
Figure 5
6. Click Apply and close the Java Control Panel.
Now, test the Forms URL in the browser. While running for the first time, two pop-ups appear. Trust the pop-ups, it will not appear later.
Note: For last logged in User ID and Domain in the application, at the start of application you need to have a login.txt file in the C Drive. (For this, you need to have access to create or modify files in the Drive).
INTERNAL - This document is for INTERNAL purposes only and must not be reproduced or distributed outside of the organisation without prior written permission Page 9 of 10
Guidelines to Run Oracle Forms 11g Application
3 Revision HistoryDate Version Description Author
03.12.2012 0.1 Formatted the document Selvakala Bharathi
INTERNAL - This document is for INTERNAL purposes only and must not be reproduced or distributed outside of the organisation without prior written permission Page 10 of 10