Abstract: A data model representing a multi-model database of a product system includes a multi-model repository that holds said multi-model database's artifacts under version control. The multi-model repository holds a plurality of constituent models, wherein each model represents a discrete aspect of the system, a model registry containing a list of the constituent models in the multi-model database, a set of input attributes and a set of output attributes corresponding to each of the models, a set of interfaces representing a tuple corresponding to each of the models, a set of attribute constraints associated with the input and output attributes; and a set of notifications associated with each of the models for informing the models of defined events.

Abstract: A computer database system for multi-model integration includes remote client-side components and a multi-model database having a plurality of artifacts that define the multi-model database and a multi-model repository that holds the artifacts under version control. The remore client-side components include a multi-model manager, one or more connectors, execution automation engine, a sandbox, and a version control system client.

Abstract: An apparatus in one example comprises: a first manager component responsible for one or more first software components within one or more first executables of a distributed software application; and a second manager component responsible for one or more second software components within one or more second executables of the distributed software application. The first and second manager components communicate to initialize and/or shut down the one or more first software components and the one or more second software components in an ordered sequence based on one or more dependency relationships among two or more of: the one or more first software components; and/or the one or more second software components.

Abstract: A manager component of an apparatus in one example handles one or more checkpoint procedures for one or more software components of a distributed software application that runs within a plurality of executables.

Abstract: A distributed software application comprises a first and second software component. A manager component of a management infrastructure for the distributed software application in one example causes a first software component of the distributed software application to obtain information from a second software component of the distributed software application for initialization of the first software component.

Abstract: An apparatus in one example comprises a manager component that upon receipt of an indication of a need for a communication channel between a first software component and a second software component, instructs management support software of the first software component to set up the communication channel between the first software component and the second software component.

Abstract: An apparatus in one example comprises a manager component for a distributed software application that based on one or more of a characteristic of an executable of the distributed software application and/or a characteristic of one or more of a plurality of processors, selects a processor from the plurality of processors to run the executable upon startup of the distributed software application.

Abstract: A manager component of an apparatus in one example initializes a plurality of software components of a distributed software application, within one or more executables, in an ordered sequence based on one or more dependency relationships among the plurality of software components.

Abstract: An apparatus in one example comprises a manager component in communication with a distributed software application. The distributed software application comprises a plurality of software components that run within one or more executables. The manager component shuts down the plurality of software components in an ordered sequence based on one or more dependency relationships among the plurality of software components.

Abstract: An apparatus in one example comprises a substitute manager component that upon failure of a first manager component, obtains management responsibility for a distributed software application from the first manager component and queries one or more software components of the distributed software application for state information of the one or more software components. The substitute manager component employs the state information to determine whether one or more recovery actions are needed for the distributed software application to recover from the failure of the first manager component.

Abstract: A distributed software application comprises a plurality of software components within a plurality of executables. A manager component for the distributed software application performs a recovery of two or more software components, of the plurality of software components, in an ordered sequence based on one or more dependency relationships among the plurality of software components.