Subin R Contributor.
Contributor.
134 views

BPM 9.30:- BPM Data is not getting transferred to APM applications

Hi Team,

We are getting the below error in "bpm_sample_sender.log" and we can see that some of the transactions are not being reported to the APM application. please let us know if anyone has faced this issue and how did that fixed.
17/05/2019 13:30:18 WARN [SamplesHandlerThread (Site1)] [SitesSamplesHandlerMngr] sampleData is invalid, can't create samples from JSON: D:\ProgramData\HP\BPM\workspace\agent1\Site1\data\soa\1558092611014_371\1558092611014_1_320_Finance_____\Finance.json. The JSON file/folder will be moved to archive quarantine
17/05/2019 13:30:18 WARN [SamplesHandlerThread (Site1)] [SitesSamplesHandlerMngr] sampleData is invalid, can't create samples from JSON: D:\ProgramData\HP\BPM\workspace\agent1\Site1\data\soa\1558092611014_371\1558092612123_1_321_Pages_______\Pages.json. The JSON file/folder will be moved to archive quarantine
17/05/2019 13:30:18 WARN [SamplesHandlerThread (Site1)] [SitesSamplesHandlerMngr] sampleData is invalid, can't create samples from JSON: D:\ProgramData\HP\BPM\workspace\agent1\Site1\data\soa\1558092611014_371\1558092614280_1_322_Procurement_\Procurement.json. The JSON file/folder will be moved to archive quarantine
17

We are using BPM 9.30 & APM 9.30

0 Likes
3 Replies
Micro Focus Expert
Micro Focus Expert

Re: BPM 9.30:- BPM Data is not getting transferred to APM applications

Hi Subin R,

usually this is a warning which appears for SOA scripts, when they contain User defined transactions.
Then the JSON files are handled as trans_t samples (like other usual scripts), the simply informs the user that the sample is not handled as SOA sample, but as trans_t sample.

You need to check if you can see all data in APM you expect, in that case you can ignore the messages.

As you miss data, you might wanna implement the change from KM03084790:

- on the BPM machines affected modify the file <BPM_data>\config\topaz_data_server.cfg

- Under the
     [general]
   section (at the bottom of the file) add the following:
     EnableSamplePerTxMechanism=false

- Save the file and restart BPM (start it as a service)

- after the problematic script(s) executed, check if the data is send to APM.

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
Subin R Contributor.
Contributor.

Re: BPM 9.30:- BPM Data is not getting transferred to APM applications

hi Siggi,

 

thanks for your suggestion, I have tried this in our UAT environment but still seeing the same issue. and the some of the transactions are missing in reports.

 

and the same error is being repeated


22/05/2019 11:30:33 WARN [SamplesHandlerThread (Site1)] [SitesSamplesHandlerMngr] sampleData is invalid, can't create samples from JSON: D:\ProgramData\HP\BPM\workspace\agent1\Site1\data\trans_t\1558517400033_7\1558517400283_1_105_NodeTracker_\NodeTracker.json. The JSON file/folder will be moved to archive quarantine
22/05/2019 11:45:30 WARN [SamplesHandlerThread (Site1)] [SitesSamplesHandlerMngr] sampleData is invalid, can't create samples from JSON: D:\ProgramData\HP\BPM\workspace\agent1\Site1\data\trans_t\1558517400033_7\1558518300013_1_105_NodeTracker_\NodeTracker.json. The JSON file/folder will be moved to archive quarantine

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: BPM 9.30:- BPM Data is not getting transferred to APM applications

Hi Subin R,

as you can see, there is a change in the warning message:

old:

sampleData is invalid, can't create samples from JSON:
D:\ProgramData\HP\BPM\workspace\agent1\Site1\data\soa\1558092611014_371\1558092612123_1_321_Pages_______\Pages.json.
The JSON file/folder will be moved to archive quarantine

new:

sampleData is invalid, can't create samples from JSON:
D:\ProgramData\HP\BPM\workspace\agent1\Site1\data\trans_t\1558517400033_7\1558518300013_1_105_NodeTracker_\NodeTracker.json.
The JSON file/folder will be moved to archive quarantine

..\data\soa\.. vs ..\data\trans_t\..

as the data sample trans_t carries the BPM metric data, you won't see the data in BSM/APM.

I reviewed similar cases and for 17 our of 19 I found the solution was the one I gave you already.
Then there was a very specific protocol issue, where the message in the log looks a little bit different.
The last one I found had to do with special characters being used in the transaction names.
Check in the workspace folder
 D:\ProgramData\HP\BPM\workspace\agent1\Site1\data\trans_t\1558517400033_7\1558518300013_1_105_NodeTracker_\
check the file <script>.usr (most likely NodeTracker.usr) and there the list under
 
[Transactions]

do the transaction steps contain any special characters?

I worked on a case where the transaction names contained german characters, for example
 05_Suche_Geschäftspartner=
 06_Geschäftsvereinbarung_anzeigen=
 07_Übersicht_öffnen=
 all transactions with a special character in the name were missing.

This is an issue with the newer versions of BPM as described in the Release Notes under Notes and Limitations, with the subject
Non-English Language Limitations
with
Virtual User Generator (VuGen) has the following known limitations when working with non-English character
sets such as Cyrillic or Japanese

Check if this applies to you.
If not (no special characters in the names) I can only advice that you open a case with support.

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.