Categories

About BigPicture

BigPicture installation and updates

Quick start with BigPicture

BigPicture Sizing Guide

Cloud vs. Server - Key Differences in BigPicture on These Platforms

BigPicture Export

Progress Tracking

Tutorials and tips

Integrations

Concept of a Program

Setting up BigGantt and BigPicture to support next-gen projects


BigPicture Cloud Backlog

About BigGantt

BigGantt installation and updates

Cloud vs. Server - Key Differences in BigPicture on These Platforms

Shortcuts

Knowledge Base

Tutorials and tips

Trust Center

BigPicture 8 is here!

Discover the landmark edition of the Atlassian Marketplace top-selling app! The new version is available to all Cloud, Server and Data Center users. Visit BigPicture 8 Documentation to learn more about it.

This configuration affects BigPicture, BigPicture Enterprise, BigGantt and BigTemplate, indicated as "the product" below.

SYSTEM-182 - Getting issue details... STATUS


The product can communicate with Jira database using one of the following strategy:

Jira database connection as configured in dbconfig.xml

This is a default configuration, no action required. In this mode, database configuration is loaded from dbconfig.xml file located in Jira home folder.

In this scenario, Jira database connection pool is shared with the product. BigPicture is optimized for database reads (utilizing caching quite aggresively) and does execute very few queries after its warm-up process. As a result sharing the same database connection pool with Jira has very little impact on Jira itself (if any). 

Advantages

  • default configuration
  • no configuration needed
  • works very well for a vast majority of deployments
  • user can easily configure Jira database connection pool to handle an extra load from the product

Disadvantages

  • database connection pool is shared with core Jira database connection pool, it may decrease performance in a highly concurrent environment with a heavy load
  • lack of flexibility in configuration Jira 

Custom database connection pool 

The product may work with its own database connection pool using Apache DBCP2 library. In this scenario a dedicated database pool is created, hence Jira database connection pools is completely unaffected. 

To configure your own connection pool for the product follow the steps below:

  1. Locate Jira Home directory. You should have a dbconfig.xml file in that location
  2. Create a new file called dbconfig-[productName].xml file. For BigPicture the file name is dbconfig-bigpicture.xml. 
  3. Add the following content to the file
<?xml version="1.0" encoding="UTF-8"?>
<softwareplant-database-config> 
  <driverClassName>org.postgresql.Driver</driverClassName>
  <url>jdbc:postgresql://localhost:5432/jiraXXX</url>
  <username>xxx</username>
  <password>xxx</password>
  <initialSize>5</initialSize>
  <minIdle>1</minIdle>
  <maxIdle>10</maxIdle> 
  <maxTotal>50</maxTotal>
</softwareplant-database-config> 

Here is a list of attributes required:

TagDescription
driverClassNameJDBC database driver class
urlURL as defined by JDBC driver

username

Database username
passwordDatabase user password
initialSizeConnection pool initial size
minIdleA number of a minimum idle connections hold in a connection pool
maxIdleA number of a maximum idle connections hold in a connection pool
maxTotalMaximum connection pool size

If you decide to configure a custom database connection pool with a different user, please remember to GRANT ALL privilieges to the user. If you fail to do so you may not be able to use the product properly after the upcoming upgrade.

Please find the appropriate DDL command for Postgres database:

GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA public TO <db user>;
GRANT ALL PRIVILEGES ON ALL SEQUENCES IN SCHEMA public TO <db user>;
GRANT ALL PRIVILEGES ON DATABASE <db name> TO <db user>;

Advantages

  • all database requests executed by the product can be easily tracked by a database engine (different connection properties, different user)

Disadvantages

  • complexity
  • No labels