Browse Prior Art Database

Dynamic Generation Of Runtime Artifacts From Solution Metadata Based On Runtime Resource Managers

IP.com Disclosure Number: IPCOM000202382D
Publication Date: 2010-Dec-14
Document File: 4 page(s) / 48K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method to generate runtime artifacts based on target resource managers from the metadata that defines the solution. The runtime artifacts are created based on Solution Metadata.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 4

Dynamic Generation Of Runtime Artifacts From Solution Metadata Based On Runtime Resource Managers

Current components and process for generating runtime artifacts may include:
1.

                    (RSM) and its extensions that provide a model for a manufacturing enterprise and associated equipment.
2. Model file associated with the manufacturing platform. Business processes may be based on incoming events, the definition of event templates, and the mapping of incoming events to actions (business processes).

3. The Solution Studio,

A Reference Semantic Model

integrated information about an oil platform, associated equipment, events coming in from the equipment, and actions to be taken based on those events. It is also used to define and individually model Key Performance Indicators (KPI) for the platform and equipment.
4. Definitions of Process Templates, Events, KPIs and other assets in a Solution Studio model. Once these assets are created in the Solution Studio, they are tested in the build sandbox, and released in the Solution Life Cycle Management component.

5. Solution Bundle.

versioning are consolidated to create a Solution Bundle.
6. Solution Life Cycle Management Component (SLCM) provides a method to deploy the entire Solution Bundle created in the build environment onto a production environment and manage the life cycle of each of the components.

7. Integrated Information Framework (IIF) Components. Each component has an associated asset type defined in the SLCM. When an asset (e.g., Process Template) is created in the Solution Studio, tested, and ready to be versioned, the creator checks it in to the SLCM. The SLCM versions the asset and adds the asset information to the solution bundle metadata.

8. When all such assets have been created and versioned in the studio (build environment), complete solution metadata is ready to be deployed to the production environment.

9. When a solution bundle is approved for deploy to a production environment, the SLCM component provides the method to generate the runtime artifacts based on the runtime resource managers from this solution metadata. Thus, the configuration that was created and tested in the build environment can be replicated and deployed dynamically to any runtime environment.

Typically, code artifacts are deployed to runtime for execution. This usually happens through the deployment of the built code directly on the runtime environment.

The disclosed invention is a method to generate runtime artifacts based on target resource managers (e.g., Business Process Execution Language for Process Server, mediation for Enterprise Service Bus) from the metadata that defines the solution. The runtime artifacts are created based on Solution Metadata.

This invention is a method to...