ORACLE TECHNOLOGY

1. An application module pool is a collection of application module instances of the same type. 2. This pool of application module instances is shared by multiple browser clients whose typical "think time" between submitting web pages allows optimizing the number of application module components to be effectively smaller than the total number of active users working on the system. 3. That is, twenty users visiting the web site from their browser might be able to be serviced by 5 or 10 application module instances instead of having as many application module instances as you have browser users. 4. As a performance optimization, when an instance of an application module is returned to the pool in "managed state" mode, the pool tracks session references to the application module. The application module instance is still in the pool and available for use, but it would prefer to be used by the same session that was using it the last time because main...

1. For performance reasons, ADF keeps a pool of application modules in memory. It tries to give each session the same application module as the session used during the last request; however, this might not be possible during peak load of your application. 2. In this case, ADF saves the application modules state in a database table so the application module can be used by another session. This is called passivation . 3. When the first session needs the application module again, its state is retrieved from the database process known as activation . 4. If you have made an error in your code and depend on some variable that is not persisted correctly when your application module state is stored, you will experience mysterious errors under high load.   Enable/Disable Application Module Pooling : Right-click on your application module, choose Configurations.By default, each application module has two configurations. Ensure that the one ending in …Local is selected and then c...

1.AM encapsulate the view object instances and business service methods necessary to perform a unit of work.   2.Each application module has its own transactional context and holds its own database connection. This means that all of the work a user performs using view objects from one application module is part of one database transaction.   3.Application modules can have different granularity, but typically, you will have one application module for each major piece of functionality.   4.If you wish, you can combine multiple application modules inside one root application module. This is called nesting and allows several application modules to participate in the transaction of the root application module. This also saves database connections because only the root application module needs a connection.     5. When a root application module contains other nested application modules, they all participate in the root application mod...

Q:What are Entity Objects? A: Entity objects are Data Access Objects (DAOs) that are responsible for persisting & caching data, validation, and encapsulating business rules. ·  Represent a database table or other data source. ·  Handles database caching. ·  Contains attributes representing the database columns. ·  Encapsulates attribute-level and entity –level validation logic. ·  Can contain custom business methods. Q : Can an entity object be based on two Database Objects(tables/views) or two Webservices? A : No, Directly its not possible to create EO using multiple tables.    Entity objects will always have one to one relationship with a database object or web service. Q.What is Control Hints in Entity Object configuration? A: Control hints are associated with the current view or entity attribute. All view objects inherit the hint values at run time. Control hints for data controls and bindings, including: Labels, Date & curre...

In order for an ADF application to support High Availability in clustered environment with server fail over. The below steps must be followed in developing an ADF application. 1. All Manage Beans must implement Serializable. 2. UI component bindings must be declared in a bean with shorter scope (backing bean scope or request scope). 3. If it needs to be declared in Manage Bean with PageFlowScope (Not recommended) , please ensure you declare the binding as transient. 4. Any objects that are declared as an attribute in Manage Bean must be Serialized. 5.ADF component bindings can not support the Serializable.To make them support HA use the following code for component binding,getters and setters in pageFlowScope bean .   ex. Normal ADF code for binding,getters and setters will be as follows    Private RichSelectOneChoice partySelect       public void setPartySelect(RichSelectOneChoice partySelect) {      ...

In some scenario we need to get the chields and set some value or refresh the chield components. Following code is one example for that. 1.There is one RichPanelGroupLayout with following childerns       a)RichPanelFormLayout and it has two RichInputText  RichPanelGroupLayout pGrpLayout = this. cbPopPalGrpLayout ;             List pGrpLayoutList = pGrpLayout.getChildren();                         for(int i = 0 ; i < pGrpLayoutList.size() ; i++){                 if(i > 0){                     RichPanelFormLayout pfl = (RichPanelFormLayout)pGrpLayoutList.get(i);         ...

Refer the following link for code guideline. Using this we can increase the application performance. ADF Code Guidelines for developing ADF application