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

Paul_McMahon
Paul_McMahon
Offline

Badges

Badges
21

Accepted Solutions

Accepted Solutions
142

Likes Received

Likes Received
48

Posts

Posts
235

Discussions

Discussions
5

Questions

Questions
230

Ideas

Ideas
0

Blog Posts

Blog Posts
1
Top badges earned by Paul_McMahon
Customize the badges you want to showcase on your profile
Re: AEM Author prod instance slows down too quick - Adobe Experience Manager 10-12-2015
50 concurrent users is close to the top end of the performance profile for a single authoring instance. Which version of the software are you on? What sort of hardware are you running on - what number of CPUs and how much memory? How is your storage connected - do you have a fully optimized IO solution? Have you considered that you may be at the point that you need to implement a cluster or off loading strategy? Do you have a performance testing environment. Are you able to duplicate these scena...

Views

1.5K

Likes

0

Replies

0
Re: ServiceA in BundleA injected into ServiceB in BundleB - Adobe Experience Manager 02-12-2015
Have you looked not just at the bundles but also the services? Check the following:Is bundle A activeGo to services console - check to see if Service A is active and runningGo to the services console - check to see if Service B is active? If it isn't why - are there unfilled dependencies? Try to activate the service then check error.log for message details.Some potential reasons why you might be having trouble:Service A's package isn't exported by bundle A (verify this in Felix in the package in...

Views

1.0K

Likes

0

Replies

0
Re: API for Overriding the page - Adobe Experience Manager 28-10-2015
I am not sure I fully understand you use case, but it sounds to my like what you are describing is something that falls under the Multi-Site Manager functionality. In you use case you have the same page in two locations, and one is the master and the other is a copy of the master and you want to be able to keep the copy in sync with the master? If so you wouldn't do a traditional copy you would be looking using the Live Copy functionality in Multi-Site Manager and then do a rollout. See https://...

Views

940

Likes

0

Replies

0
Re: Is this a sensible approach to use in AEM? - Adobe Experience Manager 22-10-2015
As another user pointed out using the query string means you won't caching the results in dispatcher. Can you cache the results in your other layer? Or will the result of /shop/categoryA be cached in a CDN for example? You will want to think through the performance impact of this model and be sure you have the capacity in you publish instances to deal with any increased traffic. One possible approach that would be similar but still leverage Dispatcher would be switch from a query string to a sel...

Views

882

Likes

0

Replies

0
Re: Language Copy vs Live Copy - Adobe Experience Manager 15-10-2015
The short answer to you question is that I believe language copy actually kills the live copy relationship so no roll outs will impact the copy. In general language copy is intended to be used to create language copies when you want to do something like manual translation and you simply creating the initial copy of the site. Language copy does not create a relationship between source and target the way that Live Copy does. So in the normal scenario where you creating a language copy of your mast...

Views

2.7K

Likes

0

Replies

0
Re: Guaranteed Replication Status - Adobe Experience Manager 15-10-2015
Your first constraint shouldn't impact the proposed concept. A replication event listener can listen for either sent or receive events. So the replication event listener would sit on the publish servers and listen for replication received events - which are happening in your design. A replication event listener does not require a replication agent. Now if you security restriction is that you can't have any outgoing network traffic from your publish servers than you would have an issue, but turni...

Views

1.4K

Likes

0

Replies

0
Re: Guaranteed Replication Status - Adobe Experience Manager 15-10-2015
There are probably a bunch of ways to handle it. The simplest way - assuming you have store all the information that is needed by Relay in the content you could write a replication event listener that runs on the publish instances and whenever it receives something it sends the response to Relay. That assumes that Relay will ignore all the duplicate responses since it will get 6 responses. You could set up the replication event listener to only run on one publish server - but then if that one wa...

Views

1.4K

Likes

0

Replies

0
Re: What is different between Running and Stale Status - Adobe Experience Manager 15-10-2015
The stale status is indicative of an error state. Essentially it means that the workflow instance is not going to be able to continue to run. One common reason for the stale state is that the payload of the workflow has been deleted or moved. Depending on the version you are running it may also indicate that the Sling events or jobs tied to the workflow instance no longer exist. Generally if the workflow instance has gone stale it means that the it's dead and you can't restart it so you need to ...

Views

1.5K

Like

1

Replies

0
Re: Vanity URL is not working as expected - Adobe Experience Manager 15-10-2015
My guess is that's probably the expected behavior. I don't know this for sure but my guess is that there is Modification Event Listener that listens for changes to the vanity URL property and updates the resource resolver configuration whenever changes are made to the content. Generally these kinds of listeners react quickly, but sometimes if there are lots of events happening they can be delayed which is probably what happened in your case. Again that's a total guess someone from Adobe could ve...

Views

819

Likes

0

Replies

0
Re: why we configure dispatcher at author instance? - Adobe Experience Manager 15-10-2015
You should always be configuring dispatcher at the publisher level - dispatcher in front of publisher instances is the standard approach - almost all the dispatcher documentation is geared towards how to configure dispatcher for a publisher instance. In addition to configuring dispatcher in front of you publishers you can optionally configure it in front of you author instances. This is not a replacement for dispatcher in front of publishers but an additional step to take to improve the performa...

Views

1.2K

Likes

0

Replies

0