Artemis options

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Artemis options

clebertsuconic
I have added data options to the runtime CLI, moved it from artemis-tools,

Now users will be able to do:


./artemis data print


and print all the data on the journals and paging (the option will
open the journals and print all the contents)


To export the data

./artemis data exp




you can use ./artemis help data print  (I - at the end of the email)




I tried to be as much user friendly as possible... if you could play
with it... it would help me to make sure it's really user friendly :)





I:

$ ./artemis help data print

NAME

        artemis data print - Print data records information (WARNING: don't use

        while a production server is running)


SYNOPSIS

        artemis data print [--bindings <binding>] [--broker <brokerConfig>]

                [--journal <journal>] [--large-messages <largeMessges>]

                [--paging <paging>] [--] [<configuration>]


OPTIONS

        --bindings <binding>

            The folder used for bindings (default from broker.xml)


        --broker <brokerConfig>

            This would override the broker configuration from the bootstrap


        --journal <journal>

            The folder used for messages journal (default from broker.xml)


        --large-messages <largeMessges>

            The folder used for large-messages (default from broker.xml)


        --paging <paging>

            The folder used for paging (default from broker.xml)


        --

            This option can be used to separate command-line options from the

            list of argument, (useful when arguments might be mistaken for

            command-line options


        <configuration>

            Broker Configuration URI, default

            'xml:${ARTEMIS_INSTANCE}/etc/bootstrap.xml'
Reply | Threaded
Open this post in threaded view
|

Re: Artemis options

chirino
Nice!

But perhaps the 'data' command should only be enabled in the
${ARTEMIS_INSTANCE}/bin/artemis case.  When used with
${ARTEMIS_HOME}/bin/artemis it fails since it can't find the data
files.

On Tue, May 5, 2015 at 11:33 AM, Clebert Suconic
<[hidden email]> wrote:

> I have added data options to the runtime CLI, moved it from artemis-tools,
>
> Now users will be able to do:
>
>
> ./artemis data print
>
>
> and print all the data on the journals and paging (the option will
> open the journals and print all the contents)
>
>
> To export the data
>
> ./artemis data exp
>
>
>
>
> you can use ./artemis help data print  (I - at the end of the email)
>
>
>
>
> I tried to be as much user friendly as possible... if you could play
> with it... it would help me to make sure it's really user friendly :)
>
>
>
>
>
> I:
>
> $ ./artemis help data print
>
> NAME
>
>         artemis data print - Print data records information (WARNING: don't use
>
>         while a production server is running)
>
>
> SYNOPSIS
>
>         artemis data print [--bindings <binding>] [--broker <brokerConfig>]
>
>                 [--journal <journal>] [--large-messages <largeMessges>]
>
>                 [--paging <paging>] [--] [<configuration>]
>
>
> OPTIONS
>
>         --bindings <binding>
>
>             The folder used for bindings (default from broker.xml)
>
>
>         --broker <brokerConfig>
>
>             This would override the broker configuration from the bootstrap
>
>
>         --journal <journal>
>
>             The folder used for messages journal (default from broker.xml)
>
>
>         --large-messages <largeMessges>
>
>             The folder used for large-messages (default from broker.xml)
>
>
>         --paging <paging>
>
>             The folder used for paging (default from broker.xml)
>
>
>         --
>
>             This option can be used to separate command-line options from the
>
>             list of argument, (useful when arguments might be mistaken for
>
>             command-line options
>
>
>         <configuration>
>
>             Broker Configuration URI, default
>
>             'xml:${ARTEMIS_INSTANCE}/etc/bootstrap.xml'



--
Hiram Chirino
Engineering | Red Hat, Inc.
[hidden email] | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
Reply | Threaded
Open this post in threaded view
|

Re: Artemis options

clebertsuconic
I did it like that but I always analyze user's data without a running
instance. So I would be able to do something like --

./artemis data print --bindings /users-data --journal /users-data




Maybe I should ignore that error and just print an empty report if no
folders are available?





On Tue, May 5, 2015 at 4:35 PM, Hiram Chirino <[hidden email]> wrote:

> Nice!
>
> But perhaps the 'data' command should only be enabled in the
> ${ARTEMIS_INSTANCE}/bin/artemis case.  When used with
> ${ARTEMIS_HOME}/bin/artemis it fails since it can't find the data
> files.
>
> On Tue, May 5, 2015 at 11:33 AM, Clebert Suconic
> <[hidden email]> wrote:
>> I have added data options to the runtime CLI, moved it from artemis-tools,
>>
>> Now users will be able to do:
>>
>>
>> ./artemis data print
>>
>>
>> and print all the data on the journals and paging (the option will
>> open the journals and print all the contents)
>>
>>
>> To export the data
>>
>> ./artemis data exp
>>
>>
>>
>>
>> you can use ./artemis help data print  (I - at the end of the email)
>>
>>
>>
>>
>> I tried to be as much user friendly as possible... if you could play
>> with it... it would help me to make sure it's really user friendly :)
>>
>>
>>
>>
>>
>> I:
>>
>> $ ./artemis help data print
>>
>> NAME
>>
>>         artemis data print - Print data records information (WARNING: don't use
>>
>>         while a production server is running)
>>
>>
>> SYNOPSIS
>>
>>         artemis data print [--bindings <binding>] [--broker <brokerConfig>]
>>
>>                 [--journal <journal>] [--large-messages <largeMessges>]
>>
>>                 [--paging <paging>] [--] [<configuration>]
>>
>>
>> OPTIONS
>>
>>         --bindings <binding>
>>
>>             The folder used for bindings (default from broker.xml)
>>
>>
>>         --broker <brokerConfig>
>>
>>             This would override the broker configuration from the bootstrap
>>
>>
>>         --journal <journal>
>>
>>             The folder used for messages journal (default from broker.xml)
>>
>>
>>         --large-messages <largeMessges>
>>
>>             The folder used for large-messages (default from broker.xml)
>>
>>
>>         --paging <paging>
>>
>>             The folder used for paging (default from broker.xml)
>>
>>
>>         --
>>
>>             This option can be used to separate command-line options from the
>>
>>             list of argument, (useful when arguments might be mistaken for
>>
>>             command-line options
>>
>>
>>         <configuration>
>>
>>             Broker Configuration URI, default
>>
>>             'xml:${ARTEMIS_INSTANCE}/etc/bootstrap.xml'
>
>
>
> --
> Hiram Chirino
> Engineering | Red Hat, Inc.
> [hidden email] | fusesource.com | redhat.com
> skype: hiramchirino | twitter: @hiramchirino



--
Clebert Suconic
http://community.jboss.org/people/clebert.suconic@...
http://clebertsuconic.blogspot.com
Reply | Threaded
Open this post in threaded view
|

Re: Artemis options

chirino
perhaps you should print out a nicer error messages saying they should
use the --bindings / --journal options :)

On Tue, May 5, 2015 at 5:14 PM, Clebert Suconic
<[hidden email]> wrote:

> I did it like that but I always analyze user's data without a running
> instance. So I would be able to do something like --
>
> ./artemis data print --bindings /users-data --journal /users-data
>
>
>
>
> Maybe I should ignore that error and just print an empty report if no
> folders are available?
>
>
>
>
>
> On Tue, May 5, 2015 at 4:35 PM, Hiram Chirino <[hidden email]> wrote:
>> Nice!
>>
>> But perhaps the 'data' command should only be enabled in the
>> ${ARTEMIS_INSTANCE}/bin/artemis case.  When used with
>> ${ARTEMIS_HOME}/bin/artemis it fails since it can't find the data
>> files.
>>
>> On Tue, May 5, 2015 at 11:33 AM, Clebert Suconic
>> <[hidden email]> wrote:
>>> I have added data options to the runtime CLI, moved it from artemis-tools,
>>>
>>> Now users will be able to do:
>>>
>>>
>>> ./artemis data print
>>>
>>>
>>> and print all the data on the journals and paging (the option will
>>> open the journals and print all the contents)
>>>
>>>
>>> To export the data
>>>
>>> ./artemis data exp
>>>
>>>
>>>
>>>
>>> you can use ./artemis help data print  (I - at the end of the email)
>>>
>>>
>>>
>>>
>>> I tried to be as much user friendly as possible... if you could play
>>> with it... it would help me to make sure it's really user friendly :)
>>>
>>>
>>>
>>>
>>>
>>> I:
>>>
>>> $ ./artemis help data print
>>>
>>> NAME
>>>
>>>         artemis data print - Print data records information (WARNING: don't use
>>>
>>>         while a production server is running)
>>>
>>>
>>> SYNOPSIS
>>>
>>>         artemis data print [--bindings <binding>] [--broker <brokerConfig>]
>>>
>>>                 [--journal <journal>] [--large-messages <largeMessges>]
>>>
>>>                 [--paging <paging>] [--] [<configuration>]
>>>
>>>
>>> OPTIONS
>>>
>>>         --bindings <binding>
>>>
>>>             The folder used for bindings (default from broker.xml)
>>>
>>>
>>>         --broker <brokerConfig>
>>>
>>>             This would override the broker configuration from the bootstrap
>>>
>>>
>>>         --journal <journal>
>>>
>>>             The folder used for messages journal (default from broker.xml)
>>>
>>>
>>>         --large-messages <largeMessges>
>>>
>>>             The folder used for large-messages (default from broker.xml)
>>>
>>>
>>>         --paging <paging>
>>>
>>>             The folder used for paging (default from broker.xml)
>>>
>>>
>>>         --
>>>
>>>             This option can be used to separate command-line options from the
>>>
>>>             list of argument, (useful when arguments might be mistaken for
>>>
>>>             command-line options
>>>
>>>
>>>         <configuration>
>>>
>>>             Broker Configuration URI, default
>>>
>>>             'xml:${ARTEMIS_INSTANCE}/etc/bootstrap.xml'
>>
>>
>>
>> --
>> Hiram Chirino
>> Engineering | Red Hat, Inc.
>> [hidden email] | fusesource.com | redhat.com
>> skype: hiramchirino | twitter: @hiramchirino
>
>
>
> --
> Clebert Suconic
> http://community.jboss.org/people/clebert.suconic@...
> http://clebertsuconic.blogspot.com



--
Hiram Chirino
Engineering | Red Hat, Inc.
[hidden email] | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
Reply | Threaded
Open this post in threaded view
|

Re: Artemis options

clebertsuconic
good point.. will do it!

On Tue, May 5, 2015 at 5:18 PM, Hiram Chirino <[hidden email]> wrote:

> perhaps you should print out a nicer error messages saying they should
> use the --bindings / --journal options :)
>
> On Tue, May 5, 2015 at 5:14 PM, Clebert Suconic
> <[hidden email]> wrote:
>> I did it like that but I always analyze user's data without a running
>> instance. So I would be able to do something like --
>>
>> ./artemis data print --bindings /users-data --journal /users-data
>>
>>
>>
>>
>> Maybe I should ignore that error and just print an empty report if no
>> folders are available?
>>
>>
>>
>>
>>
>> On Tue, May 5, 2015 at 4:35 PM, Hiram Chirino <[hidden email]> wrote:
>>> Nice!
>>>
>>> But perhaps the 'data' command should only be enabled in the
>>> ${ARTEMIS_INSTANCE}/bin/artemis case.  When used with
>>> ${ARTEMIS_HOME}/bin/artemis it fails since it can't find the data
>>> files.
>>>
>>> On Tue, May 5, 2015 at 11:33 AM, Clebert Suconic
>>> <[hidden email]> wrote:
>>>> I have added data options to the runtime CLI, moved it from artemis-tools,
>>>>
>>>> Now users will be able to do:
>>>>
>>>>
>>>> ./artemis data print
>>>>
>>>>
>>>> and print all the data on the journals and paging (the option will
>>>> open the journals and print all the contents)
>>>>
>>>>
>>>> To export the data
>>>>
>>>> ./artemis data exp
>>>>
>>>>
>>>>
>>>>
>>>> you can use ./artemis help data print  (I - at the end of the email)
>>>>
>>>>
>>>>
>>>>
>>>> I tried to be as much user friendly as possible... if you could play
>>>> with it... it would help me to make sure it's really user friendly :)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> I:
>>>>
>>>> $ ./artemis help data print
>>>>
>>>> NAME
>>>>
>>>>         artemis data print - Print data records information (WARNING: don't use
>>>>
>>>>         while a production server is running)
>>>>
>>>>
>>>> SYNOPSIS
>>>>
>>>>         artemis data print [--bindings <binding>] [--broker <brokerConfig>]
>>>>
>>>>                 [--journal <journal>] [--large-messages <largeMessges>]
>>>>
>>>>                 [--paging <paging>] [--] [<configuration>]
>>>>
>>>>
>>>> OPTIONS
>>>>
>>>>         --bindings <binding>
>>>>
>>>>             The folder used for bindings (default from broker.xml)
>>>>
>>>>
>>>>         --broker <brokerConfig>
>>>>
>>>>             This would override the broker configuration from the bootstrap
>>>>
>>>>
>>>>         --journal <journal>
>>>>
>>>>             The folder used for messages journal (default from broker.xml)
>>>>
>>>>
>>>>         --large-messages <largeMessges>
>>>>
>>>>             The folder used for large-messages (default from broker.xml)
>>>>
>>>>
>>>>         --paging <paging>
>>>>
>>>>             The folder used for paging (default from broker.xml)
>>>>
>>>>
>>>>         --
>>>>
>>>>             This option can be used to separate command-line options from the
>>>>
>>>>             list of argument, (useful when arguments might be mistaken for
>>>>
>>>>             command-line options
>>>>
>>>>
>>>>         <configuration>
>>>>
>>>>             Broker Configuration URI, default
>>>>
>>>>             'xml:${ARTEMIS_INSTANCE}/etc/bootstrap.xml'
>>>
>>>
>>>
>>> --
>>> Hiram Chirino
>>> Engineering | Red Hat, Inc.
>>> [hidden email] | fusesource.com | redhat.com
>>> skype: hiramchirino | twitter: @hiramchirino
>>
>>
>>
>> --
>> Clebert Suconic
>> http://community.jboss.org/people/clebert.suconic@...
>> http://clebertsuconic.blogspot.com
>
>
>
> --
> Hiram Chirino
> Engineering | Red Hat, Inc.
> [hidden email] | fusesource.com | redhat.com
> skype: hiramchirino | twitter: @hiramchirino



--
Clebert Suconic
http://community.jboss.org/people/clebert.suconic@...
http://clebertsuconic.blogspot.com