Hi Adr,
your very issue has been discussed in an internal forum, with the additional information
..
they will not allow port connectivity through the FW from the BPM back to the BSM.
Even port 443 HTTPS is being prevented.
They state the only method that would be allowed for BSM<->BPM connectivity would have to be via our SOA Access Gateway.
They have asked if the BPM instance can be configured to talk to the BSM via a WSDL on the gateway and it’s this that I don’t think is possible.
..
One guy from R&D responded
..
No, it is not possible.
BPM <-> BSM communication is based HTTP/S communication. And it is not customizable.
..
so I think there is not a lot what can be done.
I checked the R&D case again, but there is not more information (useful for your case) it it, as in the end it's a different issue, as there the HTTP communication still could be used.
I thought about some real creative ways to get this done, like setting up a BPM within the BSM network which mimics the real ones (same application / script setup, but not running the transactions), and then moving the metric data from the real BPMs to this one after updating all the data to make it like it comes from the "mimic" one, and then this mimic BPM feeds the data into BSM, but this would be an awful lot of work, and I cannot say for sure that this would work at all,
not even thinking about the support impact.
Greetings
Siggi