Description:
How to obtain the number of database connections opened during TIBCO BusinessWorks Collaborator (BWC) application deployment/undeployment. To configure for your environment, in order to limit the large number of inactive database connections during BWC application deployment/undeployment, follow the steps below.

Monitoring and configuring limits for database connections during TIBCO BusinessWorks Collaborator (BWC) application deployment/undeployment.

Procedure

======

1). Check the entries in the tables below which hold entries for minimum/max connections for the domain.

====================
select * from ADMAP

select * from AUMAP

select * from PAMAP
====================

2). For monitoring database connections opened by BWC, you can try hitting query “select count(*) from v$session table where username=bwc55” where bwc55=dummy user name to demonstrate.

====================
BWC 5.5.1 desktop is built on top of the PS 5.2.1 layer. The PS layer stores lot of information such as portlet items, layouts, pages, etc. in Admin POF.  PS accesses Admin POF using Admin APIs.
====================

3). When you stop/kill Tomcat instances, the db connections get disconnected immediately. You can check this by running the above query after stopping the Tomcat server.

4). For configuring limits for database connections set “java.property.tibcoadmin.database.expiryInterval”, follow the steps below.

==========================

You can set the expiry interval in AdministrationDomain.properties and AuthorizationDomain.properties minimum (>2000) so that we make sure that we do not have more connections open.

***********************
tibcoadmin.database.expiryInterval=2000
***********************
Note: We would have separate connection pooling for the Administrator domain and Authorization domain. Each application domain would have its own connection pooling. For Administrator, you would need to comment the following in the tibcoadmin_<domain>.tra if you want the Administrator to pick up the values that you had configured in AdministrationDomain.properties and thorizationDomain.properties.

# The maximum number of database connections to cache per ConnectionPool.
#java.property.tibcoadmin.database.maxConnections=10

# The amount of time (in milliseconds) that database connections will be
# cached when not in use.
# java.property.tibcoadmin.database.expiryInterval=1800000

# The amount of time (in milliseconds) that a database connection request
# will have to wait before a time out occurs and an error is thrown.
# java.property.tibcoadmin.database.waitTimeoutInterval=30000
=========================