Issue link: https://resources.pcb.cadence.com/i/1180190
Migration Guide for Allegro Platform Products Allegro EDM (previously ADW) October 2019 84 Product Version 17.4-2019 © 1999-2019 All Rights Reserved. Migrating to Release 17.4-2019 In the 17.4 release, there are a few changes to the way the Allegro EDM server is run and the terminology of some Allegro EDM configuration elements has changed: Important In 17.4, the Pulse Master node must always be running. This is true even if you work across releases (Multiple Library Releases/MLR mode). This is unlike in 17.2 where Designer Servers could continue working (with cached parts) even if the Master Library Server was not running. After installing the new release, you need to complete the following migration tasks to work with your existing Allegro EDM designs: 1. Updating Allegro EDM Component Database 2. Migrating Flow Files 3. Updating Project Files 4. Customizing Project Workspaces 17.2 17.4 Description Master Library Server Pulse Master node As before, the Pulse Master node is at a central location. All library data will be stored and managed here. When you run your design applications, such as Allegro System Capture, in the background, these applications connect to this central server to fetch data and connect to the Allegro EDM component database. Designer Server Pulse Data node Work with a Pulse cluster of Pulse Data nodes and a Pulse Master node, which is helpful since the cluster is used to reduce downtime and outages by distributing services and data storage and management between the Pulse Master and Pulse Data nodes in the event of an outage.