AEM 6.2: Deployment of OSGi Settings for different environments does not work correctly | Community
Skip to main content
C
ChristophSchnaedter
Level 2
January 25, 2022
Solved

AEM 6.2: Deployment of OSGi Settings for different environments does not work correctly

  • January 25, 2022
  • 3 replies
  • 3818 views

Hello everyone,

 

I have two different OSGi-Configurations. One shall be used for the productive system, the other configuration for all other environments (like dev and integration system). The plan is to deploy these settings to the right environment through configration files. The needed folder structure was already existent in the repository I am working with (like "config", "config.prod", "config.prod.publish", "config.dev" and so on.....)

 

I have placed the .conf files in the right folder structure: "config.prod" for the productive data and in "config" for all the other environments. 

 

The runmodes for the author of the productive system are: "author,prod,crx3,crx3tar".

 

As you can read in the documentation the configuration folder that matches the most runmodes will be used to lookup the .conf file. In this case this is clearly "config.prod". But after deployment I find the configuration that was placed into "config" on the productive System (system/ConfigMgr). 

 

The configuration of "config.prod" is not "overloaded" through a more matching config folder either (like for instance "config.prod.author").

 

Does anyone of you have a clue, why this might happen? Or how I can determine what has happended?

 

Greetings, Christoph

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 ChristophSchnaedter

I would suggest to take a back up of the existing config under config.prod, delete the config from config.prod then copy the required config from config to config.prod. Then change the values to reflect the prod properties.

As this is a prod environment we are talking about you could first test this in your local or lower environments and try on prod later.


Yes that helped. I used the folder "config.author.local" to deploy the config to my local dev system. The file from "config" worked, the file from "config.prod" not.

 

After inspecting the files closely I found out what was wrong. The encoding and properties were ok, but inside the file I did not put the values of the key-value-pairs into "". That broke the file. 

 

Very **bleep** error to be honest. But I simply did not see that although checking the files several times before. 

 

Thank you all for helping!

 

 

3 replies

Asutosh_Jena_
Community Advisor
Asutosh_Jena_Community Advisor
Community Advisor
January 25, 2022

Hi @christophschnaedter 

 

In AEM If multiple configurations for the same PID are available, the configuration with the highest number of matching run modes is applied.

 

As I understand you already the same configuration available in both config.prod as well as in config. So in this case the configuration should be picked from config.prod.

 

If it's not picking from the correct location, that means there is a typo in the PID name that is present in the config.prod which is why it's not finding a match and it's looking for the next available match which is config. Please review the PID names and ensure the names are exactly matching what is expected and it should resolve the issue.

 

Thanks!

    JeevanRaj
    Community Advisor
    JeevanRajCommunity Advisor
    Community Advisor
    January 25, 2022

    Hi Christoph,

     

    I second what Asutosh is telling. Adding more to his point and to avoid typos i would suggest you to copy the required working configuration node from config folder and paste this node in config.prod. Then change the properties which should be different in production environment. This way you will be sure that there are no typos in the pid.

     

    Thanks

      C
      ChristophSchnaedterAuthor
      Level 2
      January 25, 2022

      Thanks for the replies. I checked the configs and both filenames are exactly the same. If I copy one of the configs in the other folder the OS asks me whether I want to replace the existing file as both file names are equal. 

        JeevanRaj
        Community Advisor
        JeevanRajCommunity Advisor
        Community Advisor
        January 25, 2022

        Do you have the jcr:primaryType set to sling:OsgiConfig?

          C
          ChristophSchnaedterAuthor
          Level 2
          January 25, 2022

          I guess it is worth mentioning that we are using an OSGi factory here as we want to have different configs for different countries.

          The distinction happens with a country suffix in the filename. (like ....ConfigImpl-us oder ConfigImpl-uk.....). When I check the configs under system /ConfigMgr i can see that this suffix has been transformed into a long alphanumeric code for the PID. But the factory pid is as expected.

            Terms & ConditionsAccessibility statement

            Loading footer...