Rajashankar's Blog

 1.      Purpose Below approach will help the customers use the ID service on applications that does not support 1.            No Support for Adobe Launch or SDK or VisitorApi.js 2.            No Support for Adobe Launch or SDK but support for visiotrapi.js   2.      Methodologies ECID can be extracted using below methodologies 2.1 Direct trigger of API to fetch ECID(No Support for Adobe Launch or SDK or VisitorApi.js) We can fetch the ECID by directly triggering an http get to below DCS url of adobe along with corresponding Org ID.   Example: var org_id="-----------AdobeOrg";   "https://dpm.demdex.net/id?d_visid_ver=5.2.0&d_fieldgroup=MC&d_rtbd=json&d_ver=2&d_verify=1&d_nsid=0&d_orgid="+org_id; https://dpm.demdex.net/id?d_visid_ver=[VER]&d_fieldgroup=MC&d_rtbd=json&d_ver=2&d_verify=1&d_nsid=0&d_orgid=[ORGID]&ts=[TS]   ·   [VER] is the version of the JavaScript library you are trying to use. When I was testing this

  Use Case:   As per regular pattern we bind a service interface for service implementation but there might be certain use cases for which we need to bind Service Interface to a Specific Implementation Class at run time as shown below.  This can be achieved using any of the following three methods depending upon our use case.   Options: 1)    Default mapping via Service ID By Default System will do the mapping to Service ID which is created First. In the above example since the Service Impl A is created First so it binds to A(Whose service ID is 8378 in this case when compared to service id for Impl B which is 8380). Refer below for Binding by Service ID.   2)    Mapping using Service Ranking In this option we can set specific service Ranking for each of the component implementing the service as shown below.In this case component implementation which has highest(Largest number) rank gets invoked.   Example: //Option 2 Binding by using Service Ranking w

  Adobe AEM Embedding Third Party Jar as Bundle   Options: 1.       Eclipse Plugin Project to convert Jar into Bundle with manifest file 2.       Install along with AEM application using Maven Embed     Note: In the below given example I am using my custom Adobe AEM application which needs a third party jar file “jsoup.jar” in my case. I used archetype 27 for building this maven sample aem project.In your case it can be any third party Jar file required to integrate with Adobe AEM. 1.      Eclipse Plugin Project Step1: Open Eclipse IDE and select File -> New à Other à Plugin from Existing JAR Archives Step 2: In the next pop select external Jar as shown below and navigate to the downloaded third party jar in your local from maven repository.   Step 3: Provide project details as shown below for the new jar added Click Finish. It might take  some time couple of minutes to build project depending on your JAR size.   Step 4: Now in Overview Select the Man