Abstract: One or more embodiments analyze log records of applications to determine whether a composite rule pertaining to events associated with the log records occurring within a specified time window are satisfied. Satisfaction of the composite rule may facilitate real-time diagnosis and detection of patterns in logs which indicate problems, threats, systemic issues, or performance issues relating to the applications. The composite rule may specify events associated with log records from multiple different applications that occur within a same specified time window and are associated with a same tenant and entity. Satisfaction of the composite rule may be analyzed by a state machine that tracks satisfaction of the individual rules within the composite rule in a sequence of stages. A notification, alert, or alarm may be generated when the composite rule is satisfied.

Abstract: One or more embodiments analyze log records of applications to determine whether a composite rule pertaining to events associated with the log records occurring within a specified time window are satisfied. Satisfaction of the composite rule may facilitate real-time diagnosis and detection of patterns in logs which indicate problems, threats, systemic issues, or performance issues relating to the applications. The composite rule may specify events associated with log records from multiple different applications that occur within a same specified time window and are associated with a same tenant and entity. Satisfaction of the composite rule may be analyzed by a state machine that tracks satisfaction of the individual rules within the composite rule in a sequence of stages. A notification, alert, or alarm may be generated when the composite rule is satisfied.

Abstract: One or more embodiments analyze log records of applications to determine whether a composite rule pertaining to events associated with the log records occurring within a specified time window are satisfied. Satisfaction of the composite rule may facilitate real-time diagnosis and detection of patterns in logs which indicate problems, threats, systemic issues, or performance issues relating to the applications. The composite rule may specify events associated with log records from multiple different applications that occur within a same specified time window and are associated with a same tenant and entity. Satisfaction of the composite rule may be analyzed by a state machine that tracks satisfaction of the individual rules within the composite rule in a sequence of stages. A notification, alert, or alarm may be generated when the composite rule is satisfied.

Abstract: Techniques are for rule-based continuous drift and consistency management for target systems. In one embodiment, a set of rules is stored in volatile or non-volatile store. The set of rules may include one or more drift rules and/or one or more consistency rules. A rule may be applied to one or more associated targets to detect drift or inconsistency. A drift rule identifies a set of one or more attributes and a source and may be applied by comparing a first configuration of the set of one or more attributes on an associated target with a second configuration of the set of one or more attributes on the source. A consistency rule may be applied to a composite target by comparing member targets that are grouped by target type. Notification data may be output if target drift or inconsistency is detected to alert a user.

Abstract: One or more embodiments analyze log records of applications to determine whether a composite rule pertaining to events associated with the log records occurring within a specified time window are satisfied. Satisfaction of the composite rule may facilitate real-time diagnosis and detection of patterns in logs which indicate problems, threats, systemic issues, or performance issues relating to the applications. The composite rule may specify events associated with log records from multiple different applications that occur within a same specified time window and are associated with a same tenant and entity. Satisfaction of the composite rule may be analyzed by a state machine that tracks satisfaction of the individual rules within the composite rule in a sequence of stages. A notification, alert, or alarm may be generated when the composite rule is satisfied.

Abstract: Techniques are for rule-based continuous drift and consistency management for target systems. In one embodiment, a set of rules is stored in volatile or non-volatile store. The set of rules may include one or more drift rules and/or one or more consistency rules. A rule may be applied to one or more associated targets to detect drift or inconsistency. A drift rule identifies a set of one or more attributes and a source and may be applied by comparing a first configuration of the set of one or more attributes on an associated target with a second configuration of the set of one or more attributes on the source. A consistency rule may be applied to a composite target by comparing member targets that are grouped by target type. Notification data may be output if target drift or inconsistency is detected to alert a user.

Abstract: Techniques are for rule-based continuous drift and consistency management for target systems. In one embodiment, a set of rules is stored in volatile or non-volatile store. The set of rules may include one or more drift rules and/or one or more consistency rules. A rule may be applied to one or more associated targets to detect drift or inconsistency. A drift rule identifies a set of one or more attributes and a source and may be applied by comparing a first configuration of the set of one or more attributes on an associated target with a second configuration of the set of one or more attributes on the source. A consistency rule may be applied to a composite target by comparing member targets that are grouped by target type. Notification data may be output if target drift or inconsistency is detected to alert a user.

Abstract: Techniques are for rule-based continuous drift and consistency management for target systems. In one embodiment, a set of rules is stored in volatile or non-volatile store. The set of rules may include one or more drift rules and/or one or more consistency rules. A rule may be applied to one or more associated targets to detect drift or inconsistency. A drift rule identifies a set of one or more attributes and a source and may be applied by comparing a first configuration of the set of one or more attributes on an associated target with a second configuration of the set of one or more attributes on the source. A consistency rule may be applied to a composite target by comparing member targets that are grouped by target type. Notification data may be output if target drift or inconsistency is detected to alert a user.

Abstract: A method and apparatus for plan-based compliance score computation is provided. Compliance-specific target results are stored. The compliance results include, for each target, a subset of target-specific compliance results for a rule subset of compliance rules. Each target-specific compliance result of the result subset includes a compliance value. The compliance value represents compliance to a compliance rule of the rule subset. An execution plan is generated. The execution plan generates data that measures compliance to a first compliance standard. For each target-specific compliance result, an execution plan step is generated for computing the compliance value of the respective compliance rule of the respective target.

Abstract: Systems, methods, and other embodiments associated with registering a WFS feature type are described. One example method includes creating a feature instance table and a set of collection item tables to register the WFS feature type. Elements in the feature instance table and a collection item table may be related by a feature instance primary key value. The example method may also include producing an r-tree based spatial index for spatial content collection items stored in the set of collection item tables. The method may also include selectively processing a WFS request to manipulate (e.g., insert, delete, update) a WFS feature instance based, at least in part, on the feature instance table and the set of collection item tables. The method may also include selectively processing a WFS query associated with a WFS feature instance based, at least in part, on the r-tree based spatial index.

Abstract: A method and apparatus for plan-based compliance score computation is provided. Compliance-specific target results are stored. The compliance results include, for each target, a subset of target-specific compliance results for a rule subset of compliance rules. Each target-specific compliance result of the result subset includes a compliance value. The compliance value represents compliance to a compliance rule of the rule subset. An execution plan is generated. The execution plan generates data that measures compliance to a first compliance standard. For each target-specific compliance result, an execution plan step is generated for computing the compliance value of the respective compliance rule of the respective target.

Abstract: Locking feature instances in a web feature service by processing a web feature service data transformation request; identifying a table associated with the web feature service data transformation request from a feature type identified in the request; determining if the table associated with the web feature service data transformation request is enabled for long transaction locking; and, if the table is long transaction lock enabled, locking at least one feature instance associated with a filter condition of the web feature service data transformation request by associating a session transferable identifier with the at least one feature instance and identifying the client session as owner of the session transferable identifier; and enabling a transfer of the long transaction lock to another client session in response to a lock transfer request from the another client session that references the session transferable identifier in a web feature service transaction request.

Abstract: A method for maintaining a long transaction database lock across multiple database sessions. It is determined if at least one row of a long transaction lock enabled table, identified in a long transaction lock request, is locked by a short or long transaction lock. If the row is not locked, locking the at least one row with a long transaction lock. The long transaction lock on the at least one row is associated with a current client session that generated the request. The long transaction lock can be transferred to another client session in response to a lock transfer request from the another client session.

Abstract: Systems, methods, and other embodiments associated with registering a WFS feature type are described. One example method includes creating a feature instance table and a set of collection item tables to register the WFS feature type. Elements in the feature instance table and a collection item table may be related by a feature instance primary key value. The example method may also include producing an r-tree based spatial index for spatial content collection items stored in the set of collection item tables. The method may also include selectively processing a WFS request to manipulate (e.g., insert, delete, update) a WFS feature instance based, at least in part, on the feature instance table and the set of collection item tables. The method may also include selectively processing a WFS query associated with a WFS feature instance based, at least in part, on the r-tree based spatial index.

Abstract: A mechanism of specification of business process templates, to capture commonly performed business activities/workflows/projects within a business organization and encourage reuse of best practices. Long transaction workspaces based business process template execution mechanism are presented, which have several advantages over existing business process execution mechanisms in web collaboration frameworks. This execution approach provides support for an isolated environment for business process execution. This isolates the changes made on different resources while executing a business process from the external world until the business process completes. It enables the ability to concurrently manipulate same resources in different components of a business process, and later resolve conflicts if any and merge the different views of the same resource manipulated by different components of a business process.

Abstract: A method for maintaining a long transaction database lock across multiple database sessions. It is determined if at least one row of a long transaction lock enabled table, identified in a long transaction lock request, is locked by a short or long transaction lock. If the row is not locked, locking the at least one row with a long transaction lock. The long transaction lock on the at least one row is associated with a current client session that generated the request. The long transaction lock can be transferred to another client session in response to a lock transfer request from the another client session.

Abstract: Locking feature instances in a web feature service by processing a web feature service data transformation request; identifying a table associated with the web feature service data transformation request from a feature type identified in the request; determining if the table associated with the web feature service data transformation request is enabled for long transaction locking; and, if the table is long transaction lock enabled, locking at least one feature instance associated with a filter condition of the web feature service data transformation request by associating a session transferable identifier with the at least one feature instance and identifying the client session as owner of the session transferable identifier; and enabling a transfer of the long transaction lock to another client session in response to a lock transfer request from the another client session that references the session transferable identifier in a web feature service transaction request.

Abstract: A system for automatically enhancing Web pages with annotations expressed in Extensible Markup Language (XML) which describes the pages' multimedia content. Each Web page is parsed or scanned to identify markup tags which contain the URLs of separately stored multimedia data (e.g. image, audio or video files). Each referenced multimedia data entity is then retrieved and analyzed by a type-specific process to extract metadata which describes its content. Additional descriptive metadata may be obtained from the referencing markup tag, accepted from a human editor, or fetched from operating system directories which provide access to the multimedia files. The resulting metadata is expressed in text-based XML format and inserted into a copy of the Web page to form an enhanced Web page whose multimedia content may then be processed by conventional text-based indexing and searching facilities.

Abstract: A shareable application program interface infrastructure which is used in combination with a relational database to provide data storage and processing functions for location-dependent objects, and includes a mechanism for easily associating an object, such a service, with a geographic region, such as an area served by the service. The service designer is provided with a tool to choose a geographic region or a point location (specified by an address), and to associate that selected geographic region with a service. Each service is associated with a geographic region chosen from a hierarchy of predetermined system-defined regions that are preferably organized into a hierarchy composed of levels organized in order of decreasing size so that the boundaries of each child region lie within the boundaries of its parent region. The services designer is also provided with the option of creating “user defined regions” that are composed of existing system defined regions or a region centered around a selected location.

Abstract: Techniques used in database systems for dealing with metadata associated with multimedia objects. The database system includes a generic representation for metadata values. The representation includes a stratum specifier that specifies the stratum to which a metadata value applies, an extent specifier that specifies a portion of the stratum to which the metadata value applies, and a metadata item specifier that specifies the metadata value. The generic representation is implemented in an object-oriented relational database system. The generic representation of the metadata for a given multimedia object is contained in the object in the database that represents the multimedia object. Values of the representation may be returned by a query or may be used to select other values to be returned by a query, including the portion of an object associated with a metadata value.