Patent application number | Description | Published |
20090019109 | SYSTEM AND METHOD FOR PROVIDING A FINE-GRAINED RESPONSE FROM A COARSE-GRAINED SERVICE OBJECT - A system and method for generating data at a fine level of detail based on a request to a service object that provides data at a coarse level of detail. The request to the service object includes a data request and a response template indicating the level of detail or selection required in the response. The service object server accesses data using the service object api and coarse level of detail. A navigator uses the data request to develop an information model of the data and then traverses the information model to extract the data needed for a response at the level of detail indicated by the response template. The service object is thus able to return data at a fine level of detail from an object that supports only coarse levels of detail. | 01-15-2009 |
20100312737 | Semi-Automatic Evaluation and Prioritization of Architectural Alternatives for Data Integration - A systematic approach to evaluating and prioritizing architectural design pattern alternatives for data integration. A set of decision factors is derived from requirements for a system to be integrated. A default score is assigned to each decision factor based on historical data integration knowledge, and the default scores are weighted. A priority score is also assigned to each decision factor based on collected inputs from system metadata and subject matter experts in the enterprise system. Next, an individual consolidated score for each decision factor is calculated using the default score, the weighted score, and the priority score, and a total consolidated score is calculated from the individual consolidated scores for the architecture design pattern. The total consolidated score for the architecture design pattern may be compared against total consolidated scores for other architecture design patterns to determine a suitable candidate architecture design pattern for data integration. | 12-09-2010 |
20110010217 | Service Oriented Architecture Governance Using A Template - Embodiments of the invention are directed to establishing a governance procedure for a selected service oriented architecture. One embodiment of the invention, directed to a method, comprises the steps of furnishing one or more first governance tasks, and furnishing one or more second governance tasks. The method further comprises providing a user of the governance procedure with a template, wherein the template is configured for operation by the user to selectively modify at least one of the first governance tasks. The template is configured further to be incapable of modifying any of the second governance tasks, when the template is being operated by the user. Each modified first governance task is combined with each of the second governance tasks, and also with each unmodified first governance task, to provide the governance procedure. | 01-13-2011 |
20110022439 | SYSTEM FOR MANAGING EVENTS IN A CONFIGURATION OF SOA GOVERNANCE COMPONENTS - Embodiments of the invention are associated with a configuration comprising multiple integrated SOA governance components, and are generally concerned with monitoring and managing events that can or are likely to impact on different components of the configuration. One embodiment of the invention, directed to a method, comprises the steps of detecting a particular event that occurs at a particular SOA governance component of the configuration, and routing information pertaining to the detected event to a pre-specified storage location. The method further comprises operating a monitoring mechanism to selectively monitor the information routed to the location, and to determine from the monitored information that the particular event has occurred at the particular component of the configuration. Responsive to determining that the particular event has occurred at the particular component, the monitoring mechanism is further operated to query each of the remaining SOA governance components, in order to identify each of the remaining components in which the particular event does not exist. | 01-27-2011 |
20110082721 | AUTOMATED REACTIVE BUSINESS PROCESSES - A computer implemented method, data processing system, and computer usable program code for managing reactive business processes. In one embodiment, the computer implemented method provides for modeling a set of business processes as pre-defined events in a software process application, wherein the software process application is located on a data processing system. A set of performance indicators are associated to the set of business processes. A set of reactive business processes are modeled, wherein the set of reactive business processes are pre-defined templates included in the software process application. The set of reactive business processes are mapped to the set of performance indicators. The set of performance indicators are monitored and responsive to a trigger from the set of performance indicators, a reactive business process is initiated. | 04-07-2011 |
20110137869 | FLEXIBLE DATA ARCHIVAL USING A MODEL-DRIVEN APPROACH - The present invention provides a system and methods for flexible data archival using a model-driven approach. The data archive system and method of the present invention provides the operation of moving data from original data repository into archive data repository. Users can specify archive conditions describing which portions of the data will be moved. The method may have steps such as analyzing application content, defining an archive model, transforming the model by generating an archive specification based upon the modeling result and building an application based upon the archive model and deploying the new model and archive application. | 06-09-2011 |
20110137871 | PATTERN-BASED AND RULE-BASED DATA ARCHIVE MANAGER - The present invention relates to a method or system of data archival using a pattern-based and rule-based data archive manager for a flexible, generic archive solution. The method and system allow for the user to create rules and allow for the system to archive based upon those rules input by the user and to select data to be archived against the facts about the data. The system has a rule based data archive manager having a pattern matcher, a decision scheduler and a rule executor, a fact meta-data storage for storing facts, and a rule library storage for storing user input data about rules. | 06-09-2011 |
20110137872 | MODEL-DRIVEN DATA ARCHIVAL SYSTEM HAVING AUTOMATED COMPONENTS - The present invention relates to a method or system of data archival using model-driven and automated components. It provides a data archiving solution by using model-driven, automated components, such as a transformation component, for a flexible, generic data archive solution. Other components may include a testing component for testing the data archive, a deploying component for deploying the data archive specification model and a feedback component for receiving archive results, observing the archive results and feeding back the archive results for archive model optimization. | 06-09-2011 |
20110153293 | MANAGING AND MAINTAINING SCOPE IN A SERVICE ORIENTED ARCHITECTURE INDUSTRY MODEL REPOSITORY - A method of managing and maintaining scope in a of service oriented architecture industry model repository comprising defining boundaries and definitions of scope and scope propagation of topics, associations, and occurrences within the SOA IMR; managing boundaries and definitions of scope and scope propagation within the SOA IMR; and maintaining boundaries and definitions of scope and scope propagation within the SOA IMR. | 06-23-2011 |
20130152106 | MANAGING EVENTS IN A CONFIGURATION OF SOA GOVERNANCE COMPONENTS - One embodiment of the invention, directed to a method, comprises the steps of a computer detecting a predetermined type of event resulting from one of an addition of new component to the SOA infrastructure or a change to an existing component of the SOA infrastructure, wherein a notice of the detected event is stored in a repository associated with the component. In response to the detected event, the computer queries other components of the SOA infrastructure, and determines whether the other components have been updated based on the detected event and in response to determining the other components have not been updated based on the detected event, the computer automatically updates the other components of the SOA infrastructure based on the detected event. | 06-13-2013 |