Installing and Configuring Oracle Application Server Web Cache with Oracle E by aashu4uiit

VIEWS: 403 PAGES: 19

									Installing and Configuring Oracle Application Server Web Cache with Oracle E-Business Suite 11i (Aug 2007)
This document contains information for deploying the Oracle Application Server Web Cache with E-Business Suite Release 11i. This note is intended for administrators who perform the following tasks: Oracle Application Server Web Cache administration Oracle E-Business Suite Release 11i administration The most current version of this document is available on Oracle Metalink as Note 306653.1 .There is a change log at the end of this document to track the changes made to this document. Click here to access the PDF version of this document. Attention Oracle E-Business Suite Release 11i is certified for integration with Oracle Application Server Web Cache 10g (10.1.2.2.0). The Web Cache software must be installed in a separate ORACLE_HOME on an existing application tier or on a standalone server node. This integration does not include integration of E-business Suite 11i with Oracle Application Server components like Oracle Single Sign-On Server, Oracle Internet Directory, Oracle Discoverer and Oracle Portal. Section 1: Overview Oracle Application Server Web Cache Origin Server Section 2: Supported Architecture and Configurations Section 3: Deployment Options 3.1: Oracle Application Server Web Cache as a Caching Server for E-Business Suite 11i Section 4: Installation of the Oracle Application Server Web Cache 4.1: Obtain CD Pack for Oracle Application Server Web Cache 4.2: Install Oracle Application Server Web Cache on an Application Tier or on a Standalone Node

4.2.1: Installing Oracle Application Server Web Cache Standalone (10.1.2.0.2) 4.2.2: Installing Oracle Application Server Web Cache bundled with Oracle Application Server 10g (10.1.2.0.2) 4.3: Upgrade WebCache to 10.1.2.2 PatchSet 4.4: Verify the Installation 4.3.1: Verify the status of Oracle Application Server Web Cache Processes 4.3.2: Verify the Login for Performing Oracle Application Server Web Cache Administration Section 5: Required Patches Section 6: Configuration Details 6.1: Configure Oracle Application Server Web Cache to Use E-Business Suite as an Origin Server 6.1.1: Connect to the Oracle Application Server Web Cache Administration Page 6.1.2: Configure Oracle Application Server Web Cache to Listen on a Different Port (Optional) 6.1.3: Configure Web Cache Site definitions for E-Business Suite 6.1.4: Configure E-Business Suite as an Origin Server (Required) 6.1.5: Configure Network Timeouts (Required)

6.2: Add Rules for Caching E-Business Suite Content 6.3: Configure Oracle Application Server Web Cache as the Entry Point 6.4: Re-Register SSO Partner application if E-Business Suite 11i is Integrated with Infrastructure (Optional) 6.5: Configure E-Business Suite to Use Forms Servlet Mode 6.6: Configure SSL for Traffic Between Browser and Oracle Application Server Web Cache 6.7: Configure SSL for Traffic Between Oracle Application Server Web Cache and E-Business Suite Application Middle Tier 6.8: Specify OracleAS Web Cache Server in variable "OProcMgr Trusted Nodes" 6.9: Run AutoConfig on E-Business Suite 11i Application Middle Tier and Restart the Services Section 7:Configuring Oracle Web Cache As a Load Balancer (Optional) 7.1:Configure Session Binding Settings 7.2:Configure Jserv Layer Load Balancing Section 8:Known Issues

Section 9: Appendices Oracle Application Server Web Cache Administrators Guide 10g Release 2 (10.1.2.0.2) Oracle Application Server Web Cache FAQ Troubleshooting Oracle Application Server Web Cache

Section 1: Overview
Oracle Application Server Web Cache
Oracle Application Server Web Cache is designed to help E-Business Suite system administrators reduce infrastructure costs and manage Web site performance by caching data. Unlike legacy cache servers that only handle static data, Oracle Application Server Web Cache combines caching, compression and assembly technologies to accelerate the delivery of both static and dynamically generated Web content. In addition to caching, Oracle Application Server Web Cache can also be used to: Load Balance Reverse Proxy Failover and Surge Protection to minimize downtime Personalize Attributes for Caching With OracleAS Web Cache, an E-Business Suite environment can serve dynamic content faster, to more customers, using fewer computing resources than ever before.

Origin Server
Origin servers are nodes that run the business and application data. In an EBusiness Suite environment, the application web tiers are considered to be the origin servers. Please refer to the manual Oracle Application Server Web Cache Administrators Guide 10g Release 2 (10.1.2.0.2) for further information on Web Cache.

Section 2: Supported Architectures and Configurations
Oracle Application Server Web Cache version 10.1.2.0.2 must be installed in a separate ORACLE_HOME on an existing application tier server node or on a standalone server node. The following components are required for integrating Oracle Application Server Web Cache with E-Business Suite 11i:

Component Name

Version

Comments

Oracle Application Server Web Cache 10.1.2.2.0 10g Oracle E-Business Suite 11i 11.5.9 and later

For iStore, please refer to metalink for individual iStore release Web Cache version certification.

Section 3: Deployment Options 3.1: Oracle Application Server Web Cache as a Caching Server for E-Business Suite 11i
Oracle Application Server Web Cache can be used as a Caching Server for the application middle tier servers that are configured for intranet and internet users of E-Business Suite 11i. The Caching rules defined in Section 6.2: Add Rules for Caching E-Business Suite Content determine which E-Business Suite objects are cached.

Section 4: Installation of the Oracle Application Server Web Cache
This section outlines steps required to install Oracle Application Server Web Cache 10g (10.1.2.0.2).

4.1: Obtain CD Pack for Oracle Application Server Web Cache
Oracle Application Server Web Cache is shipped with the Oracle Application Server 10g CD pack. You can obtain these CD packs from Oracle Store or Oracle Technology Network.

4.2: Install Oracle Application Server Web Cache on an Application Tier or on a Standalone Node 4.2.1: Installing Oracle Application Server Web Cache Standalone (10.1.2.0.2)
The standalone version of Oracle web cache is available in the companion CDs (CD1 & CD2) shipped with the Oracle Application Server 10g CD pack. Unzip the software bundle into a stage directory ( Disk1 & Disk2) and use the Oracle Universal Installer available in Disk1 to install the standalone version of web cache. Provide the following inputs when the installer prompts: 1. Select 'Web Server Services 10.1.2.0.2' from product to install screen 2. Choose 'OracleAS Web Cache 10.1.2.0.2' from installation type screen Complete the installation by answering rest of the prompts appropriate for your installation.

4.2.2: Installing Oracle Application Server Web Cache Bundled with Oracle Application Server 10g (10.1.2.0.2)
To install Oracle Application Server Web Cache bundled with the Oracle Application Server 10g, you must choose the J2EE and Web Cache installation type available from the product to install screen. Use the Oracle Universal Installer available in Disk1 to install web cache. Complete the installation by answering the prompts appropriate for your installation.

4.3 Upgrade WebCache to latest version(10.1.2.2.0).
There are two ways to upgrade WebCache:

1. If you are using the same ORACLE_HOME for Web Cache and other Oracle Application Server 10g components such as Oracle Portal or Oracle Discoverer, all of these components will be upgraded to the same level by applying the Oracle Application Server and Oracle Developer Suite 10g Release 2 (10.1.2) Patchset 2 (10.1.2.2.0). Download patch 4960210 and complete the steps detailed in the README. 2. If you are using a standalone Web Cache configuration, you can upgrade that component to the latest version included in the Oracle Application Server and Oracle Developer Suite 10g Release 2 (10.1.2) Patchset 2 (10.1.2.2.0). Download patch 4960210 and complete the steps detailed in the README. Note The Web Cache upgrade preserves your existing Caching, Personalization, and Compression Rules.

4.4: Verify the Installation
4.4.1: Verify the status of Oracle Application Server Web Cache Processes
Oracle Web Cache processes are started automatically by the configuration assistant that is run as part of the installation process. You can verify the installation by doing the following: Issue the following command for an Oracle Application Server Web Cache Standalone installation.
[web_cache_oracle_home]/webcache/bin/webcachectl status

Issue the following command for a Oracle Application Server Web Cache bundled with Oracle Application Server 10g
[web_cache_oracle_home]/opmn/bin/opmnctl status

The above command displays the status of: Oracle Application Server Web Cache Admin Server Oracle Application Server Web Cache Cache Server Oracle Application Server Web Cache Cache Monitor Process If any of the above listed processes are down, depending on your installation type, you can use the webcachectl or opmnctl to start the processes. Refer to the Oracle Application Server Web Cache Administration guide for information.

4.4.2: Verify the Login for Performing Oracle Application Server Web Cache Administration
Verify whether the Oracle Application Server Web Cache administrator can log in to the administration page using the following URL:
http://<your_webcache_host>:<your_webacache_admin_port>/

Please refer to [web_cache_oracle_home]/install/portlist.ini for the list of ports configured by the Oracle Universal Installer for your Web Cache Installation. By default, webcache_admin_port is set to port 9400. The default username and password for the administrator user is ias_admin/<supplied password at installation time> for standalone Web Cache. If you chose a different password during the installation process, enter that password instead of the default password.

Section 5: Required Patches 5.1: Patch Requirements for Oracle E-Business Suite Release 11i
Apply the following patches in the order shown:
Required Patch No Description Component Platform Comments

3219567 Patch 11i.TXK.B Technology Stack

E-Business All Suite 11i

4104924 TXK (FND) AUTOCONFIG TEMPLATE ROLLUP PATCH K (July 2005)

E-Business All Suite 11i

This patch is included in 11.5.10 MP and RI This patch is included in the following updates: 11.5.10 ORACLE EBUSINESS SUITE CONSOLIDA TED UPDATE 2 (3460000) 11.5.10 CU2 for ATG Product family

(4125550) 4450710 Oracle 9iAS 1.0.2.2.2 Backport for UseWebCacheIP Directive Oracle 9i All Application Server 1.0.2.2.2 Apply Patch (4393827) MLR ON TOP OF 1.0.2.2-8.1.7.4 FOR CPUJUL2005 before applying this one off patch. Apply Patch (2617419) which gives opatch binary needed to apply MLR patch. Apply this before applying 4569559 Patch 4569559 includes 2 bug fixes required for Oracle EBusiness Suite 11i customers to run OracleAS WebCache 10.1.2.0.2. This patch also adds an option to configure OracleAS WebCache 10.1.2.0.2 to run in the loadbalance only mode. This mode disables all features in OracleAS WebCache except load balancing of HTTP(S)

4569559 MLR on top of Oracle All 10.1.2.0.2(Note: If you Application have already upgraded Server your system to Oracle Web Webcache10g(10.1.2.2.0), Cache you can skip this step. 10.1.2.0.2 Patch Set 2 (10.1.2.2.0) already includes this patch)

5882583 MLR on top of 10.1.2.2.0 Oracle All Application Server 10g Release 2 Patchset 2 (10.1.2.2.0)

requests. Oracle EBusiness Suite customers are not recommended to enable the load-balance only mode. By default this feature is turned off. To understand how it should be used, please refer to OracleAS WebCache documentation. Apply Patch (2617419) which gives opatch binary needed to apply MLR patch.

Section 6: Configuration Details
This section outlines steps required to configure Oracle Application Server Web Cache with E-Business Suite 11i.

6.1: Configure Oracle Application Server Web Cache to Use EBusiness Suite as an Origin Server 6.1.1: Connect to the Oracle Application Server Web Cache Administration Page
Log in to the Web Cache Administration page as the user with administration privileges.

6.1.2: Configure Oracle Application Server Web Cache to Listen on a Different Port (Optional)

By default, Oracle Application Server Web Cache listens for client requests on port 7777. If port 7777 was already assigned to another component, then Oracle Universal Installer assigns a different port for Oracle Web Cache. Refer to [web_cache_oracle_home]/install/portlist.ini for the list of ports configured by the Oracle Universal Installer for your Web Cache Installation. If you choose to configure an additional listening port or edit the default port, then select Ports > Listen Ports from the Oracle Application Server Web Cache Manager navigator frame and then add the new listen port or edit the existing listen port depending on your requirements. Refer to steps Adding a Listening Port and Changing Site Configuration documented in Task 6 of Oracle Application Server Web Cache Administration guide for further information. Note Please note that the Oracle Application Server Web Cache 10.1.2 is configured with three default Site-To-Server Mapping as shown below :
1, <Webcache Host Name>, 7777, -, Unrestricted, <Webcache Host Name>, 80, No 2, *, 7777, -, Exclude Fragments, <Webcache Host Name>, 80, No 3, *, *, -, Exclude Fragments, <Webcache Host Name>, 80, No

When creating a new Site-to-Server Mapping for the new nondefault port, the entry should be created above the entries shown above. This could be done when creating the new Site-toServer Mapping (using Insert Below/Above buttons), or could be done afterward using the Move Up/Down button.

6.1.3: Configure Web Cache Site definitions for E-Business Suite
The installation process creates a default site definition that uses the host name and listening port of the computer on which Oracle AS Web Cache was installed. If the default site definition is not adequate for your configuration, create additional site definitions. To create new site definitions from OracleAS Web Cache Manager: 1. In the navigator frame, select Origin Servers, Sites, and Load Balancing > Site Definitions. The Site Definitions page appears. 2. Specify the site information: o In the Site Definitions page, click Add Site. The Add Site dialog box appears. o In the Host Name field, enter the site host name. Do not add protocol information (http:// or https://) to the host name.

o o o o o

o

URL Path Prefix field leave it blank. In the Port Number field, enter the port number from which the Web site is listening for incoming HTTP requests. In the HTTPS Only Prefix field, enter "/" URL Parameter to Ignore leave it blank. In the Client-Side Certificate field, select Required or Not Required to specify that OracleAS Web Cache require or not require client-side certificates from browsers. Keep default value as it is for rest of the fields.

Please refer Oracle Application Server Web Cache Administration to get more information on above configurations fields.

6.1.4: Configure E-Business Suite as an Origin Server (Required)
Select Origin Servers, Sites, and Load Balancing > Origin Servers from the Oracle Application Server Web Cache Manager navigator frame. Edit or add an entry for the E-Business Suite web server hostname and port number. Enter the following values for the listed parameters: Host Name: <Your E-business suite web server hostname> Port: <Your E-business suite web server port number> Capacity: 100 Failover Threshold: 5 Ping URL: / Ping Interval: 100 Protocol: http/https Select Origin Servers, Sites, and Load Balancing > Site-to-Server Mapping from the Oracle Application Server Web Cache Manager navigator frame. Edit or add an entry for the Site-to-Origin server mapping. For section Specify Site Name, select the radio button and choose the Site Server and port you specified above when defining the listen ports. For section Select either application Web Servers or proxy servers to which this Site is mapped, choose the box for the Origin Server and Port you defined in the previous step. Note The default installation of webcache configures a site to server mapping for the webcache host port 7777 to port 80. This server mapping can be reconfigured to sent requests webcache

receives on port 7777 to the E-Business Suite origin server.

6.1.5: Configure Network Timeouts (Required)
Select Properties > Network Timeouts from the Oracle Application Server Web Cache Manager navigator frame and set values for the following: Keep Alive Timeout to 60 seconds Origin Server Timeout to 600 seconds

6.2: Add Rules for Caching E-Business Suite Content
Select Rules for Caching, Personalization, and Compression > Caching, Personalization, and Compression Rules from the Oracle Application Server Web Cache Manager navigator frame. Edit or Add the following site specific rules for compression and caching of E-Business Suite Content. Oracle Application Server Web Cache ships with a set of predefined caching, personalization and compression rules for all the sites. You can choose to delete those rules if they are not applicable to any site in your web cache configuration.
URL and HTTP POST Meth Body od(s) Param eters

Expres Name sion URL Expression Type

Post Body Expre ssion

Cac hing Polic y

ESI Propag Compre ation ssion Policy

E-biz html page s

Regul ar \.html?$ Expre ssion

E-biz Imag e files E-biz Imag e files

Regul ar \.(gif|jpe?g|png)$ Expre ssion Regul ar \.(bmp)$ Expre ssion

GET, GET with quer y N/A string , POS T GET, GET with N/A quer y string GET, GET N/A with quer

.*

For All Cac Propa Brows he gate ers

N/A

Cac Propa None he gate

N/A

For Cac Propa Nonhe gate Netsca pe

y string Regul E-biz /pls/<SID>/fndgfm/fnd_he ar help GET N/A Expre lp\.get/US/ICX/@ files ssion GET, E-biz GET File Java with Exten .js N/A script quer sion files y string GET, GET E-biz File with PDF Exten .pdf N/A quer Files sion y string E-biz Casc File ade Exten .css style sion shee ts E-biz JTF Page s E-biz Java Serv er Page s Regul ar /OA_HTML/jtflogin.jsp Expre ssion GET, GET with N/A quer y string

Brows ers Only N/A For All Cac Propa Brows he gate ers

N/A

Cac Propa None he gate

N/A

Don 't Propa None Cac gate he For NonNetsca Cac Propa pe he gate Brows ers Only Cac Propa None he gate

N/A

GET N/A GET, GET with quer y N/A string , POS T

N/A

Regul ar \.jsp Expre ssion

.*

Don For all 't Propa Brows Cac gate ers he

Note Customers using Oracle iStore may need to perform additional

setup described in Oracle iStore 11.5.10 RUP3 Release notes to take advantage of the caching features of Oracle iStore 11i with Oracle Application Server Web Cache. The caching rules mentioned in the iStore documentation need to be added above the generic rules listed in Section 6.2: Add Rules for Caching E-Business Suite Content of this document. Select Properties > Resource Limits and set the value of maximum cached Object Size to 1024kb. For the caching rules to take effect, ensure that the changes you made above are saved and Oracle Application Server Web Cache processes are restarted.

6.3: Configure Oracle Application Server Web Cache as the Entry Point (Required)
On all the Applications middle-tier nodes, run the AutoConfig Context Editor as documented in the Oracle MetaLink Note 165195.1 "Using AutoConfig to Manage System Configurations with Oracle Applications 11i ". In the Context Detail screen, set the following configuration values: set the webentry point, s_webentryhost, to the Oracle Application Server Web Cache Server set the webentry domain, s_webentrydomain, to the domain name of the Oracle Application Server Web Cache Server set the active webport, s_active_webport, to the port where the Oracle Application Server Web Cache Server listens for client requests set the webentry protocol, s_webentryurlprotocol, to the protocol value the clients use to access the Oracle Application Server Web Cache Server set the login page, s_login_page, to <webentry protocol>://<webentry point>.<webentry domain>:<active webport>/oa_servlets/AppsLogin . Replace <webentry protocol>, <webentry point>, <webentry domain>, and <active webport> with their respective values set the webssl port, s_webssl_port to the value of s_active_webport, if you have configured Oracle Application Server Web Cache to listen on a port other than 443 for SSL requests. You can also use the HTTP load balancing configuration wizard available in Oracle Applications Manager (OAM) to configure Oracle Application Server Web Cache as the entry point. For more information, refer to OAM On-line Help: Help > Oracle Applications Manager > System Configuration > AutoConfig > Configuration Wizards.

If you are using the HTTP load balancing configuration wizard to configure the entry point, make sure that "t_session_persistent" box is checked when prompted by the wizard. Note Oracle products such as Oracle Configurator, Order Management, iStore, Order Capture, Quoting, iPayment, iStore, and Pricing rely on the Oracle Wallet to establish a successful connection in SSL mode from the Database tier . Please follow the instructions in Oracle MetaLink note 123718.1 "A Guide to Understanding and Implementing SSL with Oracle Applications 11i " to configure SSL on the database server .

6.4: Re-Register SSO Partner application if E-Business Suite 11i is Integrated with Infrastructure (Optional)
This step is required only if your E-Business suite 11i is Integrated with SSO/OID following metalink Note 233436.1. After configuring OAS Web Cache as entry point for your 11i instance, you need to re-register SSO Partner application. Please follow "Manual Procedures for SSO/OID Registration and Deregistration" provided under "Appendix C: Advanced Configuration - Manual SSO/OID Registration" of metalink note 233436.1, to perform this.

6.5: Configure E-Business Suite to Use Forms Servlet Mode (Recommended)
The Forms Servlet mode allows all HTTP traffic including Forms traffic to be routed through Oracle Application Server Web Cache. Follow the Instructions in Oracle MetaLink note 201340.1 "Using Forms Listener Servlet with Oracle Applications 11i" to configure Oracle E-Business Suite to use Forms Servlet mode.

6.6: Configure SSL for Traffic Between Browser and Oracle Application Server Web Cache (Recommended)
To configure SSL for traffic between the Web Browser and Oracle Application Server Web Cache, you must follow the instructions provided in Section 9 of Oracle Application Server Web Cache Administrator's Guide 10g Release 2 (10.1.2.0.2) . If you have an existing certificate available for the server on which you have installed Oracle Application Server Web Cache, you can choose not to create a

new certificate and import the existing certificate using the Oracle Wallet Manager shipped with Web Cache. For more information, refer to Oracle Application Server Web Cache Administration guide. An example to export and import a certificate created with openssl is given below. Export the third party certificate to PKCS12 format using openssl version 0.9.7 or higher. The following command combines the certificate's public key, private key and root certficate into one file which can be be imported into Oracle Wallet Manager. $ openssl pkcs12 -export -descert -in server.crt -inkey server.key -certfile ca.crt -name <friendly name> -out ewallet.p12 Import the certificate into Oracle Wallet Manager by following the instructions in Oracle Application Server Web Cache Administration guide. Ensure that the Auto Login box is checked so that Oracle Web Cache Server can read the certificate on server startup. If you have configured Oracle Application Server Web Cache to listen on a port other than 443 for SSL requests, make sure that the value of s_webssl_port is set to the value of s_active_webport in the application's context file.

6.7: Configure SSL for Traffic Between Oracle Application Server Web Cache and E-Business Suite Application Middle Tier (Optional)
To configure SSL for traffic between the Oracle Application Server Web Cache and E-Business Suite Applications middle tier, you must follow the instructions provided in Oracle MetaLink note 123718.1 "A Guide to Understanding and Implementing SSL with Oracle Applications 11i ".

6.8: Specify OracleAS Web Cache Server in variable "OProcMgr Trusted Nodes" (Required only for Portal integration)
For Customers using Oracle Portal with Oracle E-Business Suite 11i, which includes E-Business Suite 11i portlets, additional configurations is required to allow Oracle AS Web Cache access to the E-Business portlets. Using the AutoConfig Context Editor tool update the value of variable "OProcMgr Trusted Nodes" (oacore_trusted_oproc_nodes) to include Oracle AS Web Cache Server/Host Name. "OProcMgr Trusted Nodes" is a list of comma seperated host names with domain names or IP addresses. Example: "OProcMgr Trusted Nodes" set to "ap123sun.us.oracle.com,mywebcache.us.oracle.com"

6.9: Run Autoconfig on E-Business Suite 11i Application Middle Tier and Restart the Services (Required)
Run AutoConfig on the E-Business Suite 11i Applications middle tier to complete the configuration. Please refer to the Oracle MetaLink Note 165195.1 "Using AutoConfig to Manage System Configurations with Oracle Applications 11i " for more information on AutoConfig. After AutoConfig completes successfully, restart the services.

Section 7: Configuring Oracle Web Cache as a Load Balancer (Optional)
This section outlines the setup required to configure Oracle Web Cache as a load balancer. Instructions given below assume that you have configured more than one origin server to serve the client requests. Configuring Oracle Web Cache solely as a software load balancer by specifying the parameter "LOADBALANCE ON="YES"" in the web cache configuration file "internal.xml" is not supported for Oracle E-Business Suite 11i and also this setting is not intended for Oracle EBusiness Suite 11i. Web Cache as a load balancer works without this parameter for Oracle E-Business Suite 11i. This parameter when set, it turns off the caching and compression features provided by Oracle Web Cache. Please refer to Oracle Application Server Web Cache Administration guide for more information.

7.1: Configure Session Binding Settings
Select Origin Servers, Sites, and Load Balancing > Session Binding from the Oracle Application Server Web Cache Manager navigator frame. Select the Site Name and set values for the following: Please select a session: Any Set-Cookie Please select a session binding mechanism: Cookie-based

7.2: Configure Jserv Layer Load Balancing
Repeat the following procedure for each origin server in the Load Balancing pool of machines. Run the AutoConfig Context Editor as documented in the Oracle MetaLink Note 165195.1 "Using AutoConfig to Manage System Configurations with Oracle Applications 11i ". In the Context Detail screen, set the following configuration values: Set the value of Configure Multi Web Node (s_multiwebnode) to yes Set the value of OA Core zone name (s_oacore_zone_name) to root Run AutoConfig to generate Configuration files using AutoConfig

Restart Oracle HTTP Server. Note This configuration requires the value of Oproc Manager Port (s_oprocmgr_port) to be same across all the origin servers. Refer to Oracle MetaLink Note 217368.1 "Advanced Configurations and Topologies for Enterprise Deployments of E-Business Suite 11i" for more information on Jserv Layer Load Balancing.

Section 8: Known Issues
Bug Description Number Platfor Resolution m Comments

User redirected to 501005 non-secure url on 8 timeout

All

Close the browser and start a new session.

This issue is seen only on instances configured to use ssl accelerators/terminat ors.

Customers using iStore Or Marketing and have encountered this SSL handshake fail issue, please error in event_log 464447 request a one-off file. But this is not All 8 backport for your affecting any release OR you can functionality in 11i. apply 11.5.10 CU (Consolidated Update 2) to resolve this issue. Unset the env Webcache daemon Linux variable defunct processes 444102 ( LD_ASSUME_KERN when 5 Redha EL before starting LD_ASSUME_KERN t) webcache EL is set to 2.4.19 processes.

Section 9: Appendices

Oracle Application Server Web Cache Administrators Guide 10g Release 2 (10.1.2.0.2) Oracle Application Server Web Cache FAQ Troubleshooting Oracle Application Server Web Cache


								
To top