How to Set Up and Configure the Adobe Experience Manager Connector

All BA Insight connectors can be downloaded from the Upland Right Answers Portal under Knowledge > BA Insight > Product Downloads > Connectors. This connector is installed with the same generic steps as any BA Insight connector. You must satisfy the Prerequisites for your connector before installing. The configuration specifics are detailed below.

Create Connection

Open Connectivity Hub in a local browser. If you are using the server Connectivity Hub is installed on, the address is:
- https://localhost:port
- 55001 is the default local port
Navigate to the Connections page.
Edit your connection Connection defines the how Connectivity Hub connects to your Source System (which contains your documents, graphics, etc.,). Your Connection includes identifying elements such as: URL of the BA Insight web service connector you are using, (File Share connector, SharePoint Online connector, etc.), Authentication mode, User Accounts and Credentials, Database information (for database connectors) settings.
1. If you do not have an Adobe Experience Manager connection, create one by a creating a new Web Service connection.
2. Read and enter values (or enter check mark) into all available fields.
  1. Crawl User:
    1. Name of the user created to crawl the content
    2. User must have all required permissions
  2. Password:
    1. Password of the crawl user
  3. Adobe Experience Manager Url:
    1. URL Adobe Experience Manager can be reached over the network
  4. Root Folder Paths:
    1. Paths of nodes in the repository
      - One path per line
    2. Content is crawled under the folders of sites specified here
  5. Custom User/Group Properties:
    1. Repository may contain additional information about users and groups, as synchronized by the Adobe Experience Manager.
    2. Properties specified here are retrieved during the security sync Loads User and Group tables and executes the mapping based on the connector configuration. job, and can be used in security scripts to match to users and groups in the Target A Target is a "pointer" to a specific instance of a search application, such as Elasticsearch. - (A Search application instance has one or more indexes) directory.
  6. Advanced Settings:
    1. Use this parameter to provide the following settings:
      1. Attachments Node Path:
        If a custom property is defined in AEM containing one or more paths to other items, then the referenced ones are handled as attachments.
        A page, for example, may be related to one or more assets.
        Using this feature a page can be retrieved in search results if the hit is in an attachment.
        Example: jcr:content/jcr:attachments
      2. Token Authentication Endpoint:
        Relative part of the endpoint url to get authentication token.
      3. Query Builder Endpoint:
        Relative part of the endpoint url to call Query Builder API
      4. Item Data Query Parameters:
        You can filter items by the "property" predicate.
        For example, to filter assets for PDF files only, enter the following:
        Copy
        group.property=jcr:content/metadata/dc:format group.property.value=application/pdf
        Any additional parameter you wish to send to AEM when retrieving metadata Provides context with details such as the source, type, owner, and relationships to other data sets. Metadata provides details around the item being crawled by Connectivity Hub. for the entity indexed.
        You can use this to send additional parameters to a custom AEM extension for example.
        (For additional details like case sensitivity, please check the AEM Query Builder API documentation.)
        Example: p.nodedepth=-1
  7. Authentication type:
    1. Select the type of authentication used by the connector while connecting to Adobe Experience manager.
    2. Supported types are:
      1. basic authentication
      2. token-based authentication

Click the Save button at the top of the page.
Navigate to Content Sources.
Select New>Web service content using the drop-down menu.
The Wizard appears.
Follow the wizard to configure your Connection and Target.

Content Configuration Specifics

In content type the specified filter can be set to crawl digital assets, sites or both.

Custom filters support the syntax of Query Builder API documented here:

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/full-stack/search/query-builder-api.html

The content filter can be used to split larger AEM content to smaller content sources.
To filter each content source Content Sources do the following: Receive data from the Source System via the Connection, Filter the data it receives, Provide the results to the Target, Define the specific search index that contains the content you wish to index (and later search). to a specific date range based on the create date, use the following:

Copy

group.daterange.property=jcr:created
group.daterange.lowerBound=2021-01-01
group.daterange.upperBound=2021-12-31

Using group.property or group.[n]_property (where n is 1,2...) under Custom filters is not advised. It should be used under Connection > Advanced settings > ItemDataQueryParameters instead. For more information, see step 3 in the Create Connection section above.