JTLS-GO Data Repository Concept Jane Wu & Ellen Roland ROLANDS & ASSOCIATES Corporation

Why Data Repository Traditional Standard Databases Demonstration Database Represents Real World Scenarios Needs To Be Concise Baseline Database Starting Point To Build User Databases Needs To Be Robust ROLANDS & ASSOCIATES Corporation Sept 2017

Why Data Repository Upgrade Old Version Database To Current Release Upgrade Procedure Upgrades Format Only New Data Given Default Values To Mimic Old Functionality Re-use Previously Developed Scenarios Use Portions Of Existing Scenarios Same Own-Side Force / New OPFOR Force Multi-Regions Conflict Modeling Merge Single Region Scenarios Into One Database ROLANDS & ASSOCIATES Corporation Sept 2017

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: Scenario Repository Upgrade Data In Existing Scenario Source: JTLS Data Repository Destination: Your Scenario Database ROLANDS & ASSOCIATES Corporation Sept 2017

Data Repository System (DRS) An Enhancement To DDS Examples Of Use (Con’t) New Scenario Source: Scenario Repository Destination: Scenario Database Pick 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

Data Repository System (DRS) DRS Consists Of Three Parts Tool That Configures DDS For Data Migration Option Added To DCP Tool That Migrates The Data Expanded Glassfish Server For Source Database New Data Migration Tool For Source DDS-Client The Repository Database ROLANDS & ASSOCIATES Corporation Sept 2017

Data Repository System (DRS) Configuring DDS For Data Migration New DDS Configuration Program (DCP) Capability Setup In Source Database Specify Allowable Destination Domains (Scenarios) Tools Menu -> Set Destination Domains Specify Specific Allowed Destination Scenarios (Need Similar Parametric Data) Prepares Source Glassfish Server Specify Which DDS Clients (DDSC) Migration Roles Which DDSC Can Use Migration Tool ROLANDS & ASSOCIATES Corporation Sept 2017

Data Repository System (DRS) Using DDSC To Migrate Data From DDSC Specified Migration Capable Bring Up Migration Tool Tools Menu ->Migrate ORBAT ROLANDS & ASSOCIATES Corporation Sept 2017

Data Repository System (DRS) Using DDSC To Migrate Data (Con’t) Migrate Following Migration Rules Assumed Copy Unit A From Source To Destination Unit A’s Initial Support Unit Not In Destination If Reference Does Not Exist In Destination Set To NULL Initial Support Unit Set To NULL If Reference Does Not Exist In Destination Skip Insert Unit A Not Copied ROLANDS & ASSOCIATES Corporation Sept 2017

Data Repository System (DRS) Using DDSC To Migrate Data (Con’t) Currently: There Are 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

Current And Future Improvements Post-Batch Processing Example: After All Units Moved Go Back And “Repair” Fields Set To NULL For Example: Try And Reset “Initial Support Unit” Any Table Migration Currently Start From ORBAT Only Allow Migration From Any Table ROLANDS & ASSOCIATES Corporation Sept 2017

Current And Future Improvements Synchronize Data Go To A Table – Synchronize Highlights Differences Use Can Decide To Change or Not Change More User Friendly Result Listing Migration Rule Editing Capability ROLANDS & ASSOCIATES Corporation Sept 2017

Conclusions There Is Still Massive Amounts Of Work The Glassfish Infra-Structure Well Defined Flexible From Here It Is Simply: “DO IT” ROLANDS & ASSOCIATES Corporation Sept 2017

Questions ROLANDS & ASSOCIATES Corporation Sept 2017