@@ -55,5 +55,28 @@ client side pool. Note that, when UCP is used, it takes care of attaching and
55
55
releasing server connections. There is no need to explicitly call
56
56
` attachServerConnection() ` /` detachServerConnection() ` with UCP.
57
57
58
+ ## UCPSample.java:
59
+ Universal Connection Pool (UCP) is a client side connection pool. UCP
60
+ furnishes a rich set of features to support scalability in single database
61
+ instance as well as built-in features to support high-availability and
62
+ scalability in RAC and Active Data Guard environments. UCP along with RAC,
63
+ RAC One and ADG is a tested and certified combination for handling database
64
+ failovers. Refer to this sample for using UCP and setting UCP properties
65
+ such as ` minPoolSize ` , ` maxPoolSize ` , etc.
66
+
67
+ ## UCPWithDRCPSample.java:
68
+
69
+ Database Resident Connection Pool (DRCP) is the server side connection pool.
70
+ DRCP should be used in a scenario when there are a number of middle tiers but
71
+ the number of active connections is fairly less than the number of open
72
+ connections. DRCP when used along with and Universal Connection Pool(UCP) as the client
73
+ side connection pool improves the performance. The sample shows UCP with DRCP
74
+ in action. The purpose of the client-side pooling mechanism is to maintain the
75
+ connections to Connection Broker. Client-side connection pools must attach and
76
+ detach connections to the connection broker through ` attachServerConnection() `
77
+ and ` detachServerConnection() ` . DRCP should be used in a scenario when there are
78
+ a number of middle tiers but the number of active connections is fairly less
79
+ than th number of open connections.
80
+
58
81
----
59
82
0 commit comments