-
Language:
English
-
Language:
English
Red Hat Training
A Red Hat training course is available for Red Hat Fuse
Console Reference
Quick access to the commands used to manage the broker
Red Hat
Copyright © 2011-2014 Red Hat, Inc. and/or its affiliates.
Abstract
Chapter 1. Using the Command Console
Overview
Starting the command console
Windows | bin\fuse |
*NIX | bin/fuse |
_ ____ ______ | | _ \ | ____| | | |_) | ___ ___ ___ | |__ _ _ ___ ___ _ | | _ < / _ \/ __/ __| | __| | | / __|/ _ \ | |__| | |_) | (_) \__ \__ \ | | | |_| \__ \ __/ \____/|____/ \___/|___/___/ |_| \__,_|___/\___| JBoss Fuse (6.0.0.redhat-xxx) http://www.redhat.com/products/jbossenterprisemiddleware/fuse/ Hit '<tab>' for a list of available commands and '[cmd] --help' for help on a specific command. Hit '<ctrl-d>' or 'osgi:shutdown' to shutdown JBoss Fuse. JBossFuse:karaf@root
Getting help
- console help—lists all of the commands along with a brief summary of the commands function
- command help—provides a detailed description of a command and its arguments
Example 1.1. Console Help
JBossFuse:karaf@root>
help
COMMANDS activemq:browse activemq:bstat activemq:create-broker Creates a broker instance. activemq:destroy-broker Destory a broker instance. activemq:list activemq:purge activemq:query admin:change-opts Changes the Java options of an existing container instance. admin:change-rmi-registry-port Changes the RMI registry port (used by management layer) of an existing container instance.
...JBossFuse:karaf@root>
--help
option. As shown in Example 1.2, “Help for a Command”, entering admin:start --help
displays the help for that command.
Example 1.2. Help for a Command
JBossFuse:karaf@root>
admin:start --help
DESCRIPTION admin:start Starts an existing container instance. SYNTAX admin:start [options] name ARGUMENTS name The name of the container instance OPTIONS --help Display this help message -o, --java-opts Java options when launching the instance
JBossFuse:karaf@root>
Command completion
active
followed by Tab, a list similar to Example 1.3, “Console Commands” is shown.
Example 1.3. Console Commands
activemq:browse activemq:bstat activemq:create-broker activemq:destroy-broker activemq:list activemq:purge activemq:query JBossA-MQ:karaf@root>
Command groups
Table 1.1. Apache ActiveMQ Command Groups
Command Group | Description |
---|---|
activemq | Views and manages brokers and messages. |
admin | Creates, manages, and destroys containers. |
camel | Manages Apache Camel contexts and routes |
config | Manages configuration. |
cxf | Manages Apache CXF buses and endpoints. |
dev | Utilities that are useful for a developer while testing bundles in the container. |
fab | Manages the dependency resolution mechanism used by Fuse Application Bundles. |
fabric | Performs provisioning and configuration using Fuse Fabric. |
features | Performs provisioning based on Apache Karaf feature specs. |
jaas | Manages the console's security settings. |
jbi | Manage deployed JBI artifacts. |
log | Displays and configures logging. |
nmr | Lists NMR endpoints. |
obr | Accesses the OSGi Bundle Repository (OBR). |
osgi | Manages OSGi bundles. |
packages | Lists imported and exported packages. |
patch | Manages patches. |
shell | Performs basic console functions |
ssh | Creates and connects to a remote SSH server |
web | Lists the WARs deployed in the container. |
zk | Accesses and modifies entries in the Zookeeper registry. |
Short version
- shell
- osgi
- admin
Chapter 2. Shell Console Commands
shell:
then press Tab at the prompt to view the commands in this group.
Name
shell:cat, cat — displays the contents of a file or URL
Synopsis
shell:cat
[
-n
] [
--help
] {[
path
] | [
URL
]}
Arguments
Table 2.1. shell:cat Arguments
Argument | Interpretation |
---|---|
-n | Display line numbers. |
--help | Displays the online help for this command |
path | The path(s) of the file to display, separated by whitespace (separated by - for STDIN) |
URL | The URL(s) to display, separated by whitespace (separated by - for STDIN) |
Name
shell:clear, clear — clears the console buffer
Synopsis
shell:clear
[
--help
]
Arguments
Table 2.2. shell:clear Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name
shell:each, each — execute a closure on a list of arguments
Synopsis
shell:each
[
--help
] {
values
} {
function
}
Arguments
Table 2.3. shell:each Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
values | The collection of arguments to iterate over. |
function | The function to execute. |
Name
shell:echo, echo — prints arguments to the standard output
Synopsis
shell:echo
[
--help
] [
-n
] {
argument
...}
Arguments
Table 2.4. shell:echo Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
-n | Do not print the trailing newline character. |
argument | Specifies a space delimited list of arguments to print. |
Name
shell:exec, exec — executes system processes
Synopsis
shell:exec
[
--help
] {
command
}
Arguments
Table 2.5. shell:exec Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
command | Specifies the command, with arguments, to execute. |
Name
shell:grep, grep — displays lines matching a regular expression
Synopsis
shell:grep
[
--help
] [[
-i
] | [
--ignore-case
]] [[
-w
] | [
--word-regexp
]] [[
-n
] | [
--line-number
]] [[
-x
] | [
--line-regexp
]] [[
-v
] | [
--invert-match
]] {
regex
}
Arguments
Table 2.6. shell:grep Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
-i, --ignore-case | Ignore case distinctions in both the regex and the input files. |
-w, --word-regexp |
Select only lines containing matches that form whole words.
A match qualifies if it meets one of the following conditions:
|
-n, --line-number | Display the line number of the match within its input file. |
-x, --line-regexp | Selects only those matches that exactly match the whole line. |
-v, --invert-match | Select non-matching lines. |
regex | Specifies the regular expression to match. |
Name
shell:head, head — displays the first lines of a file
Synopsis
shell:head
[
--help
] [
-n numLines
] {[
path
] | [
URL
]}
Arguments
Table 2.7. shell:head Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
-n | Specifies the number of lines to display. Default is 1. |
path | The path(s) of the file to display, separated by whitespace (separated by - for STDIN) |
URL | Specifies the URL(s) to display, separated by whitespace (separated by - for STDIN) |
Name
shell:history, history — prints the command history
Synopsis
shell:history
[
--help
]
Arguments
Table 2.8. shell:history Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name
shell:if, if — executes an if/then/else block
Synopsis
shell:if
[
--help
] {
condition
} {
ifTrue
} [
ifFalse
]
Arguments
Table 2.9. shell:if Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
condition | Boolean condition. |
ifTrue | Function to evaluate, if condition is true. |
ifFalse | Function to evaluate, if condition is false. |
Name
shell:info, info — displays system information and statistics about the container
Synopsis
shell:info
[
--help
]
Arguments
Table 2.10. shell:info Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this utility |
Name
shell:java, java — execute a Java application
Synopsis
shell:java
[
--help
] [[
-m
] | [
--method
] methodName
] {
className
} [
arguments
]
Arguments
Table 2.11. shell:java Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-m , --method | Specifies the name of a method to invoke. The default is main() . |
className | Specifies the name of the class to invoke. |
arguments | Specifies the arguments to pass to the method of the given className. |
Name
shell:logout, logout — disconnects the shell from the current session
Synopsis
shell:logout
[
--help
]
Arguments
Table 2.12. shell:logout Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name
shell:more, more — displays output as pages of a specified length
Synopsis
shell:more
[
--help
] [
--lines numLines
]
Arguments
Table 2.13. shell:more Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--lines | Specifies the number of lines to display before pausing. |
Name
shell:new, new — creates a new Java object of the specified class
Synopsis
shell:new
[
--help
] {
class
} [
arg
...]
Arguments
Table 2.14. shell:new Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
class | The class of the object to create. |
args | The constructor arguments. |
Name
shell:printf, printf — formats and prints the specified output
Synopsis
shell:printf
[
--help
] {
format
} {
arguments
}
Arguments
Table 2.15. shell:printf Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
format | The output format pattern to use |
arguments | The arguments for the given format pattern |
Name
shell:sleep, sleep — sleeps for a specified time, then wakes up
Synopsis
shell:sleep
[
--help
] [[
-s
] | [
--second
]] {
duration
}
Arguments
Table 2.16. shell:sleep Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-s, --second | Specify the duration in seconds (instead of milliseconds). |
duration | The time to sleep in milliseconds (default) or in seconds (with the -s option). |
Name
shell:sort, sort — writes a sorted concatenation of the specified files to standard output
Synopsis
shell:sort
[
--help
] [[
-t
] | [
--field-separator
] sep
] [[
-b
] | [
--ignore-leading-blanks
]] [[
-f
] | [
--ignore-case
]] [[
-r
] | [
--reverse
]] [[
-k
] | [
--key
] keys
] [[
-n
] | [
--numeric-sort
]] [[
-u
] | [
--unique
]] {
file
...}
Arguments
Table 2.17. shell:sort Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-t , --field-separator | Specifies a character to use as a field separator. The default is whitespace. |
-b , --igonore-leading-blanks | Igonores leading blanks. |
-f , --ignore-case | Ignores case when sorting. |
-r , --reverse | Reverses the result of the sort. |
-k , --key | Specifies a space delimited list of fields to use for sorting. |
-n , --numeric-set | Compares according to string numerical value. |
-u , --unique | Outputs only the first of an equal run. |
files | Specifies a space delimited list of files to sort. |
Name
shell:source, source — run a shell script
Synopsis
shell:source
[
--help
] {
script
} [
arguments
]
Arguments
Table 2.18. shell:source Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
script | A URI pointing to the script |
arguments | Arguments to pass to the script |
Name
shell:tac, tac — captures the STDIN and returns it as a string and optionally writes the content to a file
Synopsis
shell:tac
[
--help
] [
-f fileName
]
Arguments
Table 2.19. shell:tac Arguments
Option | Interpretation |
---|---|
--help | Displays the online help for this command |
-f | Specifies the name of the file into which the output is written. |
Name
shell:tail, tail — displays the last lines of a file
Synopsis
shell:head
[
--help
] [
-n lineNum
] [
-s seconds
] [
-f
] {[
path
] | [
URL
]...}
Arguments
Table 2.20. shell:tail Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
-n | Specifies the number of lines to display. The default is 1. |
-s | Specifies the interval, in seconds, to sleep before checking for changes to display. |
-f | Follow file changes. |
path | A space delimited list of file paths to display. |
URL | A space delimited list of file URLs to display. |
Name
shell:watch, watch — watches and refreshes the output of a command
Synopsis
shell:watch
[
--help
] [[
-n
] | [
--interval
] seconds
] {
command
}
Arguments
Table 2.21. shell:watch Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-n ,--interval | Specifies the interval, in seconds, between executions of the command. The default is 1. |
command | Specifies the command to watch and refresh. |
Chapter 3. ActiveMQ Console Commands
activemq:
then press Tab at the prompt to view the available commands.
Name
activemq:browse, browse — displays messages on a specified destination
Synopsis
activemq:browse
{
--amqurl brokerURL
} [
--msgsel
{
msgsel
...}
] [
--factory className
] [
--passwordFactory className
] [
--user username
] [
--password password
] [
--view
{
attr
...}
] [[
-Vheader
] | [
-Vcustom
] | [
-Vbody
]] [
--version
] [[
--help
] | [
-h
] | [
-?
]]
destName
Arguments
Table 3.1. activemq:browse Arguments
Argument | Interpretation |
---|---|
--amqurl brokerURL | Specifies the URL of the broker to which you are connecting. |
--msgsel msgsel1,msgsel2,... | Displays messages matched by the message selector. |
--factory className | Load className as the javax.jms.ConnectionFactory to use for creating connections. |
--passwordFactory className | Load className as the org.apache.activemq.console.command.PasswordFactory for retrieving the password from a keystore. |
--user username | Username to use for JMS connections. |
--password password | Password to use for JMS connections. |
-Vheader | Shows all the standard JMS message headers. |
-Vcustom | Shows all the custom fields added to each JMS message. |
-Vbody | Shows the body of the message. |
--view attr1,attr1,... | Selects the specific attribute of the message to view. |
--version | Displays the version information. |
-h, -?, --help | Displays the online help for this command. |
Message filters
--msgsel
option take the form header=value
. Table 3.2, “Message Headers for Filtering” lists the headers you can use to filter messages.
Table 3.2. Message Headers for Filtering
Name | Type |
---|---|
JMSCorrelationID | String |
JMSDeliveryMode | 1 -Non-Persistent, 2 -Persistent |
JMSDestination | javax.jms.Destination |
JMSExpiration | long |
JMSMessageID | String |
JMSPriority | int |
JMSRedelivered | boolean |
JMSReplyTo | javax.jms.Destination |
JMSTimestamp | long |
JMSType | String |
Examples
TEST.FOO
on a broker:
JBossA-MQ:karaf@root>
activemq:browse --amqurl tcp://localhost:61616 TEST.FOO
TEST.FOO
queue:
JBossA-MQ:karaf@root>
activemq:browse --amqurl tcp://localhost:61616 -Vbody TEST.FOO
10
:
JBossA-MQ:karaf@root>
activemq:browse --amqurl tcp://localhost:61616 --msgsel JMSMessaageID='*:10' TEST.FOO
3
, enter:
JBossA-MQ:karaf@root>
activemq:browse --amqurl tcp://localhost:61616 --msgsel JMSPriority=3 TEST.FOO
JBossA-MQ:karaf@root>
activemq:browse --amqurl tcp://localhost:61616 --msgsel JMSMessaageID='*:10',JMSPriority=3 TEST.FOO
Name
activemq:bstat, bstat — summarizes the statistics for a broker
Synopsis
activemq:bstat
[
--jmxurl JMXUrl
] [
--pid PID
] [
-jmxuser userName
] [
-jmxpassword password
] [
-jmxlocal
] [
--version
] [[
--help
] | [
-h
] | [
-?
]] {
brokerName
}
Arguments
Table 3.3. activemq:bstat Arguments
Argument | Description |
---|---|
--jmxurl URL | Sets the JMX URL used to locate brokers. |
--pid PID | Set the pid to connect to (only on Sun JVM). |
--jmxuser user | Sets the JMX user, used for authentication. |
--jmxpassword password | Sets the JMX password, used for authentication. |
--jmxlocal | Use the local JMX server instead of a remote server. |
--version | Displays the version information. |
-h, -?, --help | Displays the online help for this command. |
brokerName | The name of the broker |
Name
activemq:list — lists all available brokers in the specified JMX context
Synopsis
activemq:list
[
--jmxurl JMXUrl
] [
--pid PID
] [
-jmxuser userName
] [
-jmxpassword password
] [
-jmxlocal
] [
--version
] [[
--help
] | [
-h
] | [
-?
]]
Arguments
Table 3.4. activemq:list Arguments
Argument | Interpretation |
---|---|
--jmxurl URL | Sets the JMX URL to connect to |
--pid PID | Set the pid to connect to (only on Sun JVM). |
--jmxuser user | Sets the JMX user, used for authentication |
--jmxpassword password | Sets the JMX password, used for authentication |
--jmxlocal | Specifies to use the local JMX server instead of a remote server |
--version | Displays the version information |
-h, -?, --help | Displays the online help for this command |
Name
activemq:purge, purge — purges messages from a destination
Synopsis
activemq:purge
[
--msgsel
{
msgsel
...}
] [
--pid PID
] [
--jmxurl JMXUrl
] [
-jmxuser userName
] [
-jmxpassword password
] [
-jmxlocal
] [
--version
] [[
--help
] | [
-h
] | [
-?
]] {
destName
}
Arguments
Table 3.5. activemq:purge Arguments
Option | Interpretation |
---|---|
--msgsel msgsel1,msgsel2,... | Purges messages matched by the message selector. See the section called “Message filters”. |
--jmxurl URL | Sets the JMX URL used to locate the broker. |
--pid PID | Set the pid to connect to (only on Sun JVM). |
--jmxuser user | Sets the JMX user, used for authentication. |
--jmxpassword password | Sets the JMX password, used for authentication. |
--jmxlocal | Specifies to use the local JMX server instead of a remote server |
--version | Displays the version information |
-h, -?, --help | Displays the online help for this command |
destName | The specified message destination(s) |
Examples
TEST.FOO
on a broker:
JBossA-MQ:karaf@root>
activemq:purge TEST.FOO
10
:
JBossA-MQ:karaf@root>
activemq:purge --msgsel JMSMessaageID='*:10' TEST.FOO
3
, enter:
JBossA-MQ:karaf@root>
activemq:purge --msgsel JMSPriority=3 TEST.FOO
JBossA-MQ:karaf@root>
activemq:purge --msgsel JMSMessaageID='*:10',JMSPriority=3 TEST.FOO
Name
activemq:query, query — queries the for broker information on specific objects
Synopsis
activemq:query
[
-QMBeanType=name
] [
-xQMBeanType=name
] [
--objname query
] [
--xobjname query
] [
--view
{
attr
...}
] [
--jmxurl JMXUrl
] [
--pid PID
] [
-jmxuser userName
] [
-jmxpassword password
] [
-jmxlocal
] [
--version
] [[
--help
] | [
-h
] | [
-?
]]
Arguments
Table 3.6. activemq:query Arguments
Argument | Interpretation |
---|---|
-Q type=name | Adds to the search list the specific object type matched by the defined object identifier. |
-xQ type=name | Removes from the search list the specific object type matched by the object identifier. |
--objname query | Adds to the search list objects matched by the query similar. |
--xobjname query | Removes from the search list objects matched by the query. |
--view attr1,attr2,... | Selects the specific attribute of the object to view. By default, all attributes are displayed. |
--jmxurl URL | Sets the JMX URL to connect to. |
--pid PID | Set the pid to connect to (only on Sun JVM). |
--jmxuser user | Sets the JMX user, used for authentication |
--jmxpassword password | Sets the JMX password, used for authentication |
--jmxlocal | Specifies to use the local JMX server instead of a remote server |
--version | Displays the version information |
-h, -?, --help | Displays the online help for this command |
Examples
JBossA-MQ:karaf@root>
activemq:query
TEST.FOO
:
JBossA-MQ:karaf@root>
activemq:query -QTopic=TEST.FOO
host
:
JBossA-MQ:karaf@root>
activemq:query -QBroker=*host
JBossA-MQ:karaf@root>
activemq:query -QQueue=*
.FOO
except those that also begin with ActiveMQ.Advisory.
:
JBossA-MQ:karaf@root>
activemq:query -QTopic=*.FOO -xQTopic=ActiveMQ.Advisory.*
Chapter 4. Admin Console Commands
admin:
then press Tab at the FuseMQkaraf:karaf@root>
prompt to view the available commands.
Name
admin:change-opts, change-opts — changes the Java options of an existing container
Synopsis
admin:change-opts
[
--help
] {
name
} {
opts
}
Arguments
Table 4.1. admin:change-opts Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
name | The name of the container for which you want to change the Java options |
opts | The Java options to change |
Name
admin:change-rmi-registry-port, change-rmi-registry-port — changes the RMI registry port used by the management layer of a container
Synopsis
admin:change-rmi-registry-port
[
--help
] {
name
} {
port
}
Arguments
Table 4.2. admin:change-rmi-registry-port Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
name | The name of the container instance for which you want to change the port |
port | The new RMI registry port |
Name
admin:change-rmi-server-port, change-rmi-server-port — changes the RMI server port used by the management layer of a container
Synopsis
admin:change-rmi-server-port
[
--help
] {
name
} {
port
}
Arguments
Table 4.3. admin:change-rmi-server-port Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
name | The name of the container instance for which you want to change the port |
port | The new RMI server port |
Name
admin:change-ssh-port, changessh-port — changes the secure shell port of a container
Synopsis
admin:change-ssh-port
[
--help
] {
name
} {
port
}
Arguments
Table 4.4. admin:change-ssh-port Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
name | The name of the container instance for which you want to change the port |
port | The new secure shell port |
Name
admin:clone, clone — clones an existing container instance
Synopsis
admin:clone
[
--help
] [[
-l
] | [
--location
]fileName
] [[
-o
] | [
--java-opts
]JVMOpts
] [[
-s
] | [
--ssh-port
]port
] [[
-rs
] | [
--rmi-server-port
]port
] [[
-r
] | [
-rr
] | [
--rmi-port
] | [
--rmi-registry-port
]port
] [[
-v
] | [
--verbose
]] {
name
} {
cloneName
}
Arguments
Table 4.5. admin:clone Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-l, --location | Location of the cloned container instance in the file system. |
-o, --java-opts | JVM options to use when launching the cloned instance. |
-s, --ssh-port | Port number for remote secure shell connection. |
-rs, --rmi-server-port | Port number for RMI server connection. |
-r, -rr, --rmi-port, --rmi-registry-port | Port number for RMI registry connection. |
-v, --verbose | Display actions performed by the command (disabled by default). |
name | Name of the original container instance. |
cloneName | Name of the cloned container instance. |
Name
admin:connect, connect — connects to an existing container
Synopsis
admin:connect
[
--help
] [[
-u
] | [
--username
] userName
] [[
-p
] | [
--password
] password
] {
container
} [
command
]
Arguments
Table 4.6. admin:connect Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-u, --username | The remote user name; the default is karaf |
-p, --password | The remote user password; the default is karaf |
container | The container to connect to |
command | Command to execute on connecting |
Name
admin:create, create — creates a new child container
Synopsis
admin:create
[
--help
] [[
-l
] | [
--location
] filePath
] [[
-furl
] | [
--featureURL
] URL
...] [[
-f
] | [
--feature
] feature
...] [[
-s
] | [
--ssh-port
] SSHPort
] [[
-rs
] | [
--rmi-server-port
] RMIServPort
] [[
-r
] | [
-rr
] | [
--rmi-registry-port
] | [
--rmi-port
] RMIRegPort
] [[
-o
] | [
--java-opts
] javaOpts
] {
name
}
Arguments
Table 4.7. admin:create Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-l, --location | The location of the child's data folders on the file system. By default, the child's data is added to the InstallDir/instances/name directory |
-furl , --featureURL | Registers additional feature URLs with the child. |
-f , --feature | Specifies additional features loaded by the child. |
-s, --ssh-port | The port number for remote secure shell connection |
-rs, --rmi-server-port | The port number for RMI server connection |
-r, -rr, --rmi-registry-port, --rmi-port | The port number for RMI registry connection |
-o, --java-opts | JVM options to use when launching the child |
name | The name of the child |
Name
admin:destroy, destroy — destroys a child container
Synopsis
admin:destroy
[
--help
] {
name
}
Arguments
Table 4.8. admin:destroy Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
name | The name of the container to destroy |
Name
admin:list — list all of the child containers on the current host
Synopsis
admin:list
[
--help
] [[
-l
] | [
--location
] filePath
] [[
-o
] | [
--java-opts
] javaOpts
]
Arguments
Table 4.9. admin:list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-l, --location | Displays the location of the container instances |
-o, --java-opts | Displays the options used when launching the container's JVM |
Name
admin:rename, rename — renames a child container
Synopsis
admin:rename
[
--help
] {
name
} {
new-name
}
Arguments
Table 4.10. admin:rename Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
name | Current name of the container |
new-name | The new name for the container |
Name
admin:start — starts a child container
Synopsis
admin:start
[
--help
] [[
-o
] | [
--java-opts
] javaOpts
] {
name
}
Arguments
Table 4.11. admin:start Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-o, --java-opts | The Java options used when launching the container |
name | The name of the container to start |
Name
admin:stop — stops a child container
Synopsis
admin:stop
[
--help
] {
name
}
Arguments
Table 4.12. admin:stop Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
name | The name of the container to start |
Chapter 5. Camel Console Commands
Name
camel:context-info — display detailed information about the specified Camel context
Synopsis
camel:context-info
[
--help
] {
contextName
}
Arguments
Table 5.1. camel:context-info Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
contextName | The name of the Camel context. |
Name
camel:context-list — list all active Camel contexts
Synopsis
camel:context-list
[
--help
]
Arguments
Table 5.2. camel:context-list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name
camel:context-start — start up the specified Camel context
Synopsis
camel:context-start
[
--help
] {
contextName
}
Arguments
Table 5.3. camel:context-start Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
contextName | The name of the Camel context. |
Name
camel:context-stop — stop the specified Camel context
Synopsis
camel:context-stop
[
--help
] {
contextName
}
Arguments
Table 5.4. camel:context-stop Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
contextName | The name of the Camel context. |
Name
camel:endpoint-list — lists all deployed Camel endpoints
Synopsis
camel:endpoint-list
[
--help
]
Arguments
Table 5.5. camel:endpoint-list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name
camel:route-info — display detailed information about the specified Camel route
Synopsis
camel:route-info
[
--help
] {
route
} [
contextName
]
Arguments
Table 5.6. camel:route-info Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
route | The Camel route ID. |
contextName | (Optional) The Camel context name. |
Name
camel:route-list — list the Camel routes
Synopsis
camel:route-list
[
--help
] [
contextName
]
Description
Arguments
Table 5.7. camel:route-list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
contextName | (Optional) The Camel context name. |
Name
camel:route-resume — resume the specified Camel route (which was previously suspended)
Synopsis
camel:route-resume
[
--help
] {
route
} [
contextName
]
Arguments
Table 5.8. camel:route-resume Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
route | The Camel route ID. |
contextName | (Optional) The Camel context name. |
Name
camel:route-show — display the Camel route definition in XML format
Synopsis
camel:route-show
[
--help
] {
route
} [
contextName
]
Arguments
Table 5.9. camel:route-show Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
route | The Camel route ID. |
contextName | (Optional) The Camel context name. |
Name
camel:route-start — start the specified Camel route
Synopsis
camel:route-start
[
--help
] {
route
} [
contextName
]
Arguments
Table 5.10. camel:route-start Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-n ,--interval | |
route | The Camel route ID. |
Name
camel:route-stop — stop the specified Camel route
Synopsis
camel:route-stop
[
--help
] {
route
} [
contextName
]
Arguments
Table 5.11. camel:route-stop Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
route | The Camel route ID. |
contextName | (Optional) The Camel context name. |
Name
camel:route-suspend — suspend the specified Camel route
Synopsis
camel:route-suspend
[
--help
] {
route
} [
contextName
]
Arguments
Table 5.12. camel:route-suspend Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
route | The Camel route ID. |
contextName | (Optional) The Camel context name. |
Chapter 6. Config Console Commands
etc
folder.
- Start the editing session for the specified configuration.config:edit
- Edits, or creates, a configuration.
- config:proplistLists the properties in the configuration.
- config:propappendAppend a new property to the configuration.
- config:propsetSets the value for a configuration property.
- config:propdelDeletes a property from the configuration.
- config:updateSaves the changes and updates the containers using the configuration.
config:
then press Tab at the prompt to view the available commands.
Name
config:cancel — cancels the changes to the configuration being edited
Synopsis
config:cancel
[
--help
]
Details
Arguments
Table 6.1. config:cancel Arguments
Option | Interpretation |
---|---|
--help | Displays the online help for this command |
Name
config:delete, delete — deletes a configuration from the container
Synopsis
config:delte
[
--help
] [[
-f
] | [
--use-file
]] [
--no-delete-cfg-file
] {
pid
}
Details
--no-delete-cfg-file
argument, the original settings can be reloaded from the configuration file.
Arguments
Table 6.2. config:delete Arguments
Option | Interpretation |
---|---|
--help | Displays the online help for this command. |
-f , --use-file | Use a filename instead of the PID to locate the configuration. |
--no-delete-cfg-file | Does not delete the associated configuration file from the container's etc folder. |
pid | Specifies the configuration's persistent identifier. |
Name
config:edit, edit — begins an editing session for a configuration. If the configuration does not exist a new configuration is created.
Synopsis
config:edit
[
--help
] [
--force
] [[
-f
] | [
--use-file
]] {
pid
}
Details
Arguments
Table 6.3. config:edit Arguments
Option | Interpretation |
---|---|
--help | Displays the online help for this command |
--force | Forces the editing of this configuration, even if another configuration was being edited |
-f , --use-file | Use a filename instead of the PID to locate the configuration |
pid | The persistent identifier of the configuration |
Name
config:list — lists the existing configurations for the container
Synopsis
config:list
[
--help
] [
query
]
Arguments
Table 6.4. config:list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
query | An LDAP query |
Name
config:propappend, propappend — appends the given value to an existing property or creates the property with the specified name and value
Synopsis
config:propappend
[
--help
] [[
-b
] | [
--bypass-storage
]] [[
-p PID
] | [
--pid PID
]] {
name
} {
value
}
Details
-p
argument to specify a PID, however, the change is made immediately.
Arguments
Table 6.5. config:propappend Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
-b , --bypass-storage | Doe not write the change to the local file. |
-p , --pid | Specifies the PID of the configuration in which to make the change. The default is to change the configuration currently open for editing. |
name | Specifies the name of the property to change. |
value | Specifies the value to append to the property. |
Name
config:propdel, propdel — deletes a property from the configuration being edited
Synopsis
config:propdel
[
--help
] [[
-b
] | [
--bypass-storage
]] [[
-p PID
] | [
--pid PID
]] {
name
}
Details
-p
argument to specify a PID, however, the change is made immediately.
Arguments
Table 6.6. config:propdel Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
-b , --bypass-storage | Does not write the change to the local file. |
-p , --pid | Specifies the PID of the configuration in which to make the change. The default is to change the configuration currently open for editing. |
name | Specifies the name of the property to delete. |
Name
config:proplist, proplist — lists the properties in the configuration being edited
Synopsis
config:proplist
[
--help
] [[
-p PID
] | [
--pid PID
]]
Arguments
Table 6.7. config:proplist Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-p , --pid | The PID of the configuration in which to make the change |
Name
config:propset, propset — sets a property in the configuration being edited
Synopsis
config:propset
[
--help
] [[
-b
] | [
--bypass-storage
]] [[
-p PID
] | [
--pid PID
]] {
name
} {
value
}
Details
-p
argument to specify a PID, however, the change is made immediately.
Arguments
Table 6.8. config:propset Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
-b , --bypass-storage | Does not write the change to the local file. |
-p , --pid | Specifies the PID of the configuration in which to make the change. The default is to change the configuration currently open for editing. |
name | Specifies the name of the property to set. |
value | Specifies the value to set for the property. |
Name
config:update — saves the changes made to the configuration being edited and propagates then to the container
Synopsis
config:propset
[
--help
] [[
-b
] | [
--bypass-storage
]]
Arguments
Table 6.9. config:update Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-b , --bypass-storage | Do not update the copy of the configuration on the file system |
Chapter 7. CXF Console Commands
JBossFuse:karaf@root> features:install cxf-osgi
Name
cxf:list-busses — lists all Apache CXF buses
Synopsis
cxf:list-busses
[
--help
]
Arguments
Table 7.1. cxf:list-busses Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name
cxf:list-endpoints — list all active endpoints belonging to the specified Apache CXF bus
Synopsis
cxf:list-endpoints
[
--help
] {
busID
}
Arguments
Table 7.2. cxf:list-endpoints Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
busID | The Apache CXF bus ID. |
Name
cxf:start-endpoint — start the specified Apache CXF endpoint belonging to the specified bus
Synopsis
cxf:start-endpoint
[
--help
] {
busID
} {
endpointName
}
Arguments
Table 7.3. cxf:start-endpoint Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
busID | The Apache CXF bus ID. |
endpointName | The name of the Apache CXF endpoint. |
Name
cxf:stop-endpoint — stop the specified Apache CXF endpoint belonging to the specified bus
Synopsis
cxf:stop-endpoint
[
--help
] {
busID
} {
endpointName
}
Arguments
Table 7.4. cxf:stop-endpoint Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
busID | The Apache CXF bus ID. |
endpointName | The name of the Apache CXF endpoint. |
Chapter 8. Dev Console Commands
dev:
then press Tab at the prompt to view the available commands.
Name
dev:classloaders, classloaders — displays a list of leaking bundle classloaders
Synopsis
dev:classloaders
[
--help
]
Arguments
Table 8.1. dev:classloader Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name
dev:create-dump, create-dump — creates a ZIP file containing diagnostic information
Synopsis
dev:create-dump
[
--help
] [[
-d dumpFolder
] | [
--directory dumpFolder
]] {
dumpName
}
Arguments
Table 8.2. dev:create-dump Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-d , --directory | Specifies the folder into which to store the dump |
dumpName | Specifies the name for the dump file |
Name
dev:dynamic-import, dynamic-import — enables/disables dynamic imports for a bundle
Synopsis
dev:dynamic-import
[
--help
] {
bundleID
}
Arguments
Table 8.3. dev:dynamic-import Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
bundleID | A bundle ID. |
Name
dev:framework, framework — enables/disables debugging for an OSGi framework
Synopsis
dev:framework
[
--help
] {[[
-debug
] | [
--enable-debug
]] [[
-nodebug
] | [
--disable-debug
]]} {
framework
}
Arguments
Table 8.4. dev:framework Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-nodebug, --disable-debug | Disable debugging for the OSGi framework. |
-debug, --enable-debug | Enable debugging for the OSGi framework. |
framework | Name of the OSGi framework |
Name
dev:print-stack-traces, print-stack-traces — enables/disables printing of full stack traces in the console when the execution of a command throws an exception
Synopsis
dev:print-stack-traces
[
--help
] [
false
]
Arguments
Table 8.5. dev:print-stack-traces Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
false | Disables stack traces |
Name
dev:restart — restart the container
Synopsis
dev:restart
[
--help
] [[
-c
] | [
--clean
]]
Arguments
Table 8.6. dev:restart Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-c, --clean | Force a clean (cold) restart by deleting the container's data directory. |
Name
dev:show-tree, show-tree — shows the tree of bundles based on the wiring information
Synopsis
dev:show-tree
[
--help
] {
bundleID
}
Arguments
Table 8.7. dev:show-tree Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
bundleID | A bundle ID. |
Name
dev:threads, threads — shows the threads in the JVM
Synopsis
dev:threads
[
--help
] [[
-f
] | [
--flat
]]
Arguments
Table 8.8. dev:threads Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-f , --flat | Do not show the threads in a tree |
Name
dev:wait-for-service, wait-for-service — wait for the specified OSGi service
Synopsis
dev:wait-for-service
[
--help
] [[
-t
] | [
--timeout
]timeout
] [[
-e
] | [
--exception
]] {
serviceClassOrFilter
}
Description
shell:*
, admin:*
, features:*
, and so on) are represented by OSGi services of type, org.apache.karaf.shell.console.SubShell
. If you want to check that a sub-shell service is available, you could enter the following console command:
karaf@root> dev:wait-for-service -t 1000 org.apache.karaf.shell.console.SubShell true
SubShell
service installed in the container. To be more specific, you can define an LDAP filter, which specifies one or more service property values. For example, you can wait specifically for the osgi
sub-shell service by entering a command like the following:
karaf@root> dev:wait-for-service -t 1000 &(objectClass=org.apache.karaf.shell.console.SubShell)(name=osgi) true
Arguments
Table 8.9. dev:wait-for-service Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-t, --timeout | Timeout (specified in milliseconds: negative to not wait at all, zero to wait forever). Default is forever. |
-e, --exception | Throw an exception if the wait command times out (the service is not found). Default is false. |
serviceClassOrFilter | Specifies the OSGi service either by the service's class name or by an LDAP-style filter (which is applied to the OSGi service's properties). |
Name
dev:watch, watch — watches and automatically updates bundles
Synopsis
dev:watch
[
--help
] [[
--start
] | [
--stop
]] [
-i interval
] [
--list
] [
--remove
] {
bundles
...}
Arguments
Table 8.10. dev:watch Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--stop | Stop watching the specified bundles |
--start | Start watching the specified bundles |
-i | Specifies the interval, in milliseconds, to check the bundles. |
--list | List the bundles being watched. |
--remove | Remove the specified bundles from the watch list. |
bundles... | Specifies a whitespace delimited list of bundle URLs or bundle IDs. |
JBossA-MQ:karaf@root>
dev:watch *
Chapter 9. Fuse Application Bundle(FAB) Console Commands
osgi:install
command combined with the fab:
URL prefix. For example, to install the FAB mvn:org.fusesource.example/camel-example/1.0
use the following console command:
JBossA-MQ:karaf@root>
osgi:install fab:mvn:org.fusesource.example/camel-example/1.0
Name
fab:headers — displays the headers of a FAB
Synopsis
fab:headers
[
--help
] [
--indent style
] {
URL
}
Description
META-INF/MANIFEST.MF
file embedded in the FAB JAR file. This is not the same thing as the bundle headers returned by the osgi:headers
command, because the osgi:headers
command shows the effective headers after the FAB is converted into an OSGi bundle.
JBossA-MQ:karaf@root>
fab:headers mvn:org.fusesource.examples/cbr/7.0.0.fuse-beta-042
Manifest-Version = 1.0 Archiver-Version = Plexus Archiver Built-By = username Build-Jdk = 1.6.0_29 Created-By = Apache Maven
JBossA-MQ:karaf@root>
osgi:headers 228
org.fusesource.examples.cbr (228) --------------------------------- Manifest-Version = 1 Bnd-LastModified = 1334306872960 Archiver-Version = Plexus Archiver Tool = Bnd-1.43.0 Originally-Created-By = Apache Maven FAB-URL = mvn:org.fusesource.examples/cbr/7.0.0.fuse-beta-042 Generated-By-FAB-From = mvn:org.fusesource.examples/cbr/7.0.0.fuse-beta-042 Built-By = username FAB-Id = org.fusesource.examples:cbr:7.0.0.fuse-beta-042:jar Build-Jdk = 1.6.0_29 Created-By = 1.6.0_29 (Apple Inc.) Bundle-Name = org.fusesource.examples.cbr Bundle-SymbolicName = org.fusesource.examples.cbr Bundle-Version = 7.0.0.fuse-beta-042 Bundle-ManifestVersion = 2 Export-Package = OSGI-INF.blueprint, OSGI-INF
Arguments
Table 9.1. fab:headers Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--indent | Specify the indent style. Valid values are 1 , 2 , or 3 . The default is -1 . |
URL | The URL of the FAB |
Name
fab:info — display information about a FAB, including the list of shared and unshared dependencies, and the list of features installed as part of the FAB resolution process
Synopsis
fab:info
[
--help
] {
bundleID
}
Arguments
Table 9.2. fab:info Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
bundleID | The bundle ID of the FAB (for deployed FABs) or the URL location of the FAB (for FABs that are not yet deployed). |
Name
fab:start — starts the specified FAB
Synopsis
fab:start
[
--help
] [
--timeout millis
] {
bundleID
}
Description
META-INF/maven/GroupID/ArtifactID/pom.xml
. Any transitive dependencies that are shared (for example, by being marked as provided or because the dependency is already packaged as an OSGi bundle), are deployed as separate OSGi bundles in the container.
fab:start
, the runtime attempts to start all of the corresponding bundles, starting with the leaves of the dependency tree and working its way up the tree to the FAB's bundle. In particular, this implies that any OSGi services, blueprint XML files, and Spring XML files in the dependent OSGi bundles are activated in the appropriate order.
Arguments
Table 9.3. fab:start Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--timeout | Specifies, in milliseconds, how long to wait for the FAB bundle to start up. Default is 30000 . |
bundleID | The bundle ID of the FAB. |
Name
fab:stop — stops the specified FAB bundle together with its shared transitive dependencies, except for those dependencies that are being used by other bundles.
Synopsis
fab:stop
[
--help
] {
bundleID
}
Arguments
Table 9.4. fab:stop Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
bundleID | The bundle ID of the FAB. |
Name
fab:tree, tree — displays the dependency tree of a FAB
Synopsis
fab:tree
[
--help
] {
bundleID
}
Arguments
Table 9.5. fab:tree Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
bundleID | Specifies the bundle ID, URL, or filename of the FAB. |
Name
fab:uninstall — uninstall the specified FAB and all of its transitive dependencies, except for those dependencies that are being used by other bundles
Synopsis
fab:uninstall
[
--help
] {
bundleID
}
Description
META-INF/maven/GroupID/ArtifactID/pom.xml
. Any transitive dependencies that are shared (for example, by being marked as provided or because the dependency is already packaged as an OSGi bundle), are deployed as separate OSGi bundles in the container.
fab:uninstall
, the runtime attempts to uninstall all of the corresponding OSGi bundles, except for any bundles that are still being used by other applications in the container.
Arguments
Table 9.6. fab:uninstall Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
bundleID | The bundle ID of the FAB. |
Chapter 10. Fabric Console Commands
Name
fabric:cluster-list — lists the members of a cluster
Synopsis
fabric:cluster-list
[
--help
] [
Path
]
Description
fabric:cluster-list servlets
fabric:cluster-list webapps
Arguments
Table 10.1. fabric:cluster-list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Path | Path of the fabric registry node (Zookeeper registry node) to list. Relative paths are evaluated relative to the base node, /fabric/registry/clusters . If not specified, all clusters are listed |
Related topics
fabric:mq-create |
Name
fabric:cloud-firewall-edit — manage a cloud container's firewall
Synopsis
fabric:cloud-firewall-edit
[
--help
] [
--owner owner
] [
--option key=value
]
Arguments
Table 10.2. fabric:cloud-firewall-edit Arguments
Argument | Interpretation |
---|---|
--port | The target IP port. To specify multiple ports, specify this flag multiple times on the command line—for example, --port 1234 --port 5678 . |
--flush | Flush all rules. |
--revoke | Revoke the rule for the specified port. This blocks access to the specified IP port. |
--target-container | The target container name. |
--source-container | The source container, which has access granted or revoked. |
--target-node-id | The target node ID. |
--source-cidr | The source CIDR, which has access granted or revoked. |
--provider | The cloud provider name. |
--help | Displays the online help for this command. |
Name
fabric:cloud-service-add — initialize a cloud provider (which can be used for provisioning containers in the cloud)
Synopsis
fabric:cloud-service-add
[
--help
] [
--provider providerName
] [
--name name
] [
--api APIName
] [
--endpoint URL
] [
--identity accessKeyID
] [
--credential secretAccessKey
] [
--owner owner
] [
--option key=value
] [
--async-registration
]
Description
fabric:cloud-service-list
to discover when the initialization has completed.
- Commercial cloud provider—if you are using a commercial cloud provider, JClouds provides prepackaged modules that encapsulate the basic connection details for the provider. The prepackaged modules are available to install as Karaf features (named
jclouds-ProviderName
) and encapsulate such details as the endpoint URI, cloud API, and so on.For example, to install an Amazon Web Services (AWS) EC2 cloud provider, you can perform the following steps (assuming you are working in a standalone container):- Install the basic set of fabric cloud commands:
karaf@root> features:install fabric-jclouds
- Install the JClouds module specifically for AWS EC2:
karaf@root> features:install jclouds-aws-ec2
- Add the AWS EC2 provider, specifying the login credentials for your EC2 account:
karaf@root> fabric:cloud-service-add --provider aws-ec2 --identity AccessKeyID --credential SecretAccessKey
- You are now ready to start creating compute instances on the
aws-ec2
cloud service, using thefabric:container-create-cloud
command.
- Private cloud service—if you are hosting your compute instances on a private cloud service, you must specify the connection details more explicitly, by supplying the
--api
and--endpoint
options. In this case, you must also define a name for the cloud service, by supplying the--name
option.For example, to define a connection to a private cloud service that uses theopenstack-nova
API through the endpoint,http://172.16.0.1:4000/v2.0/
, you can perform the following steps (assuming you are working in a standalone container):- Install the basic set of fabric cloud commands:
karaf@root> features:install fabric-jclouds
- Install the JClouds module for the
openstack-nova
API:karaf@root> features:install jclouds-api-openstack-nova
- Add the private cloud service, specifying the login credentials, API, and endpoint URL:
karaf@root> fabric:cloud-service-add --name myOpenStack --api openstack-nova --endpoint http://172.16.0.1:4000/v2.0/ --identity AccessKeyID --credential SecretAccessKey
NoteYou can provide additional customisation of the connection by setting options through the--option
flag (which can appear multiple times in the command). - You are now ready to start creating compute instances on the
myOpenStack
cloud service, using thefabric:container-create-cloud
command.
Installing the command in a fabric
fabric-jclouds
feature. To install the fabric-jclouds
feature, deploy the cloud
profile into the current container, using the fabric:container-change-profile
command.
root
container of the Fabric, you could add the cloud
profile as follows:
JBossA-MQ:karaf@root> fabric:container-list [id] [version] [alive] [profiles] [provision status] root* 1.0 true fabric, fabric-ensemble-0000-1 success JBossA-MQ:karaf@root> fabric:container-change-profile root fabric fabric-ensemble-0000-1 cloud JBossA-MQ:karaf@root> fabric:container-list [id] [version] [alive] [profiles] [provision status] root* 1.0 true fabric, fabric-ensemble-0000-1, cloud success
Arguments
Table 10.3. fabric:cloud-service-add Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
--provider | The name of a commercial cloud provider (for example, aws-ec2 or rackspace ). |
--name | The JClouds service context name, which identifies the cloud service uniquely. Defaults to the provider name (as specified by the --provider option). |
--api | Specifies the cloud API (for example, ec2 , openstack-nova , or cloudstack ). |
--endpoint | Specifies the cloud service's endpoint URL. |
--identity | The identity used to access the cloud service. |
--credential | The credential used to access the cloud service. |
--owner | Specifies the EC2 AMI owner, which enables you to use private images (AWS EC2 only). |
--option | Provider-specific properties. For example: --option jclouds.regions=us-east-1 . If you want to specify more than one option, specify this option multiple times. |
--async-registration | Do not wait for the provider registration (that is, complete the registration in a background thread). |
Name
fabric:cloud-service-list — list the configured cloud providers
Synopsis
fabric:cloud-service-list
[
--help
]
Description
compute
or blobstore
), and registration (local
, for a standalone container, or fabric
, for a Fabric Container).
fabric-jclouds
feature. To install the fabric-jclouds
feature, deploy the cloud
profile into the current container, using the fabric:container-change-profile
command.
root
container of the Fabric, you could add the cloud
profile as follows:
JBossA-MQ:karaf@root>
fabric:container-list
[id] [version] [alive] [profiles] [provision status] root* 1.0 true fabric, fabric-ensemble-0000-1 success
JBossA-MQ:karaf@root>
fabric:container-change-profile root fabric fabric-ensemble-0000-1 cloud
JBossA-MQ:karaf@root>
fabric:container-list
[id] [version] [alive] [profiles] [provision status] root* 1.0 true fabric, fabric-ensemble-0000-1, cloud success
Arguments
Table 10.4. fabric:cloud-service-list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
Name
fabric:cloud-service-remove — removes the specified cloud provider
Synopsis
fabric:cloud-service-remove
[
--help
] {
Name
}
Description
fabric-jclouds
feature. To install the fabric-jclouds
feature, deploy the cloud
profile into the current container, using the fabric:container-change-profile
command.
root
container of the Fabric, you could add the cloud
profile as follows:
JBossA-MQ:karaf@root> fabric:container-list [id] [version] [alive] [profiles] [provision status] root* 1.0 true fabric, fabric-ensemble-0000-1 success JBossA-MQ:karaf@root> fabric:container-change-profile root fabric fabric-ensemble-0000-1 cloud JBossA-MQ:karaf@root> fabric:container-list [id] [version] [alive] [profiles] [provision status] root* 1.0 true fabric, fabric-ensemble-0000-1, cloud success
Arguments
Table 10.5. fabric:cloud-service-remove Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
Name | The JClouds service context name, which represents the cloud provider. |
Name
fabric:container-add-profile, container-add-profile — Adds the specified list of profiles to a container
Synopsis
fabric:container-add-profile
[
--help
] {
Name
} {
Profiles
}
Arguments
Table 10.6. fabric:container-add-profile Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name | Specifies the name of the container. |
Profiles | Specifies the list of profiles to add to the container. |
Name
fabric:container-change-profile, container-change-profile — replaces a fuse container's profiles with the specified list of profiles
Synopsis
fabric:container-change-profile
[
--help
] {
Name
} {
Profiles
}
Arguments
Table 10.7. fabric:container-change-profile Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name | Specifies the name of the container. |
Profiles | Specifies the list of profiles to deploy into the container. |
Name
fabric:container-connect, container-connect — connects to a remote Fabric Container and execute the specified command
Synopsis
fabric:container-connect
[
--help
] [[
-u
] | [
--username
]User
] [[
-p
] | [
--password
]Password
] {
ContainerName
} [
Command
]
Description
root2
container, you could enter a console command like Example 10.1, “Executing a Command in a Remote Container”.
Example 10.1. Executing a Command in a Remote Container
JBossA-MQ:karaf@root>
fabric:container-connect -u YourName -p YourPass root2 osgi:list
Arguments
Table 10.8. fabric:container-connect Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-u, --username | Specifies the username for logging on to the remote container. The default is admin . |
-p, --password | SPecifies the password for logging on to the remote container. The default is admin . |
ContainerName | Specifies the name of the remote container. |
Command | Specifies the console command to execute on the remote container. |
Related topics
Chapter 12, JAAS Console Commands |
Name
fabric:container-create-child — create one or more child containers
Synopsis
fabric:container-create-child
[
--help
] [
--ensemble-server
] [
--profile profileID
] [
--version version
] [
--jmx-user jmxUser
] [
--jmx-password jmxPass
] [
-b, --bind-address bindAddr
] [
--datastore-type storeType
] [
--datastore-option storeOption
] [
--zookeeper-password zooPass
] [
--jvm-opts jvmOpts
] [
--resolver policy
] [
-m, --manual-ip IPAddr
] {
parent
} {
name
} [
number
]
Description
- Each child container has a parent, so that the child containers form a hierarchy, with the root container as the ultimate ancestor.
- The child starts in a new JVM instance (JVM options can be passed to the new JVM through the
--jvm-opts
command option). - A complete set of data directories are created for the child instance, under the
ESBInstallDir/instances/ChildName
directory. TheESBInstallDir/system
directory is shared with the root container.
fabric:create
), you could add some child containers to the root container by entering the following command:
karaf@root> fabric:container-create-child root child 3
root
container. To check that the containers have been successfully created, invoke the fabric:container-list
command, as follows:
karaf@root> fabric:container-list [id] [version] [alive] [profiles] [provision status] root 1.0 true fabric, fabric-ensemble-0000-1 child1 1.0 true default success child2 1.0 true default success child3 1.0 true default success
child1
, child2
, and child3
, with the default
profile. This containers are ordinary (non-ensemble) containers, running fabric agents (ZooKeeper clients).
default
profile.
--profile
option multiple times. For example, if you want to deploy your own application profile, myApp
, together with the esb
profile, you would use a command like the following:
fabric:container-create-child --profile esb --profile myApp root childMyApp
Shutting down child containers
fabric:container-stop
command. For example, if a root container has three children—child1
, child2
, and child3
—you can issue the following commands in the root container console to shut down all of the containers:
karaf@root> fabric:container-stop child1 karaf@root> fabric:container-stop child2 karaf@root> fabric:container-stop child3 karaf@root> shutdown -f
Arguments
Table 10.9. fabric:container-create-child Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
--jmx-user | The JMX username of the parent container. |
--jmx-password | The JMX password of the parent container. |
--ensemble-server | Whether the new container should be a Fabric Server. |
--profile | A profile ID to associate with the new container. To associate multiple profiles with the container, specify this flag multiple times on the command line—for example, --profile foo --profile bar . If no profile is specified, the container is associated with the default profile. |
--resolver | Specifies how the container will report its address to other containers. Valid values are localip , localhostname , publicip , publichostname , manualip . For more information see fabric:container-resolver-set. |
-m, --manual-ip | The IP address to use, when using the manualip resolver. Used in combination with the --resolver option. |
-b, --bind-address | Specifies the default bind address. |
--datastore-type | Specifies the datastore type. |
--datastore-option | Options to pass to the container's datastore. To specify multiple options, use this flag multiple times. |
--zookeeper-password | Used in combination with the --ensemble-server option. If creating an ensemble server, specifies the Zookeeper password to use (if not specified, a password is generated automatically). |
--version | Specifies the version of the new container (the version must be created in advance using fabric:version-create ). Defaults to the current default version (use version-list to find the current default). |
--jvm-opts | Specify options to pass to the container's JVM. |
Parent | (Required) The parent container ID. |
Name | (Required) The name of the container to create. When creating multiple containers, it serves as a prefix |
Number | The number of containers that should be created. |
Related topics
fabric:container-resolver-list |
fabric:container-resolver-set |
fabric:create |
Name
fabric:container-create-cloud — creates one or more new containers on the cloud
Synopsis
fabric:container-create-cloud
[
--help
] [
--name contextName
] [
--provider cloudProvider
] [
--api cloudAPI
] [
--identity cloudIdentity
] [
--credential loginCredential
] [
--imageId imageID
] [
--os-family osFamily
] [
--os-version osVersion
] [
--hardwareId hardwareID
] [
--instanceType instanceType
] [
--locationId location
] [
--user userAcc
] [
--password userPass
] [
--public-key-file file
] [
--owner owner
] [
--group group
] [
--proxy-uri URI
] [
--ensemble-server
] [
--new-user jaasUser
] [
--new-user-password jaasUserPass
] [
--new-user-role jaasUserRole
] [
-b, --bind-address bindAddress
] [
--datastore-type storeType
] [
--datastore-option storeOption
] [
--zookeeper-password zooPass
] [
--resolver policy
] [
-m, --manual-ip IPAddr
] [
--env key=value
] [
--min-port minPort
] [
--max-port maxPort
] [
--profile profileID
] [
--version version
] [
--jvm-opts jvmOpts
] [
--add-option key=value
] [
--no-admin-access
] [
--path installPath
] {
Name
} [
Number
]
Description
fabric-jclouds
feature. To install the fabric-jclouds
feature, enter the following console command:
features:install fabric-jclouds
fabric:container-create-cloud
command provisions the container as follows:
- Creates a new node on the cloud provider. The node is created using a JClouds compute service: either by lookup in the service registry (using the provider ID as a property) or by instantiating a new node, by specifying the identity and credential of the provider.
- Connects to the created node, using the authentication metadata returned upon the node creation (this is usually a username and private key, where the username can be overridden by the
--user
option). After it connects to the node, it executes a script, which downloads the fabric distribution from the Maven proxy and untars the distribution.By default, the script uses the oldest Maven proxy server in the current ensemble (every ensemble server has a Maven proxy server deployed in it). You can optionally override the default Maven proxy by specifying the--proxy-uri
option. The script would then use the specified Maven proxy server to download the container runtime.NoteThe ability to override the Maven proxy is important in certain cases (for example, in a cloud deployment) where the remote host might not be able to access the default Maven proxy server. - Starts up the newly installed container (or containers) and installs the specified fabric profile (or profiles).
- When creating multiple containers using this command (by adding the
Number
argument), multiple nodes will be created and a root container will be installed on each node.
fabric:container-create-cloud
command with the --ensemble-server
flag, which makes the newly created container (or containers) an ensemble server, with its own fabric registry agent. The newly created ensemble server on the cloud does not join the current ensemble: it belongs to an independent ensemble (a new fabric).
Arguments
Table 10.10. fabric:container-create-cloud Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--name | (Required) JClouds service context name. |
--provider | JClouds provider name. |
--api | The cloud API name. |
--identity | The identity used to access the cloud service. |
--credential | The credential used to access the cloud service. |
--imageId | The image ID to use for the new node(s). Alternatively, the image can be specified indirectly using the --os-family and --os-version options. Defaults to an instance of the latest version of Ubuntu. |
--os-family | Specify the image by requesting a particular kind of operating system—for example, ubuntu or redhat . To see which O/S families are available, type Tab while entering this option. Defaults to ubuntu . |
--os-version | Specifies the version of the O/S family. The version number need not be exact (it will be rounded up to the latest available patch version). Defaults to the latest version available. |
--hardwareId | Kind of hardware to use. |
--instanceType | Type of instance required. |
--locationId | The location used to create the new node(s). |
--user | Specifies the O/S user account to run on the new nodes. If the user account does not already exist on the new nodes, it will automatically be created. Defaults to the username that matches the current user. |
--password | Specifies the password associated with the O/S user account defined by the --user option. |
--public-key-file | An option to specify a public key file to copy to the created node. Copying a public key file to a node can be used for SSH access using public key authentication. If no key file is specified, Fabric attempts to auto-detect the user's public key and, if found, this key will be used by default. |
--owner | Optional owner of images; only really used for EC2, and will be deprecated in future. |
--group | Group tag to use on the new node(s). Defaults to fabric . |
--proxy-uri | URL of the Maven proxy server used to download the container runtime. |
--ensemble-server | Whether the new container should be a Fabric Server (effectively creates a new fabric). |
--new-user |
Used in combination with the
--ensemble-server option to ensure that at least one user exists in the JAAS realm of the Zookeeper login module for the new fabric (otherwise it would be impossible to connect to the newly created Fabric Server).
When using this option, you must also specify a password using the
--new-user-password option.
|
--new-user-password | Used in combination with the --new-user option and the --ensemble-server option to specify the new user's password. No default value. |
--new-user-role | Used in combination with the --new-user option and the --ensemble-server to specify the new user's role. Default is admin . |
-b, --bind-address | Specifies the default bind address. |
--datastore-type | Specifies the datastore type. |
--datastore-option | Options to pass to the container's datastore. To specify multiple options, use this flag multiple times. |
--zookeeper-password |
Used in combination with the
--ensemble-server option. Specifies the Zookeeper password, which is used to access the Zookeeper nodes under the /fabric/ path. Defaults to the password of the current session user.
If you subsequently try to join the current container to the newly-created Fabric Server (ensemble server) using the
fabric:join command, you will be prompted to enter the Zookeeper password.
|
--resolver | Specifies how the container will report its address to other containers. Valid values are localip , localhostname , publicip , publichostname , manualip . For more information see fabric:container-resolver-set. |
-m, --manual-ip | The IP address to use, when using the manualip resolver. Used in combination with the --resolver option. |
--env | Sets an environment variable. To specify multiple environment variables, use this flag multiple times. |
--min-port | Specifies the minimum port number of the allowed IP port range. Default is 0 . |
--max-port | Specifies the maximum port number of the allowed IP port range. Default is 65535 . |
--profile | A list of profile IDs to associate with the new container. |
--version | Specifies the version of the new container (the version must be created in advance using fabric:version-create ). Defaults to the current default version (use version-list to find the current default). |
--jvm-opts | Specify options to pass to the container's JVM. |
--add-option | Specifies generic JCloud properties or provider-specify properties. For example, when using Amazon with Amazon VPC to create a container inside a VPN, you can specify --option subnetId=yoursubnetId to define the VPC subnet where you want the node to be created. If you want to specify more than one option, specify this option multiple times. |
--no-admin-access | Disables admin access, as it might not be feasible on all images. |
--path | Path on the remote filesystem where the container is to be installed. |
Name | (Required) The name of the container to create. When creating multiple containers, it serves as a prefix. |
Number | The number of containers that should be created. |
Related topics
Name
fabric:container-create-ssh — creates one or more new containers through SSH
Synopsis
fabric:container-create-ssh
[
--help
] [
--host host
] [
--port port
] [
--min-port minPort
] [
--max-port maxPort
] [
--path path
] [
--user user
] [
--password password
] [
--new-user newUser
] [
--new-user-password newPassword
] [
--new-user-role newRole
] [
--private-key keyPath
] [
--pass-phrase passPhrase
] [
--ssh-retries retries
] [
--proxy-uri URI
] [
--ensemble-server
] [
--profile profileID
] [
--version version
] [
-b, --bind-address bindAddress
] [
--datastore-type storeType
] [
--datastore-option storeOption
] [
--zookeeper-password zooPass
] [
--jvm-optsjvmOpts
] [
--resolver policy
] [
-m, --manual-ip IPAddr
] [
--env key=value
] [
--with-admin-access
] {
Name
} [
Number
]
Description
- Logs into the specified SSH host, using either the provided username and password or using the provided username and private key.
- Runs a script on the remote host that that downloads the container runtime to the remote host. The runtime files are downloaded through a Maven proxy server. By default, the script uses the oldest Maven proxy server in the current ensemble (every Fabric Server has a Maven proxy server deployed in it). You can optionally override the default Maven proxy by specifying the
--proxy-uri
option. The script would then use the specified Maven proxy server to download the container runtime.NoteThe ability to override the Maven proxy is important in certain cases (for example, in a cloud deployment) where the remote host might not be able to access the default Maven proxy server. - Starts up the newly installed container (or containers) and installs the specified fabric profile (or profiles).
fabric:container-create-ssh
command with the --ensemble-server
flag, which makes the newly created container (or containers) a Fuse Server. The newly created Fuse Server on the remote host does not join the current ensemble: it belongs to an independent ensemble (a new fabric).
Arguments
Table 10.11. fabric:container-create-ssh Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--host | (Required) Host name to SSH into. |
--port | The IP port number for the SSH connection. Default is 22 . |
--min-port | The minimum port number of the allowed IP port range. Default is 0 . |
--max-port | The maximum port number of the aollowed IP port range. Default is 65535 . |
--path | Path on the remote filesystem where the container is to be installed. |
--user | (Required) User name for login. |
--password | Password for login. If the password is omitted, private key authentication is used instead. |
--new-user | The username of a new user. The option refers to a Karaf user (ssh, http, jmx). Defaults is admin . |
--new-user-password | The password of the new user. The option refers to a Karaf user (ssh, http, jmx). |
--new-user-role | The role of the new user. The option refers to a Karaf user (ssh, http, jmx). |
--private-key | Specifies the path to the private key on the local file system. The default is ~/.ssh/id_rsa on *NIX platforms or C:\Documents and Settings\UserName\.ssh\id_rsa on Windows. |
--pass-phrase | The pass phrase of the key, if private key authentication is used and the private key is encrypted. |
--ssh-retries | Maximum number or times to retry SSH connection. |
--proxy-uri | URL of the Maven proxy server used to download the container runtime. |
--ensemble-server | Whether the new container should be a Fabric Server. |
--profile | A list of profile IDs to associate with the new container. |
--version | Specifies the version of the new container (the version must be created in advance using fabric:version-create ). Defaults to the current default version (use version-list to find the current default). |
-b, --bind-address | Specifies the default bind address. |
--datastore-type | Specifies the datastore type. |
--datastore-option | Options to pass to the container's datastore. To specify multiple options, use this flag multiple times. |
--zookeeper-password | Used in combination with the --ensemble-server option. If creating an ensemble server, specifies the Zookeeper password to use (if not specified, a password is generated automatically). |
--jvm-opts | Specify options to pass to the container's JVM. |
--resolver | Specifies how the container will report its address to other containers. Valid values are localip , localhostname , publicip , publichostname , manualip . For more information see fabric:container-resolver-set. |
-m, --manual-ip | The IP address to use, when using the manualip resolver. Used in combination with the --resolver option. |
--env | Sets an environment variable. To specify multiple environment variables, use this flag multiple times. |
--with-admin-access | Indicates that the target user has administrative access (password-less sudo ). When this option is specified, Fabric will attempt to install any missing dependencies on the target host. |
Name | (Required) The name of the container to create. When creating multiple containers, it serves as a prefix. |
Number | The number of containers that should be created. |
Related topics
fabric:container-resolver-list |
fabric:container-resolver-set |
fabric:create |
Name
fabric:container-default-jvm-options, container-default-jvm-options — get or set the default JVM options to use when creating a new container
Synopsis
fabric:container-default-jvm-options
[
--help
] [
JVMOptions
]
Arguments
Table 10.12. fabric:container-default-jvm-options Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
JVMOptions | Sets the default JVM options for this container. If this argument is omitted, get the current default JVM options. |
Name
fabric:container-delete, container-delete — stops and deletes a Fuse Container
Synopsis
fabric:container-delete
[
--help
] [[
-r
] | [
--recursive
]] {
Name
}
Description
-r
option.
fabric:ensemble-remove
.
Arguments
Table 10.13. fabric:container-delete Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
-r, --recursive | Recursively stops and deletes all child containers. |
Name | Specifies the name of the container to delete. |
Name
fabric:container-domains, container-domains — lists a container's JMX domains
Synopsis
fabric:container-domains
[
--help
] {
Name
}
Arguments
Table 10.14. fabric:container-domains Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
Name | Specifies the name of the container. |
Name
fabric:container-info, container-info — displays information about the specified container
Synopsis
fabric:container-info
[
--help
] [
ContainerName
]
Arguments
Table 10.15. fabric:container-info Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
ContainerName | Specifies the name of the container for which information is provided. If not specified, the container name defaults to root . |
Name
fabric:container-list, container-list — lists the containers in a fabric
Synopsis
fabric:container-list
[
--help
] [
--version Version
] [[
-v
] | [
--verbose
]] [[
ID
] | [
profile
]]
Arguments
Table 10.16. fabric:container-list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--version | Specifies a profile version to use as filter. |
-v, --verbose | Display verbose output. |
ID | Specifies a container ID to use in filtering the output. |
profile | Specifies a profile to use in filtering the output. When a profile is specified only the containers with the profile are listed. |
Name
fabric:container-remove-profile, container-remove-profile — removes the specified list of profiles from the container
Synopsis
fabric:container-remove-profile
[
--help
] {
Name
} {
Profiles
}
Arguments
Table 10.17. fabric:container-remove-profile Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name | Specifies the name of the container. |
Profiles | Specifies the list of profiles to remove from the container. |
Name
fabric:container-resolver-list — show the resolver policies for the specified containers
Synopsis
fabric:container-resolver-list
[
--help
] [
containers
]
Description
Arguments
Table 10.18. fabric:container-resolver-list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
containers | List of containers for which the resolver policy is displayed. Shows all containers by default. |
Related topics
Name
fabric:container-resolver-set — specifies how the container reports its address to other containers
Synopsis
fabric:container-resolver-set
[
--help
] [
--container name
] [
--all
] {
Resolver
}
Description
localip localhostname publicip publichostname manualip
localip
and localhostname
resolver policies are suitable for accessing a container in a LAN. The publicip
and publichostname
resolver policies are suitable for accessing a container in a WAN (Internet), but they are typically only available for cloud containers. In the case of a the cloud, localip
and localhostname
can be used for container-to-container connections within the cloud, but for container-to-container connections from outside the cloud, you must use publicip
or publichostname
.
- When you create a new container, fabric tries to discover as much as it can about the container's host address and stores this information in the following fields in the fabric registry:
localip
(local IP address);localhostname
(local hostname);publicip
(public IP address);publichostname
(public hostname).For example, if you create a new container using thefabric:container-create-ssh
command and specify the local IP address to the--host
option, fabric attempts to perform a reverse lookup to obtain the corresponding local hostname and then stores both the local IP address and the local hostname in the Fabric Registry.If you create a new container in the cloud, the metadata sent by the cloud provider typically includes a complete set of host addresses:localip
,localhostname
,publicip
, andpublichostname
. - Every container in the fabric has its own resolver policy, which determines what kind of host address is returned to another container that wants to connect to it. The container's resolver policy is set in one of the following ways:
- (Default) By inheriting the resolver policy from the global resolver policy (specified at the time the fabric is created)
- By specifying the resolver policy explicitly at the time the container is created (through the
--resolver
option). - By invoking the
fabric:container-resolver-set
command.
- The container's resolver policy is applied whenever fabric looks up the container's host address, irrespective of what protocol is involved. In particular, the resolver policy determines the form of the host address used in the following URLs:
- Fabric Ensemble URL,
- SSH URL (console client port),
- Maven proxy URL,
- JMX URL.
SSH1
(originally created using the fabric:container-create-ssh
command) and the SSH1
container is configured with the localip
resolver policy, any container that tries to connect to SSH1
will automatically receive the local IP address of SSH1
when it looks up the Fabric Registry.
X
, Y
, and Z
want to connect to container SSH1
, the form of host address they get is determined by SSH1
's resolver policy. But if SSH1
wants to connect to container X
, it is container X
's resolver policy that is used.
Manual IP resolver policy
manualip
resolver policy is a special case. If none of the standard resolver policies are suitable for your network set-up, you can manually specify a container's host address by setting the following key in the Fabric Registry:
/fabric/registry/containers/config/ContainerName/manualip
Arguments
Table 10.19. fabric:container-resolver-set Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--container | Apply the resolver policy to the specified container. To specify multiple containers, specify this flag multiple times on the command line—for example, --container foo --container bar . |
--all | Apply the resolver policy to all containers in the fabric. |
Resolver | (Required) The resolver policy to set on the specified container(s). Possible values are: localip , localhostname , publicip , publichostname , manualip . |
Name
fabric:container-rollback — roll back the specified containers to an older version
Synopsis
fabric:container-rollback
[
--help
] [
--all
] {
Version
} [
ContainerList
]
Description
Arguments
Table 10.20. fabric:container-rollback Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--all | Roll back all containers. |
Version | (Required) The version to roll back to. |
ContainerList | The list of containers to roll back. An empty list implies the current container. |
Name
fabric:container-start, container-start — start the specified container
Synopsis
fabric:container-start
[
--help
] {
name
}
Arguments
Table 10.21. fabric:container-start Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name | Specifies the name of the container. |
Name
fabric:container-stop, container-stop — shuts down the specified container
Synopsis
fabric:container-stop
[
--help
] {
Name
}
Arguments
Table 10.22. fabric:container-stop Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name | (Required) The name of the container. |
Name
fabric:container-upgrade — upgrade the specified containers to a new version
Synopsis
fabric:container-upgrade
[
--help
] [
--all
] {
Version
} [
ContainerList
]
Description
fabric:profile-edit
command to guarantee atomicity of profile modifications. That is, if multiple edits need to be made to a profile, you can use fabric:container-upgrade
to roll out all of the changes in one step.
child1
, which is currently assigned to version 1.0 and has the sample
profile deployed inside it. If you need to make multiple changes to the sample
profile, you can roll out these changes atomically, as follows:
- Create a new version, 1.1, to hold the pending changes, as follows:
karaf@root> fabric:version-create Created version: 1.1 as copy of: 1.0
- Now start editing the new version of the sample profile, remembering to specify
1.1
, so that the modifications are applied to version 1.1 ofsample
. For example, to add thecamel-quartz
feature to the sample profile, enter the following command:fabric:profile-edit --features camel-quartz sample 1.1
NoteInstead of adding the option1.1
to every edit command, you could change the default version to 1.1 by entering the command,fabric:version-set-default 1.1
. - When you have finished editing the
sample
profile and you are ready to let the changes take effect on the container,child1
, you can roll out the changes by upgrading thechild1
container to version 1.1, as follows:fabric:container-upgrade 1.1 child1
- If you are not happy with the changes you made, you can easily roll back to the old version of the
sample
profile, using thefabric:container-rollback
command, as follows:fabric:container-rollback 1.0 child1
Arguments
Table 10.23. fabric:container-upgrade Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--all | Upgrade all containers. |
Version | (Required) The version to upgrade to. |
ContainerList | The list of containers to upgrade. An empty list implies the current container. |
Name
fabric:create — creates a new fabric and imports fabric profiles
Synopsis
fabric:create
[
--help
] [
--clean
] [
--no-import
] [
--import-dir dir
] [[
-v
] | [
--verbose
]] [[
-t
] | [
--time
]millis
] [[
-n
] | [
--non-managed
]] [[
-p
] | [
--profile
]profile
] [[
-b
] | [
--bind-address
]bindAddr
] [
--new-user username
] [
--new-user-password password
] [
--new-user-role role
] [
--zookeeper-password zooPassword
] [
--generate-zookeeper-password
] [
--zookeeper-data-dir dataDir
] [
--zookeeper-init-limit ticks
] [
--zookeeper-sync-limit ticks
] [
--zookeeper-ticktime millis
] [
--wait-for-provisioning
] [
--provision-timeout millis
] [[
-t
] | [
--time
]millis
] [[
-g
] | [
--global-resolver
]policy
] [[
-r
] | [
--resolver
]policy
] [[
-m
] | [
--manual-ip
]ipAddress
] [
--min-port port
] [
--max-port port
] [
--external-git-url gitURL
] [
--external-git-user gitUser
] [
--external-git-password gitPass
] [
ContainerList
]
Description
- The contents of a container should now be managed using fabric profiles. Do not try to deploy bundles and features directly in a fabric container.
- The default JAAS realm is superseded by the Zookeeper login module, which stores user data in the Zookeeper registry. As the fabric is created it initializes the user data by importing all of the user data that it finds in the
etc/users.properties
file. If theusers.properties
file is empty, you can specify a new user explicitly using the--new-user
and--new-user-password
options (at least one user must be defined).
- Create a fabric that imports the sample profiles (for example, using
fabric:create
). - Modify the sample profiles using the
fabric:profile-create
,fabric:profile-delete
, andfabric:edit
commands. - Export the modified profiles using the
fabric:export
command.
Arguments
Table 10.24. fabric:create Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--clean | Clean local zookeeper cluster and configurations. |
--no-import | Disable the import of the sample registry data. |
--import-dir | Directory of files to import into the newly created ensemble. |
-v, --verbose | Flag to enable verbose output of files being imported. |
-t, --time | How long to wait (milliseconds) for the ensemble to start up, before trying to import the default data. |
-n , --non-managed | Specifies that the container remains unmanaged. |
-p, --profile | Specifies the profile (or profiles) to use for the ensemble containers in the new fabric. To specify multiple profiles, specify this flag multiple times on the command line—for example, --profile foo --profile bar . |
-b, --bind-address | The default bind address. |
--new-user |
Create a new user in the new fabric's JAAS realm. Because the
fabric:create command automatically imports user data from the etc/users.properties file, you would only need to specify this option, if the etc/users.properties file contains no valid user entries.
When using this option, you must also specify a password using the
--new-user-password option.
|
--new-user-password | Used in combination with the --new-user option to specify the new user's password. No default value. |
--new-user-role | Used in combination with the --new-user option to specify the new user's role. Default is admin . |
--zookeeper-password |
Specifies the Zookeeper password, which is used to access the Zookeeper nodes under the
/fabric/ path. Defaults to the password of the current session user.
Subsequently, because the Zookeeper password is cached in the current session, you normally do not need to provide it when executing fabric commands. You can display the Zookeeper password at any time using the
fabric:ensemble-password command.
|
--generate-zookeeper-password | Directs Fabric to generate a random Zookeeper password. Subsequently, you can display the Zookeeper password using the fabric:ensemble-password command. |
--zookeeper-data-dir | The location where ZooKeeper stores the in-memory database snapshots and, unless specified otherwise, the transaction log of updates to the database. Defaults to data/zookeeper . |
--zookeeper-init-limit | The amount of time, in ticks, to allow followers to connect and sync to a leader. Defaults to 10. |
--zookeeper-sync-limit | The amount of time, in ticks, to allow followers to sync with ZooKeeper. Defaults to 5. |
--zookeeper-ticktime | The length of a single tick, which is the basic time unit used by ZooKeeper, as measured in milliseconds. It is used to regulate heartbeats and timeouts. For example, the minimum session timeout is two ticks. Defaults to 2000 . |
--wait-for-provisioning | Flag to wait for the initial container provisioning. |
--provision-timeout | How long to wait (in milliseconds) for the initial container provisioning. Defaults to 120000. |
-t, --time | How long to wait (in milliseconds) for the ensemble to start up before trying to import the default data. Defaults to 2000. |
-g, --global-resolver | Specifies the global resolver policy, which becomes the default resolver policy applied to all new containers created in this fabric. Possible values are: localip , localhostname , publicip , publichostname , manualip . The default is localhostname . |
-r, --resolver | Specifies the local resolver policy. Possible values are: localip , localhostname , publicip , publichostname , manualip . The default is localhostname . |
-m, --manual-ip | If you select the manualip resolver policy (using either the --resolver or --global-resolver options), specifies the IP address to use for the resolver. |
--min-port | Specifies the minimum port number of the allowed IP port range. Default is 0 . |
--max-port | Specifies the maximum port number of the allowed IP port range. Default is 65535 . |
--external-git-url | Specifies an external git url. |
--external-git-user | Specifies an external git user. |
--external-git-password | Specifies an external git password. |
ContainerList | The list of containers to include in the ensemble. An empty list implies the current container. |
Examples
ESBInstallDir/fabric/import
directory, as follows:
fabric:create --clean
fabric:create --clean --no-import
fabric:create --clean --import-dir CustomImportDir
reg1
, reg2
, and reg3
, are now included in the registry ensemble (an ensemble must consist of an odd number of containers):
fabric:create reg1 reg2 reg3
Related topics
Name
fabric:ensemble-add — extend the current Fabric Ensemble by converting the specified containers into Fuse Servers
Synopsis
fabric:ensemble-add
[
--help
] {
ContainerList
}
Description
root1
, root2
, and root3
—where root1
is an Fuse Server and root2
and root3
are ordinary Fabric Containers. You can now add root2
and root3
to the current ensemble by entering the following console command:
fabric:ensemble-add root2 root3
Arguments
Table 10.25. fabric:ensemble-add Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
ContainerList | The list of containers to add. |
Name
fabric:ensemble-list — lists the Fuse Servers in the current Fabric Ensemble
Synopsis
fabric:ensemble-list
[
--help
]
Description
fabric:container-list
instead.
Arguments
Table 10.26. fabric:ensemble-list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name
fabric:ensemble-password — display the ensemble password
Synopsis
fabric:ensemble-password
[
--help
]
Description
/fabric/
path, which contains critical configuration data for the fabric. To ensure integrity of the fabric configuration data, you should modify the fabric configuration exclusively using the fabric:*
console commands.
Arguments
Table 10.27. fabric:ensemble-password Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name
fabric:ensemble-remove — remove the specified containers from the current ensemble
Synopsis
fabric:ensemble-remove
[
--help
] {
ContainerList
}
Description
Arguments
Table 10.28. fabric:ensemble-remove Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
ContainerList | The list of containers to remove. Must be an even number of containers. |
Name
fabric:export — export the contents of the Fabric Registry to the specified directory in the filesystem
Synopsis
fabric:export
[
--help
] [
-d|--delete
] [
-p|--path path
] [
-f|--regex regex
] [
-rf|--reverse-regex regex
] [
-t|--trim
] [
--dry-run
] {
target
}
Description
fabric
commands.
-f
and -rf
, provide you with considerable flexibility at specifying which parts of the Fabric Registry to export. For example, to export every version of the default
profile's data, you could use a command like the following:
fabric:export -f /fabric/configs/versions/[0-9\\.]*/profiles/default/.*
\\
, is required to escape the period, .
, so that the period gets interpreted as a character literal.
Arguments
Table 10.29. fabric:export Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-d,--delete | Delete the existing contents of the target directory before exporting. Caution: Performs a recursive delete! |
-p,--path | Top-level znode to export. Default is / . |
-f,--regex | Specifies a regular expression that matches the znode paths you want to include in the export. For multiple include expressions, specify this option multiple times. The regular expression syntax is defined by the java.util.regex package. To specify multiple regular expressions, specify this flag multiple times on the command line—for example, --regex foo --regex bar . |
-rf, --reverse-regex | Specifies a regular expression that matches the znode paths you want to exclude from the export. For multiple exclude expressions, specify this option multiple times. The regular expression syntax is defined by the java.util.regex package. To specify multiple regular expressions, specify this flag multiple times on the command line—for example, --reverse-regex foo --reverse-regex bar . |
-t,--trim | Trims the first timestamp comment line in properties files starting with the # character. |
--dry-run | Log the actions that would be performed during an export, but do not actually perform the export. |
-v, --version | Not supported. Since JBoss Fuse 6.1, versioned data is stored in a Git repository, not in the Zookeeper registry. |
-p, --profile | Not supported. Since JBoss Fuse 6.1, profile data is stored in a Git repository, not in the Zookeeper registry. |
target | Path of the directory to export to. Default is ./export . |
Name
fabric:import — import data either from a filesystem or from a properties file into the Fabric Registry
Synopsis
fabric:import
[
--help
] [
-fs|--filesystem
] [
-props|--properties URL
] [
-t|--target path
] [
-d|--delete
] [
-f|--regex regex
] [
-rf|--reverse-regex regex
] [
-v|--verbose
] [
--dry-run
] [
--version version
] [
-p|--profile profileID
] {
source
}
Arguments
Table 10.30. fab:start Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-fs,--filesystem | Indicates that the source argument is a directory on the filesystem. Defaults to true . |
-props,--properties | Indicates that the source argument is a properties file. Defaults to false . |
-t,--target | Path of the znode that the data is imported into. Default is / . |
-d,--delete | Delete any paths that are not in the tree being imported. Ignored when importing a properties file. Caution: Using this option could permanently delete all or part of the Fabric Registry. |
-f,--regex | Specifies a regular expression that matches the znode paths you want to include in the import. For multiple include expressions, specify this option multiple times. The regular expression syntax is defined by the java.util.regex package. To specify multiple regular expressions, specify this flag multiple times on the command line—for example, --regex foo --regex bar . |
-rf, --reverse-regex | Specifies a regular expression that matches the znode paths you want to exclude from the import. For multiple exclude expressions, specify this option multiple times. The regular expression syntax is defined by the java.util.regex package. To specify multiple regular expressions, specify this flag multiple times on the command line—for example, --reverse-regex foo --reverse-regex bar . |
-v,--verbose | Verbose log of files being imported. |
--dry-run | Log the actions that would be performed during an import, but do not actually perform the import. |
--version | Not supported. Since JBoss Fuse 6.1, versioned data is stored in a Git repository, not in the Zookeeper registry. |
-p, --profile | Not supported. Since JBoss Fuse 6.1, profile data is stored in a Git repository, not in the Zookeeper registry. |
source | Location of a filesystem (if --filesystem is specified) or a properties file (if --properties is specified). Defaults to ./import . |
Name
fabric:join — join a container to an existing fabric
Synopsis
fabric:join
[
--help
] [[
-f
] | [
--force
]] [[
-p
] | [
--profile
]Profile
] [[
-n
] | [
--non-managed
]] [
--zookeeper-password zooPassword
] [[
-r
] | [
--resolver
]policy
] [[
-m
] | [
--manual-ip
]ipAddress
] [
--min-port port
] [
--max-port port
]
URL
[
ContainerName
]
Description
fabric:join
command can be used in either of the following scenarios:
- You have an existing fabric, A, and you want to join a standalone container to fabric A.
- You have two separate fabrics, A and B, and you want to transfer a container from fabric B to fabric A.
Arguments
Table 10.31. fabric:join Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
-f , --force | Forces the provided container name to be used. |
-p , --profile | Specifies the profile to associate with the container after it joins the fabric. The fabric profile, which installs the Fabric Agent, is automatically assigned to all managed containers. |
-n , --non-managed | Registers the container with the fabric's ensemble, but does not install a Fabric Agent into the container. The container's configuration is not managed by the fabric and continues to behave like a standalone container except that it can be discovered through the fabric's ensemble. |
--zookeeper-password | The ensemble password for the fabric that you are trying to join. If you do not specify this option, you will be prompted to enter the password. |
-r, --resolver | Specifies the local resolver policy. Possible values are: localip , localhostname , publicip , publichostname , manualip . The default is localhostname . |
-m, --manual-ip | If you select the manualip resolver policy (using the --resolver option), specifies the IP address to use for the resolver. |
--min-port | Specifies the minimum port number of the allowed IP port range. Default is 0 . |
--max-port | Specifies the maximum port number of the allowed IP port range. Default is 65535 . |
URL | Specifies the URL of one of the Fabric Servers, specified in the format Host[:Port] . The Port value defaults to 2181 . |
ContainerName | Specifies a unique name for the container to use when joining the fabric. By default, the value of the karaf.name property from the etc/system.properties file is used. |
Examples
fabric:join myhostA ishmael
myhostA
is the hostname of a Fabric Server (you must connect to a Fabric Server, not an ordinary fabric container) and the container is assigned the name ishmael
. You will be prompted to enter the fabric's Zookeeper password.
karaf.name
property from the etc/system.properties
file. The default setting for this property is root
. To avoid conflicts, you should either specify a container name or change the value of the karaf.name
property.
-p
argument as follows:
fabric:join -p whaler myhostA ishmael
ishmael
is assigned the profile, whaler
, when it joins the fabric.
fabric:join -n myhostA ishmael
Name
fabric:mq-create — create a new broker profile
Synopsis
fabric:mq-create
[
--help
] [
--group groupName
] [
--networks
brokerGroup,
...
] [
--networks-username user
] [
--networks-password password
] [
--create-container
containerID,
...
] [
--assign-container
containerID,
...
] [
--config configFile
] [
--data dataDir
] [
--kind brokerKind
] [
--replicas num
] [
--ports ports
] [
--profile profile
] [
--parent-profile parentProfile
] [
--client-profile clientProfile
] [
--client-parent-profile clientParentProfile
] [
--minimum-instances num
] [[
--property
] | [
-D
]prop] [
--jmx-user jmxUser
] [
--jmx-password jmxPassword
] [
--jvm-opts jvmOpts
] [
--version version
] {
name
}
Arguments
Table 10.32. fabric:mq-create Arguments
Argument | Description |
---|---|
--help | Displays the online help for this command. |
--group groupName | Specifies the name of the group to which brokers using this profile are assigned. By default brokers are assigned to the default group. |
--networks brokerGroup | Specifies a broker group to which brokers using this profile will establish network connections to form a network of brokers. To specify multiple broker groups, specify this flag multiple times on the command line—for example, --networks GroupA --networks GroupB . |
--networks-username | Specifies the username part of the credentials that are used to connect to the broker networks specified by the --networks option. |
--networks-password | Specifies the password part of the credentials that are used to connect to the broker networks specified by the --networks option. |
--create-container containerID,... | Specifies a comma separated list of child containers to create using the new profile. The new containers will be children of the container from which the command is executed. |
--assign-container containerID,... | Specifies a comma separated list of containers to which the new profile will be deployed. |
--config configFile | Specifies the ensemble path of the XML configuration template used by the profile. The path will have the syntax /fabric/configs/versions/version/profiles/profile/config.xml . |
--data dataDir | Specifies the path, relative to the container, for storing the persistence data for a broker using the profile. |
--kind brokerKind | The kind of broker to create. |
--replicas num | Number of replicas required for replicated brokers (which typically use a parent-profile of mq-replicated profile). |
--ports port | Port number for a transport connector, specified using the syntax --ports transportConnectorName=port , where transportConnectorName is the value of the name attribute from a transportConnector element in the configuration template. To specify multiple ports, specify this flag multiple times on the command line—for example, --ports openwire=11111 --ports mqtt-ssl=4321 . |
--no-ssl | Disables support for SSL/TLS protocol. |
--profile profile | The profile name to create or update, if defining N+1 broker groups. Defaults to mq-broker-$GROUP.$NAME . |
--parent-profile parentProfile | The parent profile to extend. |
--client-profile clientProfile | The profile name for clients to use to connect to the broker group. Defaults to mq-client-$GROUP . |
--client-parent-profile clientParentProfile | The parent profile used for the client-profile for clients connecting to the broker group. Defaults to default . |
--minimum-instances num | Minimum number of containers required of this broker's profile. |
--property, -D | Additional properties to define in the profile. To specify multiple properties, specify this flag multiple times on the command line—for example, --property keyA=valA --property keyB=valB . |
--jmx-user | The JMX username for logging on to the parent's JMX port. |
--jmx-password | The JMX password for logging on to the parent's JMX port. |
--jvm-opts | Specify options to pass to the container's JVM. |
--version version | Specifies the version into which the profile is stored. Defaults to the current default version. |
name | Specifies the name of the new broker profile. |
Examples
myBrokerProfile
that uses the XML template file myConfigTemplate.xml
use the command:
fabric:mq-create --config /fabric/configs/versions/1.0/profiles/mq-base/myConfigTemplate.xml myBrokerProfile
fabric:mq-create --config /fabric/configs/versions/1.0/profiles/mq-base/myConfigTemplate.xml --create-container broker1 myBrokerProfile
fabric:mq-create --config /fabric/configs/versions/1.0/profiles/mq-base/myConfigTemplate.xml --assign-container container1 myBrokerProfile
SSL/TLS support
keytool
, must be available on your PATH. To disable SSL/TLS support, specify the --no-ssl
option.
Name
fabric:patch-apply — apply a patch to the specified version or versions.
Synopsis
fabric:patch-apply
[
--help
] [[
-u
] | [
--username
]User
] [[
-p
] | [
--password
]Password
] [
--version Version
] [
--all-versions
] {
URL
}
Arguments
Table 10.33. fabric:patch-apply Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
-u, --username | Remote user name. |
-p, --password | Remote user password. |
--version | Applies the patch to the specified version. Defaults to the current default version. |
--all-versions | Applies the patch to all versions. |
URL | Specifies the URL from which the patch is downloaded. |
Name
fabric:profile-change-parents — replace the profile's parents with the specified list of parents (where the parents are specified as a space-separated list)
Synopsis
fabric:profile-change-parents
[
--help
] [
--version version
] {
Name
} {
ParentList
}
Arguments
Table 10.34. fabric:profile-change-parents Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--version | The profile version. Defaults to the current default version (use version-list to find the current default). |
Name | (Required) Name of the profile. |
ParentList | (Required) The list of new parent profiles. |
Name
fabric:profile-copy, profile-copy — copies the specified version of the source profile (where the version defaults to the current default version)
Synopsis
fabric:profile-copy
[
--help
] [
--version Version
] [
-f
] [
--force
] {
SourceProfile
} {
TargetProfile
}
Arguments
Table 10.35. fabric:profile-copy Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
--version | The profile version to copy. Defaults to the current default version. |
-f, --force | Flag to allow overwriting the target profile (if it already exists). |
SourceProfile | The name of the profile to copy. |
TargetProfile | The name of the newly created copy. |
Name
fabric:profile-create — create a new profile with the specified name and version
Synopsis
fabric:profile-create
[
--help
] [
--version version
] [
--parents parentList
] {
Name
}
Description
fabric:profile-create
separately for each version (use fabric:version-list
to list all versions).
fabric:profile-edit
command.
test
, which has the current default version and inherits from the parent profiles, mq
and camel
, enter the following console command:
fabric:profile-create --parents mq --parents camel test
Arguments
Table 10.36. fabric:profile-create Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--version | The profile version. Defaults to the current default version (use version-list to find the current default). |
--parents | Optionally specifies one or multiple parent profiles. To specify multiple parent profiles, specify this flag multiple times on the command line—for example, --parents foo --parents bar . |
Name | (Required) Name of the new profile. |
Name
fabric:profile-delete — delete the specified version of the specified profile (where the version defaults to the current default version)
Synopsis
fabric:profile-delete
[
--help
] [
--version version
] {
Profile
}
Arguments
Table 10.37. fabric:profile-delete Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--version | The profile version to delete. Defaults to the current default version (use version-list to find the current default). |
Profile | (Required) Name of the profile to delete. |
Name
fabric:profile-display — displays information about the specified version of the specified profile (where the version defaults to the current default version)
Synopsis
fabric:profile-display
[
--help
] [
--version version
] [[
-o
] | [
--overlay
]] {
Profile
}
Arguments
Table 10.38. fabric:profile-display Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--version | Select a specific profile version. Defaults to the current default version (use version-list to find the current default). |
-o, --overlay | Enable overlay. Shows the effective profile settings, taking into account the settings inherited from parent profiles. |
Profile | (Required) The name of the profile. |
Name
fabric:profile-edit — edits the specified version of the specified profile (where the version defaults to the current default version)
Synopsis
fabric:profile-edit
[
--help
] [[
-p
] | [
--pid
]PID
] [[
-r
] | [
--repositories
] | [
-f
] | [
--features
] | [
-b
] | [
--bundles
] | [
--fabs
] | [
-c
] | [
--config
] | [
-s
] | [
--system
] | [
-o
] | [
--overrides
] | [
-l
] | [
--libs
] | [
-n
] | [
--endorsed
] | [
-x
] | [
--extension
]] [[
--set
] | [
--delete
]] [[
--append
] | [
--remove
]] [
--import-pid
] [[
--delimiter
]delim
] [[
--resource
]ResourceName
] {
Profile
} [
Version
]
Description
- Feature repository locations—to add a feature repository to the profile, enter a command in the following format:
fabric:profile-edit --repositories RepoURL Profile [Version]
For example, to add thefuse-fabric
feature repository to the profile, enter a command like the following:fabric:profile-edit --repositories mvn:io.fabric8/fuse-fabric/6.1.0.redhat-379/xml/features Profile [Version]
To delete repositories, enter a command of the following form:fabric:profile-edit --delete --repositories RepoURL Profile [Version]
To edit repository locations directly, using a visual text editor, enter the following command:fabric:profile-edit Profile [Version]
The visual editor opens, showing the contents of the specified profile's agent properties. To edit the repository settings, add, modify, or delete lines of the following form:repository.ID=URL
WhereID
is an arbitrary unique identifier andURL
gives the location of a single feature repository. Only one repository URL can be specified on each line. - Features to install—to add features to the profile, enter a command in the following format:
fabric:profile-edit --features FeatureName Profile [Version]
To add multiple features, you can specify the--features
flag multiple times in this command. For example, to add thecamel-jetty
and thecamel-quartz
features to the default version of thesample
profile, enter a command like the following:fabric:profile-edit --features camel-jetty --features camel-quartz sample
To delete features, enter a command of the following form:fabric:profile-edit --delete --features FeatureName Profile [Version]
To edit features directly, using the visual text editor, enter the following command:fabric:profile-edit Profile [Version]
The visual editor opens, showing the contents of the specified profile's agent properties. To edit the features, add, modify, or delete lines of the following form:feature.ID=FeatureName
WhereID
is an arbitrary unique identifier andFeatureName
is the name of a feature. - Bundles to install—to add bundles to the profile, enter a command in the following format:
fabric:profile-edit --bundles BundleURL Profile [Version]
For example, to addcamel-quartz
bundle to thesample
profile, enter a command like the following:fabric:profile-edit --bundles mvn:org.apache.camel/camel-quartz/2.12.0.redhat-610379 sample
To delete bundles, enter a command of the following form:fabric:profile-edit --delete --bundles BundleURL Profile [Version]
To edit bundles directly, using the visual text editor, enter the following command:fabric:profile-edit Profile [Version]
The visual editor opens, showing the contents of the specified profile's agent properties. To edit the bundles, add, modify, or delete lines of the following form:bundle.ID=URL
WhereID
is an arbitrary unique identifier andURL
specifies the bundle's location. - Configuration settings for the OSGi Config Admin service—to modify or create a configuration setting from the OSGi Config Admin service, enter a command in the following format:
fabric:profile-edit --pid PID/Property=Value Profile [Version]
Where PID is a persistent ID, which is used in the context of the OSGi Config Admin service to identify a collection of related properties. For example, to change the value of the secure HTTPS port used by the Jetty server in thesample
profile, you could edit theorg.osgi.service.http.port.secure
property from theorg.ops4j.pax.web
PID using a command like the following:fabric:profile-edit --pid org.ops4j.pax.web/org.osgi.service.http.port.secure=8553 sample
To delete a property, enter a command of the following form:fabric:profile-edit --delete --pid PID/Property Profile [Version]
If the value of the PID property has the form of a comma-separated list, you can use the--append
option and the--remove
option to manipulate the list value. For example:fabric:profile-edit --pid org.example.foo/my.prop=a Profile [Version] fabric:profile-edit --append --pid org.example.foo/my.prop=b Profile [Version] fabric:profile-edit --append --pid org.example.foo/my.prop=c Profile [Version] fabric:display Profile ... PID: org.example.foo my.prop a,b,c
To edit OSGi Config Admin settings directly, using the visual text editor, enter the following command:fabric:profile-edit --pid PID Profile [Version]
The visual editor opens, showing the contents of the specified profile'sPID.properties
file (which is actually stored in the ZooKeeper registry). To edit the properties, add, modify, or delete lines of the following form:Property=Value
- Property settings from etc/config.properties—to modify or create a Java system property in the container's
etc/config.properties
file (which affects the container), enter a command in the following format:fabric:profile-edit --config Property=Value Profile [Version]
For example, to change the value of thekaraf.startlevel.bundle
Java system property inconfig.properties
, you would enter a command like the following:fabric:profile-edit --config karaf.startlevel.bundle=80 Profile [Version]
To delete a Java system property fromconfig.properties
, enter a command of the following form:fabric:profile-edit --delete --config Property Profile [Version]
If the value of the configuration property has the form of a comma-separated list, you can use the--append
option and the--remove
option to manipulate the list value. For example:fabric:profile-edit --config my.prop=a Profile [Version] fabric:profile-edit --append --config my.prop=b Profile [Version] fabric:profile-edit --append --config my.prop=c Profile [Version] fabric:display Profile ... Config Properties : my.prop = a, b, c
To edit the Java system properties directly, using the visual text editor, enter the following command:fabric:profile-edit Profile [Version]
The visual editor opens, showing the contents of the specified profile's agent properties. To edit the Java system properties (analogous toetc/config.properties
), add, modify, or delete lines of the following form:config.Property=Value
- Property settings from etc/system.properties—to modify or create a Java system property in the container's
etc/system.properties
file (which affects bundles deployed in the container), enter a command in the following format:fabric:profile-edit --system Property=Value Profile [Version]
For example, to change the default port for the OSGi HTTP service, you would enter a command like the following:fabric:profile-edit --system org.osgi.service.http.port=8181 Profile [Version]
If the system property,Property
, is already set at the JVM level (for example, through the--jvm-opts
option to thefabric:container-create
command), the precedingfabric:profile-edit
command will not override the JVM level setting. If you want to override the JVM level setting, you must indicate this explicitly by adding thekaraf.override
prefix to the property name,Property
—for example:fabric:profile-edit --system karaf.override.Property=Value Profile [Version]
To delete a Java system property fromsystem.properties
, enter a command of the following form:fabric:profile-edit --delete --system Property Profile [Version]
If the value of the system property has the form of a comma-separated list, you can use the--append
option and the--remove
option to manipulate the list value. For example:fabric:profile-edit --system my.prop=a Profile [Version] fabric:profile-edit --append --system my.prop=b Profile [Version] fabric:profile-edit --append --system my.prop=c Profile [Version] fabric:display Profile ... System Properties : my.prop = a, b, c
To edit the Java system properties directly, using the visual text editor, enter the following command:fabric:profile-edit Profile [Version]
The visual editor opens, showing the contents of the specified profile's agent properties. To edit the Java system properties (analogous toetc/system.properties
), add, modify, or delete lines of the following form:system.Property=Value
If you want to ensure that this setting overrides any JVM level setting, set the system property as follows:system.karaf.override.Property=Value
fabric:profile-edit
are immediately propagated to the containers that use that profile. This is not the recommended way to edit profiles, however: if you change multiple settings in the profile, you could potentially put the affected containers into an inconsistent state. To guarantee atomicity, it is better to use the fabric:profile-edit
command in combination with the fabric:container-upgrade
command—see fabric:container-upgrade.
Enclosing an Option Value in Quotes
http.nonProxyHosts="myserver1|myserver2"
, on the default
profile, you would use the following command:
fabric:profile-edit --system "karaf.override.http.nonProxyHosts=\"myserver1|myserver2\"" default
karaf.override
prefix is prepended to the property name, because http.nonProxyHosts
is already set at the JVM level and needs to be overridden.
Arguments
Table 10.39. fabric:profile-edit Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-p, --pid | Edit an OSGi configuration property, specified in the format PID/Property. To specify multiple values, specify this flag multiple times on the command line—for example, --pid PID/Property=Value --pid PID/Property=Value . |
-r, --repositories | Add (or delete) a feature repository. To specify multiple values, specify this flag multiple times on the command line—for example, --repositories foo --repositories bar . |
-f, --features | Add (or delete) a feature. To specify multiple values, specify this flag multiple times on the command line—for example, --features foo --features bar . |
-b, --bundles | Add (or delete) a bundle. To specify multiple values, specify this flag multiple times on the command line—for example, --bundles foo --bundles bar . |
--fabs | Add (or delete) a FAB. To specify multiple values, specify this flag multiple times on the command line—for example, --fabs foo --fabs bar . |
-c, --config | Edit the Java system properties that affect the container (analogous to editing etc/config.properties in a root container). To edit multiple configuration properties, specify this flag multiple times on the command line—for example, --config Property=Value --config Property=Value . |
-s, --system | Edit the Java system properties that affect installed bundles (analogous to editing etc/system.properties in a root container). To edit multiple system properties, specify this flag multiple times on the command line—for example, --system Property=Value --system Property=Value . |
-o, --overrides | Add (or delete) a bundle override. A bundle override can be used to override the bundle version installed by a feature. For example, if a feature installs version 1.0.0 of a particular bundle, you could use a bundle override to install version 1.0.1 of the bundle instead. To specify multiple values, specify this flag multiple times on the command line—for example, --overrides BundleURL --overrides BundleURL . |
-l, --libs | Add (or delete) a library. To specify multiple values, specify this flag multiple times on the command line—for example, --libs LibURL --libs LibURL . |
-n, --endorsed | Add (or delete) an endorsed library. To specify multiple values, specify this flag multiple times on the command line—for example, --endorsed LibURL --endorsed LibURL . |
-x, --extension | Add (or delete) an extension library. To specify multiple values, specify this flag multiple times on the command line—for example, --extension LibURL --extension LibURL . |
--set | Set or create values (selected by default). |
--delete | Delete values. |
--append | When editing list values, append the specified value to the list. Can only be used in combination with the --config , --system , and --pid options. |
--remove | When editing list values, remove the specified value from the list. Can only be used in combination with the --config , --system , and --pid options. |
--delimiter | Specifies the delimiter to use in combination with the --append and --remove options. Default is , (comma). |
--resource | When editing with the visual text editor, specifies the name of the resource to edit. |
-i, --import-pid | Imports the PIDs that are edited, from local OSGi Config Admin. |
Profile | (Required) Name of the profile to edit. |
Version | Version of the profile to edit. Defaults to the current default version (use version-list to find the current default). |
Name
fabric:profile-list — lists all profiles that belong to the specified version (where the version defaults to the current default version)
Synopsis
fabric:profile-list
[
--help
] [
--version version
] [
--hidden
]
Description
Arguments
Table 10.40. fabric:profile-list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--version | Specifies the version of the profiles to list. Defaults to the current default version (use version-list to find the current default). |
--hidden | Shows hidden profiles. |
Name
fabric:profile-refresh, profile-refresh — performs a change to the profile, that triggers the deployment agent. It's intended to be used for scanning for snapshot changes
Synopsis
fabric:profile-refresh
[
--help
] {
Profile
} [
Version
]
Arguments
Table 10.41. fabric:profile-refresh Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
Profile | The profile to refresh. |
Version | The profile version to refresh. Defaults to the current default version. |
Name
fabric:profile-rename, profile-rename — rename the specified version of the source profile (where the version defaults to the current default version)
Synopsis
fabric:profile-rename
[
--help
] [
--version Version
] [
-f
] [
--force
] {
OldName
} {
NewName
}
Arguments
Table 10.42. fabric:profile-rename Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
--version | The profile version to rename. Defaults to the current default version. |
-f, --force | Flag to allow replacing the target profile (if it already exists). |
OldName | The current name of the profile. |
NewName | The new name of the profile. |
Name
fabric:require-profile-delete — deletes requirements on the specified profile
Synopsis
fabric:require-profile-delete
[
--help
] {
Profile
}
Arguments
Table 10.43. fabric:require-profile-delete Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Profile | A profile ID. |
Name
fabric:require-profile-list — lists all profile requirements in the current fabric
Synopsis
fabric:require-profile-list
[
--help
]
Description
example-camel
profile and the example-cxf
profile have requirements set, you could see output like the following:
karaf@root> fabric:require-profile-list [profile] [# minimum] [# maximum] [depends on] example-camel 2 4 example-cxf 2 4
Arguments
Table 10.44. fabric:require-profile-list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name
fabric:require-profile-set — associates requirements with the specified profile
Synopsis
fabric:require-profile-set
[
--help
] [
--minimum MinInstance
] [
--maximum MaxInstance
] [
--dependsOn Dependency
] {
Profile
}
Description
example-camel
profile, you would enter the following command:
karaf@root> require-profile-set --minimum 2 --maximum 4 example-camel
Arguments
Table 10.45. fabric:require-profile-set Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--minimum | The minimum number of instances of this profile expected to be running in the fabric. |
--maximum | The maximum number of instances of this profile expected to be running in the fabric. |
--dependsOn | The profile IDs that must be provisioned before this profile. To specify multiple profile IDs, specify this flag multiple times on the command line—for example, --dependsOn foo --dependsOn bar . |
Profile | A profile ID. |
Name
fabric:status — displays the current status of the fabric, based on the configured profile requirements
Synopsis
fabric:status
[
--help
]
Description
fabric:require-profile-set
command. For example, if you configured the example-camel
profile to require a minimum of two instances and a maximum of four instances, and there is currently only one instance running, the example-camel
profile would get a health rating of 50%.
fabric:status
command produces output like the following:
karaf@root> fabric:status [profile] [instances] [health] cloud 1 100% example-camel 0 0% example-cxf 0 0% fabric 1 100% fabric-ensemble-0000-1 1 100%
Arguments
Table 10.46. fabric:status Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Related topics
Name
fabric:version-create — create a new version
Synopsis
fabric:version-create
[
--help
] [
--parent parentVersion
] {
Version
}
Description
--parent
option. If no version is specified, the command creates a new minor version by default. For example:
karaf@root> fabric:version-list [version] [default] [# containers] 1.0 true 1 karaf@root> fabric:version-create Created version: 1.1 as copy of: 1.0 karaf@root> fabric:version-list [version] [default] [# containers] 1.0 true 1 1.1 false 0
Arguments
Table 10.47. fabric:version-create Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
--default | Set the created version to be the new default version. |
--parent | The parent version. By default, use the latest version as the parent. |
Version | The new version to create. If not specified, defaults to the next minor version. |
Name
fabric:version-delete — delete the specified version
Synopsis
fabric:version-delete
[
--help
] {
Version
}
Description
Arguments
Table 10.48. fabric:version-delete Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Version | (Required) The version to delete. |
Name
fabric:version-list — lists the existing versions
Synopsis
fabric:version-list
[
--help
]
Description
karaf@root> fabric:version-list [version] [default] [# containers] 1.0 true 1 1.1 false 0
Arguments
Table 10.49. fabric:version-list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name
fabric:version-set-default — set the new default version (must be one of the existing versions)
Synopsis
fabric:version-set-default
[
--help
] {
Version
}
Description
fabric:profile-create
, the new profile is created in the default version by default. The fabric:version-set-default
changes the default version that is used by these commands.
Arguments
Table 10.50. fabric:version-set-default Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Version | (Required) Version number to use as the new default version. |
Chapter 11. Features Console Commands
features:
then press Tab at the karaf>
prompt to view the available commands.
Name
features:addurl, addurl — registers one or more URLs to feature repositories with the container
Synopsis
features:addurl
[
--help
] [[
-i
] | [
--install-all
]] {
urls
}
Description
Arguments
Table 11.1. features:addurl Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-i, --install-all | Install all of the features in the specified feature repository URLs. |
urls | One or more repository URLs separated by whitespaces. |
Name
features:chooseurl, chooseurl — registers the feature repository URL for a well known project
Synopsis
features:chooseurl
[
--help
] {
project
} {
version
}
Description
Arguments
Table 11.2. features:chooseurl Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
feature | Specifies the project name for the feature repository to add. |
version | Specifies the version of the project's feature repository to add. |
Name
features:info — show information about the specified feature with the optionally specified version
Synopsis
features:info
[
--help
] [[
-c
] | [
--configuration
]] [[
-b
] | [
--bundle
]] [[
-t
] | [
--tree
]] [[
-d
] | [
--dependency
]] {
featureName
} {
version
}
Arguments
Table 11.3. features:info Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-c, --configuration | Display configuration information. |
-b, --bundle | Display bundle information. |
-t, --tree | Display feature tree. |
-d, --dependency | Display dependency information. |
command |
Name
features:install — installs a feature
Synopsis
features:install
[
--help
] {
name
} [
version
]
Arguments
Table 11.4. features:install Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
name | The name of the feature to install |
version | The version of the feature |
Name
features:list — Lists all existing features available from the defined repositories
Synopsis
features:list
[
--help
] [[
-i
] | [
--installed
]]
Arguments
Table 11.5. features:list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-i, --installed | Displays the list of all installed features |
Name
features:listurl — lists the features repository URLs
Synopsis
features:listurl
[
--help
] [[
-v
] | [
--validate
]] [[
-vo
] | [
--verbose
]]
Arguments
Table 11.6. features:listurl Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-v ,--validate | Validate current version of descriptors. |
-vo ,--verbose | Shows validation output. |
Name
features:listVersions, listVersions — lists all versions of a feature available from the current feature repositories
Synopsis
features:listVersions
[
--help
] {
feature
}
Arguments
Table 11.7. features:listVersions Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
feature | Name of a feature. |
Name
features:refreshUrl — reloads the list of available features from the repositories
Synopsis
features:refreshUrl
[
--help
] {
urls
}
Arguments
Table 11.8. features:refreshUrl Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
urls | The repository URLs to reload (leave empty for all). |
Name
features:removeUrl — removes the specified list of repository URLs from the features service
Synopsis
features:removeUrl
[
--help
] {
urls
}
Arguments
Table 11.9. features:removeUrl Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-n ,--interval | |
urls | One or more repository URLs separated by whitespace. |
Name
features:removeRepository — removes the specified repository from the features service
Synopsis
features:removeRepository
[
--help
] {
repository
}
Arguments
Table 11.10. features:removeRepository Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
repository | The name of a features repository. |
Name
features:uninstall — uninstalls a feature with the specified name and version
Synopsis
features:uninstall
[
--help
] {
features
}
Arguments
Table 11.11. features:uninstall Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
features | A space-separated list of features to uninstall, where each feature is specified in the format feature[/version] (that is, the version is optional). |
Chapter 12. JAAS Console Commands
- Start the editing session.jaas:manage
- Edit the realm's user data.
- jass:usersLists all of the users.
- jass:useraddAdd a new user.
- jass:userdelDelete a user.
- jass:roleaddAdd a new role to a user.
- jass:roledelDelete a role from a user.
- jass:pendingLists all of the pending changes that have been made to the realms, but have not been applied to the container.
- Apply the changes to the JAAS realm and ends the editing session.jaas:update
jaas:
then press Tab at the prompt to view the available commands.
Name
jass:cancel, cancel — cancels a JAAS editing session without applying the pending changes
Synopsis
jaas:cancel
[
--help
]
Details
Arguments
Table 12.1. jaas:cancel Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name
jaas:manage, manage — opens a JAAS realm for editing
Synopsis
jaas:manage
[
--help
] {[
--realm realm
] | [
--index index
]} [
--module module
] [
--force
]
Details
Arguments
Table 12.2. jaas:manage Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
--realm | Select the realm to edit by specifying its realm name. |
--index | Select the realm to edit by specifying its index. |
--module | Specify which of the realm's login modules are to be edited. |
--force | Force the switch to the specified realm. If a different realm was already opened for editing its changes are abandoned without being applied. |
Examples
--realm
option. For example, if the container is a standalone instance (no fabric installed), you can start to edit the karaf
realm as follows:
jaas:manage --realm karaf
fabric-jaas
feature automatically installs another realm named karaf
at a higher priority, so that it overrides the default karaf
realm. For example, in a fabric, the jaas:realms command returns a list similar to the following:
Index Realm Module Class 1 karaf org.apache.karaf.jaas.modules.properties.PropertiesLoginModule 2 karaf io.fabric8.jaas.ZookeeperLoginModule
--index
option, specifying one of the index values from the list. The current active karaf
realm is the ZookeeperLoginModule
, which is selected by the index value, 2
, as follows:
jaas:manage --index 2
Name
jaas:pending, pending — lists the changes waiting to be applied to the realm being edited
Synopsis
jaas:pending
[
--help
]
Details
Arguments
Table 12.3. jaas:pending Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
Name
jaas:realms, realms — lists the JAAS realms know to the container
Synopsis
jaas:realms
[
--help
]
Arguments
Table 12.4. jaas:realms Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
Name
jaas:roleadd, roleadd — adds a role to a user
Synopsis
jaas:roleadd
[
--help
] {
username
} {
role
}
Details
Arguments
Table 12.5. jaas:roleadd Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
username | Specifies the name of the user to modify. |
role | Specifies the role which is appended to the user data. |
Name
jaas:roledel, roledel — deletes a role from a user
Synopsis
jaas:roledel
[
--help
] {
username
} {
role
}
Details
Arguments
Table 12.6. jaas:roledel Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
username | Specifies the name of the user to modify. |
role | Specifies the role which is removed from the user data. |
Name
jaas:update — applies all pending changes to the JAAS realm and closes the editing session
Synopsis
jaas:update
[
--help
]
Details
Arguments
Table 12.7. jaas:update Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
Name
jaas:useradd, useradd — adds a user to the JAAS realm being edited
Synopsis
jaas:useradd
[
--help
] {
username
} {
password
}
Details
Arguments
Table 12.8. jaas:useradd Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
username | Specifies the name of the user to add. |
password | Specifies the password used to authenticate the user. |
Name
jaas:userdel, userdel — deletes a user from the JAAS realm being edited
Synopsis
jaas:userdel
[
--help
] {
username
}
Details
Arguments
Table 12.9. jaas:userdel Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
username | Specifies the name of the user to add. |
Name
jaas:users, users — lists the users in the JAAS realm being edited
Synopsis
jaas:users
[
--help
]
Arguments
Table 12.10. jaas:users Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
Chapter 13. JBI Console Commands
jbi:
then press Tab at the JBossFuse:karaf@root>
prompt to view the available commands.
Name
jbi:list — lists JBI endpoints
Synopsis
jbi:list
[
--help
]
Arguments
Table 13.1. jbi:list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name
jbi:shutdown — shuts down a JBI artifact
Synopsis
jbi:shutdown
[
--help
] [[
-a
] | [
--service-assembly
] serviceAssembly
] [[
-c
] | [
--component
] component
] [
--force
] {
VAL
}
Arguments
Table 13.2. jbi:shutdown Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-a, --service-assembly | Specifies a service assembly |
-c, --component | Specifies a component |
--force | Forces a shutdown of the specified JBI artifact |
VAL | The name of the JBI artifact |
Name
jbi:start — starts a JBI artifact
Synopsis
jbi:start
[
--help
] [[
-a
] | [
--service-assembly
] serviceAssembly
] [[
-c
] | [
--component
] component
] {
VAL
}
Arguments
Table 13.3. jbi:start Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-a, --service-assembly | Specifies a service assembly |
-c, --component | Specifies a component |
VAL | The name of the JBI artifact |
Name
jbi:stop — stops a JBI artifact
Synopsis
jbi:stop
[
--help
] [[
-a
] | [
--service-assembly
] serviceAssembly
] [[
-c
] | [
--component
] component
] {
VAL
}
Arguments
Table 13.4. jbi:stop Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-a, --service-assembly | A service assembly |
-c, --component | A component |
VAL | The name of the JBI artifact |
Chapter 14. Log Console Commands
log:
then press Tab at the prompt to view the available commands.
Name
log:clear — clears the log
Synopsis
log:clear
[
--help
]
Arguments
Table 14.1. log:clear Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name
log:display, display, ld — displays log entries
Synopsis
log:display
[
--help
] [
-p pattern
] [
-n numLines
] [
--no-color
]
Arguments
Table 14.2. log:display Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-p | The pattern for formatting the output |
-n | The number of entries to display |
--no-color | Do not use syntax highlighting when displaying the log. |
Name
log:display-exception, display-exception, lde — displays the last thrown exception from the log
Synopsis
log:display-exception
[
--help
]
Arguments
Table 14.3. log:display-exception Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name
log:get, get — shows the log level
Synopsis
log:get
[
--help
] {
logger
}
Arguments
Table 14.4. log:get Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
logger | Specifies the logger name, ALL , or ROOT . The default is ROOT . |
Name
log:set, set — sets the log level
Synopsis
log:set
[
--help
] {[
DEFAULT
] | [
TRACE
] | [
DEBUG
] | [
INFO
] | [
WARN
] | [
ERROR
]} {
logger
}
Arguments
Table 14.5. log:set Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
level | Specifies the logging level. |
logger | Specifies the logger name. The default is ROOT . |
Name
log:tail — continually displays log entries
Synopsis
log:tail
[
--help
] [
-p pattern
] [
-n numLines
] [
--no-color
]
Arguments
Table 14.6. log:tail Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-p | The pattern for formatting the output |
-n | The number of entries to display |
--no-color | Do not use syntax highlighting when displaying the log. |
Chapter 15. The nmr:list Command
Name
nmr:list — lists NMR endpoints
Synopsis
nmr:list
[
--help
]
Arguments
Table 15.1. nmr:list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Chapter 16. OBR Console Commands
obr
shell, run the following command:
JBossFuse:karaf@root:>
features:install obr
obr:
then press Tab at the JBossFuse:karaf@root>
prompt to view the available commands.
Name
obr:addUrl — adds a list of repository URLs to the OBR service
Synopsis
obr:addUrl
[
--help
] {
urls
}
Arguments
Table 16.1. obr:addUrl Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
urls | The repository URLs to add to the OBR service, separated by whitespaces |
Name
obr:deploy — deploys a list of bundles using the OBR service
Synopsis
obr:deploy
[
--help
] {
bundles
}
Arguments
Table 16.2. obr:deploy Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
bundles | A list of bundle names to deploy, separated by whitespaces |
Name
obr:info — prints information about OBR bundles
Synopsis
obr:info
[
--help
] {
bundles
}
Arguments
Table 16.3. obr:info Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
bundles | Specifies the bundles to query for information, separated by whitespaces |
Name
obr:list — lists OBR bundles
Synopsis
obr:list
[
--help
] {
args
}
Arguments
Table 16.4. obr:list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
args | The arguments |
Name
obr:listUrl — displays the repository URLs currently associated with the OBR service
Synopsis
obr:listUrl
[
--help
]
Arguments
Table 16.5. obr:listUrl Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Name
obr:refreshUrl — reloads the repositories to obtain a fresh list of bundles
Synopsis
obr:refreshUrl
[
--help
] {
urls
}
Arguments
Table 16.6. obr:refreshUrl Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
urls | The repository URLs to refresh (leave empty for all) |
Name
obr:removeUrl — removes a list of repository URLs from the OBR service
Synopsis
obr:removeUrl
[
--help
] {
urls
}
Arguments
Table 16.7. obr:removeUrl Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
urls | The repository URLs to remove from the OBR service, separated by whitespace |
Name
obr:source — downloads the sources for an OBR bundle
Synopsis
obr:source
[
--help
] [
-x
] {
folder
} {
bundles
}
Arguments
Table 16.8. obr:source Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-x | Extracts the archive |
folder | The local directory or folder for storing sources |
bundles | A list of bundles to download the sources for |
Name
obr:start — deploys and starts a list of bundles using OBR
Synopsis
obr:start
[
--help
] {
bundles
}
Arguments
Table 16.9. obr:start Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
bundles | List of bundle names to deploy, separated by whitespaces |
Chapter 17. OSGi Console Commands
osgi:
then press Tab at the prompt to view the available commands.
Name
osgi:bundle-level, bundle-level — gets or sets the start level of a given bundle
Synopsis
osgi:bundle-level
[
--help
] [
--force
] {
id
} [
startLevel
]
Arguments
Table 17.1. osgi:bundle-level Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
--force | Forces the command to execute. |
id | Specifies the id for the bundle. |
startLevel | Specifies the new start level for the bundle. |
Name
osgi:bundle-services, bundle-services — lists the OSGi services provided by a bundle
Synopsis
osgi:bundle-level
[
-u
] [
-p
] [
-a
] [
--help
] [
--force
] {
id
}
Arguments
Table 17.2. osgi:bundle-services Arguments
Argument | Interpretation |
---|---|
-u | Displays the services used by the bundle. |
-p | Displays the properties for each service. |
-a | Displays all of the services provided by the bundle including the Apache Karaf commands which are hidden by default. |
--help | Displays the online help for this command. |
--force | Forces the command to execute. |
id | Specifies the id for the bundle. |
Name
osgi:classes, classes — lists all of the classes in the specified bundle or bundles
Synopsis
osgi:classes
[
--help
] [
--force
] [[
-a
] | [
--display-all-files
]] {
ids
}
Arguments
Table 17.3. osgi:classes Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
--force | Forces the command to execute. |
-a, --display-all-files | Also lists the files contained in the bundles. |
ids | Space-separated list of bundle IDs. |
Name
osgi:find-class, find-class — locates a specified class in any deployed bundle
Synopsis
osgi:find-class
[
--help
] {
className
}
Arguments
Table 17.4. osgi:find-class Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
className | Class name or partial class name to find. |
Name
osgi:headers, headers — displays the headers of a specified OSGi bundle
Synopsis
osgi:headers
[
--help
] {
id
...}
Arguments
Table 17.5. osgi:headers Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
id | Specifies a space delimited list of bundle IDs. |
Name
osgi:info — displays detailed information about OSGi bundles
Synopsis
osgi:info
[
--help
] {
id
...}
Arguments
Table 17.6. osgi:info Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
id | Specifies a space delimited list of bundle IDs. |
Name
osgi:install, install — installs one or more OSGi bundles
Synopsis
osgi:install
[
--help
] [[
-s
] | [
--start
]] {
url
...}
Arguments
Table 17.7. osgi:install Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-s , --start | Starts the bundles after installation |
url | Specifies a space delimited list of bundle URLs. |
Name
osgi:list, list — lists the installed bundles whose start level equals or exceeds the specified threshold
Synopsis
osgi:list
[
--help
] [
-u
] [
-t threshold
] [
-l
] [
-s
]
Arguments
Table 17.8. osgi:list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-u | Shows the update locations |
-t | Specifies the start level threshold. The default is the value of the karaf.systemBundlesStartLevel property whose default value is 50. |
-l | Shows the locations of the bundles |
-s | Shows the symbolic names of the bundles |
Name
osgi:ls, ls — lists OSGi services
Synopsis
osgi:ls
[
--help
] [
-a
] [
-u
] [
--force
] [
id
...]
Arguments
Table 17.9. osgi:ls Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-a | Lists all services |
-u | Lists the services in use |
--force | Forces the command to execute |
id | Specifies a space separated list of bundle IDs. |
Name
osgi:refresh, refresh — refreshes an OSGi bundle
Synopsis
osgi:refresh
[
--help
] [
--force
] {
id
...}
Arguments
Table 17.10. osgi:refresh Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
--force | Forces the command to execute. |
id | Specifies a space delimited list of bundle IDs. |
Name
osgi:resolve, resolve — resolves an OSGi bundle's dependencies
Synopsis
osgi:resolve
[
--help
] [
--force
] {
id
...}
Arguments
Table 17.11. osgi:resolve Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
--force | Forces the command to execute. |
id | Specifies a space delimited list of bundle IDs. |
Name
osgi:restart, restart — stops and restarts an OSGi bundle
Synopsis
osgi:restart
[
--help
] [
--force
] {
id
...}
Arguments
Table 17.12. osgi:restart Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
--force | Forces the command to execute. |
id | Specifies a space delimited list of bundle IDs. |
Name
osgi:shutdown, shutdown — stops the OSGi framework
Synopsis
osgi:shutdown
[
--help
] [[
-f
] | [
--force
]] [[
hh:mm
] | [
+m
]]
Arguments
Table 17.13. osgi:shutdown Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
-f , --force | Forces the command to execute. |
hh:mm | Specifies the time to shut down the broker in hours and minutes. The time is specified in 24 hour time. For example, 13:30 specifies that the container will shutdown at 1:30pm. |
+m | Specifies the time, in minutes, to pause before shutting down the OSGi framework. For example, +30 specifies that the container will wait thirty minutes before shutting down the OSGi framework. |
Name
osgi:start, start — starts an OSGi bundle
Synopsis
osgi:start
[
--help
] [
--force
] {
id
...}
Arguments
Table 17.14. osgi:start Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
--force | Forces the command to execute. |
id | Specifies a space delimited list of bundle IDs. |
Name
osgi:start-level, start-level — gets or sets the OSGi framework's active start level
Synopsis
osgi:start
[
--help
] [
level
]
Arguments
Table 17.15. osgi:start-level Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
level | Specifies the new start level to set. |
Name
osgi:stop, stop — stops an OSGi bundle
Synopsis
osgi:stop
[
--help
] [
--force
] {
id
...}
Arguments
Table 17.16. osgi:stop Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
--force | Forces the command to execute. |
id | Specifies a space delimited list of bundle IDs. |
Name
osgi:uninstall, uninstall — uninstalls an OSGi bundle
Synopsis
osgi:uninstall
[
--help
] [
--force
] {
id
...}
Arguments
Table 17.17. osgi:uninstall Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
--force | Forces the command to execute. |
id | Specifies a space delimited list of bundle IDs. |
Name
osgi:update, update — updates an OSGi bundle
Synopsis
osgi:update
[
--help
] [
--force
] {
id
} [
location
]
Arguments
Table 17.18. osgi:update Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
--force | Forces the command to execute. |
id | Specifies ID of the bundle. |
location | Specifies the location from which the update is loaded. If no location is specified the container will use either the bundle's Bundle-UpdateLocation property or the bundle's original location. |
Chapter 18. Packages Console Commands
packages:
then press Tab at the prompt to view the available commands.
Name
packages:exports, exports — displays the packages exported OSGi bundles
Synopsis
packages:export
[
--help
] [[
-d
] | [
--details
]] [
-s
] [[
-i
] | [
--imports
]] [
id
...]
Arguments
Table 18.1. package:exports Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-d, --details | Reformat the output in master/detail layout, which makes it easier to see how related details are grouped together. |
-s | Show the Symbolic name column, which shows the symbolic name of the bundle to which the exported package belongs. |
-i, --imports | Show the Imported by column, which lists all of the bundles that import the exported package. |
id | Specifies a whitespace separated list of bundle IDs to check. |
Name
packages:imports, imports — displays the packages imported by OSGi bundles
Synopsis
packages:imports
[
--help
] [[
-i
] | [
--show-importer
]] [
id
...]
Arguments
Table 18.2. package:imports Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-i, --show-importer | Show the bundle(s) that import a package. |
id | Specifies a whitespace separated list of bundle IDs to check. |
Chapter 19. Patch Console Commands
- the patch name
- a description of the patch
- the list of bundles included in the patch
- You receive a notice from customer support that a patch is available.
- Using the URL provided by customer support, you download the patch using the patch:add command.This command downloads an archive file, unzips the archive, and puts the relevant JAR files under the container's
system/
directory. The patch does not overwrite any of the existing JAR files and the patch is not actually installed until you run thepatch:install
command. - You install the patch using the patch:install command.
- If you notice that the patch is causing issues, you can remove it using the patch:rollback command.
patch:
then press Tab at the prompt to view the available commands.
Name
patch:add, download — download a patch file from a remote location and places the relevant JAR files in the container's system
directory
Synopsis
patch:add
[
--help
] [
--bundles
] {
URL
}
Arguments
Table 19.1. patch:add Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
--bundles | List the bundles included in the patch. |
URL | Specifies the URL from which the patch is downloaded. |
Name
patch:install — installs a patch that was previously downloaded
Synopsis
patch:install
[
--help
] {
patch
}
Arguments
Table 19.2. patch:install Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
patch | Specifies the name of the patch to install. |
Name
patch:list — lists all known patches, showing the patch name and status (installed or not)
Synopsis
patch:list
[
--help
] [
--bundles
]
Arguments
Table 19.3. patch:list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
--bundles | List the bundles for each patch. |
Name
patch:rollback — reverses a patch installation
Synopsis
patch:rollback
[
--help
] {
patch
}
Arguments
Table 19.4. patch:rollback Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
patch | Specifies the name of the patch to roll back. |
Name
patch:simulate, simulate — logs all of the actions that would be performed during a patch install, without actually performing the install
Synopsis
patch:simulate
[
--help
] {
patch
}
Arguments
Table 19.5. patch:simulate Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
patch | Specifies the name of the patch to simulate installing. |
Chapter 20. Service Component Runtime (SCR) Console Commands
Name
scr:activate — activate the specified SCR component
Synopsis
scr:activate
[
--help
] {
ComponentName
}
Arguments
Table 20.1. scr:activate Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
ComponentName | The SCR component name (which can be found from the listing produced by the scr:list command). |
Name
scr:deactivate — deactivate the specified SCR component
Synopsis
scr:deactivate
[
--help
] {
ComponentName
}
Arguments
Table 20.2. scr:deactivate Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
ComponentName | The SCR component name (which can be found from the listing produced by the scr:list command). |
Name
scr:details — show details for the specified SCR component
Synopsis
scr:details
[
--help
] [[
-s
] | [
--show-hidden
]] {
ComponentName
}
Arguments
Table 20.3. scr:details Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
-s, --show-hidden | Show all installed components, including the system components (which are hidden by default). |
ComponentName | The SCR component name (which can be found from the listing produced by the scr:list command). |
Name
scr:list — list all of the components defined using the OSGi Declarative Services framework
Synopsis
scr:list
[
--help
] [[
-s
] | [
--show-hidden
]]
Arguments
Table 20.4. scr:list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command. |
-s, --show-hidden | Show all installed components, including the system components (which are hidden by default). |
Chapter 21. SSH Console Commands
Name
ssh:ssh, ssh — connects to a remote SSH server
Synopsis
ssh:ssh
[
--help
] [[
-l username
] | [
--username username
]] [[
-P password
] | [
--password password
]] [[
-p port
] | [
--port port
]] {
hostname
} [
command
]
Arguments
Table 21.1. ssh:ssh Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-l, --username | The username for remote login |
-P, --password | The password for remote login |
-p, --port | The port to use for the SSH connection |
hostname | The hostname to connect to via SSH |
command | Specifies a command to execute upon connecting. |
Name
ssh:sshd, sshd — creates an SSH server
Synopsis
ssh:sshd
[
--help
] [[
-b
] | [
--background
]] [[
-p port
] | [
--port port
]]
Arguments
Table 21.2. ssh:sshd Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-b, --background | Specifies that the service will run in the background. |
-p, --port | Specifies the port to setup for the SSH server. The default is 8101 . |
Chapter 22. Web Console Commands
web:
then press Tab at the prompt to view the commands in this group.
Name
web:list — lists the WARs deployed in the container
Synopsis
web:list
[
--help
]
Arguments
Table 22.1. web:list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
Chapter 23. The wrapper:install Command
wrapper
shell, run the following command:
JBossFuse:karaf@root:>
features:install wrapper
Name
wrapper:install — installs the container as a system service in the operating system
Synopsis
wrapper:install
[
--help
] [[
-s
] | [
--start-type
] mode
] [[
-n
] | [
--name
] serviceName
] [[
-d
] | [
--display
] displayName
] [[
-D
] | [
--description
] description
]
Arguments
Table 23.1. wrapper:install Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-s, --start-type | The mode in which the service is installed, either AUTO_START or DEMAND_START ; the default is AUTO_START |
-n, --name | The service name used when installing the service; the default is karaf |
-d, --display | The display name of the service |
-D, --description | The description of the service |
Chapter 24. ZooKeeper Console Commands
fabric-zookeeper-commands
feature, as follows:
features:install fabric-zookeeper-commands
Name
zk:create — create a znode
Synopsis
zk:create
[
--help
] [
-r|--recursive
] [
-i|--import
] [
-e|--ephemeral
] [
-s|--sequential
] [
-a|--acl ListOfACLs
] [
-o|--overwrite
] {
path
} {
data
}
Description
- Persistent
- The new znode is permanently stored in the ZooKeeper registry. This is the default.
- Persistent sequential
- The new znode is permanently stored in the ZooKeeper registry and a 10-digit sequence number is appended to the specified znode name. Selected by the
--sequential
option. - Ephemeral
- The new znode exists only for the duration of the current client session. When the session is over, the znode is removed. Selected by the
--ephemeral
option. - Ephemeral sequential
- The new znode exists only for the duration of the current client session and a 10-digit sequence number is appended to the specified znode name. When the session is over, the znode is removed. Selected by combining the
--ephemeral
option with the--sequential
option.
Scheme:ID:Permissions
world:anyone
- The permissions apply to all users.
auth:
- The permissions apply to all authenticated users, irrespective of their identity (the
ID
field is left empty). digest:MD5Hash
- The permissions apply to the user whose username and password generate the specified MD5 hash value,
MD5Hash
. ip:IPAddress
- The permissions apply to the ZooKeeper client with the specified IP address.
Permissions
string consists of one or more of the following characters: r
(read), w
(write), c
(create), d
(delete), and a
(admin). For example, to create a new znode that explicitly grants all permissions to all users (which is, in fact, the default), you could use a command like the following:
karaf@root> zk:create --acl world:anyone:rwcda /path/to/the/new/znode
/fabric/
path using the zk:create
command. These registry nodes should only be created through the fabric
console commands—see Chapter 10, Fabric Console Commands.
world:anyone:rwcda
ACL setting).
Arguments
Table 24.1. zk:create Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-r,--recursive | Automatically create any missing parent nodes in the specified path. |
-i,--import | Interpret the data argument as a URL that locates a resource containing the initial data for the new znode. |
-e,--ephemeral | Make the new znode epehemeral, so that it is automatically deleted after the current ZooKeeper client session closes. |
-s,--sequential | Make the new znode sequential, which implies that a unique 10-digit suffix is appended to the znode name. |
-a,--acl | Specifies the znode's ACL as a comma-separated list, where each entry in the list has the format, Scheme:ID:Permissions . The Permissions string consists of the following characters, concatenated in any order: r (read), w (write), c (create), d (delete), and a (admin). |
-o,--overwrite | Overwrite the existing znode at this location, if there is one. |
path | (Required) Path of the znode to create. |
data | Initial data for the node or, if --import is specified, a URL pointing at a location that contains the initial data. |
Name
zk:delete — delete the specified znode
Synopsis
zk:delete
[
--help
] [
-v|--version version
] [
-r|--recursive
] {
path
}
Arguments
Table 24.2. zk:delete Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-v,--version | The ZooKeeper znode version to delete. Defaults to -1 (all versions). |
-r,--recursive | Recursively delete children. Defaults to false . |
path | Path of the znode to delete. |
Name
zk:get — get a znode's data
Synopsis
zk:get
[
--help
] {
path
}
Arguments
Table 24.3. zk:get Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
path | (Required) Path of the znode to get. |
Name
zk:list — list a znode's children
Synopsis
zk:list
[
--help
] [
-r|--recursive
] [
-d|--display
] {
path
}
Arguments
Table 24.4. zk:list Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-r, --recursive | List children recursively. |
-d, --display | Display a znode's value, if set. |
path | Path of the znode to list. Defaults to / . |
Name
zk:set — set a znode's data
Synopsis
zk:set
[
--help
] [
-i|--import
] {
path
} {
data
}
Description
/fabric/
path using the zk:set
command. These registry values should only be changed through the fabric
console commands—see Chapter 10, Fabric Console Commands.
Arguments
Table 24.5. zk:set Arguments
Argument | Interpretation |
---|---|
--help | Displays the online help for this command |
-i,--import | Import data from a URL. |
path | (Required) Path of the znode to set. |
data | (Required) The new data or URL to import. |
Legal Notice
Trademark Disclaimer
Legal Notice
Third Party Acknowledgements
- JLine (http://jline.sourceforge.net) jline:jline:jar:1.0License: BSD (LICENSE.txt) - Copyright (c) 2002-2006, Marc Prud'hommeaux
mwp1@cornell.edu
All rights reserved.Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- Neither the name of JLine nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - Stax2 API (http://woodstox.codehaus.org/StAX2) org.codehaus.woodstox:stax2-api:jar:3.1.1License: The BSD License (http://www.opensource.org/licenses/bsd-license.php)Copyright (c) <YEAR>, <OWNER> All rights reserved.Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - jibx-run - JiBX runtime (http://www.jibx.org/main-reactor/jibx-run) org.jibx:jibx-run:bundle:1.2.3License: BSD (http://jibx.sourceforge.net/jibx-license.html) Copyright (c) 2003-2010, Dennis M. Sosnoski.All rights reserved.Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- Neither the name of JiBX nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - JavaAssist (http://www.jboss.org/javassist) org.jboss.javassist:com.springsource.javassist:jar:3.9.0.GA:compileLicense: MPL (http://www.mozilla.org/MPL/MPL-1.1.html)
- HAPI-OSGI-Base Module (http://hl7api.sourceforge.net/hapi-osgi-base/) ca.uhn.hapi:hapi-osgi-base:bundle:1.2License: Mozilla Public License 1.1 (http://www.mozilla.org/MPL/MPL-1.1.txt)