Abstract: A system and method include association of a first plurality of software licenses of a first type with a first subscription associated with a first plurality of cloud-based resources, determination of a first number of the first plurality of software licenses to activate based on the types of the first plurality of resources, activation of the first number of the first plurality of software licenses, monitoring of usage of the first plurality of resources, determination, based on the monitored usage, of a second one or more resources to associate with the first subscription, determination, in response to determining the second resources, of a second number of the first plurality of software licenses to activate based on the types of the second one or more resources, activation of the second number of the first plurality of software licenses, and association of the second resources with the first subscription.

Abstract: A system and method include association of a first plurality of software licenses of a first type with a first subscription associated with a first plurality of cloud-based resources, determination of a first number of the first plurality of software licenses to activate based on the types of the first plurality of resources, activation of the first number of the first plurality of software licenses, monitoring of usage of the first plurality of resources, determination, based on the monitored usage, of a second one or more resources to associate with the first subscription, determination, in response to determining the second resources, of a second number of the first plurality of software licenses to activate based on the types of the second one or more resources, activation of the second number of the first plurality of software licenses, and association of the second resources with the first subscription.

Abstract: Semi-automatic failover includes automatic failover by a service provider as well as self-serviced failover by a service consumer. A signal can be afforded by a service provider based on analysis of an incident that affects the service provider. Initiation of self-serviced failover by a service consumer can be predicated on the signal. In one instance, the signal provides information that aids a decision of whether or not to failover. In another instance, the signal can grant or deny permission to perform a self-serviced failover.

Abstract: Semi-automatic failover includes automatic failover by a service provider as well as self-serviced failover by a service consumer. A signal can be afforded by a service provider based on analysis of an incident that affects the service provider. Initiation of self-serviced failover by a service consumer can be predicated on the signal. In one instance, the signal provides information that aids a decision of whether or not to failover. In another instance, the signal can grant or deny permission to perform a self-serviced failover.

Abstract: Service virtualization containers to aggregate service functionality from a plurality of services into an apparent service exhibiting the aggregated functionality. A plurality of service implementations is assigned to a service virtualization container. The container selects some of the service operations from the service implementations. One or more message characteristics are assigned to the service operations in one or more routing tables. A message is received at a service endpoint different from the service endpoints of any of the service implementations. A determination is made of one or more message characteristics. The one or more routing tables are consulted to select a determined service operation based on the message characteristics. The message is routed to the selected service implementation.

Abstract: A virtual environment can be configured to coordinate life cycles of virtual machines and application programs executing therein. In one implementation, the virtual environment includes an application layer and a virtual machine layer. The application layer communicates with the virtual machine layer to coordinate and directs virtual machine creation and deletion in a coordinated fashion with application programs. For example, the application layer receives a request to initiate an application program. The application layer determines from associated application properties the type and/or number of virtual machines to be created. The application layer then directs creation of the appropriate virtual machines (through the virtual machine layer), and further directs installation of the requested application programs therein.

Abstract: A template creator creates a template class that stores at least one template parameter. The template creator also specifies at least one additional object to be created when an instance of the template class is created. A template user initiates the creation of a new instance of the template class. If an error occurs during the creation of the new instance of the template class, the template user receives a report identifying the error.

Abstract: Service virtualization containers to aggregate service functionality from a plurality of services into an apparent service exhibiting the aggregated functionality. A plurality of service implementations is assigned to a service virtualization container. The container selects some of the service operations from the service implementations. One or more message characteristics are assigned to the service operations in one or more routing tables. A message is received at a service endpoint different from the service endpoints of any of the service implementations. A determination is made of one or more message characteristics. The one or more routing tables are consulted to select a determined service operation based on the message characteristics. The message is routed to the selected service implementation.

Abstract: A template creator creates a template class that stores at least one template parameter. The template creator also specifies at least one additional object to be created when an instance of the template class is created. A template user initiates the creation of a new instance of the template class. If an error occurs during the creation of the new instance of the template class, the template user receives a report identifying the error.

Abstract: A virtual environment can be configured to coordinate life cycles of virtual machines and application programs executing therein. In one implementation, the virtual environment includes an application layer and a virtual machine layer. The application layer communicates with the virtual machine layer to coordinate and directs virtual machine creation and deletion in a coordinated fashion with application programs. For example, the application layer receives a request to initiate an application program. The application layer determines from associated application properties the type and/or number of virtual machines to be created. The application layer then directs creation of the appropriate virtual machines (through the virtual machine layer), and further directs installation of the requested application programs therein.

Abstract: Subscription-based notification using event channels that each correspond to a particular scope. Each channel manages notifications through the use of a schema definition. The event subscriptions identify the position and attributes that any desired event notification would take in the schema definition. The channel then receives event notifications in the form of XML fragments. The channel then determines the position that the XML fragment would take as defined by the schema definition. The channel determines whether the position and attributes of the event notification matches the position and attributes of the event subscription. If a match is found, then the event notification is copied and forwarded to the recipient designated in the corresponding subscription.

Abstract: An event management system includes an email consumer for handling email, a paging consumer, an active scripting consumer, a log file consumer, an event log consumer, and a command line consumer. The events in the event management system are represented as objects and each consumer is represented as a class. The system also includes an event forwarding consumer to forward events. The event management system allows the creation of an instance of an event filter which filters events based on event filter properties. The system also allows the creation of an instance of an event consumer which defines an action and creation of a binding between the instance of the event filter and the instance of the event consumer such that the binding includes properties identifying the instance of the event filter and the instance of the event consumer.

Abstract: An event management system includes an email consumer for handling email, a paging consumer, an active scripting consumer, a log file consumer, an event log consumer, and a command line consumer. The events in the event management system are represented as objects and each consumer is represented as a class. The system also includes an event forwarding consumer to forward events. The event management system allows the creation of an instance of an event filter which filters events based on event filter properties. The system also allows the creation of an instance of an event consumer which defines an action and creation of a binding between the instance of the event filter and the instance of the event consumer such that the binding includes properties identifying the instance of the event filter and the instance of the event consumer.

Abstract: A correlation system receives multiple events and multiple data elements. The multiple events and data elements are applied to a correlation function which is implemented as a state machine. A specific event is generated if the correlation function is satisfied by the multiple events and the multiple data elements. Additional events and data elements are received if the correlation function is not satisfied by the original events and data elements. The system allows for the identification of a schema for creating state machines that correlate events and/or data. An instance of a particular state machine is created and transitions for the particular state machine are defined by subscribing to one or more events. An update consumer is applied to the particular state machine to update the state of the particular state machine.

Abstract: A template creator creates a template class that stores at least one template parameter. The template creator also specifies at least one additional object to be created when an instance of the template class is created. A template user initiates the creation of a new instance of the template class. If an error occurs during the creation of the new instance of the template class, the template user receives a report identifying the error.

Abstract: Subscription-based notification using event channels that each correspond to a particular scope. Each channel manages notifications through the use of a schema definition. The event subscriptions identify the position and attributes that any desired event notification would take in the schema definition. The channel then receives event notifications in the form of XML fragments. The channel then determines the position that the XML fragment would take as defined by the schema definition. The channel determines whether the position and attributes of the event notification matches the position and attributes of the event subscription. If a match is found, then the event notification is copied and forwarded to the recipient designated in the corresponding subscription.

Abstract: Subscription-based notification using event channels that each correspond to a particular scope. Each channel manages notifications through the use of a a schema definition. The event subscriptions identify the position and attributes that any desired event notification would take in the the schema definition. The channel then receives event notifications in the form of XML fragments. The channel then determines the position that the XML fragment would take as defined by the schema definition. The channel determines whether the position and attributes of the event notification matches the position and attributes of the event subscription. If a match is found, then the event notification is copied and forwarded to the recipient designated in the corresponding subscription.

Abstract: Subscription-based notification using event channels that each correspond to a particular scope. Each channel manages notifications through the use of a a schema definition. The event subscriptions identify the position and attributes that any desired event notification would take in the the schema definition. The channel then receives event notifications in the form of XML fragments. The channel then determines the position that the XML fragment would take as defined by the schema definition. The channel determines whether the position and attributes of the event notification matches the position and attributes of the event subscription. If a match is found, then the event notification is copied and forwarded to the recipient designated in the corresponding subscription.

Abstract: A template creator creates a template class that stores at least one template parameter. The template creator also specifies at least one additional object to be created when an instance of the template class is created. A template user initiates the creation of a new instance of the template class. If an error occurs during the creation of the new instance of the template class, the template user receives a report identifying the error.

Abstract: An event management system includes an email consumer for handling email, a paging consumer, an active scripting consumer, a log file consumer, an event log consumer, and a command line consumer. The events in the event management system are represented as objects and each consumer is represented as a class. The system also includes an event forwarding consumer to forward events. The event management system allows the creation of an instance of an event filter which filters events based on event filter properties. The system also allows the creation of an instance of an event consumer which defines an action and creation of a binding between the instance of the event filter and the instance of the event consumer such that the binding includes properties identifying the instance of the event filter and the instance of the event consumer.