Java Runtime Environment 1.7.0_67 (a.k.a. JRE 7u67-b01) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 11i and 12.0, 12.1, and 12.2 for Windows-based desktop clients.
Effects of new support dates on Java upgrades for EBS environments
Support dates for the E-Business Suite and Java have changed. Please review the sections below for more details:
- What does this mean for Oracle E-Business Suite users?
- Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?
- Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?
All JRE 6 and 7 releases are certified with EBS upon release
Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops from JRE 1.6.0_03 and later updates on the 1.6 codeline, and from JRE 7u10 and later updates on the JRE 7 codeline. We test all new JRE 1.6 and JRE 7 releases in parallel with the JRE development process, so all new JRE 1.6 and 7 releases are considered certified with the E-Business Suite on the same day that they’re released by our Java team.
You do not need to wait for a certification announcement before applying new JRE 1.6 or JRE 7 releases to your EBS users’ desktops.
What’s new in this release?
JRE 1.7.0_67 fixes a regression in JRE 1.7.0_65 which prevented applets launching when using a “java_ arguments” parameter. This is the only change, it does not include any further security enhancements. Oracle E-Business Suite users are unlikely to be affected by this issue so moving to this release is optional, see the Update Release Notes for further information.
JRE 1.7.0_67 is available for download through the usual Java and Oracle Java SE Downloads public sites. If you are already running 1.7.0_65 auto-update will not be triggered to upgrade to 1.7.0_67. The standard release is also available through Patch 19295656 as well as a special release which has the auto-update function turned off through Patch 19295660.
32-bit and 64-bit versions certified
This certification includes both the 32-bit and 64-bit JRE versions for various Windows operating systems. See the respective Recommended Browser documentation for your EBS release for details.
Where are the official patch requirements documented?
All patches required for ensuring full compatibility of the E-Business Suite with JRE 7 are documented in these Notes:
For EBS 11i:
For EBS 12.0, 12.1, 12.2
EBS + Discoverer 11g Users
This JRE release is certified for Discoverer 11g in E-Business Suite environments with the following minimum requirements:
Worried about the ‘mismanaged session cookie’ issue?
No need to worry — it’s fixed. To recap: JRE releases 1.6.0_18 through 1.6.0_22 had issues with mismanaging session cookies that affected some users in some circumstances.
The fix for those issues was first included in JRE 1.6.0_23. These fixes will carry forward and continue to be fixed in all future JRE releases on the JRE 6 and 7 codelines. In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22 on the JRE 6 codeline, and JRE 7u10 and later JRE 7 codeline updates.
Implications of Java 6 End of Public Updates for EBS Users
The Support Roadmap for Oracle Java is published here:
The latest updates to that page (as of Sept. 19, 2012) state (emphasis added):
Java SE 6 End of Public Updates Notice
After February 2013, Oracle will no longer post updates of Java SE 6 to its public download sites. Existing Java SE 6 downloads already posted as of February 2013 will remain accessible in the Java Archive on Oracle Technology Network. Developers and end-users are encouraged to update to more recent Java SE versions that remain available for public download. For enterprise customers, who need continued access to critical bug fixes and security fixes as well as general maintenance for Java SE 6 or older versions, long term support is available through Oracle Java SE Support .
What does this mean for Oracle E-Business Suite users?
EBS users fall under the category of “enterprise users” above. Java is an integral part of the Oracle E-Business Suite technology stack, so EBS users will continue to receive Java SE 6 updates from February 2013 to the end of Java SE 6 Extended Support in June 2017.
In other words, nothing changes for EBS users after February 2013.
EBS users will continue to receive critical bug fixes and security fixes as well as general maintenance for Java SE 6 until the end of Java SE 6 Extended Support in June 2017.
How can EBS customers obtain Java 6 updates after the public end-of-life?
EBS customers can download Java 6 patches from My Oracle Support. For a complete list of all Java SE patch numbers, see:
Both JDK and JRE packages are contained in a single combined download after 6u45. Download the “JDK” package for both the desktop client JRE and the server-side JDK package.
Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?
This upgrade is highly recommended but remains optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 desktop clients.
Java 6 is covered by Extended Support until June 2017. All E-Business Suite customers must upgrade to JRE 7 by June 2017.
Coexistence of JRE 6 and JRE 7 on Windows desktops
The upgrade to JRE 7 is highly recommended for EBS users, but some users may need to run both JRE 6 and 7 on their Windows desktops for reasons unrelated to the E-Business Suite.
Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 7 will be invoked instead of JRE 6 if both are installed on a Windows desktop. For more details, see “Appendix B: Static vs. Non-static Versioning and Set Up Options” in Notes 290807.1 and 393931.1.
Applying Updates to JRE 6 and JRE 7 to Windows desktops
Auto-update will keep JRE 7 up-to-date for Windows users with JRE 7 installed.
Auto-update will only keep JRE 7 up-to-date for Windows users with both JRE 6 and 7 installed.
JRE 6 users are strongly encouraged to apply the latest Critical Patch Updates as soon as possible after each release. The Jave SE CPUs will be available via My Oracle Support. EBS users can find more information about JRE 6 and 7 updates here:
What do Mac users need?
Mac users running Mac OS X 10.9 can run JRE 7 plug-ins. See this article:
- EBS Release 12 Certified with Mac OS X 10.9 with Safari 7 and JRE 7
Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?
JRE is used for desktop clients. JDK is used for application tier servers
JDK upgrades for E-Business Suite application tier servers are highly recommended but currently remain optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6 for application tier servers.
Java SE 6 is covered by Extended Support until June 2017. All EBS customers with application tier servers on Windows, Solaris, and Linux must upgrade to JDK 7 by June 2017. EBS customers running their application tier servers on other operating systems should check with their respective vendors for the support dates for those platforms.
References
R12 – How to Find XML Publisher Version
The version of a specific Java Class has a one to one relationship with the currently installed version of Oracle XML Publisher.
/home/applprod >strings $OA_JAVA/oracle/apps/xdo/common/MetaInfo.class|grep -i ‘XML Publisher’
Oracle XML Publisher 5.6.3
/home/applprod >
Version 5.6.3 ships with update pack 12.1.3, which is Patch 8919491
“Patch R12.ATG_PF.B.delta.3: Oracle Applications Technology 12.1.3 Product Family Release Update Pack”
Method Two: SQL Query
Method Three: Output PDF of the report (Document Properties)
Share this:
R12 – GL-Receiving India Drill Down Query
Here is the query for Link between General Ledger and Receiving India data’s.
SELECT msib.segment1 item,
msib.description,
rsh.receipt_num,
mp.organization_code,
gjl.accounted_dr,
gjl.accounted_cr,
gjh.je_source,
gjh.je_category
FROM apps.gl_je_headers gjh,
apps.gl_je_lines gjl,
apps.gl_code_combinations_kfv gcc,
apps.gl_import_references gir,
apps.rcv_transactions rt,
apps.rcv_shipment_headers rsh,
apps.rcv_shipment_lines rsl,
apps.gl_je_batches gjb,
apps.mtl_parameters mp,
apps.mtl_system_items_b msib
WHERE gjh.je_header_id = gjl.je_header_id
AND gjh.je_header_id = gir.je_header_id
AND gir.je_header_id = gjl.je_header_id
AND gir.je_line_num = gjl.je_line_num
AND gjb.je_batch_id = gir.je_batch_id
AND GJH.JE_SOURCE = ‘Purchasing India’
AND gjh.period_name =’Nov-14′
AND gjl.reference_2 = ‘India Localization Entry’
AND gjl.code_combination_id = gcc.code_combination_id
AND rt.organization_id = mp.organization_id
AND rt.transaction_id = gjl.reference_5
AND rt.shipment_header_id = rsh.shipment_header_id
AND rsl.shipment_header_id = rsh.shipment_header_id
AND rsl.shipment_line_id = rt.shipment_line_id
AND msib.inventory_item_id = rsl.item_id
AND msib.organization_id = rt.organization_id
AND gjl.period_name IN
(SELECT DISTINCT period_name
FROM APPS.GL_PERIODS
WHERE START_DATE BETWEEN :P_FROM_PERIOD AND :P_TO_PERIOD
);
Note: This one was not linked with India Localization SLA Tables, its a direct link between GL and Localization Info’s
Share this:
Difference between Oracle E-Business Suite R12.1 and R12.2
I will try to analyze architectural overview of the latest updates, installation and upgrade options, new configuration options, and new tools for hot-cloning and automated “lights out” cloning in R12.2.
Release 12.2 will replace Oracle Containers for Java (OC4J) 10g with WebLogic Server 11g
Release 12.2 Database tier will run RDBMS 11gR2 to support online patching
There will be number of updates coming in release R12.2, from a technology stack perspective, EBS 12.2 will be notable for two things:
1-Replacing Oracle Containers for Java (OC4J) 10g with WebLogic Server 11g
EBS 12.2 will use WebLogic Server from Fusion Middleware 11g in place of OC4J 10g as part of the release’s internal technology stack. Other additional new Fusion Middleware 11g components used will include WebLogic JSP and UIX 11g
2-Online Patching support via 11gR2 Edition-Based Redefinition
EBS 12.2 will use the 11gR2 Database’s Edition-Based Redefinition features to provide support for Online Patching. Edition-Based Redefinition is really exciting new technology. From the 11gR2 Application Developer’s Guide:
“Edition-based redefinition enables you to upgrade the database component of an application while it is in use, thereby minimizing or eliminating down time.
“To upgrade an application while it is in use, you copy the database objects that comprise the application and redefine the copied objects in isolation. Your changes do not affect users of the application—they continue to run the unchanged application. When you are sure that your changes are correct, you make the upgraded application available to all users.”
It is not released yet but It will include significant changes to the Application Server architecture, It will use RDBMS Version 11gR2 or higher, It will change Patching, Cloning, the User Experience
Comparison of Oracle E-Business Suite 12.1 vs 12.2 Installation Steps
Oracle E-Business Suite 12.1 installation
Database Technology Stack
Database
Apps Technology Stack
Apps File System
Oracle E-Business Suite 12.2 installation
Following will be main features planned for R12.2 installations:
Native Technology Stack Install
Database RMAN Restore
Dual File System
Optional 11g Home for Upgrades
WebLogic Server (WLS)
Graphical UI to manage WLS Domain
Administration (Start/Stop WLS Instances)
Configuration (Config and Deploy, Cluster, Host, JDBC, JMS Messaging)
Monitoring (Server & Application Performance)
Troubleshooting (Performance Tuning, Log Viewer)
Following will be main features planned for R12.2 Native Technology Stack Install:
Better integration with Oracle
Universal Installer
Faster Technology Stack Installation
Silent-mode calls to install and configure Oracle Database 11.2, WebLogic Server (WLS) and Oracle HTTP Server (OHS)
AutoConfig Integration
Following will be main features planned for R12.2 Database RMAN Restore:
Simplifies Integration with Grid Infrastructure
Seamless integration with different storage methods (OCFS2, NFS, etc)
Faster integration with Automatic Storage Management (ASM)
Following will be main features planned for R12.2 Dual File System:
Online Patching allows users to continue using the application while patching
Dual File System allows replacing files with minimum downtime
Improves High Availability
Dual Port Pool configuration
Easier port assignments
Allows port customization in runtime and patching file systems
Following will be main features planned for R12.2 Optional 11g Home for Upgrades:
Allow integration with an existing 11gR2 Oracle Home
Simplified Technology Stack Upgrade
Reduced Upgrade time
Following will be main features planned for R12.2 WebLogic Server (WLS):
Graphical User Interface
WebLogic Scripting Tool (WLST)
High Availability & Failover
Consolidated Administration, Configuration and Deployment
Monitoring & Messaging
Troubleshooting framework
Integration with OAM
Share this:
Now JRE 1.7.0_67 Certified with Oracle E-Business Suite
You do not need to wait for a certification announcement before applying new JRE 1.6 or JRE 7 releases to your EBS users’ desktops.
For EBS 11i:
For EBS 12.0, 12.1, 12.2
EBS + Discoverer 11g Users
The fix for those issues was first included in JRE 1.6.0_23. These fixes will carry forward and continue to be fixed in all future JRE releases on the JRE 6 and 7 codelines. In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22 on the JRE 6 codeline, and JRE 7u10 and later JRE 7 codeline updates.
EBS users will continue to receive critical bug fixes and security fixes as well as general maintenance for Java SE 6 until the end of Java SE 6 Extended Support in June 2017.
Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?
Java SE 6 is covered by Extended Support until June 2017. All EBS customers with application tier servers on Windows, Solaris, and Linux must upgrade to JDK 7 by June 2017. EBS customers running their application tier servers on other operating systems should check with their respective vendors for the support dates for those platforms.
Share this:
Solved: Internet explorer has closed this webpage to help protect your computer
Internet explorer has closed this webpage to help protect your computer
A malfunctioning or malicious add-on has caused Internet Explorer to close this webpage.
We were unable to return you to the page you were viewing. Internet Explorer has stopped trying to restore this website. It appears that the website continues to have a problem.
Solution-1:
1) Take backup of jvm.dll located at c:Program FilesOracleJInitiator1.3.1.xbinhotspot directory. (Depending on JInitiator version you have)
2) Copy jvm.dll from C:Program FilesJavajre1.6.0_07binclient (or whichever highest version of jre you have) to c:Program FilesOracleJInitiator 1.3.1.xbinhotspot
3) Clear browser cache and also Oracle Jar cache
For XP:
(Remove all files from c:documents and settings<username>Oracle Jar cache)
4) Close all the browsers and restart.
Solution-2:
In case if you are unable to find the jvm.dll in that location or if the above solution didn’t work for you, you can download the working jvm.dll from here.
I hope your issue should have been resolved now !
Share this: