Binary-less distribution is supported for deployments over a shared data store and involves agents that leverage the Vault-based Distribution package exporter (factory PID: org.apache.sling.distribution.serialization.impl.vlt.VaultDistributionPackageBuilderFactory) package builder.
With binary-less mode enabled, the content packages distributed contain references to binaries rather than the actual binaries.
To enable binary-less distribution, deploy with a shared blob store.
Check the useBinaryReferences property in the OSGI configuration with the factory PID (org.apache.sling.distribution.serialization.impl.vlt.VaultDistributionPackageBuilderFactory) that your agent is using.
Check the Network panel (of Chrome browser) where a personal setup (JS has not been minified).
View the Initiator column to determine what the initiator of a request was. It provides the files and the line numbers from where the AJAX calls are made. Later, you can trace the error handling function and change the error message as per your requirement.
Create a language root and language copy inside the root, before creating a translation project.
Create a language root at /content/geometrixx with name as fr_LU (and title as French (Luxembourg)). Subsequently, create language copy of page from the references panel and navigate to Create structure only option in Create & Translate. Finally, create a translation project and then add the language copy to the translation job.
For details, refer to the additional resources below:
AEM has introduced the ability to log administrative changes for better troubleshooting and audit. By default, the information is logged in the error.log file. To make monitoring easier, it is recommended that they be redirected to a separate log file.
To redirect the output to a separate log file, see How to audit user management operations in AEM.
Adobe Experience Manager (AEM) 6.4 ships with the SSL wizard and offers a User Interface to configure Jetty and Granite Jetty SSL support.
To enable SSL by default, see SSL by default.
What is the recommended architecture when using AEM’s Content Services from a mobile app, ideally React Native?
The Content Services are based on the Sling Models and the AEM developers must provide a Sling Model pojo for each component that is exported.
To understand how to consume AEM content services from a React application, see Get Started with AEM Content Services tutorial.
Also, if the developers want to export a tree of components they can also implement the ComponentExporter and ContainerExporter interfaces as well as use the ModelFactory to iterate over the child components and return their model representation. See the resources below:
You can opt into usage statistics collection by using either the Touch UI or the Web Console. For detailed instructions, see Opting into aggregated usage statistics collection.
Please refer to Understanding Reasons to Upgrade AEM that describes high-level breakdown of key features for customers considering upgrading to the latest version of Adobe Experience Manager.
PorterStem filter applies the Porter Stemming Algorithm for English. The results are similar to using the Snowball Porter Stemmer with the language="English" argument. But this stemmer is coded directly in Java and is not based on Snowball. It does not accept a list of protected words and is only appropriate for English language text.
Oak exposes a set of lucene-provides analyzer configuration elements for use in AEM. To learn how to use filters, please refer to Apache Oak Analyzers in Simple search implementation guide.
Re-indexing should always be approached with proper consideration on its impact to AEM's overall performance, and performed during periods of low activity or maintenance windows.
Please refer to the Best Practices for Queries and Indexing to understand the reasons for re-indexing.
You need to change the JS processor default configs property of the Adobe Granite HTML Library Manager to min:gcc. To import the Design Package successfully, it is recommended to include pre-minified 3rd party libraries in our Client-Side Libraries.
Where to find list of all the functionalities that are only working in Touch UI and not in Classic UI?
Starting with version 6.0, AEM introduced a new user interface referred to as the "touch-enabled UI" (also known simply as "touch UI") that is aligned to the Adobe Marketing Cloud and to the overall Adobe user interface guidelines.
Refer to Touch UI Feature Status that shows the current status of the capabilities as implemented in AEM 6.4.
Why the Assets workflow repeats itself while uploading MP4 files (for example, using drag-and-drop method)?
If the user, uploading the movie files does not have delete permissions under asset node, the delete chunk nodes fail and the upload restarts.
Adobe Experience Manager (AEM) 6.4 currently lets you upload up to 2 GB of assets at a time.
For additional information on maximum number of assets that can be operated with AEM 6.4, see Assets sizing guide.
When creating language copies through classic UI, Assets are not moved under the new language hierarchy but used from the language master.
Whereas, when you create a language copy through Touch UI (References -> Update Language Copy), a new DAM folder is created under the new language and assets are referenced from there.
This is default setting for OOTB configurations. You can set Translate Page Assets = Do not translate in Translation configurations.
For AEM 6.4, Tools > Cloud Services > Translation Cloud services.
You can disable the OSGi Component Disabler. To use this service, see OSGi Component Disabler.
As a workaround, you can also manually disable the component either via the UI or via a curl command (example below), after every AEM restart.
curl -u admin:$(pass CQ_Admin) 'http://localhost:4502/system/console/components/com.day.cq.analytics.sitecatalyst.impl.importer.ReportImporter' --data 'action=disable'
To setup and configure Asset Insights for Experience Manager deployed via Adobe Activation (DTM), please refer to Set up Asset Insights with AEM Assets.
AEM provides various mechanisms to enable you to customize the consoles and the page authoring functionality of your authoring instance. To learn how to create a custom console and customize a default view for a console, please refer to Customizing the Consoles.
A new set of Sling components of Granite UI Foundation is created for Coral3 and is located under /libs/granite/ui/components/coral/foundation. There is one set for CoralUI 2-based components and one set for CoralUI 3-based components. The new set will not be just a copy-paste of the old set, rather it will be cleaned up (for example streamlining, removing deprecated feature). So it is recommended that a page only use either CoralUI 3-based or CoralUI 2-based set.
To learn more in detail, please refer to Migration Guide to CoralUI 3-based.
To learn about search boost/ranking and further implementation information, please refer to Simple search implementation guide.
The Simple search implementation are the materials from the 2017 Summit lab AEM Search Demystified.
No, the customer cannot access Assets (or anything other than Sites). Even though all of Adobe Experience Manager (AEM) On-premises is included in the JAR, the customer is authorized access to only those components in the JAR for which they are licensed in their contract. If they want to explore other components, they can either use the AEM trial program for up to 45 days or can sign a $0 Sales Order that authorizes them to evaluate (no production use) named components such as Assets.
Please refer to the following resources to learn more about AEM On-premise software and Adobe Managed Services: