Prime Radiant Release 2020.8.0

Downloads:

• Prime Radiant Full App 2020.8.1
• Prime Radiant Upgrade 2020.8.1
• NSF classic 2020.8.0
  • NSF classic no longer contains Prime Radiant

New Packaging

Starting with version 2020.8.0, Prime Radiant is no longer packaged alongside the classic NSF base. Instead, it exists as a separate application that manages your existing and new NsfBases (NSF directories).

• See Prime Radiant Directory Structure for C:\primeradiant structure description.
• See NsfBase for C:\NSF (nsfBase) directory structure description.

First Installation

NOTE: Prime Radiant 2020.8.0 is not compatible with previous versions. However, it is installed in a different directory, therefore you can keep using your older Prime Radiant in case of any issues.

(Optional) If you don’t have an existing NSF base, download NSF classic (see links above) and unpack it to C:\NSF

1. Download Prime Radiant zip (see links above)
2. Unpack the zip to C:\primeradiant
   • you can place the installation directory anywhere; if you choose to do so, modify the next steps accordingly
3. Open C:\primeradiant\config\custom_vars.bat
   • Here you can adjust java and maven that will be used by Prime Radiant
   • By default it uses system-wide configuration of JAVA_HOME, and mvn available in PATH. This is the recommended setup.
   • If you want to use the ones from your NSF directory, uncomment the preconfigured examples and modify as needed
   • Adjust the rest of configuration to your liking
4. (Optional) Open C:\primeradiant\config\nsfBases.xml
   • Add or modify Nsf Bases to your liking. You can have multiple Nsf Bases, e.g. one for workspace, several for deployment, etc. See NsfBases for more info.
5. Run C:\primeradiant\PrimeRadiant.bat

If you have an existing NsfBase, add the following file C:\NSF\primespace\expansionsPR\expandBase.xml

<expandBase name="Expansions 3.0 - PR">
  <baseRoot>expansionsPR</baseRoot>
  <useAppId value="false"/>
  <description>-</description>
</expandBase>

1. Open Prime Radiant in your browser http://localhost:9000/primeRadiant/
   • (Optional) If you customized PRIME_RADIANT_BASE_PORT in custom_vars.bat, adjust the url accordingly
2. Log in
3. Navigate to Upgrade page (accessible from Dashboard, or from menu Configuration | PrimeBase, http://localhost:9000/primeRadiant/elements/primeBase/all)
4. Select the available PrimeBase and sequentially click all buttons from left to right
   • For more information on the individual actions, see PrimeBase.
5. Navigate to NsfBase (menu Configuration | NsfBase, http://localhost:9000/primeRadiant/elements/nsfBase/all)
   • Here you see all NsfBases configured in C:\primeradiant\config\nsfBases.xml, and additionally dist (Prime Radiant’s internal distribution base).
6. Click on Synchronize All
   • Synchronize (All) scan NsfBase(s) and looks for all existing sourceBases (projects), expandBases (expansions), and deployBases (servers)
   • Prime Radiant console window also lists all found entries
   • Rerun this action when you add/remove new entries, such as cloning a new project to your workspace

Your Prime Radiant is now ready.

Major Changes And Fixes

Fixes and Changes:

• Prime Radiant is no longer internally coupled to the NSF directory or its infrastructure
• Fixed expanding with non-semver versions of expanders (e.g. 4.0.8.1 or 4.1.1.1)
• Fixed some edge-cases when (clean) importing (DataFlowTasks, ApplicationDeployments, component dependency order)
• Default expansion directory is now <applicationInstance.name>/<application.shortName> (e.g. bookingApp_experimental/bookingApp)
  • this addresses issue with clean import changing applicationInstance ids (so e.g. bookingApp-id20/bookingApp changed to bookingApp-id50/bookingApp after import)
  • the legacy style (<applicationInstance.shortName>/<application.shortName>) can be temporarily enabled, however it will be removed completely in a future release
• Expanding/harvesting/etc. now runs directly on files in your sourceBase (workspace)
  • doesn’t eliminate ghost changes (e.g. dataElement removed from disk, but not from PR), but makes it more obvious (because git now sees a new/changed file)
  • to export model before expansion, Expand Applications page now has a separate button
  • this is a step in direction of having files disk and data in PR be in sync at all times
• For projects using legacy expansion (<4.4.0 expanders / not using PROVIDED), expanderVersion is now automatically created on import if it doesn’t exist
• Fixed some edge cases breaking expansion for <4.4.0 expanders
  • oldest tested is v4.0.8.1, but in principle we support any 4.x version (and if it doesn’t work, it should be reported as a bug, even for old expanders)

Additions and Changes:

• Prime Radiant location, port, infrastructure, etc. can be trivially customized by users
• Upgrades automatically backup previous version of Prime Radiant AND it’s database (so revert should be trivial)
• Added Synchronization of NsfBases to easily manage your projects, expansions, and deployments on disk
• Users can now easily import user data files (custom fieldOptionTypes, technologies, etc.)
  • future version will support import from jars (to ease usage of additional expanders / expansion resources)
• UI of Expand Applications is now more compact and provides a better overview of the selected instance
  • You can select which expansionSettings you want to use for expansion/harvesting/…
  • If no expansionSettings are defined, you can create them directly from the Expand Applications page
  • All actions now run on model in your workspace, to export data from Prime Radiant, run Export first
• Reorganized menu (note that all dataElement pages are still available and accessible via url)

Expansion Page

The expansion page has been modified to work better with expansionSettings and be more consistent with expanding from disk (cli).

Expanding from Prime Radiant