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 11 Next »

Installation of Creative Cloud Connector on the local machine:

This step can be performed at any time, independently of the remaining installation process.

The extension can be installed in two ways:

  1. It can be done via the Adobe Exchange portal, search for "Digizuite Creative Cloud Connector".
  2. Or by a manual installation:
    • Aquire the installation files from your contact at Digizuite. You'll be sent a zip named something like"digizuite-adobe-connector.5.x.x-xxx.zip"
    • Unzip it into a folder you name anything - for this guide we've chosen to call it: com.digizuite.creative-cloud-connector 
    • Move the folder to either of the following paths:
  • Windows: C:\Program Files\Common Files\Adobe\CEP\extensions\com.digizuite.creative-cloud-connector
  • MacOS: ~/Library/Application Support/Adobe/CEP/extensions/com.digizuite.creative-cloud-connector

Windows only

If you place the files in both the Program Files AND the Program Files (x86) - you will very likely encounter issues.

Only place the files in Program Files.

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.


If you choose option 2, please follow the installations steps below:

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), and rename it to be that same as the URL you wish for your CCC to be accessible through. (In other words: The name matching the DNS record for the Creative Cloud Connector in the location your IIS server has the access to)
  3. This location is usually the folder named "Webs" (usually C:/Webs is used, but it can also be located on a different drive).
    An alternative method of finding the relevant "Webs" folder is by using Internet Information Services (IIS) Manager. In order to do that, you need to:
    1. Unfold the menu with the server name
    2. Unfold "Sites"
    3. Right click on the name of one of the existing Digizuite products, for example your DAM center
    4. Click "Explore"
  4. The folder named something along the lines of "digizuite-adobe-connector-website.5.x.x-xxxx.zip" is used for setting up the proxy website. After unpacking it, you need to place its contents into the folder created in the previous step.
  5. Create a new folder with the same name as your DNS record in the folder "LogFiles". You will need to specify the path to the newly created folder in one of the following steps.


DNS entry

As stated in the requirements document, you must set up a DNS entry for the website.

If you do not have a way of setting up the DNS, you can instead edit your own computer's "hosts" file, located in C:\Windows\System32\drivers\etc.


Step 2: Creating a new Creative Cloud Connector version

The DAM Center enables the opportunity of creating multiple Creative Cloud Connector versions with the help of the Config Manager. Usually, however, you will only have one version corresponding to your one Adobe CC Connector.

It is strongly recommended to create at least one version of the application (Default) at this stage of the installation process.

To create a new version, you'll have to access your DAM Center.

In your DAM Center, navigate to System tools → ConfigManager → Media Manager 5 and select the correct version. 

While standing in the root of Media Manager 5's Config Manager, look to the upper right corner where a button says "Create new version".

To the left of the button, there is a text field. In the field, type the title of the version.  Name the new version something like this CCC.

Press the "Create new version" button.

It can be noticed that under System tools → ConfigManager → Media Manager 5 a new folder has been created that contains the current version and the newly created one.

You will need to access the version ID of this newly created version in the next step in order to mark it as the current one.

Step 3: Website Configuration for the Creative Cloud Connector

Before the Creative Cloud Connector can be used, it needs to have some base configuration set, such as which DAM Center it should use. This configuration can be found in the appsettings.json file. This file was part of the content that you have copied into the folder with the name matching the DNS record for the site

This is the relevant part of the configuration file that you will see once you open it with e.g. Notepad++:

{
  "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/"
  }
}

While you fill out the required fields, the same rules as with the configuration file for the installation scripts apply.

Here is the description of what to put into the placeholders:

PlaceholderDescription
ApiDomainYou need to replace ApiDomain with the base Domain of the DAM Center that Media Manager 5 should be connected to.
ProductVersion

The version of the product that has been installed.

Example: 5.0.0-1404

VersionId

This is the current version ID of Media Manager 5 ConfigManager version to be used.

The easiest way to find it is by opening and logging in to your DAM Center, as demonstrated on the screenshot below:

Use "!" in front of the VersionId to set that specific version as the current one, and not any version available beneath.

Remember to include the character "/" at the end! 

InstrumentationKeyE.g. e08240fb-c3b6-4b1f-9013-361c81dc506d
UseFederatedAuthenticationMust be set to "true" if using SSO.
EnableNormalLoginMust be set to "true" if normal login should be enabled together with SSO.

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

Step 4: Creation of a New IIS Website

To add a new website on Windows Server, open the "Server Manager" console. Then, under the "Tools" drop-down menu, select "Internet Information Services (IIS) Manager".

Unfold the menu under the server name. Next, right-click the webserver and select "Add website...".

Once you select "Add website...", a new window will show up. Here you have to do the following:

  1. Type in your "Site name". The name should be the same as the folder that you created in "Webs" folder for your Digizuite™ Adobe CC Connector in the preparation process (second step).
  2. Specify your "Physical path". You do this by clicking "..." next to the text box and searching for Adobe CC Connector folder mentioned above.
  3. Specify the prepared DNS record name in "Host name", which matches "Site name".
  4. Change type to "https".
  5. Check the box "Require Server Name Identification"
  6. Select the correct SSL certificate from the drop-down menu.
  7. Click "OK".

Once the site has been created, go into the bindings for the site in the IIS and create http site on the same domain.

Step 5: Application Pool Setup

  1. Expand the server content from the IIS Manager window and select the "Application Pools" menu.
  2. Locate the pool with the same name as your website and double-click it.
  3. The "Edit Application Pool" window will appear. Confirm that the selected .Net CLR version is 4+.
  4. Close "Edit Application Pool" and open the "Advanced Settings".
  5. Under "Process Model" change the Identity to "LocalService".



  • No labels