McDewey

value of a parameter removeAllParameters() public void removeAllParameters() remove all the parameters in the list removeParameter(String) public void removeParameter(java.lang.String parameterName) remove a particular parameter if it is in the list toString() public java.lang.String toString() Overrides: toString in class Object Alarm Interface Hierarchy The following interface hierarchy is contained in the com.cisco.services.alarm package. com.cisco.services.alarm.Alarm, on page 688 com.cisco.services.alarm.AlarmWriter, on page 693 Alarm The Alarm interface is used to define Alarms in. An Alarm has an XML representation that it must adhere to in order to be recognized by the Alarm Service, with a DTD as shown below. An application can implement this interface or use the AlarmFactory to generate Alarms of the correct format. The Alarm is the a specification that needs to be sent to an AlarmService that will take some action based on the Alarm. Using this specification the AlarmService will access definitions available in a catalog. This catalog is maintained by the user requiring the Alarm function to effect the appropriate action for the Alarm. The severity specified the Alarm can over-ride the severity associated with this Alarm in the catalog. If no severity is specified in the Alarm the catalog severity is used. Alarm severities are derived from Syslog and are defined as follows: 0 = EMERGENCIES System unusable 1 = ALERTS Immediate action needed 2 = CRITICAL Critical conditions 3 = ERROR Error conditions 4 = WARNING Warning conditions 5 = NOTIFICATION Normal but significant condition Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 688 Cisco Unified JTAPI Alarms and Services Alarm Interface Hierarchy