Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

StevenRymenans
Community profile StevenRymenans Level 2
Job title here
Belgium
9 BADGES
Level 2

Level 2

Learn more
Joined the community 03-12-2015 1:06:56 PM
Online
Top badges earned by StevenRymenans
Customize the badges you want to showcase on your profile
Personalization Offer in AEM 6.5
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager
Hi, I'm trying to get the Offers in AEM to work in combination with the AEM target component (/libs/cq/personalization/components/target) to display banners on fixed locations based on the configuration of an on-off time in the Offers.But it seems as if this functionality is really outdated, the TeaserPage (/libs/cq/personalization/components/teaserpage) doesn't even have a touch ui dialog that allows the author to change the location. And the TargetedContentManager does not return the offers th...

Views

398

Likes

0

Replies

0
Re: Create sub assets throws nullpointer
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager Assets
The issue was resolved by opening and saving the configuration of the CQ DAM Buffered Image Cache.

Views

749

Likes

0

Replies

0
Create sub assets throws nullpointer
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager Assets
We are using the workflow to 'Dam Update Asset' to create renditions for all the new assets that are added in AEM.And since yesterday we see the following error appearing in the log files:18.07.2017 07:24:15.270 *ERROR* [JobHandler: /etc/workflow/instances/server1/2017-07-18/model_6797382541536:/content/dam/test/homepage/2017/06-19/homepage-logo.png/jcr:content/renditions/original] com.day.cq.workflow.compatibility.CQWorkflowProcessRunner Process execution resulted in an error: nulljava.lang.Nul...

Views

976

Likes

0

Replies

1
Re: Issues after upgrade from AEM 6.1 to AEM 6.3
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager
I found the issue, I skipped a step in the upgrade documentation.I did not run the unpack of the new version of the AEM jar. After changing that, the upgrade worked perfectly.

Views

4.5K

Likes

0

Replies

0
Re: Issues after upgrade from AEM 6.1 to AEM 6.3
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager
Hi,No after the upgrade I don't see the system user(s).However we did follow the migration steps and it does not mention adding additional users.Are there still steps to need to be executed after the upgrade?

Views

4.5K

Likes

0

Replies

0
Issues after upgrade from AEM 6.1 to AEM 6.3
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager
After following the documentation on : Upgrading to AEM 6.3​ , we have successfully migrated the repository from 6.1 to 6.3, however when we restart AEM we see a few errors in the log file.Example:09.07.2017 14:14:09.219 *WARN* [Shell Script Executor Thread for diskusage.sh] org.apache.sling.jcr.resource.internal.JcrSystemUserValidator The provided service user id 'monitoringScripts' is not a known JCR system user id and therefore not allowed in the Sling Service User Mapper.09.07.2017 14:14:09....

Views

7.6K

Likes

0

Replies

5
Re: AEM 6.1 doing full reindex of oak:index on startup and causing very slow startup
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager
Hi,I logged a daycare ticket and hope they will have a look soon, at the moment the indexes on startup are really causing issues on our production system.We are using AEM 6.1 with oak version Oak 1.2.11 (we installed Hotfix 7700) We are using offline tar compaction, that runs at night.Kind regardsSteven

Views

3.1K

Likes

0

Replies

1
AEM 6.1 doing full reindex of oak:index on startup and causing very slow startup
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager
Hi,We have an AEM 6.1 running with multiple websites and every night we run tar compaction. When tar compaction finishes we often get SegmentNotFound exceptions in our log file and have to roll back (manually by changing the journal.log). When I roll back the changes AEM starts reindexing the /oak:index/ entries and takes hours to start.What could cause the segment not found exceptions after tar compaction? And how do I have to change the /oak:index/ entries to make sure that the startup time do...

Views

3.4K

Likes

0

Replies

3
Configure dispatcher for permission-sensitive caching - Using an external service
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager
Hi,I followed the documentation on https://docs.adobe.com/docs/en/dispatcher/permissions-cache.html to configure the auth_checker to check the permissions. When I check the dispatcher log I see that the authentication checker is used, but the url is always called on the publish instance. Is it possible to use an external service to validate the permissions?I want to use an external service, because AEM doesn't contain the users session information.Kind regards

Views

694

Likes

0

Replies

1
Fixed name for truststore alias
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager
Is it possible to provide a fixed alias name for a certificate that is upload to the truststore instead of an autogenerated name?

Views

446

Likes

0

Replies

0
Re: Sling:alias not working on dispatcher
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager
Another update: I debugged the sling engine code to determine when the alias was resolved and the sling code tries several strategies to resolve the content node, one of them is starting at the root node ('/') and adding everything until the path is resolved or an alias is found in the aliasMap. Granting the anonymous user access to root ('/') solves the issue.I should add that the hotfix cq-6.1.0-hotfix-7700-2.2.zip is also necessary for this to work.Everyone who tried to help, thank you very m...

Views

1.0K

Likes

0

Replies

0
Re: Sling:alias not working on dispatcher
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager
Update: I am able to reproduce the issue on a "new" publish instance, I also installed all the hotfixes for AEM 6.1 just to make sure that isn't an old problem.I changed the Sling Authentication to allow anonymous access. I even gave the anonymous user access to read/write/.... for all the paths using the useradmin screen, but still the sling:alias is not resolved.I'm going to set logging for sling on debug now and hopefully I can extract the issue from the log file.

Views

992

Likes

0

Replies

0
Re: Sling:alias not working on dispatcher
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager
After trying to reproduce the issue on a new publish instance I noticed that a request filter is also not working. Is it possible that some filters are disabled?

Views

994

Likes

0

Replies

0
Re: Sling:alias not working on dispatcher
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager
Yes it is AEM 6.1

Views

993

Likes

0

Replies

0
Re: Sling:alias not working on dispatcher
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager
I checked the security settings, the "Allow Anonymous Access" was already selected. And I provided read-only access to everyone on the /content/www-company-com/ node (and all the subnodes).Still no success, the page is "not found"RegardsSteven

Views

995

Likes

0

Replies

0
Re: Sling:alias not working on dispatcher
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager
That is where it get's strange. When I go to my publish instance and open the jcrresolver page, I enter my url: "http://ac2.company.com.aws.intranet/nl/catelog/ladies.html" and I select resolve. It successfully resolves the url to a page under /content/www-company-com/nl/categories/5 which is the page containing the "sling:alias".When I navigate to http://publish-a.ac2.aws.intranet:4503/content/www-company-com/nl/categories/ladies.html it also displays the page, but when I log out on the crx, I'...

Views

991

Likes

0

Replies

0
Re: Sling:alias not working on dispatcher
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager
In the dispatcher.log I can see the followingFound farm ac2-company-com-aws-intranet for ac2.company.com.aws.intranet checking [/nl/categories/ladies.html] cachefile does not exist: /var/www/html/content/www-company-com/nl/categories/ladies.html try to create new cachefile: /var/www/html/content/www-company-com/nl/categories/ladies.html cache-action for [/nl/categories/ladies.html]: CREATE Creating new socket: publish-a.ac2.aws.intranet:4503 Connected to backend rend01 (publish-a.ac2.aws.intrane...

Views

992

Likes

0

Replies

0
Re: Sling:alias not working on dispatcher
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager
Hi, This link describes that a "production-ready" aem secures the sling get servlet: https://docs.adobe.com/docs/en/aem/6-1/administer/security/production-ready.htmlI don't know whether this could be the cause of my issue.The publish is indeed setup with anonymous access and I am able to request every page of my website. But when I try to access the page using it's "sling:alias" the page is not found. Regards,Steven

Views

1.0K

Likes

0

Replies

0
Sling:alias not working on dispatcher
Avatar
Give Back 10
Level 2
StevenRymenans
Level 2

Likes

0 likes

Total Posts

19 posts

Correct reply

2 solutions
Top badges earned
Give Back 10
Give Back 5
Ignite 5
Ignite 3
Validate 1
View profile
StevenRymenans
- Adobe Experience Manager
Hi,I have a question about "sling:alias". I have a few pages with a sling:alias configured. During development everything works and when we publish the page, the page is available and can be opened on the publish instance. As I'm setting up the dispatcher and configuring the sling mappings (/etc/map/) I noticed that the pages can't be resolved using the sling alias. When I tested the page on the publish again, when I wasn't logged in, I couldn't retrieve the page as well. It seems like I have to...

Views

3.9K

Likes

0

Replies

13
Likes given to