DX Application Performance Management

 View Only
  • 1.  Java Agent - setting agentManager.url.1 on JVM

    Posted Sep 29, 2017 03:27 PM

    We are installing 10.5.2 and we had version 10.0.  In 10.0 we had to have an agent configuration for each of our environments, which made things a bit harder to manage.

     

    One of the big differences is that the agentManager.url.1 was one of there MOMs.  

     

    Is there a way to set the agentManager.url.1 on the JVM arguments:

     

             -d agentManager.url.1=<momhostname>:5001

     

    And comment out the agentManager.url.1=localhost:5001 in the profile?

     

    That way we could have a single agent configuration for all of our application servers and not a custom one per Production/qa/stress/test/dev.

     

    Thank you,

     

    Billy



  • 2.  Re: Java Agent - setting agentManager.url.1 on JVM
    Best Answer

    Broadcom Employee
    Posted Oct 02, 2017 06:20 AM

    Hi Billy,

    Yes, you can use -DagentManager.url.1 as a jvm argument and comment agentManager.url.1 in the agent profile

     

    Additional reminders:

    a) you can simplify it more: -DagentManager=URL is equivalent to -DagentManager.url.1=URL

     

    b) you add add multiple EM connections
    -DagentManager.url.1=scheme://address:port
    -DagentManager.url.1=serverHostOrIP1:Port
    -DagentManager.url.2=serverHostOrIP2:Port
    ..

    c) Supported protocols:
    - agentManager.url.1=serverHostOrIP:Port to specify a direct Isengard TCP connection
    - agentManager.url.1=tcp://serverHostOrIP:Port to specify a direct Isengard TCP connection
    - agentManager.url.1=ssl://serverHostOrIP:Port to specify an Isengard SSL/TLS connection
    - agentManager.url.1=http://serverHostOrIP:Port to specify an Isengard HTTP connection
    - agentManager.url.1=https://serverHostOrIP:Port to specify an HTTPS connection

    If no protocol scheme supplied, assumes direct TCP Isengard connection

    You can use any of the above options as a jvm argument.

     

    For more information, see Configure Java Agent - CA Application Performance Management - 10.5 - CA Technologies Documentation 

     

    I hope this helps,

    Regards,

    Sergio