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: Systems and methods for supporting multi-tenancy in a multi-tenant application server environment are provided. A first partition in a multi-tenant server environment can include a first composite and the first composite includes first metadata that is configured to be customized for a first tenant of the first partition. A second partition in the multi-tenant server environment can include a second composite and the second composite includes second metadata that is configured to be customized for a second tenant of the second partition. A global runtime in the multi-tenant server environment can include a global composite and the global composite include global metadata that is configured to be shared by the first partition and the second partition.

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: Systems and methods for supporting multi-tenancy in a multi-tenant application server environment are provided. A first partition in a multi-tenant server environment can include a first composite and the first composite includes first metadata that is configured to be customized for a first tenant of the first partition. A second partition in the multi-tenant server environment can include a second composite and the second composite includes second metadata that is configured to be customized for a second tenant of the second partition. A global runtime in the multi-tenant server environment can include a global composite and the global composite include global metadata that is configured to be shared by the first partition and the second partition.

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: Additional synonym pairs are inferred from a pair of schema elements (of different schemas) mapped by a user, and the inferred pairs are added to a dictionary. According to one aspect of the present invention, a mapped pair is inferred as a synonym pair if the elements of the mapped pair cannot be mapped according to a program logic otherwise. According to one more aspect of the present invention, the parents of the mapped elements are also inferred as synonym pairs if sufficient peer (to the mapped elements) elements are already mapped or considered synonyms.

Abstract: Determining data elements for possible mapping in heterogeneous schema definitions. According to one aspect of the present invention, a user indicates whether two non-leaf elements (in respective schemas) are structurally similar, and the probability of possible match of a first element (in a first schema) and a second element (in a second schema) as a synonym pair is computed to be more if the two elements are below the respective ones of the structurally similar nodes, compared to in a situation in which the elements are not present in such hierarchies.

Abstract: Additional synonym pairs are inferred from a pair of schema elements (of different schemas) mapped by a user, and the inferred pairs are added to a dictionary. According to one aspect of the present invention, a mapped pair is inferred as a synonym pair if the elements of the mapped pair cannot be mapped according to a program logic otherwise. According to one more aspect of the present invention, the parents of the mapped elements are also inferred as synonym pairs if sufficient peer (to the mapped elements) elements are already mapped or considered synonyms.