[
https://issues.apache.org/jira/browse/KARAF-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063252#comment-13063252
]
Jean-Baptiste Onofré commented on KARAF-475:
--------------------------------------------
I will create a wiki page to deal about Karaf distributions, Karaf profiles,
etc.
> Better support for creating a custom server
> -------------------------------------------
>
> Key: KARAF-475
> URL: https://issues.apache.org/jira/browse/KARAF-475
> Project: Karaf
> Issue Type: Improvement
> Components: runtime
> Affects Versions: 2.1.3
> Reporter: Bengt Rodehav
> Fix For: 3.1.0
>
>
> Every time I upgrade my applications with a new version of Karaf I have to
> modify several files included in the Karaf distribution. This is very
> cumbersome and error prone. I would like it to be easier to customise a Karaf
> server. I think the goal with a customised server should be that all
> customisation (within reasonable limits) should be possible to do without
> modifying any files that come with the Karaf distribution. My customisation
> should solely exist of files that I add to Karaf and therefore do normally
> not need to be updated with every new Karaf version.
> When it comes to launching of Karaf I presently have to customise karaf.bat,
> karaf-service.bat and karaf-wrapper.conf. I would like those existing files
> to be more customisable/brandable so that I don't have to modify the Karaf
> distribution at all. In production, I use the wrapper service which doesn't
> come "unpacked" with Karaf. When I download a new version of Karaf I have to
> install it, start it and finally install the wrapper service. Then I have a
> base for customisation since until then I didn't even have access to the
> wrapper files bundled with Karaf.
> Personally I need to customise the following ("my reasonable limits"?):
> - Console title
> - Windows service title/name/display name/description
> - Memory requirements (-Xmx and -XX:MaxPermSize)
> - Define system properties on the command line (-D)
> - Probably need to customise the entire java command line since I might want
> to override parameters that are set by the Karaf distribution (e g the Derby
> data directory)
> - KARAF_HOME/KARAF_BASE (when running as a service)
> - Wrapper log configuration (the normal logging is specified in
> org.ops4j.pax.logging.cfg in which case I use my own version)
> - What features to install. I use my own org.apache.karaf.features.cfg which
> is fine.
> - What ports to use. The reason is that we must allow more than one Karaf
> installation on the same server (e g production and test). Presently I
> therefore modify org.apache.karaf.management.cfg, org.ops4j.pax.web.cfg and
> org.apache.karaf.shell.cfg where I replace the ports with property
> placeholders that I filter with maven-assembly-plugin.
> - Additional bundles to load at startup (the reason why I started this thread
> on the mailing list) which I now have to add in startup.properties.
> Some of the above might be solved by using custom.properties. I have
> encountered problems there which is is reported in KARAF-474.
> This was discussed in the following thread:
> http://mail-archives.apache.org/mod_mbox/karaf-user/201102.mbox/browser
> It started on the user list but continued on the dev list, here:
> http://mail-archives.apache.org/mod_mbox/karaf-dev/201102.mbox/browser
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
