since ‎30-11-2017
‎28-09-2020
Ashish_Ranjan1
Level 2
Secure Page Authoring Capabilites Ashish_Ranjan1 - Adobe Experience Manager Assets
Hello Team, We have a requirement where we there are few product detail pages which needs to secured for some sensitive authoring which shouldn't be know to many till go-live. Step wise details below: Suppose standard we -retail MSM structure is followed and we have a product detail page like /content/xyz/language-masters/en/products/product1 . There also exists a published livecopy of the same as /content/xyz/us/en/product1.htmlNow there is some sensitive content to be added on the page which o...
121
Views
0
Likes
1
Answers and Comments
jcr:isCheckedOut Property set to true on using AssetManager createOrUpdateAsset method Ashish_Ranjan1 - Adobe Experience Manager Assets
We are programmatically trying to create/update assets . Code looks like below: Asset asset = assetManager.createOrUpdateAsset(path, assetBinary, documentMimeType, true); Now the first time asset gets created. If the asset is updated using the same method it is adding jcr:isCheckedOut = true. As per https://docs.adobe.com/docs/en/spec/jcr/1.0/8.2.6_Check_Out.html documentation this property states that the node is checkedOut while its versions are created/updated. Can we get clarity if this prop...
120
Views
0
Likes
0
Replies
Re: AEM Publisher throwing maintenance exception in logs Ashish_Ranjan1 - Adobe Experience Manager
This is happening in AEM 6.5.2 . Due to this request combined with ACS Commons we noticed that The call that AEM is getting, that call in itself is 404 always, checked it on vanilla server. Since the call is 404, it would invoke your error handler JSP.. and the vanity check code is throwing some code error, when the incoming URL pattern is: /libs/granite/operations/config/maintenance/granite:daily.infinity.json So we had to wrap the 404.jsp to catch the exception.
3857
Views
0
Likes
0
Comments
Re: AEM Publisher throwing maintenance exception in logs Ashish_Ranjan1 - Adobe Experience Manager
Yes these are frequently in our logs. And due to this request combined with ACS Commons we noticed that The call that AEM is getting, that call in itself is 404 always, checked it on vanilla server. Since the call is 404, it would invoke your error handler JSP.. and the vanity check code is throwing some code error, when the incoming URL pattern is: /libs/granite/operations/config/maintenance/granite:daily.infinity.json So we had to wrap the 404.jsp to catch the exception.
2186
Views
0
Likes
0
Comments
Re: AEM Publisher throwing maintenance exception in logs Ashish_Ranjan1 - Adobe Experience Manager
Yes these are frequently in our logs. And due to this request combined with ACS Commons we noticed that The call that AEM is getting, that call in itself is 404 always, checked it on vanilla server. Since the call is 404, it would invoke your error handler JSP.. and the vanity check code is throwing some code error, when the incoming URL pattern is: /libs/granite/operations/config/maintenance/granite:daily.infinity.json So we had to wrap the 404.jsp to catch the exception.
2104
Views
0
Likes
0
Comments
AEM Publisher throwing maintenance exception in logs Ashish_Ranjan1 - Adobe Experience Manager
We have two AEM Publishers and the below exception is continuously thrown on both the publishers. 29.04.2020 16:50:21.804 *INFO* [qtp279028224-11690] log.request 29/Apr/2020:16:50:21 +0000 [130007] -> GET /libs/granite/operations/config/maintenance/granite:daily.infinity.json HTTP/1.1 The maintenance jobs for daily and weekly is configured and working fine. Any other reason why this might be happening?
6264
Views
0
Likes
7
Answers and Comments
Enable XMP Extraction and write-back on Ubuntu Ashish_Ranjan1 - Adobe Experience Manager
Hello All,Are there any recorded steps to enable xmp extraction and write-back on ubuntu as there are steps for Red-Hat Linux server (Enable XMP extraction and write-back on 64-bit Linux ) ?XMP extraction & write-back is not working on ubuntu.Thanks in AdvanceAshish Ranjan
817
Views
0
Likes
0
Replies
Re: redirect to a content page in aem servlet Ashish_Ranjan1 - Adobe Experience Manager
Are you trying to achieve this from a button in Granite UI dialog?
4422
Views
0
Likes
0
Replies
Permanent Links for DAM Assets Ashish_Ranjan1 - Adobe Experience Manager
Hello All,We have a requirement where we have to expose a permanent link for every DAM Asset which should not change even on Asset Update or Asset Move ? This link will be used for integration with external CMS for e.g. Wordpress and Adobe DAM is used as Digital Asset Management System.Is there something available OOTB? One possible solution what we have thought is generating a unique id for each asset on asset upload, store it as metadata and construct the Asset Url using the same and upon each...
1210
Views
0
Likes
2
Answers and Comments
Re: Need to add one custom button besides move button in dam admin Ashish_Ranjan1 - Adobe Experience Manager
Hello,Please use Sling Resource Merger to achieve this.Some useful links below:-Using the Sling Resource Merger in AEM http://www.aemcq5tutorials.com/tutorials/sling-resource-merger-in-aem/ Using this you can achieve something like belowThanks & RegardsAshish Ranjan
1057
Views
1
Like
0
Answers
Re: DAM Video Asset Version Creation Ashish_Ranjan1 - Adobe Experience Manager
Hello Tuhin,Thanks for the answer but I found the cause and solution to the above issue. Basically Asset Update Workflow is running and the metadata writeback step has the code to create versions and the configuration is maintained via the Ncomm XMP Handler.So if we add the video format to com.day.cq.dam.core.impl.handler.xmp.NCommXMPHandler versions start getting created. Also this issue is not only with Videos but also xlsx, pptx etc, basically any format not mentioned in the supported formats...
1138
Views
0
Likes
0
Answers
DAM Video Asset Version Creation Ashish_Ranjan1 - Adobe Experience Manager
Hello All,OOTB whenever we upload/modify metadata for images, pdf etc version gets created but it doesn't happen in case of video. Can anyone help us understand why?Moreover if I create a workflow with the step Create Version it works fine but if I add it to the DAM Update Asset (ffmpeg configured) it doesn't work fine. I have also checked that there is launcher as below :-However even if I satisfy the condition dam:scene7FileStatus==NeedsReupload , versions are not creating , rest everything is...
1608
Views
0
Likes
2
Answers and Comments
Re: Dispatcher- publisher System/console is giving 500 error. Ashish_Ranjan1 - Adobe Experience Manager
Ideally the deny everything rule should work. Below is a sample filters.any which works fine to deny access to any request to /system/*. # Deny everything first and then allow specific entries/0001 { /type "deny" /glob "*" }# Open consoles# /0011 { /type "allow" /url "/admin/*" } # allow servlet engine admin# /0012 { /type "allow" /url "/crx/*" } # allow content repository# /0013 { /type "allow" /url "/system/*" } # allow OSGi console# Allow non-public content directories# /0021 { /type "allow" ...
1111
Views
0
Likes
0
Answers
Re: Give us your 2019 Ask the AEM Community Expert Session ideas Ashish_Ranjan1 - Adobe Experience Manager
A working session on best practices to integrate Adobe Recommendation using Adobe I/O API to consume recommendation data through backend. Information to track DAM workflows progress/steps through DTM to capture information.
15673
Views
1
Like
0
Replies
GLOBALLINK-TRANSLATION-CONNECTOR for AEM 6.4 Ashish_Ranjan1 - Adobe Experience Manager
Hello Experts,Is there a GLOBALLINK-TRANSLATION-CONNECTOR package available for AEM 6.4? I could only find connector the latest package (Package Id: translations:GLOBALLINK-TRANSLATION-CONNECTOR:2.2.0) which is for AEM 6.2 & AEM 6.3 ?If not can I use this for even AEM 6.4?Thanks & RegardsAshish Ranjan
1581
Views
0
Likes
2
Answers and Comments
ACS Commons Shared Component Properties Ashish_Ranjan1 - Adobe Experience Manager
Hello All,I am using Shared Component in my site but have few questions which are as follows:-The site hierarchy of my site is /content/moduleName/en and the same is specified as the root page for Shared Component too. Hence the shared properties are stored on the node /content/moduleName/en/jcr:content/shared-component-properties and global properties on the node /content/moduleName/en/jcr:content/global-component-properties . Now if I edit the shared component on a page under /content/moduleNa...
1388
Views
1
Like
1
Answers and Comments
Likes from