Tech Mastery: Deep Dives into AEM, Cloud Technologies, AI Innovations, and Advanced Marketing Strate

IndexConnector prefetch failed - Adobe Search and Promote 

Index Connector can be used to define additional input sources for indexing XML pages or any kind of feed.

The  Index Connector is not enabled in the Search and Promote account by default, the  Index Connector can be only enabled by reaching out to Search and Promote consultant or support team.


After enabling the Index Connector the regular indexing stopped working with the following exception.

1: 12/14 13:10:14 CST ======== Starting manual crawl of account spxxxxxx. ========
2: 12/14 13:10:14 CST ERROR: IndexConnector prefetch failed.
3: 12/14 13:10:15 CST Starting update of slice list.
4: 12/14 13:10:15 CST Skipping update of slice list - no change since last update.
5: 12/14 13:10:15 CST Refreshing auto-complete word list.
6: 12/14 13:10:15 CST Finished refreshing auto-complete word list.
7: 12/14 13:10:15 CST Creating GS config.
8: 12/14 13:10:15 CST Finished creating GS config.
9: 12/14 13:10:15 CST --------------------------------------------------------------------
10: 12/14 13:10:15 CST *** Crawl Summary ***
11: 12/14 13:10:15 CST Start Time: 12/14/2017 13:10:14 CST
12: 12/14 13:10:15 CST End Time: 12/14/2017 13:10:15 CST
13: 12/14 13:10:15 CST Elapsed Time: 1 second
14: 12/14 13:10:15 CST Pages Crawled: 0 pages
15: 12/14 13:10:15 CST Words/Bytes Indexed: 0 words/ 0 bytes
16: 12/14 13:10:15 CST Depth: 1
17: 12/14 13:10:15 CST Errors: 1
18: 12/14 13:10:15 CST Starting update of slice list.
19: 12/14 13:10:15 CST Skipping update of slice list - no change since last update.
20: 12/14 13:10:15 CST *** Index Summary ***
21: 12/14 13:10:15 CST Total Pages: 278
22: 12/14 13:10:15 CST --------------------------------------------------------------------
23: 12/14 13:10:15 CST ======== Finish manual crawl of account spxxxxx: Aborted. ========

This will be fixed after enabling at least one Index Connector configuration, if the actual Index Connector Configuration can't be created then create a dummy configuration with disabled status that will fix the indexing issue.

Different approaches to integrate Adobe Experience Manager(AEM) with Eloqua

This post will explain the different approaches to integrate Adobe Experience Manager(AEM) with Eloqua to capture the user data.

Eloqua Landing Page:

Define a Landing page in Eloqua with requred form fields and action, redirect the user to the Landing page from AEM whenever required to capture the data.User data will be directly submitted to the Eloqua without any interaction from AEM.

In this approach while defining the Landing page in Eloqua the look and feel of the landing page should be matched with AEM pages look and feel for better user experience.

Refer the following URL to more details on defining a landing page -
https://docs.oracle.com/cloud/latest/marketingcs_gs/OMCAA/Help/LandingPages/Tasks/CreatingNewLandingPagesDesignEditor.htm

Submit the data through Eloqua form - Directly to Eloqua Form Action URL:

Define the form in Eloqua with required fields, place the form in a AEM component- change the look and feel accordingly.

How to display the Google Adsense at the bottom of the page in mobile view?

Sometimes we may required to display the specific ad only in the mobile view at the bottom of the page. This post will explain the approach to display the adsense ads at the bottom of the page in mobile view.

 Enable Custom template for Mobile view: 

 Make sure the custom template for the mobile view is selected

 Enable adsense at the bottom of the page in mobile view: 

 Add a HTML/JavaScript widget at the bottom of side bar


 Add the google adsense script in the widget
 Identify the the widget id of the new widget added



 Save the widget and the Layout arrangement

 Go to Blogger Dashboard > Theme > EDIT HTML

Locate widget with the widget id and add mobile='only' configuration as shown below - this will make sure this widget will be displayed only in mobile view

  <b:widget id='HTML6' locked='false' mobile='only' title='' type='HTML'>
 
 
  Save Theme
 
  This will display the add at the bottom of the blogger mobile view.
  You can how test if the Google Adsense is displaying at the bottom of the blogger mobile view

How to display the Google Adsense between blogger posts in mobile home page view?

 This post will explain the approach to display the adsense ads between posts in mobile home page view.

 Enable Custom template for Mobile view:

 Make sure the custom template for the mobile view is selected

 Add adsense between posts in mobile home view: 

Go to Blogger Dashboard > Theme > EDIT HTML

 Locate <b:include data='post' name='mobile-index-post'/>

 Replace

 <b:loop values='data:posts' var='post'>
    <b:include data='post' name='mobile-index-post'/>
 </b:loop>
 
  With
 
  <b:loop index='x' values='data:posts' var='post'>
    <b:include data='post' name='mobile-index-post'/>
  <b:if cond='(data:x+1)%2==0'>  
  <!-- Add adsense code here -->  
</b:if>
  </b:loop>
 
  Save Theme
 
  This will display the add after every two posts in the blogger mobile home view - Change the condition based on your requirement
 
  You can how test if the Google Adsense is displaying between the posts in mobile home view.

Flush the dispatcher cache for dam assets used on multiple websites through ACS AEM Commons - Dispatcher Flush Rules

Some cases, the same DAM asset is used on multiple websites(Domains) and the individual websites caches the assets locally, the regular replication agent configuration will not clear the cache for all the websites that use the common DAM asset.

This post will explain the approach to flush the dispatcher cache for common DAM assets used om multiple websites through ACS AEM Commons - Dispatcher Flush Rules - Adobe Experience Manager(AEM).

Install acs-aem-commons-content-3.9.0.zip package(ignore if it is already available):

ACS commons package download link:
https://github.com/Adobe-Consulting-Services/acs-aem-commons/releases/tag/acs-aem-commons-3.9.0
 

Configure the ResourceOnly Flush agent in publisher:

Create the Flush agent in publisher with following configuration