Hi Adr,
I didn't even think about this API, as it seems it was documented up to BPM 9.24, and then not anymore (at least I checked on BPM 9.26 IP1 and BPM 9.30).
With BPM 9.24 the documentaion (<BPM>\ServletContainer\webapps\ROOT\help\BPMWeb\Content\API\overview.htm) shows
..
Web Services API
The BPM Web Services API enables you to run the following operations on your BPM machine:
..
add - Adds a new instance on the BPM machine according to the passed parameters.
..
setSpecificUser - Defines the user for running the BPM process.
..
Note: The WSDL contains additional functions to those listed above, which are not supported in BPM version 9.23 or later.
..
I just tested on BPM 9.30, and the URL still works http://localhost:2696/jsp/agent/api/BPMApi.wsdl, so at least parts of still work,
but after going over the list of operations I cannot find the stuff you would need, like retrieving metric data from BPM and alike,
plus, only the listed subset would be supported.
And I think that this API wouldn't resolve your issue:
there is the EUM Admin API, which would allow you to perfom various EUM configuration tasks without the BSM GUI, but on the BSM side.
And there is this BPM API, which allows some actions on the BPM side,
but the main issue - data-wise, would remain:
- BPM creates .sba files and sends byte array data to BSM.
BPM is not sending any files in file stream. It always converts them to byte arrays before sending to BSM.
- BPM will send *.json, *.metadata, *.endstatus as part of transaction samples data,
*.html, jpeg, *.inf and etc will send as part of error data. But, all files will be converted into encrypted byte arrays before sending to BSM.
- BPM will use only 80 port in case of HTTP communication. If the communication is on HTTPS protocol, then BPM will use 443 port.
BSM <-> BPM communication is using SOAP web service,
for example
BSM sends request <http or https>://<bpm fqdn or ip>:<port>/jsp/agent/api/BPMApi.wsdl
BPM uses
http://GW/ext/mod_mdrv_wrap.dll...
to access WDE on GW server (to upload metric data and more)
So will all API in place, the middleman would still be missing.
Perhaps you can somehow fool BSM, setup all as usual, then regularly collect the data from the BPM system,
copy it to BSM and then mimic the calls to
http://GW/ext/mod_mdrv_wrap.dll...
but ...
BTW, I found a case with R&D with this setup:
..
customer will use a third party software (DataPower) which will be in the middle of the communication between BPM and BSM
so he needs the full information about all files and connections that BPM uses/sends during its communication to BSM.
..
The information from above (files, ports) was sufficient to implement this, so maybe it helps you as well?
Greetings
Siggi
