ÃÛ¶¹ÊÓƵ

DocumentationCampaignCampaign Classic v7 Documentation

How to enable Microsoft Edge Chromium on your environment edge-conf

Last update: Wed Jun 19 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

What changed?

Following the end of life of Microsoft Internet Explorer 11, the HTML rendering engine for dashboards in the client console is using Edge Chromium, starting Campaign Classic v7.3.

In addition to the installation of Microsoft Edge Webview 2 runtime, which is now required for any client console installation, Microsoft Edge Chromium must be enabled on your instance(s).

NOTE
After enabling Microsoft Edge Chromium, the Ctrl+F (Windows) or Command+F (Mac) shortcut to open the browser’s search dialog box will no longer work.

Are you impacted?

If your environment has been upgraded to Campaign Classic v7.3 (or later), you are impacted.

How to update?

  • As a hosted customer, ÃÛ¶¹ÊÓƵ already enabled Microsoft Edge Chromium on your instance(s). No additional action is required.

  • As an on-premise/hybrid customer, you need to enable Microsoft Edge Chromium on your instance(s).

    When upgrading to Campaign Classic v7.3 (and later), a new webView2Mode attribute is available in the Campaign server configuration file serverConf.xml. This attribute must be enabled.

    To perform this, apply the following steps on all your environments (MKT, MID, RT):

    1. Edit the Campaign server configuration file (serverConf.xml)

    2. In the <web> module, set webView2Mode = "1"

    3. Run the following command to reload the server configuration:

      code language-none 
      nlserver config -reload

    4. Run the following command to restart the web server:

      code language-none 
      nlserver restart web

    5. If your environment uses Apache as a web server, run the following command to restart Apache:

      code language-none 
      /etc/init.d/apache2 restart
NOTE
For any questions about these changes, contact .
recommendation-more-help
601d79c3-e613-4db3-889a-ae959cd9e3e1