Stimmen - 0, Durchschnittliche Bewertung: 0
(
)
)
|
Dieses Gerät hat auch andere Anweisungen:
PC Desktops - HP Integrity NonStop H-Series (16.73 mb)
PC Desktops - HP Integrity NonStop H-Series (957.56 kb)
PC Desktops - HP Integrity NonStop H-Series (881.66 kb)
PC Desktops - HP Integrity NonStop H-Series (965.62 kb)
PC Desktops - HP Integrity NonStop H-Series (676.93 kb)
PC Desktops - HP Integrity NonStop H-Series (393.72 kb)
PC Desktops - HP Integrity NonStop H-Series (776.57 kb)
Anleitung Zusammenfassung
java.util.properties
r
parameter have a higher precedence over the command-line properties.
command-line properties have a higher precedence over file properties set through the
r
-Dt4sqlmx.properties option.
The connection pooling feature is available when the Java application uses the
q
DriverManager class to obtain a JDBC
connection. The connection pool size is determined by the maxPoolSize property value and minPoolSize property value.
The Type 4 driver has a connection-pool manager for a combination of catalog, schema, username, and serverDataSource.
q
Therefore, connections with the same catalog, schema, username, and serverDataSource combinations are pooled together. The
connection pooling property values that are used at the time of obtaining the first connection for a given catalog, schema,
username, and serverDataSource combination is effective throughout the life of the process. An application cannot change these
property values subsequent to the first connection for a given catalog, schema, username, and serverDataSource combination.
As in the basic
q
DataSource object implementation, a Java application can enable statement pooling by setting the property to a
non-zero positive value.
Connection Using the DataSource Interface
The javax.sql.DataSource interface is the preferred way to establish a connection to the database because it enhances the
application portability. The Type 4 driver implements the javax.sql.DataSource interface and returns a connection object when
an application requests a connection using the getConnection method in the DataSource interface.
Using a DataSource object increases application portability by allowing the application to use a logical name for a data source instead
of providing driver-specific information in the application. A logical name is mapped to a javax.sql.DataSource object by means
of a naming service that uses the Java Naming and Directory Interface (JNDI).
The following table describes the properties that you can use to identify a Type 4 driver data source object:
DataSource Object Properties
Property Name
Type
Value
Description
If the default catalog and schema
are not specified, the Type 4 driver
catalog
String
See catalog.
allows SQL/MX to follow its own
rules for defaults.
schema
String
See schema
See catalog above.
The registered
ConnectionPoolDataSource
name. When this string is empty,
connection pooling is used by
dataSourceName
String
default with the pool size
determined by the maxPoolSize
property and minPoolSize
property of the basic
DataSource object.
description
String
Any valid identifier
The description of the data source.
Sets maximum number of physical
See
connections that the pool could
maxPoolSize
maxPoolSize
int
contain. This number includes both
Property.
free connections and connections in
use.
The total number of
See maxStatements
PreparedStatement objects
maxStatements
int
Property.
that the connection pool should
cache.
See
Limits the number of physical
minPoolSize
minPoolSize
int
connections that can be in the free
Property.
connection pool.
...Dieses Handbuch ist für folgende Modelle:
PC Desktops - HP Integrity NonStop J-Series (303.72 kb)
PC Desktops - HP NonStop G-Series (303.72 kb)
PC Desktops - HP NonStop L-Series (303.72 kb)