Namespace: urn:mace:shibboleth:2.0:resolver
Schema: http://shibboleth.net/schema/idp/shibboleth-attribute-resolver.xsd
...
We suggest the use of externally defined connections using the <BeanManagedConnection> element to fully tailor a suitable connection pool.
Reference
| Localtabgroup |
|---|
Name | Type | Required? | Description |
|---|
jdbcDriver
| string | Y | Java class name of the JDBC driver used to connect to the database | jdbcURL
| string | Y | JDBC URL to connect to. These are usually of the form jdbc:databaseProduceName:databaseSpecificInformation | jdbcUserName
| string |
| The username to use to communicate with the database | jdbcPassword
| string |
| The password to use to communicate with the database |
|
Examples
| Code Block |
|---|
|
<SimpleManagedConnection
jdbcDriver="org.hsqldb.jdbc.JDBCDriver" jdbcURL="jdbc:hsqldb:mem:RDBMSDataConnectorStore"
jdbcUserName="jdbcUser" jdbcPassword="Whatever" /> |
This is exactly equivalent to defining a <BeanManagedConnection> referring to this configuration.
Equivalent Native Spring definition
| Code Block |
|---|
| language | xml | title | Equivalent Native Spring definition |
|---|
|
<bean id="simpleDataConnector" class="org.apache.commons.dbcp2.BasicDataSource"
p:driverClassName="org.hsqldb.jdbc.JDBCDriver"
p:url="jdbc:hsqldb:mem:RDBMSDataConnectorStore"
p:username="jdbcUser"
p:password="Whatever"
p:maxTotal="20"
p:maxIdle="5"
p:maxWaitMillis="5000" /> |
...