Resolved | ATG 11.1 CRS TargetingException No value for the targeter parameter

After ATG 11.1 CRS Setup. Home page targeter section was blank.

Here is exception from log : TargetingException No value for the targeter parameter

CRS Blank Page

Solution : Start NoPublishing submodule [ADD Store.Storefront.NoPublishing in ATG module list in dynamo.env].

After this home page is displaying properly.

CRS Home Page

Resolved | ATG 11.1 CRS SetUp ATGJRE variable issue

While configuring CRS for ATG 11.1 encountered below issue.

ATGJRE Error

Solution : Set ATGJRE environment variable. Don't forgot to include java at the end of the path. Otherwise you will get error

ATGJRE Path Variable

Resolved | FATAL : Multiple root installs found

While deploying Discover electronics application [CAS based] using deployment template.

You may encounter below error.

FATAL : Multiple root installs found. Only one installer config file may have the update attribute unspecified or set to false.

Solution : You should enter N for the Install base deployment question.

Install base deployment? [Y/N] : N

Easily Test ATG REST API using HttpRequester

While implementing ATG REST WebServices, We need to test them. There are number of tools available to achieve this. Recently I have used HttpRequester, its a great tool.

Below are the key features of this tool.

• Easy to install (Available as addon to firefox).
• Simple User Interface.
• Preserves the history of request So that user can review or re-execute the request.

Here I am going to explain login\logout using HttpRequester. Sometimes we need to test functionality for registered user, to validate login flows. Using below steps user can login into application and then perform activities finally logout from system

Step 1 : Obtain the session identifier.

Call /atg/rest/SessionConfirmationActor/getSessionConfirmationNumber actor chain. This will return the session identifier.

Session Confirmation Request

Session Confirmation Response

Step 2 : Pass this session identifier in further requests using _dynSessConf request parameter.

Login Request

Note : For logout call also you need to use the same identifier.

Logout Request

Below is the Request history window. Here double click on any request, pop up will appear to re-execute the request.

HttpRequester Request History Window

Endeca | Expression Record Manipulator

In Endeca record manipulators are used to change the data associated with record during indexing. 
There are 3 types of manipulators available.

1. Perl Manipulators
2. Java Manipulators
3. Record (Expression) Manipulators

Here we will learn how to configure  Record (Expression) Manipulators.

Below are the steps to configure Record (Expression) Manipulators.

1. Open Endeca project in developer studio.
2. Right Click on pipeline editor select New then Record followed by Manipulator.

 3. In Pop up box enter record manipulator name and record source details.

4.  Double click on newly created manipulator. You will see the below expression editor window.

Now create the expressions as per requirement. Below is the example of expression to create new property based on the value of existing property.

Below algorithm used in this example expression.
if value of Dep_ID property is 123
    then create new property named Location with value Delhi
else if value of Dep_ID property is 456
    then create new property named Location with value Bangalore
else
    then create new property named Location with value Pune 

====================================================================
<EXPRESSION LABEL="" NAME="IF" TYPE="VOID" URL="">

  <EXPRESSION LABEL="" NAME="MATH" TYPE="INTEGER" URL="">
    <EXPRNODE NAME="TYPE" VALUE="STRING"/>
    <EXPRNODE NAME="OPERATOR" VALUE="EQUAL"/>
    <EXPRESSION LABEL="" NAME="IDENTITY" TYPE="PROPERTY" URL="">
      <EXPRNODE NAME="PROP_NAME" VALUE="Dep_ID"/>
    </EXPRESSION>
    <EXPRESSION LABEL="" NAME="CONST" TYPE="INTEGER" URL="">
      <EXPRNODE NAME="VALUE" VALUE="123"/>
    </EXPRESSION>
  </EXPRESSION>

  <EXPRESSION LABEL="" NAME="CREATE" TYPE="VOID" URL="">
    <EXPRNODE NAME="PROP_NAME" VALUE="Location"/>
    <EXPRESSION LABEL="" NAME="CONST" TYPE="STRING" URL="">
      <EXPRNODE NAME="VALUE" VALUE="Delhi"/>
    </EXPRESSION>
  </EXPRESSION>

  <EXPRNODE NAME="ELSE_IF" VALUE=""/>

  <EXPRESSION LABEL="" NAME="MATH" TYPE="INTEGER" URL="">
    <EXPRNODE NAME="TYPE" VALUE="STRING"/>
    <EXPRNODE NAME="OPERATOR" VALUE="EQUAL"/>
    <EXPRESSION LABEL="" NAME="IDENTITY" TYPE="PROPERTY" URL="">
      <EXPRNODE NAME="PROP_NAME" VALUE="Dep_ID"/>
    </EXPRESSION>
    <EXPRESSION LABEL="" NAME="CONST" TYPE="INTEGER" URL="">
      <EXPRNODE NAME="VALUE" VALUE="456"/>
    </EXPRESSION>
  </EXPRESSION>

  <EXPRESSION LABEL="" NAME="CREATE" TYPE="VOID" URL="">
    <EXPRNODE NAME="PROP_NAME" VALUE="Location"/>
    <EXPRESSION LABEL="" NAME="CONST" TYPE="STRING" URL="">
      <EXPRNODE NAME="VALUE" VALUE="Bangalore"/>
    </EXPRESSION>
  </EXPRESSION>

  <EXPRNODE NAME="ELSE" VALUE=""/>

  <EXPRESSION LABEL="" NAME="CREATE" TYPE="VOID" URL="">
    <EXPRNODE NAME="PROP_NAME" VALUE="Location"/>
    <EXPRESSION LABEL="" NAME="CONST" TYPE="STRING" URL="">
      <EXPRNODE NAME="VALUE" VALUE="Pune"/>
    </EXPRESSION>
  </EXPRESSION>

</EXPRESSION>
=====================================================================

5. Edit other pipeline component to use this manipulator as record source.

6. Save the Endeca project and run the baseline. Below is the example data indexed using configuration.

ATG - Endeca | Understanding Assembler Architecture

Here I am going to explain how assembler works behind the scenes.

Few key points about assembler.
1. Accepts Content Item in request.
2. Populates and returns response Content Item. 

Assembler

In ATG-Endeca Integration Assembler can be invoked using one of the three ways.
1. InvokeAssembler Droplet [When portion of page is rendered using Assembler].
2. AssemblerPipelineServlet pipeline servlet [When complete page is rendered using Assembler].
3. Custom Droplet [Can be used to render complete or partial page using Assembler].

Here I will explain the assembler mechanism from invokeAssemler() method of the AssemblerTools. 
Below diagram explains this architecture.

Assembler Architecture

Explanation :
1. Application Invokes the invokeAssembler() method of AssemblerTools.
2. Invoke Assembler method calls NucleusAssemblerFactory.
3. NucleusAssemblerFactory returns NucleusAssembler instance.
4. AssemblerTools invoke assemble method of NucleusAssembler.
5. NucleusAssembler creates initial version of root and sub content response items. Here it uses the XML     configuration for content along Experience Manager modifications (From Endeca Configuration repository).
6. NucleusAssembler invokes cartridge handlers on root and each sub content items. Cartridge handlers are used to manipulate the content items.
7. NucleusAssembler return the response content item to AssemblerTools.
8. AssemblerTools return the response content item to Application.

MDEX | Revert Endeca Index to Particular Baseline

Follow below steps to revert\restore MDEX indexes to previous baseline update.

1. Stop the MDEX Engine.
2. Clean up dgraph_input and sub directories [Delete the content].
3. Copy the previous backup indexes from dgidx_output.<YYYY_MM_DD.HH_MM_SS> to dgraph_input directory.
4. Start the MDEX Engine. MDEX Engine reads the files in dgraph_input and its sub directories.

Here is the example.

1. Old baseline data

2. Latest indexed data

3. Restore the old indexed data using above steps