Customisng OSGI Config for target environment | Community
Skip to main content
A
Anonymous
October 16, 2015
Solved

Customisng OSGI Config for target environment

  • October 16, 2015
  • 1 reply
  • 672 views

Hi.

I'm interested in a mechanism of customising the osgi run mode configurations for a given environment before an AEM build is deployed to that environment.  I'm generally against maintaining a config.<env> for each environment as i feel this introduces an unnecessary dependency on the development team who have nothing to do with maintaining the AEM environment.

Has anyone come across any automated ways of achieving this? I am using AEM V.6.0 SP1.

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 joerghoh

Hi,

It depends on the number of environiments and the amount of different settings for each. If both numbers are low, I (as operation team) would want the developers taking care of maintaining these settings (exact values are delivered by ops team then). But if one or both numbers are getting larger, I would recommend to choose a different approach: Maintain a maven-module which is dedicated to hold these settings as a content-package. Then give the ops team a short introduction and let them do the maintainenance of these values themselves (you need a good documentation about what data you expect there). This requires that the ops team is familiar with writing some form of XML and is used to use a version control system.

You cannot offload the configuration by 100% to the ops team. And at a point you probably need to have environment-dependent runmodes.

kind regards,
Jörg

1 reply

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

Hi,

It depends on the number of environiments and the amount of different settings for each. If both numbers are low, I (as operation team) would want the developers taking care of maintaining these settings (exact values are delivered by ops team then). But if one or both numbers are getting larger, I would recommend to choose a different approach: Maintain a maven-module which is dedicated to hold these settings as a content-package. Then give the ops team a short introduction and let them do the maintainenance of these values themselves (you need a good documentation about what data you expect there). This requires that the ops team is familiar with writing some form of XML and is used to use a version control system.

You cannot offload the configuration by 100% to the ops team. And at a point you probably need to have environment-dependent runmodes.

kind regards,
Jörg

Terms & ConditionsAccessibility statement

Loading footer...