Abstract: A content replication connector receives control data associated with replication of content data from a source system. Based on the control data, the content replication connector fetches the content data from the source system, converts the content data from a first data format to a second data format, and sends the content data to a content replication server. The content replication server replicates the content data, and a target system fetches the content data from the content replication server.

Abstract: A selection of data types is defined from available log data for an evaluation of events associated with an entity. One or more evaluations associated with the entity are defined and reference data is generated from the selection of data types based on the one or more defined evaluations. The one or more evaluations are grouped into a pattern. A three dimensional (3D) score diversity diagram visualization is initialized for display in a graphical user interface, where a point representing the entity in the visualization is localized in 3D space at a coordinate based on two-dimensional (2D) coordinates in a 2D coordinate system of a centroid of the calculated area of a polygon placed to into the 2D coordinate system and defined by the values of each evaluation associated with the entity.

Abstract: A Content Service executing in a cloud-computing-based Cloud Platform receives enterprise threat detection (ETD) Content transmitted from an ETD Content Development System (CDS) as a publication of the ETD Content from the ETD CDS. The received ETD Content is stored into a Content Management System (CMS). A determination is made of a registered Client ETD System for which the ETD Content is relevant. The ETD Content is published to the registered Client ETD System.

Abstract: A selection of data types is defined from available log data for an evaluation of events associated with an entity. One or more evaluations associated with the entity are defined and reference data is generated from the selection of data types based on the one or more defined evaluations. The one or more evaluations are grouped into a pattern. A three dimensional (3D) score diversity diagram visualization is initialized for display in a graphical user interface, where a point representing the entity in the visualization is localized in 3D space at a coordinate based on two-dimensional (2D) coordinates in a 2D coordinate system of a centroid of the calculated area of a polygon placed to into the 2D coordinate system and defined by the values of each evaluation associated with the entity.

Abstract: A selection of data types is defined from available log data for an evaluation of events associated with an entity. One or more evaluations associated with the entity are defined and reference data is generated from the selection of data types based on the one or more defined evaluations. The one or more evaluations are grouped into a pattern. A three dimensional (3D) score diversity diagram visualization is initialized for display in a graphical user interface, where a point representing the entity in the visualization is localized in 3D space at a coordinate based on two-dimensional (2D) coordinates in a 2D coordinate system of a centroid of the calculated area of a polygon placed to into the 2D coordinate system and defined by the values of each evaluation associated with the entity.

Abstract: A log processing job executing on a log producing computing system is initiated for processing log data associated with the log producing computing system. Log entries are determined to be available for processing. At least one instance of a Log Extractor Factory, Reader, and Transformation component are instantiated for reading and transforming the log data. Read log data is transformed into a common semantic format as transformed log data and transmitted in real-time to a Streaming Component for storage in an Enterprise Threat Detection (ETD) System. A recovery point is stored with a recovery timestamp indicating a next log entry in the log data to process.

Abstract: A log processing job executing on a log producing computing system is initiated for processing log data associated with the log producing computing system. Log entries are determined to be available for processing. At least one instance of a Log Extractor Factory, Reader, and Transformation component are instantiated for reading and transforming the log data. Read log data is transformed into a common semantic format as transformed log data and transmitted in real-time to a Streaming Component for storage in an Enterprise Threat Detection (ETD) System. A recovery point is stored with a recovery timestamp indicating a next log entry in the log data to process.

Abstract: A Content Service executing in a cloud-computing-based Cloud Platform receives enterprise threat detection (ETD) Content transmitted from an ETD Content Development System (CDS) as a publication of the ETD Content from the ETD CDS. The received ETD Content is stored into a Content Management System (CMS). A determination is made of a registered Client ETD System for which the ETD Content is relevant. The ETD Content is published to the registered Client ETD System.

Abstract: A content replication connector receives control data associated with replication of content data from a source system. Based on the control data, the content replication connector fetches the content data from the source system, converts the content data from a first data format to a second data format, and sends the content data to a content replication server. The content replication server replicates the content data, and a target system fetches the content data from the content replication server.

Abstract: A selection of data types is defined from available log data for an evaluation of events associated with an entity. One or more evaluations associated with the entity are defined and reference data is generated from the selection of data types based on the one or more defined evaluations. The one or more evaluations are grouped into a pattern. A three dimensional (3D) score diversity diagram visualization is initialized for display in a graphical user interface, where a point representing the entity in the visualization is localized in 3D space at a coordinate based on two-dimensional (2D) coordinates in a 2D coordinate system of a centroid of the calculated area of a polygon placed to into the 2D coordinate system and defined by the values of each evaluation associated with the entity.

Abstract: Methods and apparatus, including computer program products, implement techniques for visualizing data dependencies. A specification of a component encapsulating one or more controllers is received. Each controller has an associated data structure of data elements. The component includes one or more data mappings, where each data mapping is either a context mapping or a model mapping. A context mapping binds the data element to another data element. A model mapping specifies a supply function operable to derive a value of the data element from a model. A data dependency relationship is derived whenever there is at least one data mapping between the controller and another controller or a model. Each data dependency relationship is directed from a controller to one other controller or to one of the models. A data dependency relationship is visualized by displaying a link showing a direction of data dependency.

Abstract: Methods and apparatus, including computer program products, implement techniques for structuring applications into reusable components. A reusable component having an external interface and an internal interface is implemented. The component encapsulates functionality, where multiple instances of the component are reusable at the same time. The component is configurable to embed one or more specified components. The external interface comprises an external programming interface, an external data-binding interface, and an external visual interface. The internal interface comprises an embedding interface, an internal programming interface, an internal data-binding interface, and an internal visual interface. The embedding interface specifies one or more component interfaces of components that can be embedded.

Abstract: Methods and apparatus, including computer program products, for developing an application. The development includes the use of a data model (e.g., a metamodel represented using UML) from which an API is derived. The API can include features derived from customizable extensions within the data model.

Abstract: A prototype page for simulating navigation between objects in a computer program. A selection of a distribution of presentation areas is received. A placement of first and second icon symbols in at least one of the presentation areas is received. The first and second icon symbols represent first and second objects, respectively, of a computer program. A placement of a navigation symbol is received. The navigation symbol represents a navigation between the first and second objects. Markup language code is provided for a prototype page. The code includes location indicating code corresponding to the distribution of presentation areas. The code includes picture code for first and second pictures corresponding to the first and second icon symbols, respectively. The markup language code further includes interaction code corresponding to the navigation symbol. The prototype page is capable of simulating the navigation between the first and second objects in the computer program.

Abstract: Methods and apparatus, including computer program products, implement techniques for structuring applications into reusable components. A reusable component having an external interface and an internal interface is implemented. The component encapsulates functionality, where multiple instances of the component are reusable at the same time. The component is configurable to embed one or more specified components. The external interface comprises an external programming interface, an external data-binding interface, and an external visual interface. The internal interface comprises an embedding interface, an internal programming interface, an internal data-binding interface, and an internal visual interface. The embedding interface specifies one or more component interfaces of components that can be embedded.

Abstract: Methods and apparatus, including computer program products, implement techniques for visualizing data dependencies. A specification of a component encapsulating one or more controllers is received. Each controller has an associated data structure of data elements. The component includes one or more data mappings, where each data mapping is either a context mapping or a model mapping. A context mapping binds the data element to another data element. A model mapping specifies a supply function operable to derive a value of the data element from a model. A data dependency relationship is derived whenever there is at least one data mapping between the controller and another controller or a model. Each data dependency relationship is directed from a controller to one other controller or to one of the models. A data dependency relationship is visualized by displaying a link showing a direction of data dependency.

Abstract: Methods and apparatus, including computer program products, for developing an application. The development includes the use of a data model (e.g., a metamodel represented using UML) from which an API is derived. The API can include features derived from customizable extensions within the data model.

Abstract: Methods and apparatus, including computer program products, for developing user interfaces with views and executing applications with such user interfaces. User input is received specifying a view composition. The view composition includes a set of views, a layout of the views, and at least one navigation link. Each view includes a layout of one or more user interface elements selected from a set of user interface elements. Each navigation link specifies a potential transition from one view in the set of views to another view in the set of views. The view composition is stored in a repository. A user interface can be generated according to the layout of views specified in the view composition, and modified based on the navigation links. In some embodiments, views can be nested. In addition, view compositions can be associated with application components, can include views from nested components, and can be modified dynamically.

Abstract: A prototype page for simulating navigation between objects in a computer program. A selection of a distribution of presentation areas is received. A placement of first and second icon symbols in at least one of the presentation areas is received. The first and second icon symbols represent first and second objects, respectively, of a computer program. A placement of a navigation symbol is received. The navigation symbol represents a navigation between the first and second objects. Markup language code is provided for a prototype page. The code includes location indicating code corresponding to the distribution of presentation areas. The code includes picture code for first and second pictures corresponding to the first and second icon symbols, respectively. The markup language code further includes interaction code corresponding to the navigation symbol. The prototype page is capable of simulating the navigation between the first and second objects in the computer program.