Adding a subsystem via CLI

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

Adding a subsystem via CLI

Scott Stark
Can a complete subsystem configuration be added via the CLI? Based on
the current docs and help, it does not seem so. One common usage in
openshift is the desire to extend the base as7 cartridge to add new
application type support. Examples are torquebox and switchyard. I don't
expect that the modules for the subsystem would be added via the CLI,
just the domain configuration.

[standalone@localhost:9999 /] help --commands
Commands available in the current context:
add-jms-cf         add-jms-queue      add-jms-topic      batch
cd                 clear              command            connect
data-source        deploy             help               history
ls                 pwd                quit               remove-jms-cf
remove-jms-queue   remove-jms-topic   undeploy           version
xa-data-source
To read a description of a specific command execute 'command_name --help'.

_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: Adding a subsystem via CLI

jtgreene
Administrator
Yes but you have to use operations (unless someone creates helper
commands). Subsystems often involve multiple resources, so for best
results you need to do a "composite" operation with mutliple ADD
operations for every subresource. Otherwise everytime becomes runtime
updates after the initial subsystem add operation and you might get into
a situation where one of the runtime updates requires a server restart

On 10/21/11 10:21 AM, Scott Stark wrote:

> Can a complete subsystem configuration be added via the CLI? Based on
> the current docs and help, it does not seem so. One common usage in
> openshift is the desire to extend the base as7 cartridge to add new
> application type support. Examples are torquebox and switchyard. I don't
> expect that the modules for the subsystem would be added via the CLI,
> just the domain configuration.
>
> [standalone@localhost:9999 /] help --commands
> Commands available in the current context:
> add-jms-cf         add-jms-queue      add-jms-topic      batch
> cd                 clear              command            connect
> data-source        deploy             help               history
> ls                 pwd                quit               remove-jms-cf
> remove-jms-queue   remove-jms-topic   undeploy           version
> xa-data-source
> To read a description of a specific command execute 'command_name --help'.
>
> _______________________________________________
> jboss-as7-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev


--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: Adding a subsystem via CLI

Scott Stark
Ok, I did figure out the syntax for adding the jmx subsystem as an
example. The initial add of the extension cannot be part of the
composite operation that adds the subsystem because there are no
handlers for the subsystem=jxm add until this is done. The following two
CLI commands accomplish adding the jmx subsystem and related socket
bindings:

/extension=org.jboss.as.jmx:add
/:composite(steps=[{"operation" => "add","address" => [("subsystem" =>
"jmx")], "show-model" => true}, {"operation" => "add-connector",
"address" => [("subsystem" => "jmx")], "server-binding" =>
"jmx-connector-server", "registry-binding" => "jmx-connector-registry"},
{"operation" => "add", "address" => [("socket-binding-group" =>
"standard-sockets"), ("socket-binding" => "jmx-connector-registry")],
"port" => 1090, "interface" => "management"}, {"operation" => "add",
"address" => [("socket-binding-group" => "standard-sockets"),
("socket-binding" => "jmx-connector-server")], "port" => 1091,
"interface" => "management"}])

I documented this here:
http://community.jboss.org/wiki/AddingANewExtensionSubsystemViaTheCLI

On 10/21/11 8:33 AM, Jason T. Greene wrote:

> Yes but you have to use operations (unless someone creates helper
> commands). Subsystems often involve multiple resources, so for best
> results you need to do a "composite" operation with mutliple ADD
> operations for every subresource. Otherwise everytime becomes runtime
> updates after the initial subsystem add operation and you might get into
> a situation where one of the runtime updates requires a server restart
>
> On 10/21/11 10:21 AM, Scott Stark wrote:
>> Can a complete subsystem configuration be added via the CLI? Based on
>> the current docs and help, it does not seem so. One common usage in
>> openshift is the desire to extend the base as7 cartridge to add new
>> application type support. Examples are torquebox and switchyard. I don't
>> expect that the modules for the subsystem would be added via the CLI,
>> just the domain configuration.
>>
>> [standalone@localhost:9999 /] help --commands
>> Commands available in the current context:
>> add-jms-cf         add-jms-queue      add-jms-topic      batch
>> cd                 clear              command            connect
>> data-source        deploy             help               history
>> ls                 pwd                quit               remove-jms-cf
>> remove-jms-queue   remove-jms-topic   undeploy           version
>> xa-data-source
>> To read a description of a specific command execute 'command_name --help'.
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>

_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: Adding a subsystem via CLI

Jaikiran Pai
Sometime back a community user posted a script to create an entire
domain configuration using the CLI
http://community.jboss.org/thread/172245?tstart=180. I haven't tried to
myself.

-Jaikiran
On Saturday 22 October 2011 01:11 AM, Scott Stark wrote:

> Ok, I did figure out the syntax for adding the jmx subsystem as an
> example. The initial add of the extension cannot be part of the
> composite operation that adds the subsystem because there are no
> handlers for the subsystem=jxm add until this is done. The following two
> CLI commands accomplish adding the jmx subsystem and related socket
> bindings:
>
> /extension=org.jboss.as.jmx:add
> /:composite(steps=[{"operation" =>  "add","address" =>  [("subsystem" =>
> "jmx")], "show-model" =>  true}, {"operation" =>  "add-connector",
> "address" =>  [("subsystem" =>  "jmx")], "server-binding" =>
> "jmx-connector-server", "registry-binding" =>  "jmx-connector-registry"},
> {"operation" =>  "add", "address" =>  [("socket-binding-group" =>
> "standard-sockets"), ("socket-binding" =>  "jmx-connector-registry")],
> "port" =>  1090, "interface" =>  "management"}, {"operation" =>  "add",
> "address" =>  [("socket-binding-group" =>  "standard-sockets"),
> ("socket-binding" =>  "jmx-connector-server")], "port" =>  1091,
> "interface" =>  "management"}])
>
> I documented this here:
> http://community.jboss.org/wiki/AddingANewExtensionSubsystemViaTheCLI
>
> On 10/21/11 8:33 AM, Jason T. Greene wrote:
>> Yes but you have to use operations (unless someone creates helper
>> commands). Subsystems often involve multiple resources, so for best
>> results you need to do a "composite" operation with mutliple ADD
>> operations for every subresource. Otherwise everytime becomes runtime
>> updates after the initial subsystem add operation and you might get into
>> a situation where one of the runtime updates requires a server restart
>>
>> On 10/21/11 10:21 AM, Scott Stark wrote:
>>> Can a complete subsystem configuration be added via the CLI? Based on
>>> the current docs and help, it does not seem so. One common usage in
>>> openshift is the desire to extend the base as7 cartridge to add new
>>> application type support. Examples are torquebox and switchyard. I don't
>>> expect that the modules for the subsystem would be added via the CLI,
>>> just the domain configuration.
>>>
>>> [standalone@localhost:9999 /] help --commands
>>> Commands available in the current context:
>>> add-jms-cf         add-jms-queue      add-jms-topic      batch
>>> cd                 clear              command            connect
>>> data-source        deploy             help               history
>>> ls                 pwd                quit               remove-jms-cf
>>> remove-jms-queue   remove-jms-topic   undeploy           version
>>> xa-data-source
>>> To read a description of a specific command execute 'command_name --help'.
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>
> _______________________________________________
> jboss-as7-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev