Vistors Access

Calendar

Archives

Authors

Author Archive

The WebLogic Server 11g comes with a built-in Web server which is adequate for displaying its own Web pages and could be used for applications hosted on the WebLogic servers. You could use a more industrial-strength Web server such as Oracle HTTP Server (OHS) from the Web Tier, but you don’t have to. In this tutorial you are going to use the built-in Web server and front-end it with the Web Tier Web Cache to speed up Web pages. The application that will be cached is the Administration console, normally found on port 7001. That port will continue to work uncached, but users of the application will be instructed to use a different URL (same host, but port 7785) for future traffic so that it will be cached. So to access the uncached Administration Console, you would use

http://yourhost:7001/console; and to access the cached Administration Console you would use http://yourhost:7785/console.

In this tutorial, you would learn how to:

Configure the Web Cache using the Enterprise Manager for caching some (and optionally all) of the traffic headed to the WLS application server

Just like the need of Multi Node architecture for high availability Oracle introduced a new file system called Edition Based File System in R12.2, which enables the high availability while the patches are being applied. For our imagination, basically it is divided into two. They are Run and Patch Edition. Conceptually there is a third one – Non Edition. Naming wise, they are referred as fs1,f2 and ne_fs. The file system fs1 and fs2 can switch their roles between patch and run based on the patching cycle. The file system ne_fs contains the data required by both, which will never be changed by run and patch file system life cycles.