WebSphere Liberty database
connection pooling with Content Manager 8.5.0.6 Java API

Content

The Content Manager Java API now supports WebSphere Liberty database connection pooling.

To use WebSphere Liberty database connection pooling with the Content Manager Java API see the following steps.

1. Setup Content Manager cmbpool.ini.

Set JavaPool=DKPoolWAS, JDBCPrefix=jdbc/ and JavaPoolSubType=Liberty in the cmbpool.ini file to use WebSphere Liberty database connection pooling.

2. Setup of WebSphere Liberty server database connection pool in server.xml.

The features for jndi-1.0 and jdbc-4.0 need to be specified in the server.xml file of your WebSphere Liberty server. Specify the data source for the database connection pool.

Example

server.xml

<server description="new server">

<!-- Enable features -->
<featureManager>
<feature>jsp-2.2</feature>
<feature>localConnector-1.0</feature>
<feature>servlet-3.1</feature>
<feature>jndi-1.0</feature>
<feature>jdbc-4.0</feature>
</featureManager>

<!-- To access this server from a remote client add a host attribute to the following element, e.g. host="*" -->
<httpEndpoint httpPort="9087" httpsPort="9450" id="defaultHttpEndpoint"/>

<!-- Automatically expand WAR files and EAR files -->
<applicationManager autoExpand="true"/>

<applicationMonitor updateTrigger="mbean"/>


<dataSource id="wascmdb1" jndiName="jdbc/wascmdb1" type="javax.sql.ConnectionPoolDataSource">
<jdbcDriver>
<library>
<fileset dir="C:/db2jar4" includes="db2jcc4.jar,db2jcc_license_cisuz.jar,db2jcc_license_cu.jar"/>
</library>
</jdbcDriver>

<properties.db2.jcc databaseName="icmnlsdb" driverType="4" password="Password" portNumber="50000" serverName="mycmsrv.ibm.com" user="icmconct"/>
<connectionManager connectionTimeout="180" maxPoolSize="100" minPoolSize="1"/>
</dataSource>

<webApplication id="SimpleServletProject" location="SimpleServletProject.war" name="SimpleServletProject"/>

<enterpriseApplication id="CMAPIEProjectT3" location="CMAPIEProjectT3.ear" name="CMAPIEProjectT3"/>
</server>



3. Setup Content Manager cmbicmsrvs.ini or DKDatastoreICM connect method connection string

ICMJNDIREF option in the cmbicmsrvs.ini or JNDIREF in the DKDatastoreICM connect method connection string should be set to the jndi name specified for your database connection pool data source in the server.xml file of your WebSphere Liberty server.

Example (This example will worked with the server.xml database connection pool data source example above)

cmbicmsrvs.ini

ICMSERVER=mycmdb1
ICMSERVERREPTYPE=DB2CON
ICMSCHEMA=ICMADMIN
ICMSSO=FALSE
ICMDBAUTH=SERVER
ICMREMOTE=FALSE
ICMHOSTNAME=mycmsrv.ibm.com
ICMPORT=50000
ICMREMOTEDB=icmnlsdb
ICMNODENAME=
ICMOSTYPE=
ICMJDBCDRIVER=
ICMJDBCURL=
ICMJNDIREF=wascmdb1
ICMDBVER=
ICMGMTSYSATTRTS=FALSE
ICMGMTDOCROUTINGATTRTS=FALSE
ICMGMTUSERATTRTS=FALSE
ICMGMTUSERATTRDATE=FALSE
ICMGMTUSERATTRTIME=FALSE
ICMRMCOMMTYPE=HTTP
ICMRMSSLTRUSTSTORE=
ICMRMSSLTRUSTSTORETYPE=
ICMRMSSLTRUSTSTOREPROVIDERNAME=
ICMRMSSLTRUSTMGRALGORITHM=
ICMRMSSLTRUSTMGRPROVIDERNAME=
ICMRMSSLKEYSTORE=
ICMRMSSLKEYSTORETYPE=
ICMRMSSLKEYSTOREPROVIDERNAME=
ICMRMSSLKEYMGRALGORITHM=
ICMRMSSLKEYMGRPROVIDERNAME=
ICMRMSSLCERTIFICATEAUTH=FALSE
ICMRMSSLCBCPROTECTION=TRUE
ICMRMSSLPROTOCOLMINTLS12=FALSE
ICMRMSSLCIPHERSUITEFILTERING=TRUE
ICMRMSSLCONTEXTPROTOCOL=
ICMRMSSLRNGALGORITHM=
ICMRMUSESSLFORURLBASEDRETRIEVES=FALSE
ICMRMCONNTIMEOUT=
ICMRMCONNPOLLINTERVAL=
ICMRMCONNREADTIMEOUT=
ICMDBSSL=FALSE
ICMDBSSLPORT=
ICMDBSSLTRUSTSTORE=
ICMDBSSLTRUSTSTORETYPE=
ICMDBSSLKEYSTORE=
ICMDBSSLKEYSTORETYPE=
ICMDBSSLVERSION=
ICMDBSSLCIPHERSUITES=
ICMDBSSLDISTINGUISHEDNAMEMATCH=FALSE
ICMINITACLCACHESIZE=1
ICMSYSATTRTSASJAVASQLTS=FALSE
ICMGMTSYSTS=FALSE
ICMJDBCPOOLCFG=FALSE
ICMJDBCPOOLTYPE=
ICMJDBCPOOLPREFIX=
ICMALLOWADMINIDFORDBPOOL=FALSE
ICMTRUSTWASAUTH=FALSE


DKDatastoreICM connect method connection string


"SCHEMA=ICMADMIN;DBAUTH=SERVER;REPTYPE=DB2CON;REMOTE=FALSE;HOSTNAME=mycmsrv.ibm.com;PORT=50000;REMOTEDB=icmnlsdb;JNDIREF=wascmdb1;SQLUID=icmconct;SQLPWD=password"