Release 2.0

General

• migFx is upgraded to Net 7.0
  
  
• Studio and Portal are redesigned to align with the new Hopp visual identity
  

Studio

• A number of changes to improve user experience
  
  
• Event Severity has been refactored into 2 separate notions: Impact (Critical, Advisory, Information) and Disposition (Full discard, Partial discard, Retain). The current severity is mapped like so (a refactor utility is provided for existing Source- and Target Maps, see below):
  
  

Visual Studio extension

• The extension is now communicating with the Portal for both authorization and for debug and deploy of migration engines

Portal

• A number of changes to improve user experience
  
  
• Addition of Api endpoints required by the Visual Studio extension for deploy and debug of migration engines
  
  
• ItemMgr
  • new option added to ItemType called "Default Owner" to allow automatically setting the current user as the Owner of a new Item

DataServices

• Metadata Providers and Valueset Providers now expose a timeout parameter for the execution of the sql statement related to the metadata/valueset
  

Director Client decommissioned

• Director Windows client application is fully replaced by Operations inside the Portal application

Installation and Refactoring 

Artifacts can be downloaded from the download page here: Version 2.0

• Database
  • Please back up all databases before running refactor scripts
  • Run attached MigrationDb.11.0.sql script in all Migration databases
  • Run attached ProjectDb.05.0.sql script in all Project databases
  • Run attached UtilityDB.1.0.sql script in Utility databases
    • NOTE: only if all Migration and Project database were updated with above scripts. This utility DB script is removing some functions that are needed in previous DB versions.
  • Run attached MigFx.PortalDb.Setup.sql in the Portal database
  • Run attached MasterDb.04.sql in the Master database
  • If ItemMgr is installed: Run attached MigFx.ItemMgrDb.Setup.sql script in the ItemMgr database
  • If Dashboards is installed: Run attached MigFx.DashboardsDb.Setup.sql script in the Dashboards database
    
    
• Studio Source- and Target Maps
  • A value must be provided for the new Timeout parameters for Metadata and Valueset Providers in any DataService
     
  • A refactor utility is provided to refactor Studio Source- and Target Maps in order to separate the current Severity into a combination of Disposition and Impact. Please run this command after reinstall of Studio:  
    
    (Studio Install Path)\MigFx.Studio.Refactor SplitSeverity --DataSource (sql server instance) --InitialCatalog (repository database) --WorkingFolder (temporary working folder) --Commit --CommitMessage "Split Severity into Disposition/Impact"  
    
    
  • Current Severity values will be refactored in accordance to the table above
    
    
• Net 7.0
  • All Net 6.0 applications are upgraded to Net 7.0
  • Ensure the Net SDK 7.0 is installed on all servers
  • Reinstall Director Agent on all Execution Servers
    • NOTE: Please preserve the MigFx.Agent.dll.config file before uninstall and restore after install
  • Any extensions developed in-house should be upgraded to Net 7.0 (Portal extensions, Data Services extensions, etc.) 
    • The following NuGet Packages should be upgraded, if referenced:
      • AutoMapper: Version=12.0.1 
      • AutoMapper.Collection: Version=9.0.0

      • Microsoft.EntityFrameworkCore: Version=7.0.10

• Visual Studio Engine Projects
  • Upgrade to Net 7.0
  • Ensure that NuGet Package Reference versions are correct
    • Microsoft.EntityFrameworkCore.SqlServer: Version=7.0.10
    • System.Data.SqlClient: Version=4.8.5

• Workstations
  • Visual Studio 2019 is no longer supported
    • Upgrade to Visual Studio 2022, minimum release 17.7 (required for Net 7.0)
  • Reinstall VsExtension.2022.vsix
    • In Visual Studio Tools/Options, set the Portal URL to the address used to access the Hopp Portal
      • Hint: The address to the Portal is the one that is currently set in the Director Client options. Just add the prefix with https://
        
  • Uninstall Director Client (decommissioned)
  • Reinstall DataServices Extensions (if installed)
    • Sql Server
    • Oracle
    • DB2
      
      
• Master Server  
  • Uninstall Director ClientService (decommissioned)

  • Reinstall Director Runtime

  • Redeploy Portal and all extensions

    • For this deploy, do not preserve your version of wwwroot/index.html but instead deploy the new version and update the base tag after deploy
      
      

  • Update the appsettings.json file of the Portal
    • Connection strings as described below
    • If present, remove these settings
      • Hosting (entire section)
      • Authentication/ShowPII
      • Authentication/ValidateIssuer
      • Authentication/UseBasePathAsIssuerUri
        
        
    • Add to the Authentication section:
      • PortalUrl = the url entered in the browser to access the portal (previously Hosting/BasePath)

        
        

• Execution Servers

  • Reinstall DataServices Extensions (if installed)
    • Sql Server
    • Oracle
    • DB2
  • Update the Master connection string in the MigFx.Agent.dll.config file of the Director Agent Service as described below

    
    

• Changes to connection strings
  • Due to a changed default for Sql Server connection encryption by Microsoft in Net 7.0, all connection strings should be updated
  • This concerns the following connection strings
    • The app config of the Director Agent Service on all execution servers
    • All connection strings in the Portal appsettings.json file
    • The Default Connection Options in the Configuration: Operations/Runtime/Config section of the Portal
      
  • There are the following alternatives
    • Either add the property Encrypt=false (it is the default for this property that has been changed to true by Microsoft)
    • Or add the properties Encrypt=true and TrustServerCertificate=true
    • Or add the properties Encrypt=true and TrustServerCertificate=false. In this case it is necessary to install a trusted certificate on the Sql Server

0 Votes