Cisco Cisco Unified Customer Voice Portal 10.0(1) Release Notes
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
7
Release Notes for Cisco Customer Voice Portal, Release 3.0(0) Updated 6/24/05
CVP 3.0 Considerations
JNDI Name:
User Management:
If you wish to activate the User Management System, in your CVP VXML Studio Application, go to the
Properties page by right-clicking on the Application in Studio and choose Properties. Under the General
Settings tab, check the Enable checkbox next to the User Management label. Then choose the type of
database you are using, either MySQL or MSSQL. Now enter the string you entered in the
<LABEL_YOU_CHOOSE> from the above Context into the JDNI Name text field.
Properties page by right-clicking on the Application in Studio and choose Properties. Under the General
Settings tab, check the Enable checkbox next to the User Management label. Then choose the type of
database you are using, either MySQL or MSSQL. Now enter the string you entered in the
<LABEL_YOU_CHOOSE> from the above Context into the JDNI Name text field.
Database Node:
If you are using the Database node, enter the string you entered in the <LABEL_YOU_CHOOSE> from
the above Context into the JDNI Name property of the Settings tab of your Database node.
the above Context into the JDNI Name property of the Settings tab of your Database node.
Database Connection Pooling:
Under heavy load conditions, enabling Database Connection Pooling is strongly recommended. A
database connection pool creates and manages a pool of connections to a database. Recycling and
reusing already existing connections to a database is more efficient than opening a new connection. For
further information on Tomcat Database Pooling please see,
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html.
database connection pool creates and manages a pool of connections to a database. Recycling and
reusing already existing connections to a database is more efficient than opening a new connection. For
further information on Tomcat Database Pooling please see,
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html.
MySQL:
If you are connecting to a MySQL database, add these entries to your <ResourceParams> list to turn on
and fine turn your database connection pool.
and fine turn your database connection pool.
<!--To configure a DBCP DataSource so that abandoned dB connections are removed and recycled-->
<parameter>
<name>removeAbandoned</name>
<value>true</value>
<value>true</value>
</parameter>
<!--Use the removeAbandonedTimeout parameter to set the number of seconds a dB connection has been
idle before it is considered abandoned-->
idle before it is considered abandoned-->
<parameter>
<name>removeAbandonedTimeout</name>
<value>60</value>
<value>60</value>
</parameter>
<!--Use the removeAbandonedTimeout parameter to set the number of seconds a dB connection has been
idle before it is considered abandoned-->
idle before it is considered abandoned-->
<parameter>
<name>logAbandoned</name>
<value>true</value>
<value>true</value>
</parameter>
<!-- The logAbandoned parameter can be set to true if you want DBCP to log a stack trace of the code which
abandoned the dB connection resources. -->
abandoned the dB connection resources. -->
<parameter>
<name>maxActive</name>
<value>100</value>
<value>100</value>