Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Website installation

To install the Office Connector (henceforth referred to as "OC"), install an OC the exact same way you would install a Media Manager 5 site (MM).

  • Create a new website folder and copy the content from SWInstall into the created website folder.

Website configuration

The OC has it own appsettings.json file, identical to the appsettings.json file for MM. Some parameters are of particular interest in the OC.

VersionId

Note that the OC does not have a separate entry in the ConfigManager in the DC. If an OC entry exists, it belongs to the old OC and it will not affect the new one.

Instead, the OC uses an MM configuration, which can be found as a child of the Media Manager 5 node in the ConfigManager. The following options are available:

  1. (Recommended) Create a new child configuration for the OC based on the MM configuration. This makes it possible to change e.g. searches and configuration parameters independently of MM.
  2. Use an existing MM configuration.

Create or choose a configuration to use, and then change the "VersionId" parameter in the appsettings.json for the OC appropriately.

SSO

If you want to enable SSO, change "UseFederatedAuthentication" to "true" in the appsettings.json file.

...

After updating the manifest file (NOTE: not after updating the website itself), a user might not see the effects of the update immediately. To fix this, try following the steps under "Remove an add-in from local cache" on the user's computer: https://docs.microsoft.com/en-us/office365/enterprise/use-the-centralized-deployment-powershell-cmdlets-to-manage-add-ins?redirectSourcePath=%252farticle%252f94f4e86d-b8e5-42dd-b558-e6092f830ec9#delete-an-add-in

...

in

...

It is possible to configure the OC to show asset crops in the asset list, alongside the original assets:

...