Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

ChristophSchnaedter
ChristophSchnaedter
Online

Badges

Badges
9

Accepted Solutions

Accepted Solutions
1

Likes Received

Likes Received
6

Posts

Posts
6

Discussions

Discussions
0

Questions

Questions
6

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by ChristophSchnaedter
Customize the badges you want to showcase on your profile
Re: AEM 6.2: Deployment of OSGi Settings for different environments does not work correctly - Adobe Experience Manager 25-01-2022
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 hel...

Views

491

Likes

2

Replies

0
Re: AEM 6.2: Deployment of OSGi Settings for different environments does not work correctly - Adobe Experience Manager 25-01-2022
Hi @Asutosh_Jena_ There is no config under /apps/system/config. And changing some values in config folder and reploying is not that easy as we have that problem with deployment on productive system. I would have to wait for the next scheduled release.

Views

499

Like

1

Replies

0
Re: AEM 6.2: Deployment of OSGi Settings for different environments does not work correctly - Adobe Experience Manager 25-01-2022
jcr:primaryType is set to "nt:file" but this is the case with all our config files. But there is a difference when I check the jcr content nodes. In "config.prod" there is a property "jcr:mimeType: application/octet-stream" and in "config" the property is "jcr:mimeType: text/plain" and also a property that says encoding is UTF-8. So maybe the config from "config.prod" is invisible to aem because of wrong encoding?

Views

503

Like

1

Replies

2
Betreff: AEM 6.2: Deployment of OSGi Settings for different environments does not work correctly - Adobe Experience Manager 25-01-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.

Views

509

Like

1

Replies

0
Re: AEM 6.2: Deployment of OSGi Settings for different environments does not work correctly - Adobe Experience Manager 25-01-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.

Views

515

Like

1

Replies

6
AEM 6.2: Deployment of OSGi Settings for different environments does not work correctly - Adobe Experience Manager 25-01-2022
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 str...

Views

534

Likes

0

Replies

10
Likes from