...
- Common commands
- Other commands
- Geronimo Plugins
...
In the case of Geronimo, each configuration store is a separate target. Geronimo does not yet support clusters as targets.
UnlockKeystore
Use the unlockKeystore command to unlock a keystore and private keys. The list-targets command has the following syntax:
<geronimo_home>/bin/deploy <general_options> unlockKeystore <keyStoreName> <keyAlias1> <keyAlias2> {
}
Where <keyStoreName> specifies a locked keystore to get unlocked, <keyAlias1> and <keyAlias2> are optionally used to specify one or more locked private keys in the keystore to get unlocked.
Note that before you can use the unlockKeystore command, you need to ensure that the following lines are added to <WASCE_HOME>/var/config/config-substitutions.properties:
Code Block |
---|
_keyStoreName_=_keyStoreEncryptedPassword_
_keyAlias1_=_keyAlias1EncryptedPassword_
_keyAlias2_=_keyAlias1EncryptedPassword_
...
|
Where
*keyStoreName is the name of the keystore
*keyStoreEncryptedPassword is the encrypted password for the keystore, which can be generated by using the encrypt command. When you copy and paste the generated encrypted password to <WASCE_HOME>/var/config/config-substitutions.properties, there should be no space in the encrypted password string.
*keyAlias1, keyAlias2 are the names of the private keys in the keystore.
*keyAlias1EncryptedPassword, keyAlias2EncryptedPassword are the encrypted passwords for the private keys, which can also be generated by using the encrypt command.
Examples:
Use this syntax to unlock the keystore whose name is mykeystore
Code Block |
---|
deploy --user myadmin --password mypassword unlockKeystore mykeystore
|
Use this syntax to unlock the keystore whose name is mykeystore and the private key whose alias is key1
Code Block |
---|
deploy --user myadmin --password mypassword unlockKeystore mykeystore key1
|
Install-plugin
...