About Alarm Events
An alarm event occurs when Integration Server generates a message related to the status of the server. An alarm event can be generated for the following reasons:
A client experiences a logon failure or is denied access to
Integration Server. A client cannot log on because of “invalid credentials.”
Errors occur in the Cluster Manager. The inability to add a port to a cluster can cause errors in Cluster Manager.
A user tries to access a port and is denied access to the port. (This can happen when a user tries to execute a service not allowed on the port.) This type of alarm event is sometimes called a
port access exception.
A port cannot be started. The most common reason a port cannot start is that the port is being accessed by another application.
A service cannot be loaded or executed due to setup errors. For a flow service, a possible error is a missing XML metafile. For a Java service, possible errors include a missing class file or method.
You can use alarm events to invoke event handlers that execute when the server generates messages related to the status of the server. For example, you might want to create an event handler that notifies the administrator when a user is denied access to the server or to a port, when a service fails to load or execute, or when a port does not start. You can also create event handlers to send data to a network monitoring system.