Installation of Creative Cloud Connector on the local machine:
...
- 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
| Info | ||
|---|---|---|
| ||
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. |
...
- Copy the provided zip file "digizuite-adobe-connector-website.5.x.x-xxxx.zip" onto your server and unzip it into a new folder.
- Copy the unzipped folder into the "Webs" folder (usually located on C:\webs)
- Rename the folder URL you wish for your CCC to be accessible through.
Step 2: Creating a
...
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.
The new version can be located under System tools → ConfigManager → Media Manager 5 where a new folder has been created.
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
...
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.
| Info |
|---|
| 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 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:
| Code Block | ||
|---|---|---|
| ||
{
"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 placeholdersThe 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:
| Placeholder | Description |
|---|---|
| ApiDomain | You 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:
|
| 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 VersionId to set that specific version as the current one, and not any version available beneath.Remember to include the character "/" at the end! Thus making it say e.g. "!/1/1/" |
| UseFederatedAuthentication | Must be set to "true" if using SSO. |
| EnableNormalLogin | Must 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 CCC and can be disregarded.
Step 4: Creation of a New IIS Website
...