Roundtable TSMS Roundtable and Dynamics Thomas Hansen Managing

What is Roundtable TSMS ? • TSMS : Total Software Management System • SCM : Software Configuration Management – More than version control (check-in / check-out) – Complete management of the different work environments • Written in PROGRESS 4 GL – Specifically suited for Progress based development – Maximum benifit with Progress environments • Developed by Star. Base Corporation, USA • Sold and supported by Progress Software Corporation and selected Starpartners © 2002, MIP Europe A/S 2

OBJECTS Roundtable Objects PCODE - Menu. w © 2002, MIP Europe A/S • OBJECTS Basic Configuration Item (building blocks) that make up an application Configuration • 5 Kinds of object – PCODE Physical Files managed – PDBASE Logical Database Objects – PFILE Logical Database Table Objects – PFIELD Logical Database Field Objects – DOC (not often used) 3

OBJECTS PCODE Objects • Code Sub-types – Classification of PCODE objects – Examples : program include window Smart. Window Smart. Browser – Primarily defined by object file extension – Contains object attributes e. g. : PCODE - Menu. w SUB-TYPE - Window • • Compilable with Progress compiler Runable Encryptable Deployable – Each logical object can consist of up to 9 physical parts (individual files) © 2002, MIP Europe A/S 4

Workspace OBJECTS WORKSPACE Devel Workspace Root Path // • Stand alone complete application area (isolated environment) • Contains full set of source code, schema, scripts etc. • Each workspace has a root path • Contains Products and Product Modules for configuration control • Contains a configuration of an application • Each workspace represents a stage in the QA flow of environments e. g. Development, testing, deployment APP. DB PDBASE - App PFILE - Customer PFIELD - Cust-num PCODE - Menu. w SUB-TYPE - Window © 2002, MIP Europe A/S 5

OBJECTS Products & Product Modules • Products - header for logical application model • Product Modules : WORKSPACE – Logical grouping of objects Devel P MODULE Often along functional Base. AP baselines P MODULE Cust 1 OE – Used for configuration Base. Dict P MODULE control Cust 1 AP – Key component of the Workspace primary index used to Path PDBASE - App store unique objects in the PFILE - Customer APP. DB PFIELD - Cust-num repository PCODE - Menu. w SUB-TYPE - Window © 2002, MIP Europe A/S 6

Workspace Modules WORKSPACE Devel P MODULE Base. AP P MODULE Cust 1 OE OBJECTS P MODULE Base. Dict P MODULE Cust 1 AP Workspace Path APP. DB • Physical grouping of objects • 1 workspace module for each sub-directory • Assigned to one or more product modules • Link between the logical application model (products & pmods) and the physical application structure PDBASE - App PFILE - Customer PFIELD - Cust-num W/S MODULE - AP PCODE - Menu. w SUB-TYPE - Window © 2002, MIP Europe A/S 7

Task WORKSPACE Devel P MODULE Base. AP P MODULE Cust 1 OE OBJECTS P MODULE Base. Dict P MODULE Cust 1 AP Workspace Path APP. DB 1. Add 2. Delete 3. Assign 4. Assign 5. Add • Task is the unit of work definition • Task is required to create a new object or version an existing object • Used to group object changes together • Task completion (check-in) or single object check-in creates workspace events PDBASE - App PFILE - Customer PFIELD - Cust-num W/S MODULE - AP PCODE - Menu. w SUB-TYPE - Window © 2002, MIP Europe A/S 8

Release WORKSPACE Devel P MODULE Base. AP P MODULE Cust 1 OE OBJECTS P MODULE Base. Dict P MODULE Cust 1 AP Workspace Path APP. DB 1. Add 2. Delete 3. Assign 4. Assign 5. Add • Certification of the workspace • Capture the current workspace event number as it is available to other workspaces or remote sites • Allows work to quickly continue once the release has been created - Release PDBASE - App PFILE - Customer PFIELD - Cust-num W/S MODULE - AP PCODE - Menu. w SUB-TYPE - Window © 2002, MIP Europe A/S 9

Import Control • The process of replicating objects from one workspace to another based on a release or one or more tasks WORKSPACE Devel P MODULE Base. AP OBJECTS P MODULE Cust 1 OE P MODULE Base. Dict P MODULE Cust 1 AP Workspace W/S MODULE Path - AP APP. DB IMPORT 1. Add 2. Delete 3. Assign 4. Assign 5. Add W/S SOURCE Test - Release PDBASE - App PFILE - Customer PFIELD - Cust-num PCODE - Menu. w SUB-TYPE - Window © 2002, MIP Europe A/S 10

Deployment WORKSPACE Devel P MODULE Base. AP P MODULE Cust 1 OE OBJECTS P MODULE Base. Dict P MODULE Cust 1 AP Workspace Path APP. DB W/S MODULE - AP PCODE - Menu. w SUB-TYPE - Window © 2002, MIP Europe A/S IMPORT 1. Add 2. Delete 3. Assign 4. Assign 5. Add W/S SOURCE Test DEPLOYMENT 1. Add 2. Delete 3. Assign 4. Assign 5. Add - Release SITE Cust 2 - Release • Process of copying objects for installation outside of Roundtable PDBASE - App PFILE - Customer • Made at release levels PFIELD - Cust-num • Different deployment types : – First deployment is always FULL – Others always INCREMENTAL 11

Roundtable Repository REPOSITORY WORKSPACE Devel P MODULE Base. AP P MODULE Cust 1 OE OBJECTS P MODULE Base. Dict P MODULE Cust 1 AP Workspace Path APP. DB W/S MODULE - AP PCODE - Menu. w SUB-TYPE - Window © 2002, MIP Europe A/S IMPORT 1. Add 2. Delete 3. Assign 4. Assign 5. Add W/S SOURCE Test DEPLOYMENT 1. Add 2. Delete 3. Assign 4. Assign 5. Add - Release PDBASE - App PFILE - Customer PFIELD - Cust-num SITE Cust 2 - Release • Progress database that stores the following information – Source code for all PCODE objects 12

Roundtable Repository. . . Test Base. AP P MODULE Cust 1 OE OBJECTS P MODULE Base. Dict P MODULE Cust 1 AP Workspace Path APP. DB W/S MODULE - AP PCODE - Menu. w SUB-TYPE - Window © 2002, MIP Europe A/S IMPORT 1. Add 2. Delete 3. Assign 4. Assign 5. Add W/S SOURCE WORKSPACE Devel P MODULE REPOSITORY DEPLOYMENT 1. Add 2. Delete 3. Assign 4. Assign 5. Add - Release PDBASE - App PFILE - Customer PFIELD - Cust-num SITE Cust 2 - Release – All schema objects – Configuration information for all workspaces – Release information – Deployment information – Xref information per workspace!!!! 13

Roundtable and Dynamics™ • Partner Deployment Package with Dynamics™ delivered by Progress Software – Preconfigured RTB environment as starting point for new Dynamics™ applications • FCS Commercial version of Dynamics & Service Packs • Contains : – Dynamics Core application (src/icf), ADM 2, Some of ADE • Not in synch with POSSE Dynamics • rtb_010300_020000. zip (upgrade from 1. 1 ASp 3 to 2. 0 A) • rtb_020000. zip (full 2. 0 A) • Integration with RTB is an implementation of the generic SCM support in Dynamics™ • NB: Requires understanding of Roundtable Use and Configuration © 2002, MIP Europe A/S 14

Links between RTB & Dynamics • Product Modules – RTB Product Modules prefixed with site number e. g. 019 s 2 k-obj – Dynamics Product Modules without site prefix e. g. s 2 k-obj – Base product module names must match • Object Classification : – RTB Code Subtypes = Dynamics Object Types • e. g. SDO, Smart. Window, Static. SDV – For customized Object Types : • <site number>_Object Type_xxxx = RTB Code Subtype © 2002, MIP Europe A/S 15

Links between RTB & Dynamics. . . • Automated version control (check-out) from Dynamics – Handled by triggers – Using RTB API and normal checks for concurrent checkouts etc. • Version control of Data using XML – Automated creation and update of. ado (XML) files for Dynamic Objects – Enables version control and Configuration Management of any data as XML – XML integration allows for Export / Import between RTB and Dynamics repositories • Useful for loading existing applications – Deployment of Data (Data. Sets) handled as part of Configuration Management © 2002, MIP Europe A/S 16

Links between RTB & Dynamics. . . • Integration with DCU – Schema updates and data processing can be handled by DCU on Workspace Updates • Version control of ERWin diagrams and Forward Engineered schema files © 2002, MIP Europe A/S 17

Customizations • Extension of Event Handler in RTB – examples : – Date & Time Stamping of objects on check-out / check-in – Extension of deployment to support Deployment Partitioning for Web. Client installations – Extend support for App. Server compilations –. . . © 2002, MIP Europe A/S 18