Abstract: A highly reliable and readily scalable solution for managing events. In particular, an event is received and processed in a transaction. Any one of a plurality of event servers is selected to obtain event data based on the event and store the event data in an event data store. The event can be published to allow a subscribing event consumer to conduct further processing for the event data.

Abstract: A method, apparatus, and computer-usable medium for retrieving a first entry from a collection of trickle confirmation entries (associated with a first collection of resources that require configuration confirmation) from a trickle confirmation queue. A first resource among the first collection of resources associated with the first entry from the collection of trickle confirmation entries is queried for a potential change in configuration of the first resource. If a potential change in configuration is detected, the first entry from the collection of trickle confirmation entries is inserted on a trickle update queue. A first entry from a collection of trickle update entries (associated with a second collection of resources that require configuration update) is retrieved from the trickle update queue. Configuration information regarding a first resource associated with the first entry from the collection of trickle update entries is updated.

Abstract: A namespace exploits individual resource identity attributes of an application to allow the integration of resource instances from applications into a configuration management database (CMDB), prior to any data cleansing or namespace harmonization activities. An approach for incremental reconciliation of resource instances within the CMDB is defined.

Abstract: Under the present invention, when an event is received on a server, it is stored and then categorized. In being categorized, an event group pertaining to the event is identified. Based on the group of events, a set (e.g., one or more) of destinations to which the event should be routed can be determined. The group of events is then associated with an access control list (ACL) that contains entries identifying users (or groups of users) and their permissions to interact with events in that group. Once the association is made, the event and optionally the ACL is routed to the appropriate destinations. Based on the permissions contained in the ACL, the destinations will interact with the event accordingly.

Abstract: Under the present invention, when an event is received on a server, it is stored and then categorized. In being categorized, an event group pertaining to the event is identified. Based on the group of events, a set (e.g., one or more) of destinations to which the event should be routed can be determined. The group of events is then associated with an access control list (ACL) that contains entries identifying users (or groups of users) and their permissions to interact with events in that group. Once the association is made, the event and optionally the ACL is routed to the appropriate destinations. Based on the permissions contained in the ACL, the destinations will interact with the event accordingly.

Abstract: A TMN system includes a multi-threaded persistent TMN agent and Management Information Bases (MIBs), each including a Managed Object Instance Cache The MIB is maintained in a general purpose database system in secondary storage such as a hard disk and not by a TMN agent in main memory. At run-time, incoming TMN manager operations are translated into Database Data Manipulation Language (DML, e.g. SQL DML) commands. The MIB to database mapping supports any database language. The agent process can terminate due to a system failure or other abnormal event. In such a case the object instances and their data, stored in the MIB, are saved in secondary cache memory so that they are not lost. The restarted managed agent process reflects the MIB state of the terminated managed agent process. The managed agent process allows “Multi-threaded” means or parallel processing of messages, including CMIP requests, received from manager processes.

Abstract: In a telecommunication management network Applications can transmit messages to other applications without maintaining routing and characteristic information for each target application. The enhanced directory services feature maintains the routing and characteristic information and provides the information as needed to either the transmitting application or a dispatcher process 304, which routes the message without further assistance of the transmitting application. This simplifies the functions that must be embedded in the application. Thus, as the routing information or the characteristic information of the application entities changes, the applications continue to function properly. Each user environment accessing the enhanced directory services database can elect when and how it handles changes to the enhanced directory services database.