Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Using Environment Variables in AEMaaCS

Avatar

Community Advisor

Hi AEM Community,

 

I have the below code configured in my dispatcher_vhost.conf - 

# Allow ingressroute checks through on /systemready (regardless of dispatcher filters)
<Location "/systemready">
ProxyPass http://${AEM_HOST}:${AEM_PORT}/systemready
RewriteEngine Off
</Location>
# Allow access to CRXDE on dev environment
<IfDefine ENVIRONMENT_DEV>
<LocationMatch "/crx/(de|server)/">
ProxyPassMatch http://${AEM_HOST}:${AEM_PORT}
RewriteEngine Off
</LocationMatch>
</IfDefine>

We have not defined any Environment Variables for AEM_HOST and AEM_PORT as referenced above.

In AEMaaCS the CRXDE access is disabled by default. Hence, the above configuration doesn't make sense to include in dispatcher_vhost.conf.

 

Query 1 - Do we need to configure these parameters  ? I checked the WKND codebase but was unable to find these parameters defined in the /conf.d/variables folder.

 

Query 2 - In AEMaaCS should these parameter be configured ? If yes, then how should these parameters be defined ?

We usually have only Program ID and Environment ID.

 

@arunpatidar@Mohit_KBansal@kautuk_sahni@Jörg_Hoh, @Jagadeesh_Prakash@Manu_Mathew_ 

Thanks in advance.

 

Rohan Garg

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

I think those are placeholder values. you can replace those with the environment variables from Cloud Manager.

 



Arun Patidar

View solution in original post

5 Replies

Avatar

Correct answer by
Community Advisor

I think those are placeholder values. you can replace those with the environment variables from Cloud Manager.

 



Arun Patidar

Avatar

Community Advisor

Thanks for the reply @arunpatidar!

But even if we replace them the rules will not work or will they ?

Even if we provide the updated hostname and port for DEV Instance, the CRX will still not be available for AEMaaCS. Isn't that correct ?

Avatar

Community Advisor

yes, CRX is not accessible in cloud instance.



Arun Patidar

Avatar

Community Advisor

I will remove the placeholder values which don't align with AEMaaCS.

This includes the following - 

# Allow ingressroute checks through on /systemready (regardless of dispatcher filters)
<Location "/systemready">
ProxyPass http://${AEM_HOST}:${AEM_PORT}/systemready
RewriteEngine Off
</Location>

# Allow access to CRXDE on dev environment
<IfDefine ENVIRONMENT_DEV>
<LocationMatch "/crx/(de|server)/">
ProxyPassMatch http://${AEM_HOST}:${AEM_PORT}
RewriteEngine Off
</LocationMatch>
</IfDefine>

 

Avatar

Employee Advisor

You should not remove the systemready setting, as it will break operation.