[cosmos-dev] Data Collection: Collecting....

[Mark D Weitzel <weitzelm@xxxxxxxxxx>]

Joel,

A few thoughts...
I've got tomcat up and running with
JMX enabled, verified by MAX.  I'd like to have the DC framework start
pumping in the data into the db.  I didn't see this on the e2e page
for dc (http://wiki.eclipse.org/index.php/COSMOSDataCollectionEnd2End)
 I'd be happy to help get fill in the details if you can put some
basic info up there.

Also, it should be noted if you are
using the WSDM WS-N function of MAX, that this also tries to listen on
port 9999.  There is a setting in preferences (Web Services Distributed
Management) that you can use to change the listening port.  Mine is
on 9998 and I'm not having any problems/conflicts.


Onto some thoughts on the data center....
One of the things we need to set when
we are configuring tomcat is the following....
set JAVA_OPTS=-Dcom.sun.management.jmxremote.port=9999
 -Dcom.sun.management.jmxremote.ssl=false  -Dcom.sun.management.jmxremote.authenticate=false

It would seem that some of these are
the kinds of configuration properties you'd expect to see in an XML document.
 These are similar to what we have already configured for the Agent
Controller.  While there is no link b/t the actual tomcat configuration
file and our XML file, this would be the kind of information that might
flow across the wire during metadata exchange.  I'd like to add these
three pieces of information to the data center example. 

Now that we are able to drive the ui
based on the work we've done in the data center example, a few new questions
have come to mind....
In the example, machine1Linux.xml has
the following entry:

<so:dataController
name="Agent
Controller">
         
               
      <tptp:ACProperties>
         
               
              <tptp:variable
name="RASERVER_HOME"
value="/home/user/AC4.3"
/>

         
               
              <pm:ports
name="ports"
input="false">
         
               
               
      <pm:port
number="10002"
/>
         
               
              </pm:ports>
         
               
      </tptp:ACProperties>
         
               
      <it:itemRef
sml:ref="true">
         
               
              <sml:uri>dataCollection/TPTP_AgentController/tptpDataControllerLinux.xml</sml:uri>
         
               
      </it:itemRef>
               
               
         
              </so:dataController>
         
      </so:softwareStack>

It seems that these items, e.g. port
number, should be in the tptpDataControllerLinux.xml, which would make
them properties in GLAController.xsd.
Also, it would be ideal if we could
have the keyset value point to the xml schema of the data.  In the
case of statistical data, this should be the xml schema that we define.
 In the case of CBE, it should be the CBE schema (http://www.ibm.com/AC/commonbaseevent1_1).

         
               
      <ctrl:componentProperties>
         
               
              <ctrl:keyset
name="Statistical
data" value="http://www.cosmos.rm/keysets/statistical"/>
         
               
      </ctrl:componentProperties>
       

WindowsServer1.xml has a similar entry:
         
               
      <ctrl:componentProperties>
         
               
              <ctrl:keyset
name="Windows
Application Log File" value="http://www.cosmos.rm/keysets/cbe"/>
         
               
      </ctrl:componentProperties>
       
         
              </ctrl:component>


Thoughts...
-mw



Mark Weitzel | STSM | IBM Software Group | Tivoli | Autonomic Computing
| (919) 543 0625 | weitzelm@xxxxxxxxxx