Patent application number | Description | Published |
20100005108 | Method and system for generating indexes in an XML database management system - The invention concerns a method for generating at least one index ( | 01-07-2010 |
20100131460 | Method, server extension and database management system for storing non XML documents in a XML database - The present invention relates to a method for storing at least one non-XML document ( | 05-27-2010 |
20130254746 | SYSTEMS AND/OR METHODS FOR EXECUTING APPROPRIATE TESTS BASED ON CODE MODIFICATIONS USING LIVE, DISTRIBUTED, REAL-TIME CACHE AND FEEDBACK LOOP - Certain example embodiments relate to systems and/or methods for determining and/or executing an appropriate subset of tests in response to a code change. In certain example embodiments, hash digests or other unique values for code structures (such as, for example, classes, methods, and/or other structural elements) may be created. Tests associated those associated code structures may be identified. New hash digests or other unique values may be generated for the code structures after the source code has been modified. In response to a mismatch as between the existing and new hash digests or other unique values, a list of associated tests for possible subsequent execution may be retrieved. Certain example embodiments additionally or alternatively provide an incremental but consistent way of analyzing performance issues, e.g., in connection with a profiler. | 09-26-2013 |
20130262646 | METHOD AND REGISTRY FOR ENABLING THE ENFORCEMENT OF DESIGN-TIME POLICIES DURING RUNTIME IN A SERVICE-ORIENTED ARCHITECTURE - Certain example embodiments relate to computer-implemented methods enabling the enforcement of design-time policies during runtime in a service-oriented architecture (SOA). The SOA includes SOA assets (e.g., web services), and at least one runtime container configured to enforce runtime policies on SOA assets executed therein. Example methods may include:
| 10-03-2013 |
20140173633 | METHOD AND SYSTEM FOR PROPAGATING MODIFICATION OPERATIONS IN SERVICE-ORIENTED ARCHITECTURE - Certain example embodiments relate to techniques for propagating modification operations for Service-oriented Architecture (SOA) objects in a SOA. The SOA includes at least two SOA objects that are connected by at least one relationship that defines one SOA object as referencing SOA object and another SOA object as referenced SOA object. Steps of an appropriate may include: receiving a request for propagating a modification operation from the referencing SOA object to the referenced SOA object; evaluating at least one propagation rule to determine whether the requested modification can be performed on the referenced SOA object; and if it is determined that the requested modification cannot be performed in accordance with the at least one propagation rule, evaluating at least one approval rule to determine whether the requested modification can be performed on the referenced SOA object. | 06-19-2014 |
20140173634 | METHOD AND INTEGRATION COMPONENT FOR INTEGRATING OSGI ENVIRONMENTS INTO A SERVICE-ORIENTED ARCHITECTURE - Certain exemplary embodiments relate to a method for integrating at least one Open Services Gateway initiative (OSGi) environment into a Service-oriented Architecture (SOA). The OSGi environment includes at least one OSGi object, and the SOA includes a SOA registry. The method includes publishing the at least one OSGi object to the SOA registry. The publishing includes creating an SOA object in the SOA registry corresponding to the at least one OSGi object. The SOA object includes information reflecting at least one relationship of the at least one OSGi object to at least one further OSGi object within the OSGi environment. | 06-19-2014 |
20140222523 | TECHNIQUES FOR BUSINESS PROCESS DRIVEN SERVICE ORIENTED ARCHITECTURE (SOA) GOVERNANCE - Certain example embodiments tie the business process governance and Service Oriented Architecture (SOA) governance processes together through the use of Business Process Model and Notation (BPMN) and Event Driven Architecture (EDA) based messaging. That is, in certain example embodiments, a BPMN agent integrated into a SOA registry and publish/subscribe agents deployed to the SOA registry and a business process engine are used to bring the business and SOA governances together through an EDA that helps generate relevant messages from a BPMN model representing the various governance mechanisms. Advantageously, a Complex Event Processing (CEP) engine and business analytics modules may provide monitoring and feedback to both parts of the overall architecture. | 08-07-2014 |
20140380267 | LIFECYCLE MANAGEMENT SYSTEM WITH CONDITIONAL APPROVALS AND CORRESPONDING METHOD - Certain example embodiments concern a lifecycle management system for at least one computing component. A lifecycle model, including lifecycle states assignable to the at least one computing component, is defined. The lifecycle states include a production state. The lifecycle management system ensures the at least one computing component can be productively used only if it is assigned the production state. A lifecycle transition request assigning a requested target lifecycle state of the lifecycle model to the at least one computing component is received. A conditional lifecycle state, different from the requested target lifecycle state, is assigned to the at least one computing component. At least one condition to be fulfilled for the at least one computing component to be assigned the requested target lifecycle state is assigned. The requested target lifecycle state is automatically assigned to the at least one computing component when the at least one condition is fulfilled. | 12-25-2014 |
20150026660 | METHODS FOR BUILDING APPLICATION INTELLIGENCE INTO EVENT DRIVEN APPLICATIONS THROUGH USAGE LEARNING, AND SYSTEMS SUPPORTING SUCH APPLICATIONS - Certain example embodiments relate to application intelligence gathering systems and/or methods, e.g., in connection with Event Driven Applications and/or the like. More particularly, certain example embodiments relate to the effective recording of application evolution and usage information for usage learning and/or event auditing purposes. With respect to usage learning, certain example embodiments may help to capture data on the usage patterns and/or apply learning algorithms that work on the captured data to provide required intelligence to the application. With respect to event auditing, certain example embodiments may help to identify the “who”, “what”, “when”, “where”, “how”, and/or “why” of particular operations. Application intelligence optionally may be used in determining application “hotspots” or commonly used features that could help in areas such as application maintenance, performance tuning, and/or the like. | 01-22-2015 |