...
toptop Anchor
4.2. Remote Console
The remote console feature allows to connect to a running ServiceMix Karaf instance from a remote computer and perform all the operations that are usually accessible from the local console.
Launch options
The ServiceMix Kernel Karaf shell scripts supports a number of options to control the remote console:
console
: launch ServiceMix Kernel Karaf in the default mode (both local and remote console activated). This is the default modeserver
: launch ServiceMix Kernel Karaf in with a remote console but no local consoleclient
: launch ServiceMix Kernel Karaf in with a local console only
These options affect two system properties that can be set if you don't use the standard shell scripts:
servicemixkaraf.startLocalConsole
servicemixkaraf.startRemoteShell
Using the client jar
From Apache ServiceMix Kernel 1.1.0 and posterior versions, it is It is also possible to use a more lightweight way to connect to a ServiceMix Kernel Karaf instance using the following command line:
...
...
There are a few parameters that can be set on the command line to change the URL used to connect to the KernelKaraf, the user or the password.
All these parameters are detailed in the help screen:
...
bgColor | #000000 |
---|
...
nopanel | true |
---|
...
For example, to shut down the Kernel Karaf from the command line, you can run the following command:
...
bgColor | #000000 |
---|
...
nopanel | true |
---|
...
...
title | Sending direct commands from the client |
---|
The client jar
...
also supports passing command line arguments to the remote
...
Karaf.
...
Using an SSH client
You can use any standard SSH client to connect to a ServiceMix Kernel Karaf instance. The default port is 8101.
...
title | Error messages when using some ssh clients |
---|
Some SSH clients will prompt some harmless warnings when connecting to ServiceMix Kernel.
In particular, openssh 5.1p1 will display the following output:
...
Using another
...
Karaf instance
First, open a terminal and launch a Kernel Karaf in server mode (you could use a Kernel Karaf instance in console mode too):
...
On another terminal, start a Kernel another Karaf instance in client mode:
...
At this point in time, you can not use the same
...
Karaf installation to start both the server and the client, so you need to create a new instance using the 'admin create xxx' command and use that one to start the client. If you are on a different host or already use another copy of
...
Karaf, this requirement does not hold.
Once the console appears, you can run the remote rsh
command to connect to the other Kernel:
Code Block |
---|
remote rsh tcp://localhost:8101/ -u smx -p smx
|
You can also do that in a single command line from the prompt by appending the previous ServiceMix command to the shell command:
...
To verify that your are connected to the remote Kernelinstance, run the following command:
...
and check the system informations.
Configuration
The TCP port is configured at the following location:
...
The defaut configuration is as below:
...
The port used can easily be changed by changing the default port 8101
in the remoteShellLocation
property.
To switch to a secured channel using SSL encryption, edit the above file and change the remoteShellLocation
property to use SSL as below:
Code Block |
---|
remoteShellLocation=tcp://0.0.0.0:8101/
|
sshPort
property.
The security The realm used by the console when authenticating remote users is named RshServer
karaf
, so you should can override this realm as explained in the 4.5. Security framework. If you want to use your own keystore and truststore when enabling SSL, you can add the following properties to the configuration file:
Code Block |
---|
clientKeyAlias=servicemix
clientKeystore=RshKeystore
clientTruststore=RshTruststore
serverKeyAlias=servicemix
serverKeystore=RshKeystore
serverTruststore=RshTruststore
|
You can either deploy another set of keystores that use the above names or change the named used and deploy new keystores. The key aliases must be set to a valid key in the store that will be used to secure the communication.
...
...