Setting up the Magellan Publishing Profile (OP) - On Premises 6.4

Author-it Knowledge Center

Important: if any of the items in the screenshots are not on your system, you may need to do a full uninstall of Author-it and then rerun the 2020r2 installer.

1. The new Magellan Publishing Profile runs a powershell script that is installed in the installation folder after installing 2020r2. If you are publishing centrally, run the installer on the publishing server or otherwise copy this script to the server (in which case you need to update the path for it):

I think we're recommending it ONLY run on server publishing: one installation of Saxon, one script, better performance etc etc.  Also, do we have examples of how (and where in) the script it should be updated, what tool to edit the script, plus recommendations for relative/UNC path name

This is the first argument in the Command Line for Compile Magellan Help Center: 

-WindowStyle Hidden -ExecutionPolicy bypass -File "C:\Program Files\Author-it\Compilers\Magellan\magellan.ps1" -PublishFolder "<SYS_PUBLISH_FOLDER>"

So if the magellan.ps1 file is located somewhere else, then you must update the path to it.

2. The SaxonFolder argument is used to run Saxon transform.exe. The argument in the publishing profile is c:\Program files\Saxonica\SaxonHE9.7N. If you installed a different version or installed in a different location than the default, update the path to it. Check the installation folder for Saxonica on your system or the publishing server to get the correct path. Note that the path should be to the top level Saxon installation folder; the exe is actually in a \bin subfolder, but the script will find it as long as that top-level folder is correct:

-SaxonFolder "C:\Program Files\Saxonica\SaxonPE9.9N" -ResolvedXML "<SYS_PUBLISH_FILENAME>" -LocaleCode "<SYS_LOCALE_ABBREVIATION>"

recommendations on whether or not to use C:, based on security?

3. The MagellanFolder argument is for the Magellan Engine, which is essentially the Framework. This folder is automatically created during the installation of 2020r2: