<div dir="ltr">i still don't get why it needs to be so complicated<div><br></div><div>If we do:</div><div><div> <subsystem xmlns="urn:org.hawkular.agent:agent:1.0" autoDiscoveryScanPeriodSecs="600" enabled="{hawkular.embedded-agent.enabled}"></div><div> <diagnostics enabled="true" interval="1" reportTo="LOG" timeUnits="minutes"/></div><div> <storage-adapter password="${hawkular.embedded-agent.password}"" serverOutboundSocketBindingRef="hawkular" type="HAWKULAR" username="${hawkular.embedded-agent.username}"/></div></div><div> instead of putting the values directly (and we can even still default the values).</div><div><br></div><div>Then we just need to provide a file such as:</div><div> hawkular.properties</div><div>with</div><div> hawkular.embedded-agent.enabled=true</div><div> hawkular.embedded-agent.username=jdoe</div><div> hawkular.embedded-agent.password=password</div><div><br></div><div>and start with:</div><div>sh standalone.sh -P hawkular.properties</div><div><br></div><div>IMO it's much easier for a user to read/modify the property files for the things that are expected to be changed by the user rather than messing with standalone.xml (it's still an option for die-hard users).</div><div><br></div><div>What am I missing ?</div><div><br></div><div>Thomas.</div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 1, 2016 at 9:11 AM, Juraci Paixão Kröhling <span dir="ltr"><<a href="mailto:jpkroehling@redhat.com" target="_blank">jpkroehling@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I like this idea. Instead of a script, we could have a "first boot"<br>
service that would perform this operation.<br>
<br>
- Juca.<br>
<span class=""><br>
On 29.01.2016 22:25, John Doyle wrote:<br>
> So how about a dedicated property file that contains the things the user<br>
> needs to set for Hawkular, and then a script that takes the values for<br>
> the property file and uses offline-cli commands to put the values into<br>
> the standalone.xml? From then on they are manageable. The user would<br>
> not have reason to go back to the property file. It would essentially be<br>
> one time use.<br>
><br>
> ~jd<br>
><br>
> On Fri, Jan 29, 2016 at 11:45 AM, Juraci Paixão Kröhling<br>
</span><span class="">> <<a href="mailto:jpkroehling@redhat.com">jpkroehling@redhat.com</a> <mailto:<a href="mailto:jpkroehling@redhat.com">jpkroehling@redhat.com</a>>> wrote:<br>
><br>
> Then it's still treated as "external" and cannot be managed by tools<br>
> that are Wildfly CLI-aware ?<br>
><br>
> - Juca.<br>
><br>
> On 29.01.2016 15:57, John Mazzitelli wrote:<br>
> > The file is NOT managed by WildFly, it can be whatever file you<br>
> want, read-only, read-write, doesn't matter. The way RHQ did it, we<br>
> shipped rhq-server.properties in a directory that was familiar with<br>
> customers so they knew where it was and could edit it easily.<br>
> ><br>
> > ----- Original Message -----<br>
> >> I did not know about this :) Do you know if the file is then<br>
> managed by<br>
> >> Wildfly, or is it read-only?<br>
> >><br>
> >> - Juca.<br>
> >><br>
> >> On 29.01.2016 15:39, John Doyle wrote:<br>
> >>> You can do this:<br>
> >>><br>
> >>> $JBOSS_HOME/bin/standalone.sh<br>
> --properties=$JBOSS_HOME/my-jboss.properties<br>
> >>><br>
> >>> Maybe I'm oversimplifying?<br>
> >>><br>
> >>> On Fri, Jan 29, 2016 at 9:16 AM, Thomas Heute<br>
> <<a href="mailto:theute@redhat.com">theute@redhat.com</a> <mailto:<a href="mailto:theute@redhat.com">theute@redhat.com</a>><br>
</span><span class="">> >>> <mailto:<a href="mailto:theute@redhat.com">theute@redhat.com</a> <mailto:<a href="mailto:theute@redhat.com">theute@redhat.com</a>>>> wrote:<br>
> >>><br>
> >>> Yes, it's what I hoped for (but really have no idea if<br>
> that can work).<br>
> >>><br>
> >>> On Fri, Jan 29, 2016 at 3:06 PM, Juraci Paixão Kröhling<br>
> >>> <<a href="mailto:jpkroehling@redhat.com">jpkroehling@redhat.com</a> <mailto:<a href="mailto:jpkroehling@redhat.com">jpkroehling@redhat.com</a>><br>
</span><span class="">> <mailto:<a href="mailto:jpkroehling@redhat.com">jpkroehling@redhat.com</a> <mailto:<a href="mailto:jpkroehling@redhat.com">jpkroehling@redhat.com</a>>>> wrote:<br>
> >>><br>
> >>> The advantage I see in managing the properties inside<br>
> >>> standalone.xml is<br>
> >>> that it can be managed via Wildfly CLI and compatible<br>
> tools.<br>
> >>> Perhaps<br>
> >>> even with future versions of Hawkular.<br>
> >>><br>
> >>> Unless there's a way to tell Wildfly to load the system<br>
> >>> properties from<br>
> >>> a separate file. This would be the best of two worlds.<br>
> >>><br>
> >>> - Juca.<br>
> >>> _______________________________________________<br>
> >>> hawkular-dev mailing list<br>
> >>> <a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
> <mailto:<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a>><br>
</span>> <mailto:<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<span class="">> <mailto:<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a>>><br>
> >>> <a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
> >>><br>
> >>><br>
> >>><br>
> >>><br>
> >>> _______________________________________________<br>
> >>> hawkular-dev mailing list<br>
> >>> <a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
> <mailto:<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a>><br>
</span>> <mailto:<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<div class="HOEnZb"><div class="h5">> <mailto:<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a>>><br>
> >>> <a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
> >>><br>
> >>><br>
> >> _______________________________________________<br>
> >> hawkular-dev mailing list<br>
> >> <a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a> <mailto:<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a>><br>
> >> <a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
> >><br>
> ><br>
> > _______________________________________________<br>
> > hawkular-dev mailing list<br>
> > <a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a> <mailto:<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a>><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
> ><br>
> _______________________________________________<br>
> hawkular-dev mailing list<br>
> <a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a> <mailto:<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a>><br>
> <a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
><br>
><br>
_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
<br>
<br>
</div></div></blockquote></div><br></div>