Abstract: A visual editor creates the meta rules for transforming mapping data between the source meta data and target meta data representation via a wide variety of Graphical User Interface (GUI). A set of transformation rules or scripts is generated by the editor using a transformation rule engine, e.g. XSL and sent to a standard transformation engine, e.g. XSLT which accepts an input data file and using the transformation rules generates a transformed output data file The meta rules are represented in a template and stored in a configuration file. The configuration file can be updated with other rules by the visual editor specifying in the rule file the transformation/mapping language as an element of the rule file. The editor specifies any attributes or parameters on the rule transformation/mapping element. The transformation rule engine reads in a new meta rule generated by the editor. Parameter values are added to complete the rule based on the description from a meta rule configuration file.

Abstract: Techniques disclosed herein describe a client and/or server process for managing Information Technology (IT) assets, such as servers and storage devices. The process dynamically generates customized information objects based on subscription requests. A client generates a request for information. The request specifies information associated with a specific managed entity or IT resource. A server that monitors the specific managed entity does not maintain such information in an existing information object. Information associated with the specific managed entity can be performance information, health information, usage information, and the like. A notification manager receives the request and identifies that existing subscription resources don not contain the requested information. The notification manager generates a new information object that contains the requested information, and notifies the client.

Abstract: A processing device comprises a processor coupled to a memory and implements an obligation management system for information technology infrastructure, with the obligation management system being configured to process a plurality of obligations on behalf of a relying party to verify implementation of corresponding controls in information technology infrastructure of a claimant. A given one of the obligations has an associated obligation fulfiller that is inserted or otherwise deployed as a component within the information technology infrastructure of the claimant and is configured to provide evidence of the implementation of one or more of the controls responsive to an obligation assertion so as to establish an associated trust aspect of the claimant. The information technology infrastructure may comprise distributed virtual infrastructure of a cloud service provider. The claimant may comprise the cloud service provider and the relying party may comprise a tenant of the cloud service provider.

Abstract: A visual editor creates the meta rules for transforming mapping data between the source meta data and target meta data representation via a wide variety of Graphical User Interface (GUI). A set of transformation rules or scripts is generated by the editor using a transformation rule engine, e.g. XSL and sent to a standard transformation engine, e.g. XSLT which accepts an input data file and using the transformation rules generates a transformed output data file The meta rules are represented in a template and stored in a configuration file. The configuration file can be updated with other rules by the visual editor specifying in the rule file the transformation/mapping language as an element of the rule file. The editor specifies any attributes or parameters on the rule transformation/mapping element. The transformation rule engine reads in a new meta rule generated by the editor. Parameter values are added to complete the rule based on the description from a meta rule configuration file.

Abstract: A visual editor creates the meta rules for transforming or mapping data between the source meta data and target meta data representation via a wide variety of Graphical User Interfaces (GUIs). A set of transformation rules or scripts is generated by the editor using a transformation rule engine, e.g., XSL, and sent to a standard transformation engine, e.g., XSLT, which accepts an input data file and using the transformation rules generates a transformed output data file. The meta rules are represented in a template and stored in a configuration file. The configuration file can be updated with other rules by the visual editor specifying in the rule file the transformation/mapping language as an element of the rule file. The editor specifies any attributes or parameters on the rule transformation/mapping element. The transformation rule engine reads in a new meta rule generated by the editor. Parameter values are added to complete the rule based on the description from a meta rule configuration file.

Abstract: Information technology infrastructure comprises a computing environment shared by multiple tenants of a service provider, and a secure assessment environment separate from the shared computing environment. An evidence collection module associated with the shared computing environment collects compliance evidence from the shared computing environment for storage in the secure assessment environment. A tenant assessment interface to the secure assessment environment is provided, through which the tenants can access the compliance evidence as stored in the secure assessment environment in a manner that does not undermine security of the shared computing environment. The compliance evidence may include, for example, information sufficient to allow a tenant to verify that the shared computing environment is configured in accordance with a specified security policy.

Abstract: An activity stream based alert processor is configured to receive product-specific alerts from respective products implemented in information technology infrastructure, and to process the product-specific alerts to generate one or more activity streams using a specified activity stream format suitable for delivery to one or more remediation elements. For example, the activity streams may be generated in a standardized activity stream format suitable for delivery to one or more social networking applications to facilitate collaborative remediation of the product-specific alerts by multiple administrative entities, such as network, storage and server administrators. The alerts in an illustrative embodiment may comprise system management alerts generated by respective software products or other products in cloud infrastructure of a cloud service provider.

Abstract: A system, method, and apparatus for representing an information topology on a computer, wherein the represented information topology comprises a plurality of information nodes and a plurality of states, representing a set of polices on the computer, wherein each policy expresses one or more requirements applied to the plurality of information nodes, and assessing compliance of the represented information topology by determining on the computer whether the plurality of states meet the requirements expressed in the plurality of policies.

Abstract: A method and system for managing service state data of a service in a service-oriented architecture by establishing a pluggable meta-data processor comprising: establishing a platform independent, extensible meta-data information model to define meta-data about service state data; establishing an extensible meta-data definition comprising an extensible set of service state data attributes; configuring one or more extensible semantic processors; configuring a controller meta-data processor; and defining contracts among the semantic processors.

Abstract: A method for dynamically associating type information about extensible messages in a service-oriented architecture includes configuring a simple object access protocol (SOAP) message header to include message meta-data and semantics, thereby facilitating a dynamic exchange of semantic type information for open content message exchange between a sender and a receiver.

Abstract: A method and system for managing state data of a service in a service-oriented architecture by establishing a gateway for service-oriented state comprising: configuring an extensible, pluggable interface to support for extensible processor interfaces; data query support on service state data, automated notification capability on service state to a client; and automated data transform on service state data to a client format; defining an interface framework for interaction between a service and the gateway. The method also includes establishing an extensible meta-data definition comprising an extensible set of service state data attributes including state data qualifiers, constraints, and access mechanisms; and utilizing one or more pluggable processors configured to utilize the extensible meta-data definition for interfaces and decision making based on the meta-data.

Abstract: A method and apparatus for generating service state data and extensible meta-data information with a service oriented state data generator (SSDG) comprising: establishing a platform independent, extensible meta-data model for the meta-data information; obtaining state data schema based on a service state data description; defining an extensible set of meta-data attributes and templates corresponding to the meta data based on requirements of a service; and utilizing the meta-data model and based on the state data schema and the attributes, generating service state data based on the service state data schema; and The service state data including at least one of: state data, state data logical mapping, state data physical mapping, meta-data associated with the service state data and meta-data model correlations associated with the meta-data.