Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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.

If you also want to enable normal login, change "EnableNormalLogin" to "true" in the appsettings.json file.

Manifest configuration

You should now have a working OC website. Please visit the URL of the installed site in a browser and check that the OC loads.

A central configuration artifact for the OC is the manifest file.

A separate manifest file must be configured for each of following the sets of applications:

  1. Word, PowerPoint and Excel: "manifest.xml".
  2. Outlook: "manifest-outlook.xml".

Note that it is not required to configure both manifest files.

The two files are both located in the "wwwroot"-folder of the installed OC. Alternatively, the files are similar to the following:

For each manifest file do the following:

  • Replace all references to localhost with the OC site reference. E.g. if OC is installed at oc.digizuite.com, then replace localhost with oc.digizuite.com.
  • Change the ID to a new, random GUID.
  • Change the "DisplayName" (title) and the "Description" appropriately. These affect the displayed text in the ribbon for the end-user.
  • Go through the labels in the manifest file and ensure that they have the desired values.

Manifest deployment

To deploy the manifest and thus make the OC available for users, go through the following steps with an Office 365 admin account: https://docs.microsoft.com/en-us/office/dev/add-ins/publish/centralized-deployment.

If an issue is encountered, please validate your manifest file with the tool at: https://github.com/OfficeDev/Office-Addin-Scripts/tree/master/packages/office-addin-manifest

Centralized deployment

With an Office 365 admin account, follow the installation steps at: https://docs.microsoft.com/en-us/office/dev/add-ins/publish/centralized-deployment.

Note that the add-in should automatically be pushed to the user for Word, PowerPoint, and Excel. This is also possible for Outlook by choosing the "Fixed" deployment method.

Thus, the OC should automatically appear in the "Insert" ribbon page:

If the OC is not found for a user which has been granted access to the add-in, please ensure that the user is logged in with his/her organizational ID in the Office applications.

This can be checked by going to: File → Account and login.

Two logins are available. Ensure that the user is logged in with his/her organizational ID in the correct location:


Updating the manifest 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

Include crops in the asset list

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

  1. Create a new child configuration of MM5, specifically for the OC. This is described in more detailed at the top of this page. Failing to do this will result in MM5 being affected too.
  2. Find the search “DigiZuite_System_Framework_Search” in the newly created child configuration.
  3. Remove the "asset.prevref" field from the search input.
  4. Save the search.


  • No labels