Example of JMX Stats Copier

Using the JMX Stats Copier process, you can copy a JMX State into ActiveSpaces distributed cache.

You can specify the schedule name as JMX Stats Copier in the JMXCopierJobPolicy.xml file.

A Job node can contain more than one job nodes. Each Job node must specify the Job class, the trigger expressions, and a JobPolicy type. The Job class for JMX Stats Copier is com.tibco.mdm.admin.jmx.cacheCopier.JMXToCacheCopier.

The following is the sample of the JMX Stats Copier process: 

<CronSchedules>
<Schedule>
<Name>JMXstatscopier</Name>
<Jobs>
  <Job>
   <Name>CachestateDump</Name>
   <Triggers>
    <TriggerExpression>* * * * * ?</TriggerExpression>
   </Triggers>
   <JobDetails>
    <Description>Dump states</Description>
    <JobDetailsClass>com.tibco.mdm.admin.jmx.cacheCopier.JMXToCacheCopier</JobDetailsClass>
   </JobDetails>
   <ExecuteOnStartup>false</ExecuteOnStartup>
   <JobInput>
    <JobPolicy>scheduler/JMXCopierJobPolicy.xml</JobPolicy>
    <JobPolicyParser>
    <Description>Copy inputs for moving JMX stats off memory.</Description>
    <ParserClass>com.tibco.mdm.admin.jmx.cacheCopier.JmxCopierPolicy</ParserClass>
    </JobPolicyParser>
   </JobInput>
  </Job>
</Jobs>
</Schedule>
</CronSchedules>