Abstract: A computer-implemented method generates a trigger registration for a selected triggering type. The generated trigger registration is stored in a triggering persistency. A received event from an event persistency is analyzed and data associated with the analyzed event is compared with the triggering persistency. Based on the comparison and using a pattern execution framework, an enterprise threat detection (ETD) pattern is processed to perform actions responsive to the received event.

Abstract: A sample log file including a plurality of log entries for log learning is accessed, using a log interpretation controller, prior to runtime as part of a log learning process. Each of the plurality of log entries is analyzed. A log entry type is assigned to each of the plurality of log entries. A log type and semantic event are assigned to each log entry type. Generation of runtime rules is triggered for analyzing unknown log entries. The runtime rules include characteristics of particular log entry types that allow unique identification of the particular log entry type for a particular unknown log entry. The generated runtime rules are loaded into a runtime parser.

Abstract: A log file including a plurality of log entries is accessed. Each log entry of the plurality of log entries is analyzed to identify components of each log entry. The components of the particular log entry indicate an event. The event is associated with roles. Each role is associated with one or more attributes. Semantic meaning of the event associated with the particular log entry is determined. A mapping is performed by applying contextual information from one or more semantic meaning models stored in a knowledgebase to the identified components of each log entry to derive semantic meaning for the particular log entry. The derived semantic meaning is modeled for the particular log entry. The modeled semantic meaning is recorded in the knowledgebase as a new semantic meaning model for future use.

Abstract: Systems, computer products, and computer-implemented methods may be directed to publishing information about a service offered by a service provider at a first services registry. The information about the service can be communicated to a second services registry. An indication of a subscription to the service may be received by a service consumer from the second services registry. Information about the subscribed service can be communicated to the second services registry.

Abstract: Techniques for managing information exchange between business entities include identifying a plurality of routing rules stored in a database of a first business entity computing system; receiving a request for a business transaction through an application of a plurality of applications of the first business entity computing system; determining, based on the identified routing rules, an identifiable business context reference (IBCR) associated with a second business entity computing system, the IBC comprising a unique identifier associated with the second business entity and a first plurality of business data attributes associated with the second business entity; determining, based on the identified IBCR, a communication connection associated with the IBC and an identifiable business context (IBC) associated with the first business entity computing system; and initiating the business transaction between the first business entity computing system and the second business entity computing system through the deter

Abstract: Techniques for managing information exchange between business entities include presenting an interface through an application of a plurality of applications to a user for an identifiable business context (IBC), the IBC including a unique identifier associated with a first business entity and a plurality of business data attributes associated with the first business entity; receiving, from the application, the IBC for storage in a repository communicably coupled to the application; defining a communication connection between the first business entity and a second business entity; associating the defined communication connection with the IBC; and publishing the IBC unique identifier, the defined communication connection, and at least a portion of the plurality of business data attributes to a registry that is exposed to the plurality of applications.

Abstract: Systems, computer products, and computer-implemented methods may be directed to publishing information about a service offered by a service provider at a first services registry. The information about the service can be communicated to a second services registry. An indication of a subscription to the service may be received by a service consumer from the second services registry. Information about the subscribed service can be communicated to the second services registry.

Abstract: Techniques for managing information exchange between business entities include identifying, through an application of a plurality of applications on a first business entity computing system, an identifiable business context (IBC) referenced on a second business entity computing system, the IBC including a unique identifier associated with the second business entity and a first plurality of business data attributes associated with the second business entity; identifying a communication connection between the first business entity computing system and the second business entity computing system based on the identification of the IBC; and generating an identifiable business context reference (IBCR) for storage on the first business entity computing system, the IBCR associated with the communication connection and including the unique identifier and a second plurality of business data objects, at least one of the second plurality of business data objects distinct from the first plurality of business data objects.

Abstract: Techniques for managing information exchange between business entities include identifying a plurality of routing rules stored in a database of a first business entity computing system; receiving a request for a business transaction through an application of a plurality of applications of the first business entity computing system; determining, based on the identified routing rules, an identifiable business context reference (IBCR) associated with a second business entity computing system, the IBC comprising a unique identifier associated with the second business entity and a first plurality of business data attributes associated with the second business entity; determining, based on the identified IBCR, a communication connection associated with the IBC and an identifiable business context (IBC) associated with the first business entity computing system; and initiating the business transaction between the first business entity computing system and the second business entity computing system through the deter