Skip to main content

Configuring Multi Data Source in Weblogic (Load-Balancing between Data Sources)

We can Create a Multi data Source in Weblogic which can perform Load balancing/ Fail-over among multiple generic Data sources. The Applications deployed on Weblogic will point to this Multi data Source and This Multidata source will do the load balancing/ fail-over internally.

Below are the steps to create a Multi data source:


  • Login to the weblogic console and click services. Click on Data Sources and create a new generic data source.


  • Provide all the connection details and test the connection with Database.


  • After this create another generic Data source. MultiData Source will do a load balancing between these 2 data sources. 
  • After both the data sources are created. Click on Services--> Data Sources. Create a new Multi Data Source.
  • Provide the name of the Multi data source, JNDI name of the Data Source and select either load balancing or Fail-Over from Algorithm type. 


  • Select the server where Multidata source will be deployed (Server where application would be running).

  • Select the type of driver.

  • Add all the generic data sources to Multi data source. click Finish.
  • Now Multidata source is created and can be used by applications to connect.
  • Below is a sample java code through which we can connect to Multi data source which internally will connect to any of generic data source.


Context ctx = null;


      Hashtable ht = new Hashtable();
      ht.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
      ht.put(Context.PROVIDER_URL,"t3://<Weblogic_host>:<port>");
       Connection conn = null;
        ctx = new InitialContext(ht);
        javax.sql.DataSource ds 
          = (javax.sql.DataSource) ctx.lookup ("JDBC Multi Data Source-0"); //Name of Multi data source
        conn = ds.getConnection();
return conn;










Comments

Popular posts from this blog

Developing Prepopulate Adapter with OIM 11g R2

1.      Prepopulate Adapter in OIM uses the plugin point oracle.iam.request.plugins.PrePopulationAdapte r. 2.      Write the Java code which returns the value which has to be populated on the form. 3.      This code will implement the plugin point oracle.iam.request.plugins.PrePopulationAdapte r. Code Snippet: - package com.oracle.oim.utility.eventhandler; import java.io.Serializable; import java.util.Iterator; import java.util.List; import java.util.logging.Logger; import oracle.iam.identity.exception.NoSuchUserException; import oracle.iam.identity.exception.UserLookupException; import oracle.iam.identity.usermgmt.api.UserManager; import oracle.iam.identity.usermgmt.vo.User; import oracle.iam.platform.Platform; import oracle.iam.platform.authz.exception.AccessDeniedException; import oracle.iam.request.exception.RequestServiceException; import oracle.iam.request.vo.Beneficiary; import oracle.iam.request.vo.RequestData; public c

OIM Tuning

Application Module tuning is a critical setting which will affect the UI performance. Following are the recommended application module settings for OIM and these are already set out-of-box (OOB) in later releases of OIM 11g R2. Ensure that these settings are implemented as recommended in your environment. -Djbo.ampool.doampooling=true -Djbo.ampool.minavailablesize=1 -Djbo.ampool.maxavailablesize=120 -Djbo.recyclethreshold=60 - Djbo.ampool.timetolive=-1 -Djbo.load.components.lazily=true - Djbo.doconnectionpooling=true -Djbo.txn.disconnect_level=1 - Djbo.connectfailover=false -Djbo.max.cursors=5 - Doracle.jdbc.implicitStatementCacheSize=5 - Doracle.jdbc.maxCachedBufferSize=19 open DOMAIN_HOME/bin/setDomainEnv.sh file for the WebLogic Server instance.find these lines: JAVA_OPTIONS="${JAVA_OPTIONS}" export JAVA_OPTIONS and change it to: JAVA_OPTIONS="-Djbo.ampool.doampooling=true -Djbo.ampool.minavailablesize=1 -Djbo.ampool.maxavailablesize=120 -D

What is Application Instance

Application instance is a provisionable entity. It is a combination of IT resource instance (target connectivity and connector configuration) and resource object (provisioning mechanism) . Creating and managing application instances are performed by using the Oracle Identity System Administration. Once Created Application Instance can be requested from the catalog. Application instances can be connected or disconnected.  Connected application  instance -It has a connector defined for the provisioning of entities. Account is created in the target system real time in case of connected Application Instance. Disconnected  application instance - It is used for the provisioning of a disconnected resource, for which  a connector is not defined, and therefore, the provisioning is performed manually by the administrator. A mail trigger system can also be attached which sends the account creation/modification/deletion mails to the application owner.