Fuse 6 is no longer supported
As of February 2025, Red Hat Fuse 6 is no longer supported. If you are using Fuse 6, please upgrade to Red Hat build of Apache Camel.Chapter 9. Managing Child Containers
Abstract
9.1. Standalone Child Containers Copy linkLink copied to clipboard!
Using the admin console commands Copy linkLink copied to clipboard!
Installing the admin console commands Copy linkLink copied to clipboard!
admin
commands are not installed by default. To install the command set, install the admin
feature with the following command:
JBossFuse:karaf@root> features:install admin
JBossFuse:karaf@root> features:install admin
Cloning a container Copy linkLink copied to clipboard!
-s
option. For example, to create a new child with the SSH port number of 8102:
JBossFuse:karaf@root> admin:clone -s 8102 root cloned
JBossFuse:karaf@root> admin:clone -s 8102 root cloned
Creating a Karaf child container Copy linkLink copied to clipboard!
admin:create
command creates a new Apache Karaf child container. That is, the new child container is not a full JBoss Fuse container, and is missing many of the standard bundles, features, and feature repositories that are normally available in a JBoss Fuse container. What you get is effectively a plain Apache Karaf container with JBoss Fuse branding. Additional feature repositories or features that you require will have to be added to the child manually.
instances/containerName
directory. The child container is assigned an SSH port number based on an incremental count starting at 8101.
Example 9.1. Creating a Runtime Instance
JBossFuse:karaf@root> admin:create finn Creating new instance on SSH port 8102 and RMI ports 1100/44445 at: /home/jdoe/apps/fuse/jboss-fuse-6.3.0.redhat-xxx/instances/finn
JBossFuse:karaf@root> admin:create finn
Creating new instance on SSH port 8102 and RMI ports 1100/44445 at:
/home/jdoe/apps/fuse/jboss-fuse-6.3.0.redhat-xxx/instances/finn
Changing a child's SSH port Copy linkLink copied to clipboard!
admin:change-port
{
containerName
} {
portNumber
}
Starting child containers Copy linkLink copied to clipboard!
Listing all child containers Copy linkLink copied to clipboard!
Example 9.2. Listing Instances
Connecting to a child container Copy linkLink copied to clipboard!
Example 9.3. Admin connect Command
admin:connect
{
containerName
} {
-u username
} {
-p password
}
- containerName
- The name of the child to which you want to connect.
-
-u
username - The username used to connect to the child's remote console. Use valid JAAS user credentials that have admin privileges (see Chapter 14, Configuring JAAS Security).
-
-p
password - This argument specifies the password used to connect to the child's remote console.
JBossFuse:karaf@harry>
JBossFuse:karaf@harry>
Stopping a child container Copy linkLink copied to clipboard!
osgi:shutdown
or simply shutdown
.
admin:stop containerName
.
Destroying a child container Copy linkLink copied to clipboard!
Changing the JVM options on a child container Copy linkLink copied to clipboard!
admin:change-opts
command. For example, you could change the amount of memory allocated to the child container's JVM, as follows:
JBossFuse:karaf@harry> admin:change-opts tom "-server -Xms128M -Xmx1345m -Dcom.sun.management.jmxremote"
JBossFuse:karaf@harry> admin:change-opts tom "-server -Xms128M -Xmx1345m -Dcom.sun.management.jmxremote"
Using the admin script Copy linkLink copied to clipboard!
InstallDir/bin
directory provides all of the admin console commands except for admin:connect.
Example 9.4. The admin Script
admin.bat list
admin.bat list
./admin list
./admin list