Adobe Experience Manager (AEM) connector for search engines
February 26, 2019
Adobe Experience Manager (AEM) is a robust content management system for creating websites and companion digital applications, such as mobile apps and web communities, in an integrated way.
For businesses with key content residing in AEM, it’s critical to have an effective solution to make content in AEM, both on-premises and in the cloud, accessible and searchable.
<<< Start >>>
<<< End >>>
The Adobe Experience Manager connector is the newest addition to our growing range of connectors designed to support secure data connectivity between search engines and third-party repositories.
Similar to our search engine independent connectors, the AEM connector works with a wide variety of search platforms, from open source like Elasticsearch and Solr to commercial solutions like Azure Search, SharePoint Search, Endeca, and others. Organizations can leverage the AEM connector to crawl their websites and digital assets within an AEM server and publish them to their existing search engines. This allows all search tasks to be completed within the search engine, reducing the AEM server’s processing load and enabling a range of search functionalities, from basic to advanced.
Accenture's AEM connector includes the following pre-built features:
- Supports full and incremental crawls of websites and assets documents in AEM
- Supports basic and form authentication
- Enables closed users and groups to allow the right users or groups to securely access the documents intended for them
- Filters the crawled documents based on properties using expected values or patterns. Because each object has different properties, the connector can filter out which documents to crawl based on those properties. The administrator can pass the name of a property and its expected value or pattern. The connector will then check for that value in each document and determine if the document is excluded from or included in the crawl. For example, an organization may have documents with certain priorities that it would want to crawl while excluding others from the crawl.
- Allows for more flexibility as specific content paths from the AEM server can be used to crawl
- Supports throttling mechanisms to manage the number of requests in a specific time period, enabling the connector to make multiple requests to the AEM server without impacting its performance and availability
