1 / 6

SDD Implementation

SDD Implementation. Two sets of tools. Authoring tools SDD editor plug-in (not implemented) Build time generator Runtime tools Core runtime (analysis/resolution) Operator Registrar. Authoring tools Example RE Flow. DLL. SO. Build Systems. EXE. JAR. MSI. Packaging Systems. ZIP.

rue
Download Presentation

SDD Implementation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SDD Implementation

  2. Two sets of tools • Authoring tools • SDD editor plug-in (not implemented) • Build time generator • Runtime tools • Core runtime (analysis/resolution) • Operator • Registrar

  3. Authoring toolsExample RE Flow DLL SO Build Systems EXE JAR MSI Packaging Systems ZIP Install Developer RPM Build systems produce binary files from source. Install developers monitor build outputs, create installation code and push the installation code to packaging systems. Packaging systems create “artifacts” which can be used to perform installation.

  4. Authoring toolsInterface to BTG RDBMS SDD SPD Readers MSI ZIP RPM SDD Build Time Generator Data and/or artifacts Custom readers interrogate artifacts such as MSI or RPM files and normalizes that data as input to the BTG. The BTG then generates and aggregates SDDs based upon that data and the customizable “rules” within the BTG’s aggregator component.

  5. Runtime SDD SPD Artifact Runtime Bootstrap GUI CLI Profile Handlers Runtime inputs The bootstrap unpacks and initializes the runtime including the orchestrator and user interface. The model builder fires to un-marshall SDD and SPD to an internal object model. The change resolver then “walks” the model firing appropriate core or custom resolvers per resource types as defined in the profile. As operations come into scope the operator fires operations. Once operations are completed, the registrar registers the change in an SML MDR or other registry format. * This process is iterative and managed by the orchestrator. Orchestrator Model builder Change resolver Handler Handler Handler Operator Registrar Install Uninstall SML MDR Other

  6. Demos • Build time generator • Runtime w/ COSMOS example • Q & A

More Related