Patent application number | Description | Published |
20120078928 | INTEGRATED CONTENT PUBLISHING - Content objects may be incorporated as metadata in application systems in the same programming environment used to create the rest of the application. Although content objects may be included as part of the application systems, in some instances a central repository storing content object information from each application system may be used to facilitate communication and data sharing between applications. Alternatively, point-to-point communications between applications may also be supported so that applications may share content object data without relying on the central repository. Some embodiments may support both central repository communications and point-to-point communications between applications. Determinations may be made to identify the type of connectivity supported in different circumstances. | 03-29-2012 |
20120137306 | SYSTEM AND METHOD FOR A PROCESS BROKER AND BACKEND ADAPTER BASED PROCESS INTEGRATION - Embodiments of the present invention may provide a local process integration component to facilitate process integration. The local process integration component may include an adapter, a process broker and a process broker handler. The process broker may collaborate with the business logic and adapter to perform business-centric integration logic. The architecture is based on is a toolkit and generator approach. For inbound communication, the adapter is responsible for control flow while the process broker handler provides generic services. For outbound communication, the process broker is responsible for control flow while the process broker handler provides generic services. The control flow orchestration is uniformed by code generation. | 05-31-2012 |
20120137307 | SYSTEM AND METHOD FOR A PROCESS BROKER AND BACKEND ADAPTER BASED PROCESS INTEGRATION - A computer-implemented method for process integration may comprise providing a business logic layer that hosts business object(s), providing process broker(s), providing adapter(s) and providing a process broker handler. Each process broker may perform process integration tasks by dynamically determining whether, when and/or how routines of the business logic layer need to be integrated with routines of a second application. Each adapter may be part of a first application and implement methods to perform communication protocol specific logic. Each adapter may also be interoperable with at least one of the process brokers and one of the business objects to transform a message exchanged between the process broker and the second application from an internal format to an external format or vice versa. The process broker handler may be operable to instantiate the process broker and to instantiate an adapter stored in association with the instantiated process broker. | 05-31-2012 |
20120198511 | WEB SERVICE SECURITY COCKPIT - A first configuration object identifies attributes of a configuration of a first web service. Security setting data is identified defining a security setting rules for the computing system. The failure of the first attribute to satisfy at least one security setting rule is determined. A second configuration object is identified that identifies attributes of a configuration of a second web service. The failure of the second attribute to satisfy at least one security setting rule is determined. A service security cockpit is presented identifying that configurations of at least the first and second web services are unsecure, based at least in part on the determination that the first and second attributes fail to satisfy security setting rules. User input is received, through the cockpit, identifying a resolution action directed to resolve the first attribute failing to satisfy at least one security setting rule. The identified resolution action is then initiated. | 08-02-2012 |
20130036094 | METHOD FOR DETERMINING A SUPPORTED CONNECTIVITY BETWEEN APPLICATIONS - A computer-implemented system and method that analyzes metadata of the first application to identify a first data object and one or more first fields of the first data object, the first data object and the first fields being part of the metadata of the first application, identifies one or more second applications having a second data object with one or more second fields, and determines, for at least one of the second applications, a supported connectivity with the first application and whether the supported connectivity is a point-to-point connectivity or a connectivity through a central design time repository. | 02-07-2013 |
20140032600 | SYSTEMS AND METHODS FOR DATA PRIVACY AND DESTRUCTION - A system and method for managing application(s)' access to personal data of an enterprise business partner is presented. The method includes selecting business partners having personal data records stored in a database connected to an enterprise computing system, for each particular business partner identifying each application that accesses the business partner's personal data records, inquiring from each identified application if it has reached an end-of-purpose period for the personal data records. If an end-of-purpose period has been reached receiving a start-of-retention-time from the application, storing the start-of-retention-time indication in a data record associated with the particular business partner, and blocking access by the particular application to the personal data records of the particular business partner. If a start-of-retention-time indication is not received allowing continued access by the particular application to the personal data records associated with the selected business partner. Applications located in remote systems can be queried and blocked. | 01-30-2014 |
20140082753 | SYSTEMS AND METHODS FOR DATA PRIVACY AND DESTRUCTION IN MULTI-SYSTEM LANDSCAPES - A method for managing personal data access in a multi-system landscape includes receiving at a first system in the multi-system landscape an end-of-purpose check result for a personal data record associated with a particular business partner, identifying other systems of the multi-system landscape that perform operations for the particular business partner if the end-of-purpose check result indicates a start-of-retention-time, transmitting requests to each of the identified systems to synchronously perform an end-of-purpose check of local personal data records associated with the particular business partner, and receiving end-of-purpose check results from each of the identified systems. The method further can include initiating a global blocking process for the particular business partner. A system for implementing the method and a non-transitory computer readable medium are also disclosed. | 03-20-2014 |