- Make sure that those requests actually reach a server that runs with a dynaTrace agent with an active UEM sensor.
- The firewall has to let those requests through.
- The load balancer has to forward those requests to a server that runs with a dynaTrace agent.
- If the web server does not run with a dynaTrace agent, it has to forward those request to an application server that runs with a dynaTrace agent.
If those requests reach an application server with a dynaTrace agent, but still generates a 404 response, the application server has to be configured in such a way, that the request is served by some existing servlet (it does not matter which Servlet is used).
For example, the following rule can be added to the global web.xml of the application server or to the web.xml of some specific application.
<servlet-name>Choose some existing servlet here</servlet-name>
If the rule is added to the global web.xml of the application server, dtagent_401.js can then be requested by using the URI /dynatrace/dtagent_401.js
If the rule is added to the web.xml of a specific application, dtagent_401.js can then be requested by using the URI /<app>/dynatrace/dtagent_401.js.
The prefix of the URI (e.g. "/dynatrace/" or "/<app>/dynatrace/") can be specified in the "User Experience" section of the system profile ("Agent location" and "Monitor request path").