Hi Szymon,
Let me tell you how it works - then you can draw your conclusions for your exact question:
a) DI adapter which is used by both:
"DIProxy" + "B1if / integration / B1iSN server"
b) To avoid "misunderstandings" between both the DI adapter version is being checked.
I am not aware that this check would have been dropped (re "...3.0.15").
c) If you install DIProxy only 1x - on the B1 machine, but have B1i* installed on more than one other
machine - then you need to make sure that the B1i* versions use the same version of the DI
adapter.
This can be tricky since release cycles are different between the products (though DIProxy is
usually not changed so much it can happen that versions in different products don't match - as you
found...).
d) You have no issues in those 2 cases:
1) Content / scenario packages can be kept apart so that only one of the B1i* uses a particular
B1 (pretty obvious, or?)
2) Install a second DIProxy on another machine - e.g. the B1if machine - or the B1iSN machine -
or a 3rd machine (e.g. a small VM).
As you might know the recommendation for B1iSN was/is to install DIProxy on the B1 machine
while using another machine for B1iSN.
In the end however it depends purely on the load on the particular system whether the
recommendation has to be applied - or whether it is "just" the reconded option...
HTH,
Frank