...
...
...
...
...
...
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 two three ways:
- It can be done via the Adobe Exchange portal, search for "Digizuite Creative Cloud Connector"
- By using a 3rd party extension manager
- #1 recommended - AEScripts Adobe ZXP Extension Manager - https://aescripts.com/knowledgebase/index/view/faq/zxp-installer-faq/
- Download the installer from the AEScripts website for either Mac or Windows and run the installer
- Once installed, 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.5 User Guides
- Anastasiy’s Extension Manager - https://install.anastasiy.com/
- ZXP Installer (Note - this only install plugins and cannot remove, so this is the last option)
- #1 recommended - AEScripts Adobe ZXP Extension Manager - https://aescripts.com/knowledgebase/index/view/faq/zxp-installer-faq/
- 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/)
- Unzip the folder
- Open the CMD (doesn't have to be "as admin")
- Change directory (CD) to the root of the folder you unzipped: cd "C:\Users\{your user}\Downloads\ExManCmd_win"
- (Optional) You may check which programs are already installed: ExManCmd.exe /list all
- Get the address of the CCC .zxp file
- 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"
- (Optional) Run the following command, to see whether the zxp file was installed: ExManCmd.exe /list all
- If you have trouble uninstalling with ExManCmd.exe /remove "com.digizuite.creative-cloud", use a 3rd party extension manager listed above.
Info The commands we're using can be found here
No regedit needed
Will install to Program Files (x86)
- Or by a manual installation: (regedit needed)
- Aquire 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.
...
If you choose option 2, please follow the installations 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), and rename it to be that same as the
- Rename the folder 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)
- 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:- Unfold the menu with the server name
- Unfold "Sites"
- Right click on the name of one of the existing Digizuite products, for example your DAM center
- Click "Explore"
- 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.
- 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.
Info | ||
---|---|---|
| ||
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
...
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/" } } |
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: Use Insert 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 VersionId to set that specific version as the current one, and not any version available beneath. Remember to include the character "/" at the end! |
InstrumentationKey | E.g. e08240fb-c3b6-4b1f-9013-361c81dc506d |
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 should can 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".
Open the IIS
Unfold the menu under the server name . Next, and right-click the webserver web server and select "Add website...".
Once you select "Add website...", a new window will show up. Here you have to do A new prompt will appear.
Input the following:
- 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).
- Specify your "Physical path". You do this by clicking "..." next to the text box and searching for Adobe CC Connector folder mentioned above.
- Specify the prepared DNS record name in "Host name", which matches "Site name".
- 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 "Require Server Name Identification"Select the correct SSL certificate from the drop-down menu
- SSL certificate: Select a SSL certificate that is usable for the URL you've chosen.
- 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
- Expand the server content from the IIS Manager window and select the "Application Pools" menu.
- Locate the pool with the same name as your website and double-click it.
- The "Edit Application Pool" window will appear. Confirm that the selected .Net CLR version is 4+.
- Close "Edit Application Pool" and open the "Advanced Settings".
- Under "Process Model" change the Identity to "LocalService".
(Optional): Go into the site's bindings and add a "http" binding: