...
- --password <password>
Where <password> is a the password required to authenticate the user name. If this flag is not specified, the deployer will attempt to perform the command with no password, but if that fails, it will prompt you to enter a password.
- --secure
Use secure channel to communicate with JMX server (only available in Geronimo 2.1.2 or greater, see #Security for details.
- --syserr <select>
Where <select> can be either true or false. If this flag is unspecified. false is assumed. Specify true when you want errors to be logged to the syserr device.
- --verbose <select>
Where <select> can be either true or false. If this flag is unspecified. false is assumed. Specify true when you need more messages to determine the cause of an error.
Security
Starting with Geronimo 2.1.2 the deployer tool can use a secure channel (SSL/TLS) to communicate with the JMX server to perform the given actions. To enable secure communication just add the --secure option. Depending on your configuration you might also need to specify some Java security properties to configure the JVM to use the right keystores and passwords. For example, on a default Geronimo installation you might need to set the following (all in one line):
Code Block |
---|
export JAVA_OPTS="-Djavax.net.ssl.keyStore=<geronimo_home>/var/security/keystores/geronimo-default -Djavax.net.ssl.keyStorePassword=secret \
-Djavax.net.ssl.trustStore=<geronimo_home>/var/security/keystores/geronimo-default -Djavax.net.ssl.trustStorePassword=secret"
|
Once that property is set, you can execute the following command (just as an example):
Code Block |
---|
<geronimo_home>/bin/deploy -u system -p manager --secure list-modules
|
Commands
The available commands for the Geronimo deployer tool are listed below:
...