Best practices for browser settings and performance on fusion applications.pdf
April 20, 2017 | Author: Srinivasa Rao Asuru | Category: N/A
Short Description
Download Best practices for browser settings and performance on fusion applications.pdf...
Description
Document 1385107.1
1 of 3
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...
Best Practices for Browser Settings and Performance on Fusion Applications (Doc ID 1385107.1) In this Document Purpose Troubleshooting Steps Client Machine Settings/Recommendations Browsers Recommendations General Best Practices Disk cache settings and recommendations for Internet Explorer, Firefox and Chrome Bookmarking URLs First Time Access - Cold Browser/Server References
APPLIES TO: Oracle Fusion Sales Cloud Service - Version 11.1.7.0.0 and later Oracle Fusion Application Toolkit - Version 11.1.1.5.1 and later Oracle Fusion Application Toolkit Cloud Service - Version 11.1.4.0.0 and later Oracle Fusion Receivables Cloud Service - Version 11.1.10.0.0 to 11.1.10.0.0 [Release 1.0] Information in this document applies to any platform.
PURPOSE This document providing best practices for best client and browser settings to be used with Fusion Applications.
TROUBLESHOOTING STEPS Client Machine Settings/Recommendations • Use a Client Machine with the minimum CPU and RAM requirements. Current recommendations are listed here: http://www.oracle.com /us/products/system-requirements/overview/index.html • Check current RAM memory usage by viewing the ‘Task Manager’, and ‘End Process’ for any unnecessary applications / processes, ensuring at least 500MB – 1GB available of RAM. • The browser downloads several megabytes of static content – ensure your C: partition is not too fragmented or low on space. Check your browser settings (see Section 3 below) to ensure they do not delete cached files upon closing the browser. • Use a ‘ping’ or ‘tracert’ command (see below) to contact the application servers and determine basic network speed. This will alert you to any network issues that may affect the performance of the application. Educate the users on inherent Network latency issues. • Be aware of anti-virus scanner processes, and similar background processes, which could begin while a demonstration, or test, is in progress. Reviewing the Task Manager will help. • XMLHTTP: XMLHTTP support must be enabled. • JavaScript: JavaScript support must be enabled. • Flash: If using Flash and the Data Visualization Tools (DVT) components, Flash 10+ is required. • Browser Add-ons: You should disable or remove any third party browser add-ons, such as httpAnalyzer, or Firebug, because they have the capability to negatively interfere with the execution of the browser, and the ADF Faces client framework, and degrades performance. Here is an example of using ping and tracert commands: C:\Documents and Settings\Myuser>ping myhost Pinging myhost [IP address] with 32 bytes of data: Reply Reply Reply Reply
from from from from
[IP [IP [IP [IP
address]: address]: address]: address]:
bytes=32 bytes=32 bytes=32 bytes=32
time=104ms time=197ms time=219ms time=106ms
TTL=57 TTL=57 TTL=57 TTL=57
Ping statistics for [IP address]: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 104ms, Maximum = 219ms, Average = 156ms
3/13/2017 9:48 PM
Document 1385107.1
2 of 3
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...
C:\Documents and Settings\Myuser>tracert myhost Tracing route to myhost [IP address] over a maximum of 30 hops: 1 2 3 4
69 59 60 213
ms ms ms ms
148 136 58 226
ms ms ms ms
58 58 58 210
ms ms ms ms
myhost1 myhost2 myhost3 myhost4
[IP [IP [IP [IP
address] address] address] address]
Trace complete.
Browsers Recommendations • Always use the latest certified version of browsers. Browsers with good performance are listed here: http://www.oracle.com/us/products /system-requirements/overview/index.html • For a list of all supported browsers, please reference the following supported browsers link: http://www.oracle.com/technetwork /developer-tools/jdev/jdev11gr2-cert-405181.html#Browsers • Browser comparison test cases for a simple page show Apple Safari, Google Chrome, and Firefox latest versions to be the fastest in that order. • Review the certified browsers on My Oracle Support -> Certifications -> Search for "Oracle Fusion Applications". Review the section "Desktop Applications, Browsers and Clients"
General Best Practices • Default Browser: For best performance of Oracle Fusion Applications, use the latest browser version of Mozilla Firefox. • First Time Access: Warm-up the server and browser cache by executing the entire Business flow. A freshly bounced server will require time to load all libraries etc. It is a known issue that the first time accessing a page can be slower due to loading the page artifacts (buttons, images, etc) in the browser. Clearing the browser cache will result in a slow page rendering at first access. The same issue can happen on the first attempt to run a page after the server was restarted. • Session: Do not close the browser session whenever possible. Use the same browser session for ongoing work, so all the artifacts that are cached on the client browser are retained. • Browser History: In Firefox Options, under Privacy -> History, if Firefox is set to "Use Custom settings for history", please make sure "Clear history when Firefox closes" is unchecked. • Tabs: Having multiple tabs in the Firefox browser might negatively impact the performance of the browser. • Anti-virus software: Reschedule any Anti-Virus software that is running during work hours to prevent slow performance of the computer. • CPU Usage: Check the Task Manager for available memory and CPU usage. If you see any processes consuming a high amount of resources, highlight them and click ‘End Process’.
Disk cache settings and recommendations for Internet Explorer, Firefox and Chrome • Firefox: Increase the disk cache to 1024MB. In Firefox type “about:config” in the url address bar to set the disk capacity for the cache. Change the value of ‘browser.cache.disk.capacity’ to ‘1024000’. Increase the cache entries size. Set a value of ‘-1’ (unlimited) for ‘browser.cache.disk.max_entry_size’.
TIP: Make a cache backup if you are using Firefox. If Firefox crashes and you lose your cache, then you can use ‘restore cache from backup’ and restart Firefox. IMPORTANT NOTE: Some Firefox installations have a bug were the disc caches are not being used. You can verify if you have this bug by entering “about:cache” in the Firefox url address bar. If the “disc cache device” section shows “Storage in Use” 0 after having used the browser on Fusion applications, then your browser has that problem. SOLUTION 1: Go to the cache directory outlined in the “disc cache device” sections via explorer and remove everything under “Profiles”. Restart Browser – use it and check again. SOLUTION 2: Upgrade to the latest version of Firefox, and then check the above steps again. • Internet Explorer: Increase the disk cache to 1024MB. In Internet Explorer, go to Tools> Internet Options> General> Browsing History> Temporary Internet Files> ‘Disk space to use’, to change cache size. Then in preferred settings, the default option is set to “Check for newer versions of stored pages”. If you choose the “Never” option to disable checking for newer files for cache files, this may lead to incompatibilities of static files when a new patch version is applied on the server. New static files can be downloaded manually by deleting the browser’s cache. For IE 9+ running on machines with low resources, pages using CSS3 styles may be slow. To fix this uncheck "Use Software rendering instead of GPU rendering" by navigating to Tools -> Internet Options -> Advanced -> Accelerated graphics. • Chrome: Increase the disk cache to 1024MB. In Chrome right Click on the Google Chrome icon in desktop. Select Properties> Shortcut Tab. Add -disk-cache-size=1073741824 at the end of the Target box. Click OK.
Bookmarking URLs
3/13/2017 9:48 PM
Document 1385107.1
3 of 3
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...
• After the initial login, bookmarked URLs (with the exception of deep linking) are NOT supported, as these URLs contain session IDs and infrastructure context that are subject to change. NOTE: Using such bookmarked URLs may cause blank page issues. • Use the short URL bookmarks without session information. Here are some examples of valid URLs after removing the session details: ATK Login: https:///homePage/faces/AtkHomePageWelcome Homepage: https:///homePage/faces/FuseWelcome HCM: https:///hcmCore/faces/HcmFusionHome CRM: https:///customer/faces/CrmFusionHome Financials: https:///ledger/faces/FinancialsFusionHome Scheduled Processes: https:///essUi/faces/EssUIShell Manage Users: https:///hcmCore/faces/UserSearch • Do NOT use the OAM login URL like: https:///oam/server/obrareq.cgi?encquery This URL is redirected initially when a user logs in to one of the above URLs, and should not be used as a bookmark for logging in.
First Time Access - Cold Browser/Server It is a known issue that first access of the page can be slower due to loading the page artifacts (buttons, images, etc) in the browser. Clearing the browser cache will result in a slow page rendering at first access. Same issue can happen on the first attempt to run a page after the server was restarted.
REFERENCES
Didn't find what you are looking for?
3/13/2017 9:48 PM
View more...
Comments