Hello friend!
The beta release of Open iT version 10.1 is now available!
Try it out and help us enhance your Open iT experience. Contact support@openit.com to get started.
#
Adobe Creative Cloud
#
Introduction
Open iT supports Adobe Creative Cloud usage reporting by collecting application usage and logs from Adobe applications and user information from the Adobe Admin Console via the User Management API (UM API). These will produce the following aggregated data types used for historical and real-time reporting:
- (89) Total License Use Licenseevents
- (90) Individual License Use Licenseevents
- (91) Usergroup License Use Licenseevents
- (108) Host License Use Licenseevents
- (109) Hostgroup License Use Licenseevents
- (118) Product Inventory
- (139) License Subscription Inventory v2
- (140) License Product Assignment v2
The following sections will guide you in setting up the necessary configuration to collect and send the required data to the server.
Apply the configurations shown in the Open iT server.
#
Requirements
- An Open iT Client connected to an Open iT Server or a coexistent Open iT setup
- Activated LicenseAnalyzer collection and Adobe workstation collectors
- Adobe Enterprise Plan
- Administrator privileges in the Adobe Developer Console
#
Obtaining the API Access Credentials
You need the following credentials to access the UM API:
- Organization ID
- Technical Account ID
- Client ID
- Client Secret
- Private Key
To obtain these access credentials, create a Service Account Integration in the Adobe Developer Console.
Log in to the Adobe Developer Console using an account with administrative rights.
Under Quick start, click Create new project.
Adobe Developer Console: Home
This redirects to the Project overview page. Click Edit project to modify the project title and description (optional).
Click Add to Project and select API.
Adobe Developer Console: Project Overview
In the Add an API prompt, under the Filter by product, select Adobe Services.
Select User Management API, then click Next.
Adobe Developer Console: Add an API
In the Configure API prompt, select your preferred option to generate a public/private key pair.
Click Generate keypair.
Securely store the automatically downloaded config
compressed folder. This contains the certificate_pub.crt
and private.key
files.
Upload the public key, then click Next.
Click Save configured API.
Adobe Developer Console: Save Configured API (Option 1)
Adobe Developer Console: Save Configured API (Option 2)
This redirects to the Details page of the API. Scroll down to view the credentials under Service account (JWT).
Adobe Developer Console: View the credentials in the API menu
You can also view the Credential details page by selecting Service Account (JWT) under Credentials from the side navigation menu.
Adobe Developer Console: View the credentials in the Credentials menu
Record the necessary credentials.
Visit Adobe's Authentication for API Access documentation for more details.
#
Downloading the Credential Files
Log in to the Adobe Developer Console using an account with administrative rights.
Go to Projects.
Adobe Developer Console: Home
Open the necessary project.
Adobe Developer Console: Projects
On the Project overview page, click Download.
Adobe Developer Console: Download from the Project Overview page
The downloaded file (e.g.,
#-#-Production.json
) here contains the overall project details.Alternatively, go to the Service Account (JWT) page, then click Download JSON.
Adobe Developer Console: Download from the Service Account (JWT) page
The downloaded file (e.g.,
#-#-Service Account (JWT).json
) here contains the project credentials.
#
Configuring Cloud Data Collection
These are the required steps to configure collection of Adobe Cloud data.
Go to the Components directory, which is by default in
C:\Program Files\OpeniT\Core\Configuration\Components
.Open
adobecloudcollector.xml
.Input the API access credentials in their respective value attribute.
adobecloudcollector.xml15| <Object> 16| <Name>org_id</Name> 17| <Value type="String">Insert the organization ID (IMS_ORG_ID or ORG_ID) here</Description> 18| </Object> 19| 20| <Object> 21| <Name>tech_acct_id</Name> 22| <Value type="String">Insert the technical account ID (TECHNICAL_ACCOUNT_ID) here</Description> 23| </Object> 24| 25| <Object> 26| <Name>client_id</Name> 27| <Value type="String">Insert the client ID (CLIENT_ID) here</Description> 28| </Object> 29| 30| <Object> 31| <Name>client_secret</Name> 32| <Value type="String">Insert the client secret (CLIENT_SECRET) here</Description> 33| </Object> 34| 35| <Object> 36| <Name>private_key</Name> 37| <Value type="String">Insert the private key here</Description> 38| </Object>
When referring to the project JSON files:
- In
#-#-Production.json
, ims_org_id corresponds to the organization ID. - In
#-#-Service Account (JWT).json
, ORG_ID corresponds to the organization ID.
The private_key value must contain the full content of the private key file, starting from
-----BEGIN PRIVATE KEY-----
until-----END PRIVATE KEY-----
.The api_access_claim object contains the metascope for User Management Service Account APIs. This scope is used to access the needed resources.
- In
Save the changes.
#
Activating Cloud Data Collection
These are the required steps to activate collection of Adobe Cloud data.
Go to the scheduler directory, which is by default in
C:\Program Files\OpeniT\Core\Configuration\scheduler
, and opencollect_license_adobe-cloud.oconf
.Locate and set
root.scheduler.jobs.collect_adobe_cloud.general.active
to true to activate the collection of Adobe Cloud data.collect_license_adobe-cloud.oconf13| } 14| general 15| { 16| active 17| { 18| type=bool 19| value=true
Save the changes.
Refer to the Adobe Cloud Data Job Scheduler Instances Configuration table to learn the attributes used to configure Adobe Cloud data collection.
#
Configuring Application Usage Tracking in the Workstations
These are the required steps to monitor Adobe application usage in the workstations.
Go to the Configuration directory, which is by default in
C:\Program Files\OpeniT\Core\Configuration
.Open
appusage_process_rules-adobe.conf
.Copy the file contents.
From the same directory, open
appusage_process_rules_master.conf
Paste the copied contents.
Add the copied contents as new entries/lines in the file. Make sure that the existing configurations in
appusage_process_rules_master.conf
are kept as is.Save the changes.
#
Distributing Files to the Clients
Files from the server automatically reflect on the client after restarting the client service or every 6 hours, which is the default schedule for file distribution. However, you can manually trigger the file distribution:
Manual File Distribution to a Client
#
Next Steps?
Renaming Vendor License Renaming Features Create and Add Report License Monitor