Re: [DISCUSS] ActiveMQ {CodeName} Web Console...

["A.Marchand" <a....@progeri.com>]

For what it is worth, we did such product. You can see it live or browse the
repo at the following address:
https://github.com/snuids/AMQC/wiki




--
View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-ActiveMQ-CodeName-Web-Console-tp4694984p4704553.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [DISCUSS] ActiveMQ {CodeName} Web Console...

["A.Marchand" <a....@progeri.com>]

Hi,

I am still thinking about getting the CORS working. It should be possible to
get it working by finding the magic configuration between the jetty
configuration and the Jolokia one.

However, I really think that the best way to go is to deploy the web app in
the jetty folder because it avoids any post install trick.

Concerning the Artemis integration, I started to have a look at it, it
should be possible to do something but to be honest, I think that the first
step would first be to define the kind of methods that must be available by
a monitoring console and to make them available via rest calls. For example,
if you have a lot of connections, I did not find a way to get all the
connection details (Consumers Enqueues/Dequeues) in a single rest call which
is far from perfect.

Another example is that I did not manage to send a message with a non string
header. The stomp protocol cannot do it and the send rest API don't let us
do it either.

Once the monitoring functions well defined, and available through rest
calls, it should be possible to easily code nice consoles using technology
like Angular JS. And more than that, people will start to use the same
interface to create monitoring consoles customised for their own projects.
Before the jolokia API, we used a lot the JMX system which is for me no
longer easy nor convenient.

Cheers,

Arnaud




--
View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-ActiveMQ-CodeName-Web-Console-tp4694984p4705188.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [DISCUSS] ActiveMQ {CodeName} Web Console...

[artnaseef <ar...@artnaseef.com>]

I would love to see this console added to the ActiveMQ code base.  Whether we
move it toward inclusion as a new console is something we can look at going
forward.

Adding it as a tool available directly from the main broker Jetty page would
be great.

Playing with AMQC against remote brokers does raise the concern of CORS. 
The recommendation on the wiki was to disable the browser CORS checking -
I'm not a fan of disabling security features.  With that said, including
AMQC with the broker's Jetty server would eliminate that concern for the
local-broker case.

The next step here would be either a Pull Request adding the code into the
AMQ codebase.  It would be awesome if the code could be reused for Artemis
as well, but following the "use before reuse" methodology, that can come
later.



--
View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-ActiveMQ-CodeName-Web-Console-tp4694984p4704931.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [DISCUSS] ActiveMQ {CodeName} Web Console...

[Christopher Shannon <ch...@gmail.com>]

+1 for adding this as a new ActiveMQ subproject.  It could then be
independent and support both ActiveMQ 5.x and Artemis.  The web console in
5.x is definitely dated and could use an upgrade and this could be a good
alternative for people who don't want to use Hawt.io.

I think it would also be worth revisiting the stomp.js proposed donation
because this new web console uses that library and it is no longer
supported.


On Fri, Dec 4, 2015 at 3:45 AM, A.Marchand <a....@progeri.com> wrote:

> Without any problem if they want it. I am using and gaining my money with
> their products since 10 years. It would be a small drop compared to the
> ocean of good things I received from them.
>
> With the new Jetty in the ActiveMQ 5.13, the CORS issues should disappear
> and we could probably propose a multi broker monitoring tool.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/DISCUSS-ActiveMQ-CodeName-Web-Console-tp4694984p4704601.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>

Re: [DISCUSS] ActiveMQ {CodeName} Web Console...

["A.Marchand" <a....@progeri.com>]

Without any problem if they want it. I am using and gaining my money with
their products since 10 years. It would be a small drop compared to the
ocean of good things I received from them. 

With the new Jetty in the ActiveMQ 5.13, the CORS issues should disappear
and we could probably propose a multi broker monitoring tool.



--
View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-ActiveMQ-CodeName-Web-Console-tp4694984p4704601.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [DISCUSS] ActiveMQ {CodeName} Web Console...

["Jamie G." <ja...@gmail.com>]

Cool :)

Thinking about donating the web console to the AMQ Community?

On Thu, Dec 3, 2015 at 3:05 AM, A.Marchand <a....@progeri.com> wrote:
> For what it is worth, we did such product. You can see it live or browse the
> repo at the following address:
> https://github.com/snuids/AMQC/wiki
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-ActiveMQ-CodeName-Web-Console-tp4694984p4704553.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.