Remote Systems
v6.4.1

com.ibm.etools.systems.universal.util
Class StatusMonitorFactory

java.lang.Object
  extended bycom.ibm.etools.systems.universal.util.StatusMonitorFactory

public class StatusMonitorFactory
extends Object

Factory for finding and creating the StatusMonitor class for a given system


Field Summary
protected static StatusMonitorFactory _instance
           
protected  HashMap _monitorMap
           
 
Constructor Summary
StatusMonitorFactory()
           
 
Method Summary
static StatusMonitorFactory getInstance()
           
 StatusMonitor getStatusMonitorFor(ISystem system, DataStore dataStore)
           
 StatusMonitor getStatusMonitorFor(ISystem system, DataStore dataStore, ICommunicationsDiagnosticFactory diagnosticFactory)
           
 void removeStatusMonitorFor(ISystem system)
           
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

_monitorMap

protected HashMap _monitorMap

_instance

protected static StatusMonitorFactory _instance
Constructor Detail

StatusMonitorFactory

public StatusMonitorFactory()
Method Detail

getInstance

public static StatusMonitorFactory getInstance()

removeStatusMonitorFor

public void removeStatusMonitorFor(ISystem system)

getStatusMonitorFor

public StatusMonitor getStatusMonitorFor(ISystem system,
                                         DataStore dataStore)

getStatusMonitorFor

public StatusMonitor getStatusMonitorFor(ISystem system,
                                         DataStore dataStore,
                                         ICommunicationsDiagnosticFactory diagnosticFactory)

Remote Systems
v6.4.1

Copyright © 2005 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.