Adobe Classifications
- Topics:
- Administering
CREATED FOR:
- Admin
Adobe Classifications exports classifications data to Adobe Analytics in a scheduled manner. The exporter is an implementation of a com.adobe.cq.scheduled.exporter.Exporter.
To configure this:
-
Navigate via Tools, Cloudservices to the Adobe Analytics section.
-
Add a new configuration. You will see that the Adobe Analytics Classifications Configuration template displays below the Adobe Analytics Framework configuration. Supply a Title and Name as required:
-
Click Create to configure the settings.
Properties include the following:
Field Description Enabled Select Yes to enable the Adobe Classifications settings. Overwrite on conflict Select Yes to overwrite any data collisions. By default, this is set to No. Delete processed If set to Yes, deletes processed nodes after they are exported. The default is False. Export job description Enter a description for the Adobe Classifications job. Notification E-mail Enter an email address for Adobe Classifications notification. Report Suite Enter the Report suite to run the import job for. Data Set Enter the dataset relation ID to run the import job for. Transformer From the drop-down menu, select a transformer implementation. Data Source Navigate to the path for the data container. Export Schedule Select the schedule for the export. The default is every 30 minutes. -
Click OK to save your settings.
Modifying Page Size
Records are processed in pages. By default, Adobe Classifications creates pages with a page size of 1000.
A page may be 25000 in size at maximum, per definition in Adobe Classifications and can be modified from the Felix console. During the export, Adobe Classifications locks the source node to prevent concurrent modifications. The node is unlocked after export, on error, or when the session is closed.
To change the page size:
-
Navigate to the OSGI console at https://<host>:<port>/system/console/configMgr and select Adobe AEM Classifications Exporter.
-
Update the Export Page Size as required, then click Save.
SAINTDefaultTransformer
An Exporter may use a Transformer to transform the export data to a specific format. For Adobe Classifications, a subinterface SAINTTransformer<String[]>
implementing the Transformer interface has been provided. This interface is used to restrict the data type to String[]
which is used by the SAINT API and to have a marker interface to find such services for selection.
In the default implementation SAINTDefaultTransformer, the child resources of the exporter source are treated as records with property names as keys and property values as values. The Key column is added automatically as first column - its value will be the node name. Namespaced properties (containing :) are disregarded.
Node structure:
-
id-classification
nt:unstructured
-
1
nt:unstructured
- Product = My Product Name (String)
- Price = 120.90 (String)
- Size = M (String)
- Color = black (String)
- Color^Code = 101 (String)
-
SAINT Header & Record:
Key | Product | Price | Size | Color | Color^Code |
---|---|---|---|---|---|
1 | My Product Name | 120.90 | M | black | 101 |
Properties include the following:
Property path | Description |
transformer | A class name of a SAINTTransformer implementation |
Notification e-mail address. | |
reportsuites | Report suite IDs to run the import job for. |
dataset | Dataset relation ID to run the import job for. |
description | Job description. |
overwrite | Flag to overwrite data collisions. Default is false. |
checkdivisions | Flag to check report suites for compatibility. Default is true. |
deleteprocessed | Flag to delete the processed nodes after export. Default is false. |
Automating Adobe Classifications Export
You can create your own workflow, so that any new imports launch the workflow to create the appropriate, and correctly structured, data in /var/export/ so that it can be exported to Adobe Classifications.
Experience Manager
- Administering User Guide overview
- Sites Features
- Website Administration
- Reusing Content: Multi Site Manager and Live Copy
- Live Copy Overview Console
- Configuring Live Copy Synchronization
- Creating and Synchronizing Live Copies
- MSM Rollout Conflicts
- MSM Best Practices
- Translating Content for Multilingual Sites
- Managing Translation Projects
- Identifying Content to Translate
- Preparing Content for Translation
- Creating a Language Root Using the Classic UI
- Connecting to Microsoft Translator
- Configuring the Translation Integration Framework
- Language Copy Wizard
- Translation Enhancements
- Translation Best Practices
- Configurations and the Configuration Browser
- AEM FAQs
- Operations
- Dashboards
- Operations Dashboard
- Backup and Restore
- Data Store Garbage Collection
- Monitoring Server Resources Using the JMX Console
- Working with Logs
- Configure the Rich Text Editor
- Configure the Video component
- The Bulk Editor
- Configuring Email Notification
- Configuring RTE for Producing Accessible Sites
- The Link Checker
- Troubleshooting AEM
- Audit Log Maintenance in AEM 6
- Editor
- Managing Access to Workflows
- Using cURL with AEM
- Configuring Undo for Page Editing
- Proxy Server Tool (proxy.jar)
- Configuring for AEM Apps
- Administering Workflows
- Configuring Search Forms
- Tools Consoles
- Reporting
- Administering Workflow Instances
- Configuring Layout Container and Layout Mode
- Enabling Access to Classic UI
- Starting Workflows
- Configure the Rich Text Editor plug-ins
- Admin Consoles
- Security
- User Administration and Security
- User, Group and Access Rights Administration
- Security Checklist
- OWASP Top 10
- Running AEM in Production Ready Mode
- Identity Management
- Adobe IMS Authentication and Admin Console Support for AEM Managed Services
- Creating a Closed User Group
- Mitigating serialization issues in AEM
- User Synchronization
- Encapsulated Token Support
- Single Sign On
- How to Audit User Management Operations in AEM
- SSL By Default
- SAML 2.0 Authentication Handler
- Closed User Groups in AEM
- Granite Operations - User and Group Administration
- Enabling CRXDE Lite in AEM
- Configuring LDAP with AEM 6
- Configure the Admin Password on Installation
- Service Users in AEM
- Encryption Support for Configuration Properties
- Handling GDPR Requests for the AEM Foundation
- Content Disposition Filter
- Personalization
- eCommerce
- Integration
- Integrating with Third-Party Services
- Integrating with Salesforce
- Integrating with Adobe Target
- Integrating with Adobe Analytics
- Connecting to Adobe Analytics and Creating Frameworks
- Configuring Link Tracking for Adobe Analytics
- Mapping Component Data with Adobe Analytics Properties
- Configuring Video Tracking for Adobe Analytics
- HTTP2 Delivery of Content FAQ
- Troubleshooting your Adobe Campaign Integration
- SharePoint Connector Licenses, Copyright Notices, and Disclaimers
- SharePoint Connector
- DHTML Viewer End-of-Life FAQs
- Integrating with Adobe Campaign Classic
- Related Community Articles
- Integrating with Adobe Campaign Standard
- Flash Viewers End-of-Life Notice
- Integrating with Adobe Creative Cloud
- Integrating with Adobe Dynamic Tag Management
- Opting Into Adobe Analytics and Adobe Target
- AEM Portals and Portlets
- Integrating with Dynamic Media Classic
- Troubleshooting Integration Issues
- Integrating with BrightEdge Content Optimizer
- Best Practices for Email Templates
- Catalog Producer
- Integrating with Silverpop Engage
- Integrating with Adobe Campaign
- Integrating with ExactTarget
- Analytics with External Providers
- Integrating with the Adobe Marketing Cloud
- Manually Configuring the Integration with Adobe Target
- Prerequisites for Integrating with Adobe Target
- Adobe Classifications
- Solutions Integration
- Target Integration with Experience Fragments
- Best Practices
- Content Management