WebLogic Server Configuration Reference
AlgorithmType=( "High-Availability" | "Load-Balancing" )
FailoverRequestIfBusy=( "true" | "false" )
PoolList="list of JDBCConnectionPool names"
Targets="list of Target names"
If set to "High availability", the connection pools are set up as an ordered list. That is, every time an application asks the Multipool for a connection, it tries to get a connection from the first pool in its list. If unable to get a valid connection, it tries the next pool in its list. The process is repeated until a valid connection is obtained, or until the end of the list is reached, in which case an exception will be thrown.
Note that the Multipool will only move to the next pool in the list when there is a real problem with the pool, for example the database is down or the pool disabled. For the cases where all connections are busy, the Multipool behaves as a single pool and an exception is thrown.
If the algorithm is set to "Load balancing," the Multipool will distribute the connection requests evenly to its member pools. This algorithm also performs the same failover behavior as the high availability algorithm.
If set, before a MultiPool fails over to the next connection pool in the list, WebLogic Server calls the callback application indicated and waits for a return. Depending on the value returned from the callback application, the MultiPool will either try the same connection pool, failover to the next connection pool, or fail and throw an exception.
A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable items of the same type. For example, the server prioritizes and deploys all EJBs before it prioritizes and deploys startup classes.
Items with the lowest Deployment Order value are deployed first. There is no guarantee on the order of deployments with equal Deployment Order values. There is no guarantee of ordering across clusters.