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 create website folder.
| Code Block | ||
|---|---|---|
| ||
{
"Logging": {
"LogLevel": {
"Default": "Warning"
}
},
"AllowedHosts": "*",
"EnablePrerendering": false,
"ForceHttps": true,
"HttpsPort": 443,
"MediaManagerConfiguration": {
"GuestUsername": "Guest",
"GuestPassword": "0ea2f02d5f73c86c220ff08b23d1c3f1",
"ApiDomain": "DAM URL",
"UseHttps": true,
"WowzaServer": "https://mm.dev.digizuite.com/",
"WowzaAppName": "mmapp",
"AbrMediaId": "666",
"EnabledFeatures": [
"workflow-management",
"bar"
],
"InstrumentationKey": "74afe12a-8df3-4efa-998d-936a1021ff6c",
"ProductVersion": "5.2.0",
"VersionId": "!/6/0/", #MM CONFIG VERSION (lowest level)
"UseFederatedAuthentication": false,
"EnableNormalLogin": false,
"BusinessWorkflowServiceUrl": "http://localhost:60000/"
}
}
|
SSO
Version 5.2.0 has a known issue with SSO. If SSO is to be used, please use version 5.2.1 or higher.
Admin Configuration
Next, locate the manifest.xml file in the "wwwroot"-folder of the installed OC, and open the file. Alternatively, the file is similar to the following:
...
The "DisplayName" (title) and the "Description" should also be changed appropriately. If there are any labels that need to be changed in the ribbon, they are found in the bottom of the XML file, and can be replaced as one sees fit.
Make sure to generate a new ID.
To check if your manifest file is valid, you can use the following tool: https://github.com/OfficeDev/office-addin-validator.
If Centralized Deployment is possible (see Digizuite™ Office Connector 2.0 - 0. Requirements), follow the instructions for "Centralized Deployment" below.
...
- For Windows users, follow the instructions at: https://docs.microsoft.com/en-us/office/dev/add-ins/testing/create-a-network-shared-folder-catalog-for-task-pane-and-content-add-ins.For Mac users, follow the instructions at: https://docs.microsoft.com/en-us/office/dev/add-ins/testing/sideload-an-office-add-in-on-ipad-and-mac.
If this approach is used, the "Centralized Deployment" section below can be skipped.
Please note that it might be possible to avoid having to install the OC separately on all client computers. However, this approach has not been tested. The approach can be tried by following the instructions at https://docs.microsoft.com/en-us/office/dev/add-ins/publish/publish-task-pane-and-content-add-ins-to-an-add-in-catalog. It involves publishing the OC to an app catalog with an on-premises SharePoint Server. Note that this approach will not make the OC available for Mac users.
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.
To install the OC on client computers, do the following steps for each client.
Installing on client computers
First of all, make sure that you are logged in with your organizational ID in the Office applications.
...
Once you have installed OC on a device for one Office product (e.g. Word), the OC will automatically be available for the two remaining Office products (e.g. Excel and PowerPoint).
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
...