How To Change The Database Connection Information For Claim Digger/Schedule Analyzer For Project Management? [ID 899593.

1]

Applies to:
Primavera P6 Enterprise Project Portfolio Management - Version: 5.0 to 7.0 - Release: 5.0 to 7.0 Primavera Contractor - Version: 5.0 to 6.1 [Release: 5.0 to 6.1] All Platforms

Goal
This document is designed to explain how to change the database connection information for Claim Digger/Schedule Analyzer and Update Baselines for Project Management/Contractor. The document also explains how the Java connection from Claim Digger/Schedule Analyzer and Update Baseline to the database works. A user might need to change this information if Claim Digger does not launch or launches and prompts for a user name and password. A user might also change this information if any of the following error messages occur when trying to run Claim Digger or Update Baseline:
com.primavera.PhoenixException: Unable to resolve privileged password Failed Logon:com.jnetdirect.jsql.u: TCP/IP connection failed host:java.net.ConnectException: Connection refused: connect url:jdbc:JSQLConnect://server:###/database=pmdb com.primavera.PhoenixException: Unable to resolve privileged password Failed Logon:com.jnetdirect.jsql.u: TCP/IP connection failed host:java.net.ConnectException: Connection refused: connect url:jdbc:JSQLConnect://[SERVER NAME]:[PORT No.]/database=pmdb$primavera username and to username and to

Solution
Claim Digger is automatically installed with current versions of Primavera Project Management and Contractor. When selecting "Claim Digger" in the Tools menu, the launch/connection process goes through three steps: Step 1: Determines where to read a connection configuration setting from: Claim Digger reads the BREBootstrap.xml file in the Primavera Common\java directory to locate the database to read a configuration setting from, and the name of the configuration from which to read.

Step 2: Reads the configuration setting to find project data database information. Using the BREBootstrap.xml from step 1, connects and reads the configuration settings on the Admin_Config table to find out what database to connect to and read project data. Step 3: Connects to the database to read project data. Using the URL java connection info found in the configuration setting setting in Step 2, Claim Differ connects to the database in the URL string and reads project data. To accomplish this, when Claim Digger is first accessed from within the Project Management desktop client menu Tools > Claim Digger (or Tools > Schedule Analyzer), configurations are automatically created and set up to point Claim Digger to the Project Management database that the Project Management Desktop Client is currently logged into. NOTE: Claim digger is designed to always attempt to connect to the same database that the PM client is logged into. Even if DBCONFIG.cmd is run to point the BREBootstrap.xml to a different database, each time Claim Digger is launched, PM overwrites the BREBootstrap java URL database value to point Claim Digger to the currently logged in database. Claim digger then looks in that database for a configuration setting with the BRE Configuration name found in BREBootstrap.xml. If a configuration with that name already exists, Claim Digger uses it. If a configuration by that name is not found, one is created with that name and the Instance1 > Database > URL value is set to the current logged in database. The configuration setting itself holds the connection information for which database to READ PROJECT DATA from. This can be customized and saved such that Claim Digger can in effect point to a different database than the PM client.

BREBootstrap.xml: Claim Digger will use this file to gain access to a PM database in order to read a configuration setting (Internal_Plugins) to learn which database it should log into to read Project data. Configuration settings are stored in the database on the ADMIN_CONFIG table URL: The java JSQLConnect string that points to the project management database from which to read the configuration settings. Username: Username to authenticate to the PM database to gain access to read the configuration settings\ BRE name: The configuration setting to read from to determine which database to read project data from. dbconfig.cmd: Used to create or modify the contents of the BREBootstrap.xml This will change the database and configuration setting that the java app will read from when starting up. (SEE NOTE BELOW) User Name: Pubuser or Privuser

Password: password for Pubuser or Privuser Database Name: name of the Project Management SQL database or Oracle SID that holds the configuration setting you want to use. Database Host Address: Server name or IP address of the database server (no SQL named instance needed) Database Host Port: Port number that SQL SERVER is listing on. admin.cmd: The java Administration Application for Claim Digger. Used to modify configuration setting parameters. ( Works like myPrimavera/P6webaccess adminpv.cmd ) URL: The java JSQLConnect string that points to the project management database from which to read Project data. Username: Username to authenticate to the PM database to gain access to read the project data. NOTE: If you have multiple databases setup, and after running dbconfig.cmd is successful following the steps above but the data you are seeing in the Claim Digger window is from a different database, please follow the steps below to correct the issue.

1. Locate the admin.cmd file The default location is: C:\Program Files\Common Files\Primavera Common\Java\admin.cmd 2. Login to the Primavera Administration tool 3. Expand the Database section of your current configuration and make the necessary changes to the Instance 1 Database URL 4. Click "Save Changes" in the bottom-right corner 5. Log back into Project Management and test Claim Digger

WORKAROUND: If the above steps do not work try the following to have Project Management automatically regenerate a configuration for Claim Digger: 1. Login to C:\Program Files\Common Files\Primavera Common\Java\admin.cmd Depending on what version you have installed, you will be prompted to log in as privuser or pubuser. 2. Right click on any configurations created in the Fix steps above and delete, also delete Internal Plugins configuration. 3. Save changes on bottom right of window. 4. Delete the BREBootstrap.xml file that Claim Digger uses (C:\Program Files Common Files\Primavera Common\Java\BREBootstrap.xml) 5. Log into Project Management and launch Claim Digger / Schedule Analyzer from the Tools menu. This will rebuild the Internal_Plugins configuration and BREBoostrap.xml file with parameters configured to connect to the database that the PM client is currently logged into. If running Contractor: 1. Locate the DBConfig.cmd file The Contractor 5.0 location is: C:\Program Files\Common Files\Primavera Common\Java\dbconfig.cmd 2. Double-click on this file. This will launch Database Configuration for Claim Digger/Schedule Analyzer. Choose the "Microsoft SQL Server of MSDE" database type and click "next". 3. Enter Database connection information and click "next": Username: pubuser Password: pubuser Database Name: pcondb Database Host Address: localhost Database Host Port: (obtained by running "svrnetcn" from Start > Run, highlighting TCP/IP and clicking "Properties") Public Group Id: 1 4. Pop-up will alert you that a new configuration was created successfully. Claim Digger / Update Baseline should now run without error.