Abstract: The present disclosure relates generally to techniques for monitoring and improving a bot system. An analytic system is integrated with a bot system for monitoring, analyzing, visualize, and improving the performance of the bot system. The analytic system monitors events occurred in conversations between end users and the bot system, aggregates and analyzes the collected events, and provides information regarding the conversations graphically on a graphic user interface at different generalization levels. The analytic system can also provide suggestions, options, or other information for improving the bot system through the graphic user interface.

Abstract: The present disclosure relates generally to techniques for analyzing and improving a bot system, and more particularly to an analytic system integrated with a bot system for monitoring, analyzing, visualizing, diagnosing, and improving the performance of the bot system. For example, an analytic system is integrated with a bot system for monitoring, analyzing, visualizing, and improving the performance of the bot system. The analytic system monitors events occurred in conversations between end users and the bot system, aggregates and analyzes the collected events, and provides information regarding the conversations graphically on a graphic user interface as insights reports at different generalization levels. The insights reports offer developer-oriented analytics to pinpoint issues with skills so a user can address them before they cause problems.

Abstract: The present disclosure relates generally to techniques for monitoring and improving a bot system. An analytic system is integrated with a bot system for monitoring, analyzing, visualize, and improving the performance of the bot system. The analytic system monitors events occurred in conversations between end users and the bot system, aggregates and analyzes the collected events, and provides information regarding the conversations graphically on a graphic user interface at different generalization levels. The analytic system can also provide suggestions, options, or other information for improving the bot system through the graphic user interface.

Abstract: A method and apparatus for an in-database sharded queue that supports JMS session ordering is provided. Messages from a plurality of enqueuers are stored in a plurality of shards of a particular queue. For each enqueuer, all messages are stored in only one of the shards. Each shard includes one or more subshards, each subshard having one or more partitions of a queue table maintained by a relational database system. All messages from a first enqueuer are stored in partitions of the queue table that are assigned to a first shard of the plurality of shards. All messages from a second enqueuer are stored in partitions of the queue table that are assigned to a second shard of the plurality of shards. Subscribers of the particular queue are caused to dequeue messages from the plurality of shards.

Abstract: A method and apparatus for an in-database sharded queue that supports JMS session ordering is provided. Messages from a plurality of enqueuers are stored in a plurality of shards of a particular queue. For each enqueuer, all messages are stored in only one of the shards. Each shard includes one or more subshards, each subshard having one or more partitions of a queue table maintained by a relational database system. All messages from a first enqueuer are stored in partitions of the queue table that are assigned to a first shard of the plurality of shards. All messages from a second enqueuer are stored in partitions of the queue table that are assigned to a second shard of the plurality of shards. Subscribers of the particular queue are caused to dequeue messages from the plurality of shards.

Abstract: A method of using a plurality of subscriber types in managing a message queue of a database management system is described and provided. The method comprises creating a subscriber with a set of rules to the message queue. The subscriber is designated as one or more of the plurality of subscriber types. Moreover, an event notification registration representing a request to be notified if a message to the message queue satisfies the set of rules may be created. In response to a new message for enqueuing to the message queue, it is determined whether the new message satisfies the set of rules. If the new message satisfies the set of rules and if so determined by a triggered event notification registration, a notification is performed according to the triggered event notification registration. A requirement that a receiver of the notification dequeue the new message from the message queue depends on the subscriber type designation.

Abstract: A computer implemented method and system for automatically removing an event registration within an event notification infrastructure of a database system is disclosed. The method includes removing an event registration from an event queue automatically if a specified active period of time has elapsed. Further, the method includes removing an event registration from an event queue automatically if the event occurred N times where N can be specified at event registration. Also, the method includes removing an event registration from an event queue automatically if either the event occurred N times where N can be specified at event registration or a specified active period of time has elapsed. Moreover, the method includes removing an event registration from an event queue if a client explicitly requests removal of said event registration.

Abstract: Techniques for processing events in parallel are provided. Multiple publishers publish events in parallel to a plurality of channels. Each channel is a queue that maintains a list of events that are awaiting to be processed by one or more slave processes. In one approach, all events that need to be persistent are published to a persistent channel, whereas all events that do not need to be persistent are published to one or more in-memory channels. In another approach, for each event, a publisher determines which channel of the plurality of channel to publish the event. The determination is based, at least in part, on the number of events in each channel and, optionally, the type of each event in each channel. In either approach, each event from a single publisher is published to the same channel.

Abstract: Techniques for managing messages in computer systems are provided. In one embodiment, in response to a publisher attempting to enqueue a message in a queue, a determination is made whether a condition is satisfied. The condition is based on the current usage of the queue by the publisher. Based on whether the condition is satisfied, a decision is made whether to enqueue the message in the queue. The decision whether to enqueue the message may comprise restricting the publisher from enqueueing any more messages in the queue until the same or a different condition is satisfied.

Abstract: One embodiment of the present invention provides a database server for securing database event notifications. The server includes a session key creation mechanism configured to create a session key when a client registers for an event, a storage mechanism configured to store the session key on the database server, a data accessing mechanism configured to access registration metadata to obtain the session key when the event occurs, a connection mechanism configured to establish a communication channel between the database server and the client, a mutual authenticating mechanism configured to using the session key to mutually authenticate the client and the database server during event notification, and an event notifying mechanism configured to send the event notification to the client.

Abstract: Techniques for grouping events in a computing system are provided. A registrant sends, to a database server, a request to register to receive a single notification based the occurrence of multiple events that satisfy certain criteria, referred to as grouping attributes. Such registrations are referred to as grouping registrations. An eventing mechanism in the database server receives and maintains grouping registrations. When an event is received, the eventing mechanism determines whether the event has been registered for in an active grouping registration, i.e., one whose start time has passed but whose completion criteria are not yet satisfied. If so, then the eventing mechanism updates grouping data associated with the grouping registration. When the completion criteria of a grouping registration are satisfied, the eventing mechanism sends a notification to the registrant and/or other intended recipient(s).

Abstract: Described herein are various approaches that allow rules to be used to specify actions, that alleviate the complexity and burden of developing and maintaining rules in a rules-based messaging system, and that provide more efficient ways of evaluating rules. The approaches allow rules to specify user-defined transformation functions for transforming messages, to specify when and how to perform row migration, and to specify other types of actions. Rules are grouped into rule sets. Several types of rule sets, referred to as positive and negative rule sets, allow users to use rules that are less complex to develop and maintain. Rule sets are evaluated more efficiently by attempting to evaluate the rule set with less information than is needed to evaluate all the rules in the rule set. Also, the results of rules evaluations that are based on a set of values are cached for later retrieval.

Abstract: Techniques for managing messages in computer systems are provided. In one embodiment, in response to a publisher attempting to enqueue a message in a queue, a determination is made whether a condition is satisfied. The condition is based on the current usage of the queue by the publisher. Based on whether the condition is satisfied, a decision is made whether to enqueue the message in the queue. The decision whether to enqueue the message may comprise restricting the publisher from enqueueing any more messages in the queue until the same or a different condition is satisfied.

Abstract: Techniques for propagating messages in a distributed system are provided. A set of messages enqueued in a source queue are sent to one or more destination queues. An acknowledgement is received from each of the one or more destination queues, where the acknowledgement indicates which messages of the set of messages have been consumed at the particular destination queue. Based on the acknowledgements, one or more messages of the set messages are ceased to be maintained in the source queue.

Abstract: Techniques for managing messages in computer systems are provided. In one embodiment, in response to a publisher attempting to enqueue a message in a queue, a determination is made whether a condition is satisfied. The condition is based on the current usage of the queue by the publisher. Based on whether the condition is satisfied, a decision is made whether to enqueue the message in the queue. The decision whether to enqueue the message may comprise restricting the publisher from enqueueing any more messages in the queue until the same or a different condition is satisfied.

Abstract: One embodiment of the present invention provides a database server for securing database event notifications. The server includes a session key creation mechanism configured to create a session key when a client registers for an event, a storage mechanism configured to store the session key on the database server, a data accessing mechanism configured to access registration metadata to obtain the session key when the event occurs, a connection mechanism configured to establish a communication channel between the database server and the client, a mutual authenticating mechanism configured to using the session key to mutually authenticate the client and the database server during event notification, and an event notifying mechanism configured to send the event notification to the client.

Abstract: Described herein are various approaches that allow rules to be used to specify actions, that alleviate the complexity and burden of developing and maintaining rules in a rules-based messaging system, and that provide more efficient ways of evaluating rules. The approaches allow rules to specify user-defined transformation functions for transforming messages, to specify when and how to perform row migration, and to specify other types of actions. Rules are grouped into rule sets. Several types of rule sets, referred to as positive and negative rule sets, allow users to use rules that are less complex to develop and maintain. Rule sets are evaluated more efficiently by attempting to evaluate the rule set with less information than is needed to evaluate all the rules in the rule set. Also, the results of rules evaluations that are based on a set of values are cached for later retrieval.

Abstract: In some messaging system architectures, messages can cycle back to the originator of a message, who may then propagate the message, causing the cycle to be repeated. Described herein are techniques that use rules and fields in a redo log, to manage message flows such that undesired cycles are prevented. The techniques may be used in messaging systems that have various topologies.

Abstract: A system for managing event monitors within a database is provided. The system can adjust the amount of notifications generated by those event monitors, so as to achieve an effective balance between probability of notification loss and available notification bandwidth, as well as provide a better quality of service to database users.

Abstract: Techniques for processing events in parallel are provided. Multiple publishers publish events in parallel to a plurality of channels. Each channel is a queue that maintains a list of events that are awaiting to be processed by one or more slave processes. In one approach, all events that need to be persistent are published to a persistent channel, whereas all events that do not need to be persistent are published to one or more in-memory channels. In another approach, for each event, a publisher determines which channel of the plurality of channel to publish the event. The determination is based, at least in part, on the number of events in each channel and, optionally, the type of each event in each channel. In either approach, each event from a single publisher is published to the same channel.