JTLSGO Data Repository Concept Jane Wu Ellen Roland














- Slides: 14
JTLS-GO Data Repository Concept Jane Wu & Ellen Roland ROLANDS & ASSOCIATES Corporation
Why Data Repository Traditional Standard Databases Demonstration Represents Needs Baseline Real World Scenarios To Be Concise Database Starting Needs Database Point To Build User Databases To Be Robust ROLANDS & ASSOCIATES Corporation Sept 2017 2
Why Data Repository Upgrade Old Version Database To Current Release Upgrade New Data Given Default Values To Mimic Old Functionality Re-use Use Procedure Upgrades Format Only Previously Developed Scenarios Portions Of Existing Scenarios Same Own-Side Force / New OPFOR Force Multi-Regions Merge Conflict Modeling Single Region Scenarios Into One Database ROLANDS & ASSOCIATES Corporation Sept 2017 3
Data Repository System (DRS) An Enhancement To DDS Migrate Data from Source to Destination Database Examples Of Use Scenario Repository Source: Scenario STARTEX Database Destination: Upgrade Scenario Repository Data In Existing Scenario Source: JTLS Data Repository Destination: Your Scenario Database ROLANDS & ASSOCIATES Corporation Sept 2017 4
Data Repository System (DRS) An Enhancement To DDS Examples New Of Use (Con’t) Scenario Source: Scenario Repository Destination: Pick Scenario Database What Is Needed Use OPFOR From Scenario 1, Use Portion of Own Forces From Scenario 2, Use Portion of Own Forces From Scenario 3. ROLANDS & ASSOCIATES Corporation Sept 2017 5
Data Repository System (DRS) DRS Consists Of Three Parts Tool That Configures DDS For Data Migration Option Tool Added To DCP That Migrates The Data Expanded New The Glassfish Server For Source Database Data Migration Tool For Source DDS-Client Repository Database ROLANDS & ASSOCIATES Corporation Sept 2017 6
Data Repository System (DRS) Configuring New DDS For Data Migration DDS Configuration Program (DCP) Capability Setup In Source Database Specify Tools Allowable Destination Domains (Scenarios) Menu -> Set Destination Domains Specify Specific Allowed Destination Scenarios (Need Similar Parametric Data) Prepares Specify Source Glassfish Server Which DDS Clients (DDSC) Migration Roles Which DDSC Can Use Migration Tool ROLANDS & ASSOCIATES Corporation Sept 2017 7
Data Repository System (DRS) Using DDSC To Migrate Data From DDSC Specified Migration Capable Bring Up Migration Tools Menu ->Migrate ORBAT ROLANDS & ASSOCIATES Corporation Sept 2017 8
Data Repository System (DRS) Using DDSC To Migrate Data (Con’t) Migrate Following Migration Rules Assumed Unit If A’s Initial Support Unit Not In Destination Reference Does Not Exist In Destination Set To NULL Initial If Copy Unit A From Source To Destination Support Unit Set To NULL Reference Does Not Exist In Destination Skip Insert Unit A Not Copied ROLANDS & ASSOCIATES Corporation Sept 2017 9
Data Repository System (DRS) Using DDSC To Migrate Data (Con’t) Currently: There Approximately 15 Different Rule Types Rules Established By JTLS-GO DDS Design Team Can Be Changed Manually – But Not Well Documented Eventually – Full Interface To Establish Rules ROLANDS & ASSOCIATES Corporation Sept 2017 10
Current And Future Improvements Post-Batch Processing Example: After Go All Units Moved Back And “Repair” Fields Set To NULL For Any Example: Try And Reset “Initial Support Unit” Table Migration Currently Allow Start From ORBAT Only Migration From Any Table ROLANDS & ASSOCIATES Corporation Sept 2017 11
Current And Future Improvements Synchronize Go To A Table – Synchronize Highlights Use More Data Differences Can Decide To Change or Not Change User Friendly Result Listing Migration Rule Editing Capability ROLANDS & ASSOCIATES Corporation Sept 2017 12
Conclusions There The Is Still Massive Amounts Of Work Glassfish Infra-Structure Well Defined Flexible From Here It Is Simply: “DO IT” ROLANDS & ASSOCIATES Corporation Sept 2017 13
Questions ROLANDS & ASSOCIATES Corporation Sept 2017 14