[
https://issues.apache.org/jira/browse/OFBIZ-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17448536#comment-17448536
]
Ioan Eugen Stan commented on OFBIZ-6164:
----------------------------------------
We need to improve configuration for deployment as container.
OFBiz has too many configuration files spread over many paths and intermingled
with source files.
This makes it very hard to deploy as containers.
We need configuration federation - ability to read configuration from multiple
sources - files, db, other configs.
It would be also good to have the option of loading configs from less / single
configuration file.
> Improve configurability of OFBiz
> --------------------------------
>
> Key: OFBIZ-6164
> URL: https://issues.apache.org/jira/browse/OFBIZ-6164
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS, ALL COMPONENTS
> Affects Versions: Trunk
> Reporter: Pierre Smits
> Priority: Major
> Labels: configuration, multi-tenant
>
> The configuration of an OFBiz is determined by 2 aspects:
> # configuration settings required to successfully start the implementation
> # configuration settings required to have component functions work properly
> The latter involve default choices for various functions to cater to the
> usability of business processes (and therefore screen/forms and/or
> screens/templates.
> Several of these configuration settings are already loaded into the
> SystemProperty table in the underlying RDBMS, to enable adjustments of the
> systemPropertyValue while the implementation is in use. While it is not
> expected that these settings change often, it is possible that they are
> required to be changed during the lifespan of the company/organisation.
> However, it should not be required to go through a deployment process of
> regarding such changed configuration settings in the OFBiz production
> instance (which most - if not all - companies/organisations require when
> files are changes).
> Having all configuration settings of components in the SystemProperty table
> enhances the usability of OFBiz allowing system administrators to adjust the
> value(s) of system property records while the instance keeps running.
> Some examples of the latter kind of configuration settings expected to change
> during the lifespan of the company (and the production instance of OFBiz) are:
> {code:java}
> <SystemProperty systemResourceId="general"
> systemPropertyId="defaultFromEmailAddress"
> systemPropertyValue="ofbizt...@example.com" description="general default
> 'fromEmailAddress' can be overridden in: EmailTemplateSetting"/>
> <SystemProperty systemResourceId="general"
> systemPropertyId="mail.notifications.enabled" systemPropertyValue="N"
> description="mail notifications enabled (Y|N)"/>
> <SystemProperty systemResourceId="general"
> systemPropertyId="mail.smtp.relay.host" description="the default mail server
> to use"/>
> <SystemProperty systemResourceId="general"
> systemPropertyId="mail.smtp.auth.user" description="SMTP Auth username
> setting"/>
> <SystemProperty systemResourceId="general"
> systemPropertyId="mail.smtp.auth.password" description="SMTP Auth password
> setting"/>
> {code}
>
> Furthermore, in a multi-tenancy OFBiz setup, configurations can differ per
> tenant.
> This is a placeholder issue to capture related issues to improve the
> configurability of OFBiz.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
