Adding new Publish and Dispatcher to Load Balancer

Avatar

Avatar
Validate 1
Level 2
saibul
Level 2

Likes

6 likes

Total Posts

52 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Ignite 1
Give Back
Boost 5
Boost 3
View profile

Avatar
Validate 1
Level 2
saibul
Level 2

Likes

6 likes

Total Posts

52 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Ignite 1
Give Back
Boost 5
Boost 3
View profile
saibul
Level 2

04-01-2021

Previously we had 1 publish and 1 dispatcher in staging, Now we have added one more publish(2) and dispatcher(2).

We have 2 dispatchers connected with load-balancer now.

 

Out of 6 sites, we have 2 sites are login-based sites. Planning to go with  “/stickyConnections”  for the authenticated site so that the dispatchers will serve from the same dispatcher & publisher.

In one of our sites, the logged-in user will create a favorite(collection of image path) and the favorite is stored under the /home/user/…/preferences/favorites/fov-1. Also, we store some information in the preferences node as well.

 

I have the below questions.

  1. Where we need to add the “/stickyConnections“  property. In those two dispatchers farm or load-balancer.
  2. How to sync the user preference & favorite node between two publishers.
  3. Any other best approach apart from stickyconnection & node sync.

 

 

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 10
MVP
kunal23
MVP

Likes

166 likes

Total Posts

565 posts

Correct reply

172 solutions
Top badges earned
Validate 10
Validate 1
Ignite 3
Ignite 1
Give Back 50
View profile

Avatar
Validate 10
MVP
kunal23
MVP

Likes

166 likes

Total Posts

565 posts

Correct reply

172 solutions
Top badges earned
Validate 10
Validate 1
Ignite 3
Ignite 1
Give Back 50
View profile
kunal23
MVP

04-01-2021

1. You should connect 1D with 1P and have the sticky sessions configured at load balancer level. This is a simple and recommended topology and it will be easier for you to manage sticky configuration at one single place. 

2.  For synchronizing content I will recommend you to use Sling Content Distribution. However, it will be better if you can manage the UGC outside AEM in an external storage to avoid any sync failures. But if not possible then go with sling content distribution. [0]

3. Along with the above you should also configure Encapsulated token authentication for achieving stateless authentication. This will help in continuing the login session in case one publisher goes down or becomes unresponsive. [1]

 

[0] - https://sling.apache.org/documentation/bundles/content-distribution.html#multidatacenter-sync-distri... 

[0] - https://medium.com/tech-learnings/sling-content-distribution-in-aem-part-3-sync-distribution-sync-co... 

[1] - https://experienceleague.adobe.com/docs/experience-manager-65/administering/security/encapsulated-to... 

Answers (0)