<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Java Agent Configuration in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/Java-Agent-Configuration/m-p/732918#M8210</link>
    <description>Andreas,&lt;BR /&gt;&lt;BR /&gt;I am curious;   What is your use-case for requiring JVMs to frequently move between tiers?&lt;BR /&gt;&lt;BR /&gt;Generally, tier naming is driven by the logical purpose of the JVM (often, what service it implements for a microservice architecture) and isn’t too volatile for any given JVM&lt;BR /&gt;&lt;BR /&gt;It would be helpful to understand how your deployment differs from this model.&lt;BR /&gt;&lt;BR /&gt;Warm regards,&lt;BR /&gt;Peter&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 28 Mar 2018 11:13:08 GMT</pubDate>
    <dc:creator>Peter_Holditch</dc:creator>
    <dc:date>2018-03-28T11:13:08Z</dc:date>
    <item>
      <title>Java Agent Configuration</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Java-Agent-Configuration/m-p/732916#M8208</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;I have the following questions on Java Agent configuration.&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;I have many number of JVM nodes, configuring one by one maually (providing the Application,Tier and Node names) is painful process. Is there any easy options available?&lt;/LI&gt;
&lt;LI&gt;Is there way to switch a given JVM node from one tier to another without JVM restart.&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Andreas&lt;/P&gt;</description>
      <pubDate>Mon, 26 Mar 2018 14:52:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Java-Agent-Configuration/m-p/732916#M8208</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2018-03-26T14:52:09Z</dc:date>
    </item>
    <item>
      <title>Re: Java Agent Configuration</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Java-Agent-Configuration/m-p/732917#M8209</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;Andreas,&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN&gt;Unfortuantely this the only process you need to follow to configure agent.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Jvm restart is&amp;nbsp; required in second scenario.&lt;/P&gt;


&lt;P&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Atyuha&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Mar 2018 09:49:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Java-Agent-Configuration/m-p/732917#M8209</guid>
      <dc:creator>Atyuha_Pal</dc:creator>
      <dc:date>2018-03-28T09:49:22Z</dc:date>
    </item>
    <item>
      <title>Re: Java Agent Configuration</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Java-Agent-Configuration/m-p/732918#M8210</link>
      <description>Andreas,&lt;BR /&gt;&lt;BR /&gt;I am curious;   What is your use-case for requiring JVMs to frequently move between tiers?&lt;BR /&gt;&lt;BR /&gt;Generally, tier naming is driven by the logical purpose of the JVM (often, what service it implements for a microservice architecture) and isn’t too volatile for any given JVM&lt;BR /&gt;&lt;BR /&gt;It would be helpful to understand how your deployment differs from this model.&lt;BR /&gt;&lt;BR /&gt;Warm regards,&lt;BR /&gt;Peter&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Mar 2018 11:13:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Java-Agent-Configuration/m-p/732918#M8210</guid>
      <dc:creator>Peter_Holditch</dc:creator>
      <dc:date>2018-03-28T11:13:08Z</dc:date>
    </item>
  </channel>
</rss>

