Abstract: A method includes receiving a query directed to a first data model that specifies base data fields. The method includes determining extension bindings for the first data model. A binding specifies an extension to the first data model and specifies one of the base data fields as a node at which the specified extension is added. The extension specifies a non-empty set of data fields. The method includes retrieving base data values according to the base data fields and extension data values according to, for a first binding, the set of data fields. The method includes generating a data object from the base and extension data values according to a second data model. The second data model is based on the first data model extended by adding the data fields from the extension specified by the first binding to the first data model at the specified node.

Abstract: A query processing method includes receiving a query from a requestor. The query is directed to a first data model specifying multiple base data fields. The method includes determining a set of extension bindings for the first data model based on the query. Each binding specifies an extension to the first data model from a set of model extensions and specifies one of the base data fields of the first data model as a node at which the extension is added. The method includes generating a data object from base data values and extension data values according to an extended data model. The extended data model is defined by the first data model extended by, for each binding of the set, adding data fields from the specified extension to the first data model at the specified node. The method includes returning the data object to the requestor.

Abstract: A query processing method includes receiving a query from a requestor. The query is directed to a first data model specifying multiple base data fields. The method includes determining a set of extension bindings for the first data model based on the query. Each binding specifies an extension to the first data model from a set of model extensions and specifies one of the base data fields of the first data model as a node at which the extension is added. The method includes generating a data object from base data values and extension data values according to an extended data model. The extended data model is defined by the first data model extended by, for each binding of the set, adding data fields from the specified extension to the first data model at the specified node. The method includes returning the data object to the requestor.

Abstract: Methods and systems for patching an instance of a composite executing in a runtime environment are provided. A method can include at a computer system comprising a processor and a memory executing, by an application server, one or more instances of a composite, and enabling a patch to be applied to the one or more instances of the composite without stopping execution of the one or more instances in the application server, wherein the patch comprises one or more changes to be made to the composite.

Abstract: Techniques are described for determining correlations between data in a repository system. The data may include information about corresponding to resources (e.g., an application, a process, a service, an endpoint, or a method) in a computing environment. A correlation between objects can indicate a similarity or a relationship based on one or more of the attributes of each object that is correlated. The repository system can store information about each object in a data structure, such as an entity, including the attributes about the object. The repository system can determine the relationships between entities based on correlations identified from the attributes of entities. The repository system can perform correlations based on groups of entities corresponding to a group of objects. Upon determining that two groups of entities match, the repository system can compare individual entities in the groups to identify correlations between individual entities corresponding to objects that are correlated.

Abstract: Methods and systems for patching an instance of a composite executing in a runtime environment are provided. A method can include at a computer system comprising a processor and a memory executing, by an application server, one or more instances of a composite, and enabling a patch to be applied to the one or more instances of the composite without stopping execution of the one or more instances in the application server, wherein the patch comprises one or more changes to be made to the composite.

Abstract: Techniques described herein relate to automatic upstream service resumption after downstream system failure. An automatic resumption module may be configured to monitor a downstream endpoint (of a problematic downstream service provider) and determine when it again successfully can process requests by periodically processing inbound requests (e.g., from suspended upstream service providers) and automatically re-enabling upstream endpoints for the suspended upstream service providers in the case of success. The automatic resumption module may start a trickle feed timer for each upstream endpoint to allow messages to be processed at a configured retry rate while the upstream endpoint remains suspended. The trickle feed timer may be configured to start upon the triggering of a circuit breaker for the involved downstream service. When downstream endpoint invocation succeeds, the automatic resumption module can resume all upstream endpoints associated with the downstream endpoint.

Abstract: Methods and systems for patching an instance of a composite executing in a runtime environment are provided. A method can include at a computer system comprising a processor and a memory executing, by an application server, one or more instances of a composite, and enabling a patch to be applied to the one or more instances of the composite without stopping execution of the one or more instances in the application server, wherein the patch comprises one or more changes to be made to the composite.

Abstract: Techniques described herein relate to automatic system suspension based upon downstream system failure in service-oriented architecture (SOA) applications. A system management module of a SOA system may be configured to detect a problem with a downstream service provider involved with a SOA application, and in response, automatically suspend particular processing within the application to prevent requests that may end up at the downstream service provider from entering the SOA application. The system management module may implement a circuit breaker module that maintains a circuit breaker structure specific to a downstream endpoint leading to a downstream service provider. Upon a triggering of a circuit breaker for a downstream endpoint, one or more upstream service providers are identified as associated with faulted traffic causing the triggering, and the system management module can automatically cause further traffic from these upstream service providers to be suspended.

Abstract: Methods and systems for patching an instance of a composite executing in a runtime environment are provided. A method can include at a computer system comprising a processor and a memory executing, by an application server, one or more instances of a composite, and enabling a patch to be applied to the one or more instances of the composite without stopping execution of the one or more instances in the application server, wherein the patch comprises one or more changes to be made to the composite.

Abstract: Techniques described herein relate to automatic system suspension based upon downstream system failure in service-oriented architecture (SOA) applications. A system management module of a SOA system may be configured to detect a problem with a downstream service provider involved with a SOA application, and in response, automatically suspend particular processing within the application to prevent requests that may end up at the downstream service provider from entering the SOA application. The system management module may implement a circuit breaker module that maintains a circuit breaker structure specific to a downstream endpoint leading to a downstream service provider. Upon a triggering of a circuit breaker for a downstream endpoint, one or more upstream service providers are identified as associated with faulted traffic causing the triggering, and the system management module can automatically cause further traffic from these upstream service providers to be suspended.

Abstract: Techniques described herein relate to automatic upstream service resumption after downstream system failure. An automatic resumption module may be configured to monitor a downstream endpoint (of a problematic downstream service provider) and determine when it again successfully can process requests by periodically processing inbound requests (e.g., from suspended upstream service providers) and automatically re-enabling upstream endpoints for the suspended upstream service providers in the case of success. The automatic resumption module may start a trickle feed timer for each upstream endpoint to allow messages to be processed at a configured retry rate while the upstream endpoint remains suspended. The trickle feed timer may be configured to start upon the triggering of a circuit breaker for the involved downstream service. When downstream endpoint invocation succeeds, the automatic resumption module can resume all upstream endpoints associated with the downstream endpoint.

Abstract: Techniques are described for determining correlations between data in a repository system. The data may include information about corresponding to resources (e.g., an application, a process, a service, an endpoint, or a method) in a computing environment. A correlation between objects can indicate a similarity or a relationship based on one or more of the attributes of each object that is correlated. The repository system can store information about each object in a data structure, such as an entity, including the attributes about the object. The repository system can determine the relationships between entities based on correlations identified from the attributes of entities. The repository system can perform correlations based on groups of entities corresponding to a group of objects. Upon determining that two groups of entities match, the repository system can compare individual entities in the groups to identify correlations between individual entities corresponding to objects that are correlated.