Enable Wasm threading - HxGN SDx - Update 63 - Administration & Configuration

Administration and Configuration of HxGN SDx

Language
English
Product
HxGN SDx
Search by Category
Administration & Configuration
SmartPlant Foundation / SDx Version
10

This functionality was modified in an update. For more information, see Enable Wasm threading (modified in an update).

WebAssembly (Wasm) threads enhance viewing performance of large files requiring strict security configuration.

To enable Wasm threading:

  1. Locate the Web Client settings.json file. For example:

    [drive]\SDx Server Files\WebClient_Sites\[SiteName]\settings.json

  2. Edit the following setting:

    Setting

    Value

    PDFTRON_WASM_ENABLED

    true

    If the PDFTRON_WASM_ENABLED setting is not present in settings.json, then it defaults to false.

Enable cross-origin isolation of a HxGN SDx site

If your browser has Wasm threads enabled, you must do the following to download files using Save Target As.

  1. Locate the Web.config file. For example:

    [drive] \SDx Server Files\Web_Sites\[Site Name]\Web.config

  2. Add the following XML tags as a child of <customHeaders>:

    <add name="Cross-Origin-Opener-Policy" value="same origin" />

    <add name="Cross-Origin-Embedder-Policy" value="require-corp" />

  3. Recycle all application pools and clear the browser cache. For instructions, see Recycle all application pools.

It can take up to 24 hours for system changes to appear.

Enable cross-origin isolation of a Web Client site

If your browser has Wasm threads enabled, you must do the following to download files using Save Target As.

  1. Locate the Web Client Web.config file. For example:

    [drive]\SDx Server Files\WebClient_Sites\[SiteName]\Web.config

  2. Add the following XML tags as a child of <system.webServer/>:

    <httpProtocol>

       <customHeaders>

          <add name="Cross-Origin-Opener-Policy" value="same-origin" />

          <add name="Cross-Origin-Embedder-Policy" value="require-corp" />

       </customHeaders>

    </httpProtocol>

  3. Recycle all application pools and clear the browser cache. For instructions, see Recycle all application pools.

It can take up to 24 hours for system changes to appear.