Installation of Creative Cloud Connector on the local machine:
Info |
---|
This step can be performed at any time, independently of the remaining installation process. |
The extension can be installed in three ways:
...
- Download the installer from the AEScripts website for either Mac or Windows and run the installer
- When you've installed it, if you're not an administrator, go to the ZXP Installer's settings and ensure that "Install for current user only (When possible)" is enabled.
- go to "File > Open" or use the shortcut command CTRL+O (on Windows) or Command+O (on Mac)
- Find the ZXP package provided by your Digizuite consultant in your file browser and click "Open"
- You will get the below window and click "Install"
- You should then receive the message "creative-cloud was successfully installed"
- You can then follow the steps on this page to access Digizuite Adobe Creative Cloud Connector - CCC5.7 User Guides
...
Info |
---|
The commands we're using can be found here No regedit needed Will install to Program Files (x86) |
...
- 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
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. |
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:
- Use the MM5's Config Manager version by pointing to the MM5's url.
- 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:
- 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 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 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:
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/"
}
}
|
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:
...
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/"
...
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:
- Site name: Input the URL
- Physical path: Input the path to the folder in webs. Either click "..." or simply paste in the path yourself.
- Host name: Input the URL
- Type: Change type to "https".
- Require Server Name Indication: Check off the box
- SSL certificate: Select a SSL certificate that is usable for the URL you've chosen.
- 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]
The installation of the Adobe Creative Cloud Connector involves the following steps:
The installation of application on the local machine (required)
CCC installation (recommended method) (the default method that should be followed, unless stated otherwise by the Digizuite consultant)
CCC installation (alternative methods) (alternative methods, mostly for internal use)Setting up a proxy site (optional - only if separate configuration is required)
Creating a proxy site (optional)Setting up the connector in Adobe Creative Cloud application (required)
CCC5.7 How to access the CCC