DX Application Performance Management

Expand all | Collapse all

AXA- Different JS Browser Agents

Jump to Best Answer
  • 1.  AXA- Different JS Browser Agents

    Posted 07-24-2018 01:40 PM
    I'm installing an isolated DXC and I was wondering if any of you could answer whether if it is better to point directly to dxc JS
    http://<..>/mdo/v1/sdks/browser/BA.js" or to point to
    https://<..>/api/1/urn:ca:tenantId:DEFAULTORG/urn:ca:appId:web_teste/profile?agent=browser" data-tenantID="DEFAULTORG" data-appID="web_teste" data-appKey="a04f03a0-83cc-11e8-a4a7-eb289434d14f" ~

    Because from what i see they're different , and by looking at the doc on isolated DXC it points to the first one, although when I see doc on AXA it points to the second one.
    Can someone clear me this out? Is it the same?
    Best Regards









  • 2.  Re: AXA- Different JS Browser Agents

    Posted 07-24-2018 03:53 PM

    DXC can be used with AXA or without AXA (eg. for APM browser agent).

     

    If you are using AXA, I would recommend the second one.

     

    Francis



  • 3.  Re: AXA- Different JS Browser Agents
    Best Answer

    Posted 07-24-2018 07:02 PM

    Yes in general it is best to use the default snippet from the DXC file default.basnippet:

    How Do I Find the Default Browser Agent Snippet After Installing Digital Experience Collector? - CA Experience Collector… 



  • 4.  Re: AXA- Different JS Browser Agents

    Posted 07-25-2018 06:37 AM

    Thanks for your help guys, is it possible to make this variables defined in the snippet, dynamic ?So the development team doesn't need to upgrade each time an end-point is changed.



  • 5.  Re: AXA- Different JS Browser Agents

    Posted 07-25-2018 10:39 PM

    Hi Tiago,

    With regard to your original question I think your confusion was maybe due to you mixing up the setup of the DXC-AXA integration with the Browser Agent snippet used for the DXC-APM agent integration/connection.

    i.e. you found ""http://apm-axa-integration:9080/mdo/v1/sdks/browser/BA.js"" referenced here under "Integrate CA APM and CA App Experience Analytics" which is really referring to how to integrate DXC with AXA:

    Install the Digital Experience Collector on a Single System - CA Experience Collector - CA Technologies Documentation 

     

    For your question about using variables in the snippet I don't believe that is possible. However I found in my testing that you can update the snippet file without agent/AppServer restart if you first disable the autoinjection in the agent profile i.e.

    Change: introscope.agent.browseragent.autoInjectionEnabled=true

    To: introscope.agent.browseragent.autoInjectionEnabled=false

    Update the snippet file and then revert above to true i.e.

    introscope.agent.browseragent.autoInjectionEnabled=true

    The agent log (INFO mode) will show the changes

     

    Hope that helps

     

    Regards,

     

    Lynn



  • 6.  Re: AXA- Different JS Browser Agents

    Posted 07-26-2018 04:42 AM

    Thanks Lynn, what I meant was if develop team needs to wrap an apk and inject with that snippet, then if the endpoint changes they need to wrap it up again right?



  • 7.  Re: AXA- Different JS Browser Agents

    Posted 07-27-2018 06:26 AM

    Thanks Francis
    What I am trying to explain is that whenever we want to create a new app we have to wrap it or inject snippet (web app). The thing is that we are obligated to point to this url as AXA suggests?

    agent=browser src="http://axa.cqgrupocgd.com/mdo/v1/sdks/browser/BA.js" (as seen this url comes from database- only way to change it is changing endpoint in data base)

    or can we change this to go to this dynamic endpoint:

    agent=browser src="https://app.<appname>.cqcgd.pt/api/1/urn:ca:tenantId:DEFAULTORG/urn:ca:appId:web_teste/bajs?

     

     



     

     


  • 8.  Re: AXA- Different JS Browser Agents

    Posted 07-27-2018 01:15 PM

    I have not seen an example where dynamic endpoint has been used.  In the examples documented, a static path is used:

    Integrate with CA Application Performance Management - CA App Experience Analytics - 17.3 - CA Technologies Documentatio…