Hi All,
Environment Variables:
{ "externalizer.domains": [ "local $[env:AEM_EXTERNALIZER_LOCAL;default=http://localhost:4502]", "author $[env:AEM_EXTERNALIZER_AUTHOR;default=http://localhost:4502]", "publish $[env:AEM_EXTERNALIZER_PUBLISH;default=http://localhost:4503]", "preview $[env:AEM_EXTERNALIZER_PREVIEW;default=http://localhost:4503]" ] }
When I checked with our admin team, they informed there are no environment variables defined in the cloud manager.
Thanks,
RadhaKrishna
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @RadhaKrishna ,
In your provided configuration snippet, the externalizer domains are set with environment variables for different environments: local, author, publish, and preview. However, if these environment variables are not defined, default values are provided as fallbacks.
The default values provided in your configuration snippet are:
These defaults are specified using the $[env:VARIABLE_NAME;default=default_value] syntax. If an environment variable is not defined (VARIABLE_NAME), the default value (default_value) will be used instead.
So, in the absence of custom configurations or explicitly defined environment variables, the values provided above would be used as defaults for the corresponding externalizer domains in your AEMaaCS instance. These values are determined by the configuration set by the AEMaaCS platform.
Hi @RadhaKrishna ,
In your provided configuration snippet, the externalizer domains are set with environment variables for different environments: local, author, publish, and preview. However, if these environment variables are not defined, default values are provided as fallbacks.
The default values provided in your configuration snippet are:
These defaults are specified using the $[env:VARIABLE_NAME;default=default_value] syntax. If an environment variable is not defined (VARIABLE_NAME), the default value (default_value) will be used instead.
So, in the absence of custom configurations or explicitly defined environment variables, the values provided above would be used as defaults for the corresponding externalizer domains in your AEMaaCS instance. These values are determined by the configuration set by the AEMaaCS platform.
We would need to create these environment variables manually.
The AEMaaCS doesn't know the client-facing domain OOTB.
Once you have finalized the domain create these variables with proper Domain value in Cloud manager.
Example: if your dev-publish domain is abc. Register http://abc.com for AEM_EXTERNALIZER_PUBLISH for Dev environment in Cloud manager
Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community
Views
Likes
Replies