Creates an event processor for a specified application.
The name of the application.
The type of processor to create (emitter, watcher, or both).
A new or existing processor instance.
Deletes a specific type of event processor (emitter).
The application name associated with the emitter to be deleted.
Deletes an event processor, removing both its emitter and watcher capabilities.
The application name whose processor is to be deleted.
Deletes a specific type of event processor (watcher).
The application name associated with the watcher to be deleted.
Destroys a processor by removing all associated file watchers and cleaning up resources.
The name of the application whose processor needs to be destroyed.
Retrieves a generic event processor that can emit and watch events.
The application name.
An event processor capable of both emitting and watching.
Retrieves a Zowe-specific event processor. The purpose of this method is for internal
Imperative APIs to get a properly initialized processor. This processor will be used
when applications (like Zowe Explorer) call Imperative APIs that trigger events. For
example, when the user updates credentials from Zowe Explorer, this processor could be
used to emit an OnVaultChanged
event.
The Zowe event processor instance.
Generated using TypeDoc
Overview
The
EventOperator
manages event processors and sets limits on their behavior.An
EventOperator
categorizes processors into 3 types:Applications use the
EventOperator
to obtain the appropriate event processor based on their needs. For example, an application might use a watcher to react to user actions and an emitter to notify other components of state changes.App Names and Processors
Processors are tied to application names to prevent event collisions and to maintain a clear separation of event domains. Valid app names are defined in the list of extenders (formal plugin names or ZE extender names).
Understanding Event Types