since ‎26-09-2019
‎17-03-2021
Anderson_Hamer
Level 3
Can AEM live copies have different domain in MSM?
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
In AEM, say for example we have live copies for US and Russia and French countries in MSM and they all want to have different domain for every live copies for example,For US - www.abc.com/en.htmlFor Russia - www.def.com/rus.htmlFor French - www.ghi.com/fr.html We may need to create separate vhost and dispatcher and sling mapping settings to achieve above but just want to know whether it is recommended in MSM and want to hear what are the issue would come if we have different domain for each live...

Views

118

Likes

0

Replies

2
Re: Can AEM share crypto library to other system?
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
Thank you. This really helped me to understand. Like you said we should go with asymmetric cryptography, the concept of public and private key pair

Views

110

Likes

0

Replies

0
Can AEM share crypto library to other system?
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
Basically in AEM I would want to encrypt some text using AEM CryptoSupport and pass the encrypted key to other system(say ABC system), then the ABC system to decrypt the key to do some action. AEM can share Adobe Granite Crypto Support 0.0.8 jar to ABC system to do encrypt/decrypt but I wonder how does AEM share HMAC and Master file to other system to decrypt? Is this possible ? Please advise.

Views

152

Likes

0

Replies

3
Re: NPE when mocking ConfigurationManager class in AEM
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
It works. Thanks for your reply

Views

113

Likes

0

Replies

0
NPE when mocking ConfigurationManager class in AEM
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
I am trying to write a Junit for the below java method in AEM public final Resource getConfigProp(final Page page, final ConfigType configType, final ResourceResolver resolver) { final HierarchyNodeInheritanceValueMap iProp= new HierarchyNodeInheritanceValueMap( page.getContentResource()); iPropString[] services = inheritedPageProperties.getInherited(configType.PN_CONFIGURATIONS, new String[0]); final com.day.cq.wcm.webservicesupport.ConfigurationManager configurationManager = resolver .adaptTo(...

Views

160

Likes

0

Replies

2
Re: Will static template be compatiable in AEM 6.5?
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
No, it is not mentioned in release note. Just wanted to confirm on this static template since AEM is going to depreciate classic UI, maybe starting from AEM 6.5.

Views

445

Like

1

Replies

2
Re: Will static template be compatiable in AEM 6.5?
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
Is this mentioned in adobe documentation ? if yes, can you please share it?

Views

471

Like

1

Replies

4
Guideline on migrating AEM 6.4 to AEM 6.5
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
We are planning to migrate from AEM 6.4 to AEM 6.5 with in-place upgrade. what are the key areas that we would need to give a focus during migration. Is there any guidance from adobe ?

Views

190

Likes

0

Replies

1
Will static template be compatiable in AEM 6.5?
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
I heard that static template is going to be depreciated and it will be no longer available in AEM 6.5 and it will compatible only with editable template. is that true? Basically I would want to know whether static template will be compatible in AEM 6.5 and also when Adobe is planning to deprecate it ?

Views

490

Likes

0

Replies

7
Re: Modify dialog value after dialog submission in AEM
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
Can this be done without a servlet ? there is no complex in backend. just want to prefix some hard coded value /hardcodevalue/{dialogvalue}

Views

390

Like

1

Replies

0
Re: Modify dialog value after dialog submission in AEM
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
No, I am not string the value in different location. same place with hard coded prefix value.

Views

394

Like

1

Replies

0
Modify dialog value after dialog submission in AEM
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
We want to get the input from page dialog(multifield) and add some prefix string(hardcode) before store the value in node. like /hardcodevalue/{dialogvalue} and store the value in node. Can we use any listeners to do this or what is the approach that should follow? please share any reference.

Views

582

Likes

0

Replies

6
Re: cq:allowedTemplates is not working with experience fragment in AEM 6.4.8
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
Yes, change allowedPaths value from /content(/.*)? to /content(yourProjectarea)?

Views

600

Like

1

Replies

0
Re: Modify dialog field value after submit
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
I have the similar requirement. Can you tell how have you done with afteredit or cq:listners?

Views

225

Likes

0

Replies

0
Yeah but this /vanity_urls filter is not the filtering th...
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
Yeah but this /vanity_urls filter is not the filtering the vanity URLs that get stored in /temp/vanity_urls file. I could see the vanityURLS in {dispurl}/libs/granite/dispatcher/content/vanityUrls.html What happens here is, if I hit the vanity URL like - {dispURL}/vanity1, then rewrite rule comes into picture and it is adding /content/myproject/vanity1 and sending a request to publisher, getting 404 page as there is no such page in pub server. The dispatcher would want to send the same request a...

Views

571

Like

1

Replies

2
Vanity url is not working with rewrite rule
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
We are trying to make the vanity url works on both publish and dispatcher servers. Download and installed the VanityURLS-Components package and followed all the steps that documented. The vanity url is working only when we delete or comment the below rewrite rule RewriteCond %{REQUEST_URI} !^/apps RewriteCond %{REQUEST_URI} !^/bin RewriteCond %{REQUEST_URI} !^/content RewriteCond %{REQUEST_URI} !^/etc RewriteCond %{REQUEST_URI} !^/home RewriteCond %{REQUEST_URI} !^/libs RewriteCond %{REQUEST_URI...

Views

662

Likes

0

Replies

6
Re: cq:allowedTemplates is not working with experience fragment in AEM 6.4.8
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
Thanks for your reply. allowedPath is not working at /content/experience-fragments level but it worked when I change regulr expression at the static tempalte level. making this change at 20+ template may not be a correct approach. Why cq:allowedTemplates & allowedPath props are not working at ef level? Is this a bug?

Views

702

Like

1

Replies

2
cq:allowedTemplates is not working with experience fragment in AEM 6.4.8
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
I see all my static templates while creating experience fragment. Checked the property cq:allowedTemplates on /content/experience-fragments, it contains /libs/cq/experience-fragments/components/experiencefragment/template/libs/settings/screens/experience-fragments/templates/experience-fragment-template-screens/conf/we-retail-screens/settings/wcm/templates/experience-fragment-screens-variation/conf/we-retail/settings/wcm/templates/experience-fragment(.*)? Only conf and libs templates should be sh...

Views

718

Likes

0

Replies

5
Re: Vanity url is not working with dispatcher in AEM 6.4
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
Yes, it resolved. Rewrite rules were causing the issue.

Views

782

Likes

0

Replies

1
Re: Unable to add component on segment and experience fra...
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
Yes, Aem gives only warning on this page. There is no error. Are you sure it is working with sp8?

Views

576

Likes

0

Replies

0
Re: Unable to add component on segment and experience fra...
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
I have already mentioned error logs above. Error logs - 25.06.2020 18:07:21.218 *WARN* [0:0:0:0:0:0:0:1 [1593088641140] GET /editor.html/conf/we-retail/settings/wcm/segments/test123.html HTTP/1.1] org.apache.sling.caconfig.resource.impl.def.DefaultConfigurationResourceResolvingStrategy Ignoring reference to /conf/we-retail/settings from /conf/we-retail/settings - Probably misconfigured as it ends with '/settings'

Views

600

Likes

0

Replies

0
Re: Unable to add component on segment and experience fra...
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
Yes, I restarted my AEM instance after installtion of service pack 8, tried restarting my entire machine. Note I tried to setup 3 AEM instances and all ended up the same problem

Views

669

Likes

0

Replies

0
Unable to add component on segment and experience fragment - AEM 6.4 with service pack 8
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
We can not add any component on segment page, the parsys does not have + button to add component and drag and drop is also not working. Tried to create a segment with new configuration and also with we.retail config, facing the same problem on both.Note - we have not overlay any component, it is just plain Vennila Instance + SP 8Segmentation page screen shotEven experience fragment also have the same problem, no + plus button and drag and drop is also not working.Experience fragment page screen ...

Views

754

Likes

0

Replies

6
Re: AEM 6.4 - Editable Template not allowing to add new component
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
I am facing this problem on segment and experince grament page . Can you pls tell me in detail to resolve this issue.

Views

535

Likes

0

Replies

0
Re: Vanity url is not working with dispatcher in AEM 6.4
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
Updated the dispatcher logs in description section

Views

11.6K

Like

1

Replies

0
Re: Vanity url is not working with dispatcher in AEM 6.4
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
Dispatcher logs- [root@disp-server-1:/path/path]# tail -f *.log | grep vanityUrls [Fri May 15 10:21:27 2020] [D] checking [/libs/granite/dispatcher/content/vanityUrls.html] [Fri May 15 10:21:27 2020] [D] cache-action for [/libs/granite/dispatcher/content/vanityUrls.html]: NONE [Fri May 15 10:21:27 2020] [I] "GET /libs/granite/dispatcher/content/vanityUrls.html?Ad3=3" 200 none [farm/rend01] 40ms 10.56.0.58 - - [15/May/2020:10:21:27 +0000] "GET /libs/granite/dispatcher/content/vanityUrls.html?Ad3=...

Views

11.5K

Like

1

Replies

0
Re: Vanity url is not working with dispatcher in AEM 6.4
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
Downloaded the package from package share - https://www.adobeaemcloud.com/content/marketplace/marketplaceProxy.html?packagePath=/content/companies/public/adobe/packages/cq600/component/vanityurls-components Package version - vanityurls-components-1.0.2 Is there any higher versions available?

Views

11.5K

Like

1

Replies

0
Re: Vanity url is not working with dispatcher in AEM 6.4
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
Hi Noksc - No, the dispatcher is not blocking this path. vanityUrls service is accessible even from dispatcher URL – https:/{disaptherDomain}/libs/granite/dispatcher/content/vanityUrls.html. I could also the Dispatcher is making call to AEM publisher, the response to this request is 200 as well. Allowing this path - /0100 { /type "allow" /url "/libs/granite/dispatcher/content/vanityUrls.html" } Not caching this path - /0001 { /type "deny" /glob "/libs/granite/dispatcher/content/vanityUrls.html" ...

Views

11.6K

Like

1

Replies

3
Vanity url is not working with dispatcher in AEM 6.4
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
I am trying to setup vanity url in AEM 6.4. Followed and verified the below stepsInstalled the VanityURLS-ComponentsAllowed ‘Read’ permission to /libs/granite/dispatcher/content/vanityUrls for the ‘everyone’ group on the publish serversAdded a filter rule in the dispatcher to allow the vanity URL/0100 { /type "allow" /url "/libs/granite/dispatcher/content/vanityUrls.html" }Added a caching rule to prevent caching of this URL/0001 { /type "deny" /glob "/libs/granite/dispatcher/content/vanityUrls.h...

Views

12.2K

Likes

0

Replies

9
Re: How to specify nested “not” operation in specific gro...
Avatar

Anderson_Hamer

Anderson_Hamer
- Adobe Experience Manager
No, it is not applying operator on given group id. Posted solution, Please check it

Views

3.5K

Likes

0

Replies

0