<?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 Why does AppDynamics NodeJS client install Java Runtime Environment within its npm packages? in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/Why-does-AppDynamics-NodeJS-client-install-Java-Runtime/m-p/722373#M3133</link>
    <description>&lt;P&gt;Why does AppDynamics NodeJS client install Java Runtime Environment within its npm packages? We find this to be an undesired dependency in containerised NodeJs applications. Is there a native nodejs client or plans to develop one?&lt;/P&gt;</description>
    <pubDate>Wed, 02 Aug 2017 09:49:50 GMT</pubDate>
    <dc:creator>CommunityUser</dc:creator>
    <dc:date>2017-08-02T09:49:50Z</dc:date>
    <item>
      <title>Why does AppDynamics NodeJS client install Java Runtime Environment within its npm packages?</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Why-does-AppDynamics-NodeJS-client-install-Java-Runtime/m-p/722373#M3133</link>
      <description>&lt;P&gt;Why does AppDynamics NodeJS client install Java Runtime Environment within its npm packages? We find this to be an undesired dependency in containerised NodeJs applications. Is there a native nodejs client or plans to develop one?&lt;/P&gt;</description>
      <pubDate>Wed, 02 Aug 2017 09:49:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Why-does-AppDynamics-NodeJS-client-install-Java-Runtime/m-p/722373#M3133</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2017-08-02T09:49:50Z</dc:date>
    </item>
    <item>
      <title>Re: Why does AppDynamics NodeJS client install Java Runtime Environment within its npm packages?</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Why-does-AppDynamics-NodeJS-client-install-Java-Runtime/m-p/722374#M3134</link>
      <description>&lt;P&gt;Hi lukasz,&lt;/P&gt;

&lt;P&gt;This is explained in following document&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.appdynamics.com/display/PRO43/Dynamic+Language+Agent+Proxy" target="_blank" rel="nofollow noopener noreferrer"&gt;https://docs.appdynamics.com/display/PRO43/Dynamic+Language+Agent+Proxy&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.appdynamics.com/display/PRO43/Node.js+Agent#Node.jsAgent-Node.jsAgentandtheJavaProxy" target="_blank" rel="nofollow noopener noreferrer"&gt;https://docs.appdynamics.com/display/PRO43/Node.js+Agent#Node.jsAgent-Node.jsAgentandtheJavaProxy&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;With 4.3, Node.Js Agent supports proxiless option with few limitations&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.appdynamics.com/display/PRO43/Dynamic+Language+Agent+Proxy#DynamicLanguageAgentProxy-Node.jsproxylessoption" target="_blank" rel="nofollow noopener noreferrer"&gt;https://docs.appdynamics.com/display/PRO43/Dynamic+Language+Agent+Proxy#DynamicLanguageAgentProxy-Node.jsproxylessoption&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Let us know if you have additional questions.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Raunak&lt;/P&gt;</description>
      <pubDate>Wed, 02 Aug 2017 10:14:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Why-does-AppDynamics-NodeJS-client-install-Java-Runtime/m-p/722374#M3134</guid>
      <dc:creator>Raunak_Mohanty</dc:creator>
      <dc:date>2017-08-02T10:14:00Z</dc:date>
    </item>
    <item>
      <title>Re: Why does AppDynamics NodeJS client install Java Runtime Environment within its npm packages?</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Why-does-AppDynamics-NodeJS-client-install-Java-Runtime/m-p/722375#M3135</link>
      <description>&lt;P&gt;I understand I can make the nodejs agent not use the Java proxy (&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial',sans-serif;"&gt;&lt;A href="https://docs.appdynamics.com/display/PRO43/Dynamic+Language+Agent+Proxy#DynamicLanguageAgentProxy-Node.jsproxylessoption" target="_blank" rel="nofollow noopener noreferrer"&gt;https://docs.appdynamics.com/display/PRO43/Dynamic+Language+Agent+Proxy#DynamicLanguageAgentProxy-Node.jsproxylessoption&lt;/A&gt;&lt;/SPAN&gt;), but it will be installed anyway along the npm package? This still adds 160MB to container image. Would it be safe to delete the appdynamics-jre and appdynamics-proxy packages if the proxiless option is in use? Or is there an alternative npm package which does not include JRE and proxy dependencies?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Aug 2017 08:46:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Why-does-AppDynamics-NodeJS-client-install-Java-Runtime/m-p/722375#M3135</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2017-08-04T08:46:12Z</dc:date>
    </item>
    <item>
      <title>Re: Why does AppDynamics NodeJS client install Java Runtime Environment within its npm packages?</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Why-does-AppDynamics-NodeJS-client-install-Java-Runtime/m-p/722376#M3136</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi lukasz,&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN&gt;Yes, you can delete these two directories after the agent installation if you do not intend to use the JAVA proxy for controller communication. But, be informed that there are a few functionalities which are still not supported by native agent.&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN&gt;Best Regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Piyush&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Aug 2017 10:27:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Why-does-AppDynamics-NodeJS-client-install-Java-Runtime/m-p/722376#M3136</guid>
      <dc:creator>Piyush_Mundra</dc:creator>
      <dc:date>2017-08-04T10:27:10Z</dc:date>
    </item>
  </channel>
</rss>

