Abstract: Disclosed herein are system, method, and computer program product embodiments for performing threat detection on a monitored system. The monitored system may periodically send artifacts (e.g., database records, binaries, program code, business data) to a repository for storage and creation of a snapshot. This repository is typically held in a cloud-based system. The cloud-based system can compare a snapshot of the artifacts against prior snapshots, and generate a change log. This change log can then be provided to a threat detection system for analysis. By this approach, an intrusion can potentially be detected even when system logs cannot be trusted, due to tampering or other inaccuracies.

Abstract: Disclosed herein are system, method, and computer program product embodiments for performing threat detection on a monitored system. The monitored system may periodically send artifacts (e.g., database records, binaries, program code, business data) to a repository for storage and creation of a snapshot. This repository is typically held in a cloud-based system. The cloud-based system can compare a snapshot of the artifacts against prior snapshots, and generate a change log. This change log can then be provided to a threat detection system for analysis. By this approach, an intrusion can potentially be detected even when system logs cannot be trusted, due to tampering or other inaccuracies.

Abstract: In an example embodiment, login credentials are received from a user. These login credentials are validated. Sensitive information is received from the user. The sensitive information is then stored in a cloud-based database. One or more access limitations are established for the sensitive information. A request for the sensitive information is received, from a first third party entity, via an application program interface (API) distributed to a plurality of third party entities. It is then determined if providing access to the sensitive information to the first third party entity would violate the one or more access limitations for the sensitive information. In response to a determination that the providing access to the sensitive information to the first third party entity would not violate the one or more access limitations for the sensitive information, the sensitive information is transmitted to the first third party entity.

Abstract: In an example embodiment, login credentials are received from a user. These login credentials are validated. Sensitive information is received from the user. The sensitive information is then stored in a cloud-based database. One or more access limitations are established for the sensitive information. A request for the sensitive information is received, from a first third party entity, via an application program interface (API) distributed to a plurality of third party entities. It is then determined if providing access to the sensitive information to the first third party entity would violate the one or more access limitations for the sensitive information. In response to a determination that the providing access to the sensitive information to the first third party entity would not violate the one or more access limitations for the sensitive information, the sensitive information is transmitted to the first third party entity.

Abstract: Provided herein are techniques for distributing software. An embodiment operates by receiving a software product request including a unique identification information, verifying the unique identification information, and distributing a software product associated with the unique identification information in response to the request.

Abstract: Provided herein are techniques for distributing software. An embodiment operates by receiving a software product request including a unique identification information, verifying the unique identification information, and distributing a software product associated with the unique identification information in response to the request.

Abstract: A computer-implemented system and method for implementing a value help search that includes receiving a value help search criteria from a user and sending the value help requests to multiple backend systems using a server computer system in a service oriented architecture system. Sending the value help search criteria may include a specific search help name to one of the multiple backend systems. The value help search service receives both metadata and result data from said one of the multiple backend systems. The metadata describes the structure of a search results. The value help search service may generate a search result table from the result data received from the backend system.

Abstract: A system and method are described herein that provide a repository and tool infrastructure (“RTI”) that provides common capabilities on both a client and server end based on standardized communication patterns and a unifying protocol that decouples existing repositories from multiple tools. The repository and tool infrastructure interface interacts with a single development editing tool and any repository housed on a server end and is implemented to each server or client technology if the common capabilities and communication patterns are fulfilled.

Abstract: A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a cost model, a current account contract, and/or a collateral constellation business object.

Abstract: Systems and methods are provided for enabling communication between a composite system providing additional functionality not contained in existing legacy systems and other existing systems using different commands, variables, protocols, methods, or instructions, when data may be located on more than one system. In an embodiment, multiple software layers are used to independently manage different aspects of an application. A business logic layer may be used in an embodiment to facilitate reading/writing operations on data that may be stored locally and/or on external systems using different commands, variables, protocols, methods, or instructions. A backend abstraction layer may be used in an embodiment in conjunction with the business logic layer to facilitate communication with the external systems. A user interface layer may be used in an embodiment to manage a user interface, a portal layer to manage a user context, and a process logic layer to manage a workflow.

Abstract: A method and system for providing an integration framework to integrate a user interface framework with a persistency framework.

Abstract: A computer-implemented system and method for implementing a value help search that includes receiving a value help search criteria from a user and sending the value help requests to multiple backend systems using a server computer system in a service oriented architecture system. Sending the value help search criteria may include a specific search help name to one of the multiple backend systems. The value help search service receives both metadata and result data from said one of the multiple backend systems. The metadata describes the structure of a search results. The value help search service may generate a search result table from the result data received from the backend system.

Abstract: A computer-implemented method providing value help user interface for an underlying application where a request for field names associated with at least one value help backend system is sent by a server. The server may receive the field names from the backend system and display the field names in a user interface and provide filter criteria for each field for the user. The user may enter the search and filter criteria and the user interface may be configured to receive the filter criteria from the user. The search request may be sent to a value help service. The value help service may prompt the back end system to run a search and in turn receive results from the back end system that includes data and metadata. The metadata may describe the format of the search results. The data may be passed according to the metadata and a search results may be generated for the user. The user may make a selection from the search results and the selected data my be delivered to an underlying application.

Abstract: The present invention relates to a data processing system including a first file converter converting a set of file formats into an extended markup language format, a software development tool, and a workflow processing system. The software development tool includes a second file converter for rendering the extended markup language format into a unified modeling language graphic, a renderer for rendering a unified modeling language format converted file, a modifier for graphic modification of the rendered file, a third file converter converting the unified modeling language format to the extended markup language format, and means for deploying an extended markup language format converted file to the workflow processing system. The present invention enables to provide a meta workflow system that can be implemented on the level of existing workflow systems by integration.

Abstract: Systems and methods are provided for enabling communication between a composite system providing additional functionality not contained in existing legacy systems and other existing systems using different commands, variables, protocols, methods, or instructions, when data may be located on more than one system. In an embodiment, multiple software layers are used to independently manage different aspects of an application. A business logic layer may be used in an embodiment to facilitate reading/writing operations on data that may be stored locally and/or on external systems using different commands, variables, protocols, methods, or instructions. A backend abstraction layer may be used in an embodiment in conjunction with the business logic layer to facilitate communication with the external systems. A user interface layer may be used in an embodiment to manage a user interface, a portal layer to manage a user context, and a process logic layer to manage a workflow.

Abstract: A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a cost model, a current account contract, and/or a collateral constellation business object.

Abstract: The present invention relates to a data processing system including a first file converter converting a set of file formats into an extended markup language format, a software development tool, and a workflow processing system. The software development tool includes a second file converter for rendering the extended markup language format into a unified modeling language graphic, a renderer for rendering a unified modeling language format converted file, a modifier for graphic modification of the rendered file, a third file converter converting the unified modeling language format to the extended markup language format, and means for deploying an extended markup language format converted file to the workflow processing system. The present invention enables to provide a meta workflow system that can be implemented on the level of existing workflow systems by integration.

Abstract: Embodiments of the present invention relate to a process-oriented extendable “super-transaction” able to handle multiple business objects in an integrated manner. The embodiments may comprise computer-executable instructions to build objects associated with a business process, and to link the objects using pointers. The linkages enable multiple objects of a business process to be handled in an automated, streamlined flow without manual tracking of objects.