Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Admiral Admiral
Admiral
612 views

APM9.3 database connection string

Jump to solution

Hello community,

Is there a way to find the full database connection string from APM console?

I know I can find some infromation such as Host name, SID, Port, Schema and etc by going through Setup and Maintence->Manage Profile Database.

However, I would like to see the full database connection string. How can I achieve this? Is this something that I have to access DBA?

Please let me know.

Thanks,

Labels (1)
0 Likes
1 Solution

Accepted Solutions
Micro Focus Expert
Micro Focus Expert

Hi yangnigon,

thanks for the clarification.
I guess you can get to real full connection string only by enabling debug logging in APM to capture how it connects to the database, for example by (mis-)using
KM00908545 - BSM - how to enable Data Direct DB driver SPY / SNOOP or a DEBUG logging
https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/KM00908545
(I don't know how far you wanna go ...)
you might also be lucky and find it in the "normal" logs, I actually never had to look for this in the logs ...

Greetings
Siggi

Customer Support
Micro Focus

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.

View solution in original post

0 Likes
5 Replies
Micro Focus Expert
Micro Focus Expert

Hi yangnigon,

I know that the connection string for the APM management database is stored in the file <APM>\conf\TopaInfra.ini
..
[ManagementDb]
dbType="2"
dbEType="1"
dbPwd="1Z1Z74D79603DC5FB3843CD64FC473D62E9BZ62EB499040A04630464E5720C30775F904D8AC6F4F270797063E2000C76AA848"
dbSID=""
dbHost="sov02bac13.dont,share"
dbPath="C:\HPBSM/AppServer/webapps/site.war/DataBases"
dbName="BAC13_MGMT"
ConnectString="PROVIDER=MSDASQL;DRIVER={SQL Server};SERVER=sov02bac13.dont.share;DATABASE=BAC13_MGMT;UID=sa;PWD=1Z1Z74D79603DC5FB3843CD64FC473D62E9BZ62EB499040A04630464E5720C30775F904D8AC6F4F270797063E2000C76AA848;"
dbPort="1433"
dbUser="sa"
dbServer="sov02bac13.dont.share"
..
but this is nothing you could retrieve from the APM console (and whay would one need this information anyway?).
I also think that you cannot retrieve it via JMX.

Perhaps the type of request is better to understand (or to ersolve) if you explain what you are looking for.

Greetings
Siggi

Customer Support
Micro Focus

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
0 Likes
Admiral Admiral
Admiral

Siggi,

Thanks for response.

The reason I was asking is because we are currently testing the database connection string in a new database location (physical). Before I reach out to DBA, I wanted to see how I can find the current connection string (full) attached to APM so that I can pass that information to migration testing team without contacting DBA.

Thanks,

 

0 Likes
Micro Focus Expert
Micro Focus Expert

Hi yangnigon,

thanks for the clarification.
I guess you can get to real full connection string only by enabling debug logging in APM to capture how it connects to the database, for example by (mis-)using
KM00908545 - BSM - how to enable Data Direct DB driver SPY / SNOOP or a DEBUG logging
https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/KM00908545
(I don't know how far you wanna go ...)
you might also be lucky and find it in the "normal" logs, I actually never had to look for this in the logs ...

Greetings
Siggi

Customer Support
Micro Focus

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.

View solution in original post

0 Likes
Admiral Admiral
Admiral

Siggi,

The link that you posted does not work for me. It says I do not have enough permission to access.

I've also looked for KM00908545 but nothing came up. Is this link only accessible by support?

Thanks,

 

0 Likes
Micro Focus Expert
Micro Focus Expert

Hi yangnigon,

the document is internal only, so you got an Access Violation.

Here is the content:

How to enable spy logging in BSM
--------------------------------
1. Go to <hpbsm>\conf\jdbc.drivers.properties
   a. backup the file
 
   b. Open the file for editing, under ddoracle replace this line:
       ddoracle.url=jdbc:mercury:oracle://${host}:${port};sid=${sid} 
        with
       ddoracle.url=jdbc:mercury:oracle://${host}:${port};sid=${sid};SPYATTRIBUTES=(log=(file)c:\\TEMP\\spy.log;logTName=yes;timestamp=yes)
 
      In case of Oracle RAC replace this line:
       ddoracle.url=jdbc:mercury:oracle:TNSNamesFile=<BSM_HOME>\\conf\\bsm-tnsnames.ora;TNSServerName=${sid}
        with
       ddoracle.url=jdbc:mercury:oracle:TNSNamesFile=<BSM_HOME>\\conf\\bsm-tnsnames.ora;TNSServerName=${sid};SPYATTRIBUTES=(log=file)c:\\TEMP\\spy.log;logTName=yes;timestamp=yes)
 
   c. Make sure the folder c:\temp exists
 
   d. If your server is running UNIX/LINUX OS, replace all the double back slashes in the file path with single slashes.
 
2. Restart MERCURY_AS service or the service you want to monitor (e.g. pmanager)
 
3. Wait til the problem recreates
 
4. Open jdbc.drivers.properties and change back to the original line.
 
5. Restart MERCURY_AS service or the service you want to monitor (e.g pmanager)
 
6. Open c:\temp\spy.log and you can see what the driver was doing at the time of the failure.
 

Enable snoop logging (network sniffing)
---------------------------------------
Add this to the connection string at the <HPBSM>\conf\jdbc.driver.properties file
(similar to How to enable spy logging in BSM)
;ddtdbg.ProtocolTraceEnable=true;ddtdbg.ProtocolTraceMaxline=16;ddtdbg.ProtocolTraceShowTime=true;ddtdbg.ProtocolTraceLocation=c:\\temp\\Snoop.txt;SPYATTRIBUTES=(log=file)c:\\TEMP
spy.txt;logTName=yes;timestamp=yes)

Greetings
Siggi

Customer Support
Micro Focus

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.