Expand my Community achievements bar.

SOLVED

Handling config.publish for two domains

Avatar

Level 4

Hello Community - We have two production domains and the same content is served for both the domains. In this case, I need to apply the context-aware configuration clientIds for the domains. is there any mechanism to specify two different clientIds to support both the domains. I tried by making changes to config.publish folder but it is picking for only one domain not for two domains at the same time. is there a way to handle this usecase?

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @aemninja 

 

As you have mentioned the same content root is used to serve the content for both the domains, so the context aware config will not be able to differentiate between the domains and will not be able to apply the different client ids.

Now coming to OSGi configuration which will be applied at the run mode irrespective of the domain, that also will not be able to pick the appropriate value.

 

So I will suggest that you write a custom OSGI service which will read the host address and will check if it's from domain1 or domain 2 and based on that you can pass the appropriate value from OSGi.

 

Hope this helps!

Thanks

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Hi @aemninja 

 

As you have mentioned the same content root is used to serve the content for both the domains, so the context aware config will not be able to differentiate between the domains and will not be able to apply the different client ids.

Now coming to OSGi configuration which will be applied at the run mode irrespective of the domain, that also will not be able to pick the appropriate value.

 

So I will suggest that you write a custom OSGI service which will read the host address and will check if it's from domain1 or domain 2 and based on that you can pass the appropriate value from OSGi.

 

Hope this helps!

Thanks

Avatar

Employee Advisor

If you are trying to add multiple OSGI configurations, you can use an Identifier at the end of the config file name to uniquely define it. See the note below:

 

https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/configuring-osgi...