Skip to main content

ADF High Availability for clustered environment

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) {
            this.partySelect = partySelect;
           }

     public RichSelectOneChoice getPartySelect() {
              return partySelect;
    }


Change this to following code in your pageFlowScope bean to support HA.

import org.apache.myfaces.trinidad.util.ComponentReference;
Private ComponentReference partySelect;


     
public void setPartySelect(RichSelectOneChoice partySelect) {
      this.partySelect =ComponentReference.newUIComponentReference(partySelect);
}

public RichSelectOneChoice getPartySelect() {
       if(partySelect !=null){
           return (RichSelectOneChoice)partySelect.getComponent();
       }
     return null;
}


The following files must be modified to make an ADF application High Available in clustered environment.

adf-config.xml

<adf-controller-config xmlns="http://xmlns.oracle.com/adf/controller/config">
     <adf-scope-ha-support>true</adf-scope-ha-support>
</adf-controller-config>

weblogic.xml

<session-descriptor>
      <persistent-store-type>replicated_if_clustered</persistent-store-type>
</session-descriptor>

For testing, please add the below parameter in your weblogic domain 
setDomainEnv.cmd
-Dorg.apache.myfaces.trinidad.CHECK_STATE_SERIALIZATION=all










Comments

Popular posts from this blog

The file store "WLS_DIAGNOSTICS" could not be opened

WLS_DIAGNOSTIC ERROR weblogic.store.PersistentStoreException: [Store:280073]The file store "WLS_DIAGNOSTICS" could not be opened because it contained a file with the invalid version 1. A file of version 2 was expected. When you get this error while running your application on internal weblogic server delete the following file WLS_DIAGNOSTICS000000.DAT search the file in following path C:\jdev_work\system11.1.1.5.37.60.13\DefaultDomain this file is in DefaultDomain folder of your jdev. and delete the WLS_DIAGNOSTICS000000.DAT file . and run your applicatuon

Overview Editor for bc4j.xcfg

This is used to customize the configuration settings for the application pool, connection pool, and transactions. Select the Application Module, then select a configuration from the Configurations list. You can specify a Default Configuration from the dropdown to use with selected application module. Edit the name of the configuration in Details. Its having 3 tabs 1.Database and Scalability 2. Properties 3. Custom Properties Database and Scalability Tab : In Database and Scalability you can mention the JDBC data source definition for each application module. You can choose to connect to a JDBC data source or to a JDBC URL.The default connection type is the default data source. A data source is a vendor-independent encapsulation of a database server connection on the application server. 1. Data sources ( JNDI name) offer advantages over a JDBC URL connection because the data source can be tuned, reconfigured, or remapped without changing the deployed application. 2. JDB...

WebCenter Deployment Architecture

The main components of the deployment architecture are: • WebLogic Server • Portlets deployed in Portlet Container • Metadata storage for customization information • Enterprise Content Management solution with Content Adapters • WebCenter Services • WebCenter Search • Identity Management         WebLogic Server, which is a Java EE–compliant application server, is at the center of WebCenter. WebCenter applications are Java EE applications that are deployed to WebLogic Server. WebCenter Spaces is a prebuilt custom application using WebCenter Framework and Services. Portlets : WebCenter applications can consume portlets. Portlets are deployed into a Portlet Container and are accessed by various HTTP-based network protocols such as WSRP and SOAP. Oracle WebCenter supports several portlet APIs such as JSR 168 and PDK Java.   Metadata Services : WebCenter applications can be customized or personalize...