Abstract: Embodiments of the present invention provide a flexible approach to construct/create instances of cloud computing environments. Specifically, under embodiments of the present invention, an image of a virtual machine instance is created from the following components: image bits; content such as the liner notes, manual, metadata, etc.; end user information (so that the image can be customized for one or more specific end users); values provided to an installer; and cloud based values (e.g., IP address, hostname, etc.). By constructing the virtual machine using this approach, dynamic aspects of the image are managed external to the static binary representation of the image. This would include artifacts such as documentation, install scripts, binary files, etc. Additionally, user supplied data can be captured dynamically and copied to customize the image at the time of instance creation. Still yet, embodiments of the present invention provides system level configuration to construct the virtual machine.

Abstract: The present invention can include a solution for capturing user-defined custom elements for use in a graphical modeling application. Such a system can include a graphical modeling application and a custom element definition tool. The graphical modeling application can be configured to create semantic models that contain a static graphical elements and semantic data elements. The custom element definition tool can be configured to create a user-defined custom element for the graphical modeling application. The user-defined custom element can consist of one or more static graphical element and/or one or more semantic data element.

Abstract: Embodiments of the present invention provide a method, system and computer program product for model driven deployment of component based applications. In an embodiment of the invention, a method for model driven deployment of component based applications can include selecting units representative of corresponding programmatic objects to be deployed into a target environment and specifying a deployment topology for the target environment. The method also can include matching portions of the units to different automation signatures and filtering the different automation signatures to a set of automation signatures based upon the deployment topology. The set of automation signatures can be ordered according to known dependencies of a corresponding deployment model and the ordered set of automation signatures can be bundled into an automation workflow and published to an automation engine for execution to deploy the programmatic objects into the target environment.

Abstract: A system for managing advisories for complex model nodes that can include a complex model, a graphical modeling application, and an advisory manager. The complex model can be configured to graphically represent a user-defined system as multiple nodes and relationships. The graphical modeling application can be configured to execute operations upon the complex model. The graphical modeling application can store data defining the graphical characteristics of the complex model as a notation model and data defining the semantic characteristics of the complex model as a semantic model. The notation model and the semantic model can be stored as separate data entities. The advisory manager can be configured to aggregate notifications and potential resolutions for the nodes of the complex model. The notifications and potential resolutions can be visually presented within the graphical modeling application.

Abstract: A widget adjustment event can be detected for a widget that is part of a model that is presented on a canvas of a user interface. On-canvas objects proximate to the widget can be adjusted. The on-canvas objects can include other widgets. The adjustments can be performed relative to a layout position of the widget after the widget adjustment event has occurred. Additional on-canvas objects further from the widget can the adjusted on-canvas objects can then be adjusted as necessary due to new positions of the adjusted on-canvas objects.

Abstract: A method for deploying a software product comprising a plurality of components is provided. The method can include reading a topological description of the software product and its components, wherein the topological description defines characteristics and dependencies of the components. The method can further include reading characteristics of a plurality of publishers and matching each of the plurality of components to one of the plurality of publishers according to the characteristics and dependencies of the components and the characteristics of the plurality of publishers. A publisher may be a computer connected to a network. The method can further include distributing the plurality of components among the plurality of publishers responsive to the step of matching and validating each set of components distributed to each publisher.

Abstract: A deployment modeling platform enables a user to model application characteristics of target software and to associate application modeling parameters to the modeled application characteristics. A user may also model environment characteristics of a target deployment environment and to associate environment modeling parameters to the modeled deployment environment characteristics. Still further, a user may create a deployment model that associates and maps selected parameters of the modeled application characteristics of the target software to associated parameters of the modeled environment characteristics of the deployment environment, and to verify that each parameter that relates to a requirement is mapped to and is fulfilled by an associated parameter that relates to a corresponding capability to determine whether validation problems exist in order to deploy the target software in the associated deployment environment.

Abstract: The present invention can include a solution for capturing user-defined custom elements for use in a graphical modeling application. Such a system can include a graphical modeling application and a custom element definition tool. The graphical modeling application can be configured to create semantic models that contain a static graphical elements and semantic data elements. The custom element definition tool can be configured to create a user-defined custom element for the graphical modeling application. The user-defined custom element can consist of one or more static graphical element and/or one or more semantic data element.

Abstract: The present invention can include a solution for handling abstract entities through the realization of conceptual objects within a modeling application. Such a system can include a semantic model and a modeling application. The semantic model can be configured to present relationships between entities. The entities can include both conceptual objects and concrete objects. A conceptual object can represent an abstract definition that can contain unfulfilled functional parameters. The conceptual object can be associated with another conceptual object or concrete object using a realization relationship. The modeling application can be configured to handle conceptual objects and realization relationships, while preserving the relational integrity of the semantic model.

Abstract: A model simplification tool can receive a command to simplify the presentation of a visually complex semantic model from a graphical modeling application. The visually complex semantic model can be comprised of a multitude of object representations and their associations, such that the usability of the model is impaired. An association status can be determined for each object representation, which can designate the object representation as autonomous, containment, or subordinate. The presentation of the visually complex semantic model can be consolidated based on the association status of object representations. Subordinate objects can be nested within containment objects to produce a simplified semantic model. The simplified semantic model can be rendered within the graphical modeling application.

Abstract: Mapping information that describes the mapping of referenced projects to their container project is included in the container project, using a “module mapping” file. A module mapping file is a simple meta-data file, for use at development time only, which stores data that maps relative URIs to IDE project names. The module mapping file contains entries for the location of nested archives, relative to the virtual archive defined by the container project, mapped to the uniquely named referenced project within the IDE. The paths of the archive files are computed “on the fly” just before the application server is started, rather than being simply written into an extensions file, located within the container project, in a fixed form when the enterprise application is written/developed.

Abstract: Application configurations, including applications themselves, application components, and modules associated with the application are installed on an application-server machine and stored in system-determined locations. These locations, or absolute paths, are then stored in a “loose configuration”. As new versions of applications, components, and/or modules are installed, they are placed in unique locations and given unique version numbers. A record of each application configuration version is stored and is referred to as “snapshots”. These snapshots provide a record of and pointers to the various elements that make up the various application configuration versions, so that at any time, a current version of an application configuration can be “rolled back” to a previous version of an application configuration. The methodology can be utilized to provide a self-healing configuration, whereby a faulty version of an application configuration can be rolled back to a previous version automatically.

Abstract: Methods, systems, and computer program products for programmatically enforcing referential integrity constraints defined for classes of an arbitrary modeling framework (such as the Meta Object Facility, or “MOF”) when associations among class instances are modified. The present invention relieves the application programmer of the burden of writing code to maintain the links between instances, and applications are therefore considerably easier to write and to maintain, and programmatically maintains inverse links. This reduces the amount of data to be serialized, as the other link can be automatically resolved at the time the inverse link is reconstituted, and also helps in maintaining referential integrity among serialized instances (e.g. where associations are specified in one or more XML Metadata Interchange, or “XML”, documents) because redundant information about the values of the same association will not have to be written across different documents or storage repositories.

Abstract: Application configurations, including applications themselves, application components, and modules associated with the application are installed on an application-server machine and stored in system-determined locations. These locations, or absolute paths, are then stored in a “loose configuration”. As new versions of applications, components, and/or modules are installed, they are placed in unique locations and given unique version numbers. A record of each application configuration version are stored and are referred to as “snapshots”. These snapshots provide a record of and pointers to the various elements that make up the various application configuration versions, so that at any time, a current version of an application configuration can be “rolled back” to a previous version of an application configuration.

Abstract: Mapping information that describes the mapping of referenced projects to their container project is included in the container project, using a “module mapping” file. A module mapping file is a simple meta-data file, for use at development time only, which stores data that maps relative URIs to IDE project names. The module mapping file contains entries for the location of nested archives, relative to the virtual archive defined by the container project, mapped to the uniquely named referenced project within the IDE. The paths of the archive files are computed “on the fly” just before the application server is started, rather than being simply written into an extensions file, located within the container project, in a fixed form when the enterprise application is written/developed.

Abstract: Methods, systems, and computer program products for programmatically enforcing referential integrity constraints defined for classes of an arbitrary modeling framework (such as the Meta Object Facility, or “MOF”) when associations among class instances are modified. The present invention relieves the application programmer of the burden of writing code to maintain the links between instances, and applications are therefore considerably easier to write and to maintain, and programmatically maintains inverse links. This reduces the amount of data to be serialized, as the other link can be automatically resolved at the time the inverse link is reconstituted, and also helps in maintaining referential integrity among serialized instances (e.g. where associations are specified in one or more XML Metadata Interchange, or “XML”, documents) because redundant information about the values of the same association will not have to be written across different documents or storage repositories.