Let me correct some confusions:
1) java script (more accurately BMC stub code) resides directly on the applications that is being monitored
it is either manually added use these instrucirirons:
or can autoamtcally added using one of the follwoign injeciotn methods:
When the applicaiotn is running on customer broswer - the code monitors it and create a monitoring record - this record AKA "Beacon" is sent to the TSAVM proxy server Elarticsearch componeent for further processing.
What is failing and cuasign a timeout if the seocnd part - data was collected on the applcaiotn - but hte beacons cant be snet and has itms out since te proxy isnt accesible from cusotmer browser.
inabilitly to send the collected data 9beacons) to hte proxy server - resutls in no collection and n procwssing of the data colected - whime effectevl means no monitoring
As per best praciveces cleiant browenr can be anywher and the Proxy server will ne inside a DMZ - so its better protected by LB/Poxt etc. (we dont want ot have an open port access to DMZ). this is a standard LB/Proxy condgiraiotn that needs to be dorn bt network eperts which are part of comany's IT team.
Please let me know if you have further quesiotns.
Hello Shelly, Thanks for the response. Yes, the original issue is that we are not able to communicate ( or send beacons ) from customer bowser ( which is outside client network to proxy server via LB ( which is also outside client network ) but to investigate the root cause, when I tried to execute the URL ( https://xxxxxxxxx:8305/static-resources/aeuem.min.js ) from portal and proxy server the behavior is not OK.
As per my understanding, the URL ( https://XXXXXX:8305/stiac-resources/aeuem.min.js ) should accessible from portal server but when I hit the URL in portal`s browser then I am getting timeout. Is that mean, something need to be fix from proxy network side and if yes, then what should we check?
Note : The same URL is working in proxy and giving aeuem.min.js jar file in response.
Actually its the opposite - you nee to change URL and LB configuration, nothing to change on the TSAVM proxy side
has to accessible from any point sending beacons
if its not accessible the data cant be processes and the script doesn't fulfill its destination
it will obviously work on the proxy host itself but that isn't where the request will coming from
basically we have three participants in this scenario
client browser --> load balancer --> TSAVM Proxy server
The host and port you are currently specifing in the URL are of the proxy server - as you can see in the illustration above the server is behind an LB and thus not accessible from the outside - so that will obviously not work
in order to make it work you need to specify https://<LB host FDQN>:8305/static-resources/aeuem.min.js
LB host instead of Proxy host
and make sure port 8305 is open in the LB for outside communication
the on the LB redirect the request to TSAVM proxy server - this last part has to be done by customer network team (BMC isn't giving network advice for the variety of LB's out there - just the requirement)
once the request is correctly redirected it will get to TSAVM proxy server and this it is