Versions Compared

Old Version 54

changes.mady.by.user Alan Orth

Saved on

compared with

New Version 55

changes.mady.by.user Alan Orth

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Improve Tomcat database pooling section

...

Code Block
languagexml
titleserver.xml
  <GlobalNamingResources>
...
    <Resource
        name='jdbc/instance'
        description='Our DSpace DBMS connection pool'
        type='javax.sql.DataSource'
        auth='Container'
        username='USER'
        password='SECRET'
        driverClassName='org.postgresql.Driver'
        url='jdbc:postgresql://dbms.example.com:5432/dspace'
        initialSize='5'
        maxTotal='50'
        maxIdle='15'
        minIdle='5'
        maxWaitMillis='5000'
        />
...
  </GlobalNamingResources>

And configure Then add a <ResourceLink> for that global resource in to each web application's context configuration. The name parameter here is local to the application context, and must be jdbc/dspace:

Code Block
languagexml
<Context
...
  <ResourceLink
    name='jdbc/dspace'
    global='jdbc/instance'
    type='javax.sql.DataSource'
   />
...
</Context>

Notice that the name given in the context's ResourceLink matches the value that DSpace automatically looks for, and the global parameter in the ResourceLink matches the name of the global Resource. See the JNDI Datasource HOW-TO for more information about this configuration.

...