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 3 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 three ways:

  1. It can be done via the Adobe Exchange portal, search for "Digizuite Creative Cloud Connector"
  2. By using a 3rd party extension manager#1 recommended - AEScripts Adobe ZXP Extension Manager - https://aescripts.com/knowledgebase/index/view/faq/zxp-installer-faq/
    1. Download the installer from the AEScripts website for either Mac or Windows and run the installer
    2. When you've installed it, if you're not an administrator, you have to go to the ZXP Installer's settings and enable "Install for current user only (When possible)", as this is disabled by default.
      1.  
    3. go to "File > Open" or use the shortcut command CTRL+O (on Windows) or Command+O (on Mac)
    4. Find the ZXP package provided by your Digizuite consultant in your file browser and click "Open"
    5. You will get the below window and click "Install"
    6. You should then receive the message "creative-cloud was successfully installed"
    7. You can then follow the steps on this page to access Digizuite Adobe Creative Cloud Connector - CCC5.6 User Guides
  3. By using Adobe's command line tool: (download using Firefox. Chrome seems to distrust it) (UPDATE: This is a user friendly alternative https://zxpinstaller.com/) (UPDATE2: If you have trouble uninstalling with ExManCmd.exe /remove "com.digizuite.creative-cloud", use https://install.anastasiy.com/)
    1. Unzip the folder
    2. Open the CMD (doesn't have to be "as admin")
    3. Change directory (CD) to the root of the folder you unzipped: cd "C:\Users\{your user}\Downloads\ExManCmd_win"
    4. (Optional) You may check which programs are already installed: ExManCmd.exe /list all
    5. Get the address of the CCC .zxp file
    6. Install the connector using the following command where the path in the citation marks point to the zxp file: ExManCmd.exe /install "C:\Users\{your user}\Downloads\digizuite-adobe-connector.zxp"
    7. (Optional) Run the following command, to see whether the zxp file was installed: ExManCmd.exe /list all
    8. If you have trouble uninstalling with ExManCmd.exe /remove "com.digizuite.creative-cloud", use a 3rd party extension manager listed above.

    9. The commands we're using can be found here

      No regedit needed

      Will install to Program Files (x86)

  4. Or by a manual installation: (regedit needed)
    • Acquire 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" (Edit: The zxp file can also simply be unpacked)
    • 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 installation 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)
  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.

Please note that the name itself is not important - but, once created, it cannot be changed nor deleted.

 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:

PlaceholderDescription
ApiDomainInsert the DAM Center's url. This is used to redirect the calls to the proxy site onto the corresponding DAM Center. 
VersionId

Input the CCC's Config Manager Version ID, which we located in the last step. (e.g. "/1/1/")

Due to legacy code, please insert a "!" in front of the version.

Thus making it say e.g. "!/1/1/"

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 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:


  • No labels