Abstract: Embodiments of apparatus, systems, and methods are described for creating and managing an abstract, API-based infrastructure base model. The API-based model can abstract infrastructure assets, such as infrastructure components or connections between components, into a metadata model using standardized syntax and interfaces, for defining and building an infrastructure. Using a modeling document, connections and components of an infrastructure can be abstracted into an API-based model having semantics that covers them all. Connections and infrastructure components can be made available for selection, arrangement, and grouping to build complex infrastructure models without requiring complex API coding by the user. Other infrastructure models having different API definitions can be by abstracted to standardize the assets for building new APIs. The APIs can be further modified and exported to another or the same implementation project.

Abstract: Embodiments of apparatus, systems, and methods are described for creating and managing an abstract, API-based infrastructure base model. The API-based model can abstract infrastructure assets, such as infrastructure components or connections between components, into a metadata model using standardized syntax and interfaces, for defining and building an infrastructure. Using a modeling document, connections and components of an infrastructure can be abstracted into an API-based model having semantics that covers them all. Connections and infrastructure components can be made available for selection, arrangement, and grouping to build complex infrastructure models without requiring complex API coding by the user. Other infrastructure models having different API definitions can be by abstracted to standardize the assets for building new APIs. The APIs can be further modified and exported to another or the same implementation project.

Abstract: Embodiments of apparatus, systems, and methods are described for creating and managing an abstract, API-based infrastructure base model. The API-based model can abstract infrastructure assets, such as infrastructure components or connections between components, into a metadata model using standardized syntax and interfaces, for defining and building an infrastructure. Using a modeling document, connections and components of an infrastructure can be abstracted into an API-based model having semantics that covers them all. Connections and infrastructure components can be made available for selection, arrangement, and grouping to build complex infrastructure models without requiring complex API coding by the user. Other infrastructure models having different API definitions can be by abstracted to standardize the assets for building new APIs. The APIs can be further modified and exported to another or the same implementation project.

Abstract: Disclosed herein are system, method, and computer program product embodiments for providing a distributed alert system using actor models. The approach includes initializing an alert actor configured to run an alert action. A datapoint related to the alert action is received, and can then be processed at the alert actor against a current status of an alert (such as a running average of prior datapoints) in order to determine a new status of the alert. This allows for a notification to be provided, such as to a system administrator, based on a change in status if needed.

Abstract: Disclosed herein are system, method, and computer program product embodiments for providing a distributed alert system using actor models. The approach includes initializing an alert actor configured to run an alert action. A datapoint related to the alert action is received, and can then be processed at the alert actor against a current status of an alert (such as a running average of prior datapoints) in order to determine a new status of the alert. This allows for a notification to be provided, such as to a system administrator, based on a change in status if needed.

Abstract: Embodiments of apparatus, systems, and methods are described for creating and managing an abstract, API-based infrastructure base model. The API-based model can abstract infrastructure assets, such as infrastructure components or connections between components, into a metadata model using standardized syntax and interfaces, for defining and building an infrastructure. Using a modeling document, connections and components of an infrastructure can be abstracted into an API-based model having semantics that covers them all. Connections and infrastructure components can be made available for selection, arrangement, and grouping to build complex infrastructure models without requiring complex API coding by the user. Other infrastructure models having different API definitions can be by abstracted to standardize the assets for building new APIs. The APIs can be further modified and exported to another or the same implementation project.

Abstract: A system and method of creating and managing one or more business objects is provided. The method can include receiving a request to create a business object and presenting a first user interface that is used to create a business object. The user interface can include one or more fields that define attributes and methods in the business object. The method can further include presenting a second user interface that is used to add documentation information for the business object, and storing the business object. The attributes and methods of the business object can be stored in separate files.

Abstract: A system and method for integrating components with processes in a business catalog. The method comprises constructing a composite model of available components on a computer. The composite model defines functional dependencies between the available components. The method further comprises generating, based on the composite model, a plurality of business objects for the available components and automatically generating a synthesized module for each business object. Each synthesized module includes mechanically generated names for services offered by its associated business object. The method also comprises populating a business catalog with the synthesized modules.

Abstract: A system and method of creating and managing one or more business objects is provided. The method can include receiving a request to create a business object and presenting a first user interface that is used to create a business object. The user interface can include one or more fields that define attributes and methods in the business object. The method can further include presenting a second user interface that is used to add documentation information for the business object, and storing the business object. The attributes and methods of the business object can be stored in separate files.