Creating a proxy site (optional)

(description)

Selection of config manager version

This new version of the connector uses the Media Manager 5's (MM5) Config Manager, as opposed to previously, where the Creative Cloud Connector (CCC) had its own version in the Config Manager.

There are two ways you can point the CCC to a Config Manager version:

1. Use the MM5's Config Manager version by pointing to the MM5's url.

2. Use a CCC-only Config Manager version, by pointing to a new proxy website you create.

Installing of a proxy website

Step 1: Preparation

To install a proxy website please perform the following steps:

1. Copy the provided zip file "digizuite-adobe-connector-website.5.x.x-xxxx.zip" onto your server and unzip it into a new folder.

2. Copy the unzipped folder into the "Webs" folder (usually located on C:\webs)

3. Rename the folder URL you wish for your CCC to be accessible through.

Step 2: Creating a Config Manager version solely for CCC to use 

This step is the whole "meat and potatoes" of this guide. Here you create what the the CCC points to. In other words, the other steps are there to allow the CCC plugin to point to the Config Manager version you create here.

To start, go to you DAM Center, and navigate to System tools → ConfigManager → Media Manager 5 → 5.0.0.

In here, you have the ability to create CCC's Config Manager version.

Press the text field in the top-right corner, and input a name you find fitting. Some people go with "CCC", while other go with "Default" - or something else entirely.

 After creation, the new Config Manager version can be found beneath System tools → ConfigManager → Media Manager 5 → 5.0.0.

In here - locate the ID of the Config Manager version by pressing the Menu button → Version information (found next to the Create new version button):

You'll be seeing something akin to the following image:

Note down the Version id - in this case, it's "/1/1/". This will be used in the following step.

Step 3: CCC website configuration

The proxy website needs to point to the new version you created. Additionally, it requires some info to be set, in order to fully function.

Navigate to the CCC website files from step 1 (again, usually found in C:/webs), and open the file named appsettings.json - we recommend Notepad++ for editing such files:

{
  "Logging": {
    "LogLevel": {
      "Default": "Warning"
    }
  },
  "AllowedHosts": "*",
  "EnablePrerendering": false,
  "ForceHttps": true,
  "HttpsPort": 443,
  "MediaManagerConfiguration": {
    "GuestUsername": "Guest",
    "GuestPassword": "0ea2f02d5f73c86c220ff08b23d1c3f1",
    "ApiDomain": "",
    "UseHttps": true,
    "WowzaServer": "",
    "WowzaAppName": "mmapp",
    "AbrMediaId": "666",
    "EnabledFeatures": [],
    "InstrumentationKey": "#{instrumentationKey}",
    "ProductVersion": "#{productVersion}",
    "VersionId": "!/5/",
    "UseFederatedAuthentication": false,
    "EnableNormalLogin": false,
    "BusinessWorkflowServiceUrl": "http://localhost:60000/"
  }
}

The easiest way to configure this, is to look at your Media Manager website's appsettings.json file, and copy its values.

Here's a rundown of what the fields are used for:

Please note: The fields "WowzaServer", "EnabledFeatures" and "InstrumentationKey" are not relevant for the CCC and can be disregarded.

Step 4: Creation of a New IIS Website

Open the IIS

Unfold the menu under the server name and right-click the web server and select "Add website...".

A new prompt will appear.

Input the following:

1. Site name: Input the URL

2. Physical path: Input the path to the folder in webs. Either click "..." or simply paste in the path yourself.

3. Host name: Input the URL

4. Type: Change type to "https".

5. Require Server Name Indication: Check off the box

6. SSL certificate: Select a SSL certificate that is usable for the URL you've chosen.

7. Click "OK".

(Optional): Go into the site's bindings and add a "http" binding:

Step 5: Ensure that ProtalName is set to be the MM5 site's URL

Define PortalName which could be found withing appsettings.json "ProductConfiguration" section to be either:

• The MM’s URL if the MM does not have this defined

• The same as the MM’s if the MM has it defined

Example of relevant json files:

D:\webs\test-ccc.qa.digizuite.com\appsettings.json

D:\webs\test-mm5.qa.digizuite.com\appsettings.json

The required value for Portalname could be found within table:

SELECT TOP (1000) [ProductName]
      ,[PortalName]
      ,[MemberId]
      ,[Configuration]
  FROM [test_dam].[dbo].[LoginService_Preferences]