<?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: WCCProxy in Insight Remote Support</title>
    <link>https://community.hpe.com/t5/insight-remote-support/wccproxy/m-p/3840835#M866</link>
    <description>WCCProxy is part of the ISEE client software. Thus installing ISEE will also install WCCProxy.&lt;BR /&gt;&lt;BR /&gt;WCCproxy is needed to transport ISEE events when they occur. It's a transport service between the different components involved in ISEE. Without it events would not get passed to the next component in line.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 10 Aug 2006 02:46:41 GMT</pubDate>
    <dc:creator>A. van Berk</dc:creator>
    <dc:date>2006-08-10T02:46:41Z</dc:date>
    <item>
      <title>WCCProxy</title>
      <link>https://community.hpe.com/t5/insight-remote-support/wccproxy/m-p/3840834#M865</link>
      <description>What it the use or WCCProxy?&lt;BR /&gt;Below are the components which are required for the lifecycle of an event reaching the HP backend.&lt;BR /&gt;1)An event monitoring service detects the hardware event. &lt;BR /&gt;2)Event Handler — filters events received from the native diagnostic instrumentation that are considered of events of interest to ISEE and forwards those events to the ISEE Client software. &lt;BR /&gt;3)ISEE Client Software — Provides a web-based management GUI for configuring ISEE client specific features, viewing incident details, obtaining client system information, running MAPs (Motive Application Programs) on the ISEE client, Health checks, and ISEE communication support.&lt;BR /&gt;&lt;BR /&gt;My question is "when we have all the 3 compnonents required to process and submit and incident, why do we need WCCProxy and what is the fuction of WCCProxy?"&lt;BR /&gt;&lt;BR /&gt;Can somebody explain the fucntion of WCCProxy and where exactly is it used?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 10 Aug 2006 00:27:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/wccproxy/m-p/3840834#M865</guid>
      <dc:creator>naveem</dc:creator>
      <dc:date>2006-08-10T00:27:11Z</dc:date>
    </item>
    <item>
      <title>Re: WCCProxy</title>
      <link>https://community.hpe.com/t5/insight-remote-support/wccproxy/m-p/3840835#M866</link>
      <description>WCCProxy is part of the ISEE client software. Thus installing ISEE will also install WCCProxy.&lt;BR /&gt;&lt;BR /&gt;WCCproxy is needed to transport ISEE events when they occur. It's a transport service between the different components involved in ISEE. Without it events would not get passed to the next component in line.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 10 Aug 2006 02:46:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/wccproxy/m-p/3840835#M866</guid>
      <dc:creator>A. van Berk</dc:creator>
      <dc:date>2006-08-10T02:46:41Z</dc:date>
    </item>
    <item>
      <title>Re: WCCProxy</title>
      <link>https://community.hpe.com/t5/insight-remote-support/wccproxy/m-p/3840836#M867</link>
      <description>Hi&lt;BR /&gt;Thanx for answering my query.&lt;BR /&gt;but query is different.&lt;BR /&gt;The WCCProxy is not used on some client systems and in some models.&lt;BR /&gt;I have attached a screenshot with blank lines pointed the systems containing WCCProxy as one of the components and with Red lines pointing the systems doesnot contain the WCCProxy.&lt;BR /&gt;&lt;BR /&gt;My question is "What is the function of WCCProxy" and " Why WCCProxy is not used on some systems to report/process events" &lt;BR /&gt;</description>
      <pubDate>Thu, 10 Aug 2006 04:56:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/wccproxy/m-p/3840836#M867</guid>
      <dc:creator>naveem</dc:creator>
      <dc:date>2006-08-10T04:56:08Z</dc:date>
    </item>
    <item>
      <title>Re: WCCProxy</title>
      <link>https://community.hpe.com/t5/insight-remote-support/wccproxy/m-p/3840837#M868</link>
      <description>Different mechanisms exist to get an event&lt;BR /&gt;transported to the HP backend. In some configurations WCCproxy is needed in others not.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 10 Aug 2006 08:03:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/wccproxy/m-p/3840837#M868</guid>
      <dc:creator>A. van Berk</dc:creator>
      <dc:date>2006-08-10T08:03:17Z</dc:date>
    </item>
  </channel>
</rss>

