Externalizer in AEMaaCS | Community
Skip to main content
May 7, 2024
Solved

Externalizer in AEMaaCS

  • May 7, 2024
  • 3 replies
  • 882 views

Hi All,

 

Environment Variables:

  • AEM_EXTERNALIZER_PREVIEW
  • AEM_EXTERNALIZER_PUBLISH
  • AEM_EXTERNALIZER_AUTHOR
{
   "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. 

  1. What are the values of the environment variables in the default configuration, when there is no custom configuration defined.
  2. How it is calculated?

 

Thanks,
RadhaKrishna

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by HrishikeshKagne

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.

3 replies

HrishikeshKagne
Community Advisor
HrishikeshKagneCommunity AdvisorAccepted solution
Community Advisor
May 7, 2024

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.

Hrishikesh Kagane
aanchal-sikka
Community Advisor
Community Advisor
May 7, 2024

@radhakrishna 

 

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

 

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/environment-variables#add-variables

Aanchal Sikka
EstebanBustamante
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
May 7, 2024

@radhakrishna 

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

Esteban Bustamante