Configure the Loader Configuration Tool for a Citrix environment - SmartPlant Markup Plus - Version 2019 SP 1 (10.0.1) - Installation & Upgrade

SmartPlant Markup Plus Installation

English (United States)
SmartPlant Markup Plus
Search by Category
Installation & Upgrade
SmartPlant Foundation / SDx Version
SmartPlant Markup Plus Version
10.0 (2019)

The Loader Configuration Tool can be configured so that all users in a Citrix environment use the same custom fonts and references.

  1. Navigate to [installation location]\SmartPlant\Markup\Brava! Enterprise\JobProcessor\Igc.Loaders, and open using a text editor, such as Notepad.

  2. Set the TargetPathBase property to EXECUTABLE and the TargetPathRelative property to Igc.Loaders\.

  3. Save and close the file.

    Changes made using the Loader Configuration Tool are saved to the installation folder instead of the user's AppData folder.

After configuring the tool, set your parameter values for the loaders associated with the file types that should display custom fonts and references.

  1. On the SmartPlant Markup Plus server, run loaders.configuration.exe in the [installation location]\SmartPlant\Markup\Brava! Enterprise\JobProcessor\Igc.Loaders folder.

    • The parameter values will be set for all users.

    • For more information on using the Loader Configuration Tool, see the Loader Configuration Tool Guide delivered in: [installation location]\SmartPlant\Markup\Brava! Enterprise\JobProcessor\Igc.Loaders.

  2. Exit the Loader Configuration Tool and delete the files in the Brava! Server dlcache folder. This prevents illegible copies cached prior to the changes from being displayed.

    You can click Clear Display Cache on the Actions menu of the file or document in the Web Client.

  3. Open a file in Brava! Desktop for SmartPlant Markup Plus. The same custom fonts and references should be available for all users.

    Any preexisting driver configuration files in the [drive]:\Users\[user name]\AppData\Roaming\IGC\Brava!Desktop folder might need to be deleted since these files are not automatically replaced with the custom files created in step 4. For more information, see Custom references or fonts do not display.