MADHAN APPS DBA

JVM Parameter Settings for 64-bit Java on WLS Web Tier: ========================================= If you are running Oracle E-Business Suite on 64-bit Java, bear in mind the following key points: 1. You can support 150-180 users per 1 GB of JVM heap size. Usually, one JVM is allocated per 2 CPUs. 2. Only the maximum allocated heap (Xmx) has an impact on response time. Changing the initial heap size (Xms) does not have an impact on response time. 3. For best results, use multiple managed instances. For example, two managed instances with a total of 4 GB heap size for each instance will provide a much better response times than one JVM with a total heap size of 8 GB. 4. Further to the previous point, use JVMs with a maximum of 4 GB, and scale for more users by using additional managed instances. There are two benefits from doing this: • Garbage collection (GC) activity is more easily balanced (automatically) with multiple managed instances. • Each instance will be able to uti

EBS R12.2 Login Flow When a HTTP request is made for EBS, the request is received by the Oracle HTTP Server (OHS). When the configuration of OHS is for a resource that needs to be processed by Java, such as logging into EBS, the OHS configuration will redirect the request to the Web Logic Server (WLS) Java process (OACore in this case). WLS determines the J2EE application that should deal with the request, which is called "oacore". This J2EE application needs to be deployed and available for processing requests in order for the request to succeed.   The J2EE application needs to access a database and does this via a datasource which is configured within WLS. Login HTTP headers When the EBS login works OK, the browser will be redirected to various different URLs in order for the login page to be displayed.  The page flow below shows the URLs that will be called to display the login page: /OA_HTML/AppsLogin EBS Login URL /OA_HTML/AppsLocalLogin.jsp Redir