<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 16, 2015 at 11:58 AM, Jiri Kremser <span dir="ltr"><<a href="mailto:jkremser@redhat.com" target="_blank">jkremser@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">| In the UI it seems that "WildFly Home" doesn't get filled on my machine<br>
<br>
</span>I know, hopefully, I'll fix that today.<br>
There is poor support for the file/directory choosers in angular :/<br>
<br>
2Mazz:<br>
Rather than pre-filling the credentials (username+password), it'd be better to do that for the hawkular-security-key and hawkular-security-secret. I guess, they could be obtained via the accounts' REST api.<br>
<br>
In that case we can keep the ui as simple as possible and all the user needs to do is to select the wildfly home.<br></blockquote><div><br></div><div>Why do we need the WF Home ? Just for initial install ?</div><div><br></div><div>I can imagine that you would download the installer once for multiple WF (but a single Hawkular server and same account), so that could (should ?) be asked by the installer.</div><div><br></div><div>Thomas</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
jk<br>
<div><div class="h5"><br>
<br>
----- Original Message -----<br>
| From: "Thomas Heute" <<a href="mailto:theute@redhat.com">theute@redhat.com</a>><br>
| To: "John Mazzitelli" <<a href="mailto:mazz@redhat.com">mazz@redhat.com</a>>, "Discussions around Hawkular development" <<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a>><br>
| Sent: Monday, 16 November, 2015 11:15:16 AM<br>
| Subject: Re: [Hawkular-dev] you can now download a wildfly agent installer from kettle<br>
|<br>
| In the UI it seems that "WildFly Home" doesn't get filled on my machine<br>
| (Chrome, Fedora). It opens a dialog box to select a "Folder to upload" but<br>
| it doesn't fill in the input text.<br>
|<br>
| Great to see progress there !<br>
|<br>
| On Sat, Nov 14, 2015 at 12:09 AM, John Mazzitelli < <a href="mailto:mazz@redhat.com">mazz@redhat.com</a> > wrote:<br>
|<br>
|<br>
| Jirka put together a small UI and enhanced the download servlet, which I then<br>
| went in and enhanced further, so you can now get a wildfly agent installer.<br>
|<br>
| Here's quickly how it should work:<br>
|<br>
| 1) Go to the UI and fill in the fields, submit it, and you should be able to<br>
| save the installer jar you get back<br>
| 1b) alternatively, you can download it from the command line like this:<br>
| wget --content-disposition '<br>
| <a href="http://localhost:8080/wildfly-agent/download?installer=true" rel="noreferrer" target="_blank">http://localhost:8080/wildfly-agent/download?installer=true</a><br>
|<br>
| at this point, you have something like<br>
| "hawkular-wildfly-agent-installer-0.13.1.Final.jar" on your file system.<br>
|<br>
| 2) Run the installer jar, pointing it to the wildfly you want to install it<br>
| to:<br>
|<br>
| java -jar hawkular-wildfly-agent-installer-0.13.1.Final.jar<br>
| --wildfly-home=/path/to/your/wildfly/home<br>
|<br>
| This installs the agent to your wildfly server.<br>
|<br>
| That should be it. Run your wildfly and you've got it monitored by the agent.<br>
|<br>
| Now, of course, there are lots of ways you can customize the agent<br>
| installation. The above just gets you the default agent with jdoe/password<br>
| credentials assuming <a href="http://localhost:8080" rel="noreferrer" target="_blank">http://localhost:8080</a> is accessible when you install.<br>
|<br>
| Whatever properties that are accepted in the installer .properties file<br>
| (which are also the same cmdline options to the installer) you can pass to<br>
| the download URL so they can be preset for you in the installer's default<br>
| configuration. So, for example, if you want all of your agents to talk to "<br>
| <a href="http://your-hawk-server:8080" rel="noreferrer" target="_blank">http://your-hawk-server:8080</a> ", you can do this to get an installer that<br>
| will install an agent talking to that server:<br>
|<br>
| wget --content-disposition '<br>
| <a href="http://localhost:8080/wildfly-agent/download?installer=true&hawkular-server-url=http://your-hawk-server:8080" rel="noreferrer" target="_blank">http://localhost:8080/wildfly-agent/download?installer=true&hawkular-server-url=http://your-hawk-server:8080</a><br>
| '<br>
|<br>
| There are other properties you can pass in if you want to further customize<br>
| the installer and the agent it installs. Just look at this for all that are<br>
| available:<br>
|<br>
| <a href="https://github.com/hawkular/hawkular-agent/blob/master/hawkular-wildfly-agent-installer/src/main/resources/hawkular-wildfly-agent-installer.properties" rel="noreferrer" target="_blank">https://github.com/hawkular/hawkular-agent/blob/master/hawkular-wildfly-agent-installer/src/main/resources/hawkular-wildfly-agent-installer.properties</a><br>
|<br>
| In the future, we want to have the installer that you download preconfigured<br>
| (if you want) for the credentials of the user who requested the download,<br>
| and preconfigured for the server that you downloaded the installer from<br>
| (right now, it defaults to " <a href="http://localhost:8080" rel="noreferrer" target="_blank">http://localhost:8080</a> " which is not optimal).<br>
| But, again, you can customize this now via installer cmdline options if you<br>
| want:<br>
|<br>
| java -jar hawkular-wildfly-agent-installer-0.13.1.Final.jar \<br>
| --wildfly-home=/path/to/your/wildfly/home \<br>
</div></div>| --hawkular-server-url= <a href="http://your-server:8080" rel="noreferrer" target="_blank">http://your-server:8080</a> \<br>
<div class="HOEnZb"><div class="h5">| --hawkular-security-key=your-offline-token-key \<br>
| --hawkular-security-secret=your-offline-token-secret \<br>
| --subsystem-snippet=/path/to/my/custom/agent-subsystem.xml<br>
|<br>
| That latter one (subsystem-snippet) is a powerful way you can further<br>
| configure the agent by giving a full .xml of the agent subsystem (so you can<br>
| do things like define what resource-type-dmr definitions you want, what<br>
| metrics you want enabled or disabled, etc, etc.)<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>
|<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>
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></div>