#include <MonitorCollectorImpl.h>
List of all members.
Detailed Description
Monitor collector implementation
Constructor & Destructor Documentation
TMCDB::MonitorCollectorImpl::MonitorCollectorImpl |
( |
const ACE_CString & |
name, |
|
|
maci::ContainerServices * |
containerServices | |
|
) |
| | |
TMCDB::MonitorCollectorImpl::~MonitorCollectorImpl |
( |
|
) |
|
Member Function Documentation
void TMCDB::MonitorCollectorImpl::cleanUp |
( |
|
) |
[virtual] |
Called after the last functional call to the component has finished. The component should then orderly release resources etc. If this method is overwritten in a subclass, the developer has to make sure that all cleanup performed by the implementation of the base class take place. The best way to do this is to call the implementation of the base itself explicitly, as would be done implicitly in a destructor chain.
- Returns:
- void
Reimplemented from acscomponent::ACSComponentImpl.
void TMCDB::MonitorCollectorImpl::deregisterMonitoredDevice |
( |
const char * |
componentName |
) |
|
void TMCDB::MonitorCollectorImpl::enable_archiving |
( |
const char * |
componentName, |
|
|
const char * |
propertyName | |
|
) |
| | |
TMCDB::MonitorDataBlocks* TMCDB::MonitorCollectorImpl::getMonitorData |
( |
|
) |
|
void TMCDB::MonitorCollectorImpl::initialize |
( |
|
) |
[virtual] |
Called to give the component time to initialize itself. For instance, the component could retrieve connections, read in configuration files/parameters, build up in-memory tables, ... Called before execute. In fact, this method might be called quite some time before functional requests can be sent to the component. Must be implemented as a synchronous (blocking) call.
- Returns:
- void
Reimplemented from acscomponent::ACSComponentImpl.
MonitorComponent* TMCDB::MonitorCollectorImpl::registerMonitoredComponent |
( |
const char * |
componentName |
) |
[private] |
void TMCDB::MonitorCollectorImpl::registerMonitoredDevice |
( |
const char * |
componentName, |
|
|
const char * |
serialNumber | |
|
) |
| | |
void TMCDB::MonitorCollectorImpl::registerMonitoredDeviceWithMultipleSerial |
( |
const char * |
componentName, |
|
|
const TMCDB::propertySerialNumberSeq & |
serialNumbers | |
|
) |
| | |
void TMCDB::MonitorCollectorImpl::set_archiving_interval |
( |
const char * |
componentName, |
|
|
const char * |
propertyName, |
|
|
ACS::TimeInterval |
time | |
|
) |
| | |
void TMCDB::MonitorCollectorImpl::startMonitoring |
( |
const char * |
componentName |
) |
|
void TMCDB::MonitorCollectorImpl::stopMonitoring |
( |
const char * |
componentName |
) |
|
void TMCDB::MonitorCollectorImpl::suppress_archiving |
( |
const char * |
componentName, |
|
|
const char * |
propertyName | |
|
) |
| | |
Member Data Documentation
here we hold reference to Archive monitor controller
number of registered devices
pointer to container services
protection for monitorComponents_m and related stuff
The documentation for this class was generated from the following file: