Abstract: A solution descriptor comprises a set of component workload units, a workload unit describing a deployable application component with application binary, configuration parameters and dependency declarations. An environment descriptor specifies a set of target platforms and plugins in an execution environment. A deployer interprets the solution descriptor and the environment descriptor, and generates a list of tuples comprising compatible workload-plugin-platform combinations. The deployer determines an execution order for the list of tuples, and invokes the plugins in the list of tuples in the execution order, wherein each of the plugins executes a corresponding compatible workload on a corresponding compatible target platform specified in the list of tuples.

Abstract: A solution descriptor comprises a set of component workload units, a workload unit describing a deployable application component with application binary, configuration parameters and dependency declarations. An environment descriptor specifies a set of target platforms and plugins in an execution environment. A deployer interprets the solution descriptor and the environment descriptor, and generates a list of tuples comprising compatible workload-plugin-platform combinations. The deployer determines an execution order for the list of tuples, and invokes the plugins in the list of tuples in the execution order, wherein each of the plugins executes a corresponding compatible workload on a corresponding compatible target platform specified in the list of tuples.

Abstract: A solution descriptor comprises a set of component workload units, a workload unit describing a deployable application component with application binary, configuration parameters and dependency declarations. An environment descriptor specifies a set of target platforms and plugins in an execution environment. A deployer interprets the solution descriptor and the environment descriptor, and generates a list of tuples comprising compatible workload-plugin-platform combinations. The deployer determines an execution order for the list of tuples, and invokes the plugins in the list of tuples in the execution order, wherein each of the plugins executes a corresponding compatible workload on a corresponding compatible target platform specified in the list of tuples.

Abstract: A solution descriptor comprises a set of component workload units, a workload unit describing a deployable application component with application binary, configuration parameters and dependency declarations. An environment descriptor specifies a set of target platforms and plugins in an execution environment. A deployer interprets the solution descriptor and the environment descriptor, and generates a list of tuples comprising compatible workload-plugin-platform combinations. The deployer determines an execution order for the list of tuples, and invokes the plugins in the list of tuples in the execution order, wherein each of the plugins executes a corresponding compatible workload on a corresponding compatible target platform specified in the list of tuples.

Abstract: A solution descriptor comprises a set of component workload units, a workload unit describing a deployable application component with application binary, configuration parameters and dependency declarations. An environment descriptor specifies a set of target platforms and plugins in an execution environment. A deployer interprets the solution descriptor and the environment descriptor, and generates a list of tuples comprising compatible workload-plugin-platform combinations. The deployer determines an execution order for the list of tuples, and invokes the plugins in the list of tuples in the execution order, wherein each of the plugins executes a corresponding compatible workload on a corresponding compatible target platform specified in the list of tuples.

Abstract: A solution descriptor comprises a set of component workload units, a workload unit describing a deployable application component with application binary, configuration parameters and dependency declarations. An environment descriptor specifies a set of target platforms and plugins in an execution environment. A deployer interprets the solution descriptor and the environment descriptor, and generates a list of tuples comprising compatible workload-plugin-platform combinations. The deployer determines an execution order for the list of tuples, and invokes the plugins in the list of tuples in the execution order, wherein each of the plugins executes a corresponding compatible workload on a corresponding compatible target platform specified in the list of tuples.

Abstract: Techniques for maintaining consistent replicas of data are disclosed. By way of example, a method for managing copies of objects within caches, in a system including multiple caches, includes the following steps. Consistent copies of objects are maintained within the caches. A home cache for each object is maintained, wherein the home cache maintains information identifying other caches likely containing a copy of the object. In response to a request to update an object, the home cache for the object is contacted to identify other caches which might have copies of the object.

Abstract: An embodiment of the invention includes a system for partitioning asset management plugins. The system includes an application program interface for performing basic CRUD functions on assets having multiple asset types. At least one plugin having plugin components is provided, wherein the plugin manages at least one asset having a specific asset type (of the multiple asset types). The plugin components include a CRUD component, a state component, an actions component, and/or a view component. The system further includes plugin containers for hosting the plugin components, the plugin containers include at least one client-side plugin container and at least one server-side plugin container. The plugin components are partitioned and distributed from the plugin components to the plugin containers by a plugin server based on capabilities of the client.

Abstract: An embodiment of the invention provides a method for non-intrusive cloud services billing, including storing service log files in a data store, wherein each of the service log files include a lifecycle event of a resource in a service produced by an instance of the service. A log transformer connected to the data store converts the service log files into a standardized format. A metering descriptor describing billable entities for each offering of the service is obtained, wherein each offering of the service has a different metering descriptor, and wherein the billable entities include multiple categories of billing. A billing record generator connected to the log transformer is programmed, wherein the billing record generator converts standardized log records into metering records. The billing record generator generates a metering record with one or more of the service log files in the standardized format and the metering descriptor.

Abstract: Improved access control techniques for use in a service-oriented computing environment are disclosed. For example, one method for authenticating a client in a service-oriented environment, wherein the service-oriented environment includes a plurality of services, includes the following steps. At least one service of the plurality of services is invoked. State information is associated with the at least one service invoked. The state information is used to authenticate a client with at least one service. Further, a method for access control in a service-oriented environment, wherein the service-oriented environment includes a plurality of services, includes the following steps. A rule specification language is provided. At least one rule is specified using the rule specification language. A verification is performed to determine whether or not the client satisfies the at least one rule. The client is granted access to a service when the client satisfies the at least one rule.

Abstract: Techniques for structure-aware caching are provided. The techniques include decomposing a response from an origin server into one or more independently addressable objects, using a domain specific language to navigate the response to identify the one or more addressable objects and create one or more access paths to the one or more objects, and selecting a route to an object by navigating an internal structure of a cached object to discover one or more additional independently addressable objects.

Abstract: A system in a cloud services environment comprises one or more service offerings, one or more service instances and one or more service support utilities. Each of the one or more service offerings is described by at least one service descriptor. Each of the one or more service instances is obtained from at least one of the one or more service offerings. Each of the one or more service support utilities is customized by at least one service descriptor. A service comprises at least one component and a service descriptor comprises one or more models.

Abstract: In one embodiment, the present invention is a method and apparatus for dynamic middleware assembly. One embodiment of the inventive method for dynamically assembling middleware at a client involves selecting a middleware component from a group of middleware components, where the selection is based at least in part on a first profile defining characteristics of the client and a second profile defining characteristics the selected middleware component. The selected middleware component is then dynamically assembled (installed and configured) at the client.

Abstract: A system in a cloud services environment comprises one or more service offerings, one or more service instances and one or more service support utilities. Each of the one or more service offerings is described by at least one service descriptor. Each of the one or more service instances is obtained from at least one of the one or more service offerings. Each of the one or more service support utilities is customized by at least one service descriptor. A service comprises at least one component and a service descriptor comprises one or more models.

Abstract: A method for dynamically deploying an application in a client-server environment includes evaluating at least one constraint of at least one of the application or the client-server environment and partitioning the placement and execution of components of the application in the client-server environment dynamically at runtime according to the at least one constraint.

Abstract: Techniques for structure-aware caching are provided. The techniques include decomposing a response from an origin server into one or more independently addressable objects, using a domain specific language to navigate the response to identify the one or more addressable objects and create one or more access paths to the one or more objects, and selecting a route to an object by navigating an internal structure of a cached object to discover one or more additional independently addressable objects.

Abstract: Techniques are disclosed for adaptively determining trust in client-server environments. By way of example, a method for assigning a trust level to a client in a client-server environment including at least one client communicating with a plurality of servers includes the following steps. Information associated with a server s1 and a server s2 different from s1 is obtained regarding a request r1 sent by a client and received by s1 and a request r2 sent by the client and received by s2. The obtained information is utilized to assign at least one trust level to the client.

Abstract: An embodiment of the invention includes a system for partitioning asset management plugins. The system includes an application program interface for performing basic CRUD functions on assets having multiple asset types. At least one plugin having plugin components is provided, wherein the plugin manages at least one asset having a specific asset type (of the multiple asset types). The plugin components include a CRUD component, a state component, an actions component, and/or a view component. The system further includes plugin containers for hosting the plugin components, the plugin containers include at least one client-side plugin container and at least one server-side plugin container. The plugin components are partitioned and distributed from the plugin components to the plugin containers by a plugin server based on capabilities of the client.

Abstract: A system, method and computer program product for context-sensitive middleware service injection. A technique is described to apply desired middleware functionality to granular units of functionality in response to extra-functional requirements and context information. Context may include without limitation types of process activities, phases of execution of process activities, identities of interaction partners, system architectures and the status of a given interaction. A further technique is described to dynamically analyze processes to select middleware functionality for compatibility with declared extra-functional requirements and detected context information.

Abstract: In one embodiment, the present invention is a method and apparatus for dynamic middleware assembly. One embodiment of the inventive method for dynamically assembling middleware at a client involves selecting a middleware component from a group of middleware components, where the selection is based at least in part on a first profile defining characteristics of the client and a second profile defining characteristics the selected middleware component. The selected middleware component is then dynamically assembled (installed and configured) at the client.