Das ist nicht durch meine Arbeit enstanden, sondern durch meine Kollegen in America. Daher speziellen Dank an die Kollegen in America, hier besonders an Scott der sich sehr schnell mit den Problemen beschäftigt hat und uns allen die Information bereit gestellt hat.
Over the past day or two, I have successfully installed and configured Oracle Forms & Reports 184.108.40.206 in my Windows 7 64-bit virtual machine. As I’ve only worked with our test form and report, there are no major functionality changes that I could detect. In my test installation, I worked with Oracle WebLogic Server 10.3.6 using JDK 1.7.0_10 (this is the latest JDK available for download) as I was curious to see how JDK 7 would work with Forms. Based off the installation and configuration, I have noticed the following:
1. The installation of Oracle Forms and Reports 220.127.116.11 (as well as running config.bat) is identical to installing 18.104.22.168. The same steps are involved.
2. Environment files and formsweb.cfg work the same. In order to use the latest JRE (since I was using JDK 7 in my test), I had to configure the jpi parameters in formsweb.cfg.
3. In Forms Builder, I had to specify a web browser location in Edit ‚ Preferences before I could run a form using Forms Builder.
4. For some reason, nothing involving rwservlet would work (including viewing generated PDF reports) as I always received „REP-52262: Diagnostic output is disabled.“ In previous releases of Oracle Forms & Reports 11gR1 and 11gR2, using the default setting in rwservlet.properties would allow anyone to access anything related to rwservlet such as getjobid, showjobs, showenv, etc. For some reason in 22.214.171.124, the default settings act the same as using <webcommandaccess>L0</webcommandaccess> in the file. To fix this, I had to manually add the parameter <webcommandaccess>L2</webcommandaccess> into rwservlet.properties and restart WLS_REPORTS before I could view generated reports.
5. If you are using Oracle Forms 126.96.36.199 using WebLogic Server 10.3.6 (not 10.3.5), JDK 7 (including the latest JDK update available) works well. The tabbing issue seems to have been fixed. :
6. The OHS bug which occurred in many Oracle Forms 188.8.131.52 installations no longer occurs. The bug was the case where you had to rollback and re-apply an Oracle patch to fix an issue where OHS would lose connectivity with the WLS_FORMS server after a report was run. , and anytime I set up a developer PC on Windows 7 64-bit. I am very glad that this has been fixed in the latest version!
7. The Reports Builder bug where it crashes when viewing the Data Model in 64-bit machines has NOT been fixed. Fortunately, applying the fix as mentioned will still fix the problem.
8. Oracle Forms & Reports 184.108.40.206 is backwards-compatible with Oracle Forms & Reports 220.127.116.11. I tested this by successfully opening up or loading a form in either an 18.104.22.168 Forms Builder or PITSS.CON saved in either Forms Builder or PITSS.CON using Forms 22.214.171.124. This means that if you are working with a customer who is using Oracle Forms 126.96.36.199, you are able to use your PITSS.CON or Forms Builder using Forms 188.8.131.52 without any problems. NOTE: Forms 184.108.40.206 is not backwards-compatible with Forms 11gR1.
Other than what I mentioned above, I did not notice any other major differences. I also setup a test PITSS.CON 220.127.116.11 environment to run in Oracle Forms & Reports 18.104.22.168. Everything works the same as it did in Oracle Forms 22.214.171.124.
I have updated all of our 11gR2 prerequisite documents to reflect the newly-released Oracle Forms & Reports 126.96.36.199. They should be viewable in our knowledge base.
Thanks to Scott
Forms hängt beim starten