The Deployment Package Editor of mToolkit supports signing of generated deployment packages by calling the jarsigner tool (<jdk_home>/bin/jarsigner.exe) of your JDK.
If you will sign your deployment package, first you have to specify the alias representing the signer's keys and own certificate and the keystore to take the signer's keys and own certificate from. A single deployment package might be signed by more than one signer. Then, when building the package out of its Deployment Package Project file, the Deployment Package Editor will check if there are signers specified for the package. If you have assigned such, the editor will call the jarsigner tool to sign the package archive by using the specified signer information.
To specify the security information related to a signer:
Make sure the format of the keystore file you specify matches the Store Type value.
Note: This feature is not supported for exporting an Ant buildfile for future deployment package generation.
The signer information will be used in subsequent generation of the deployment package either by using the Quick Build command or by using the Deployment Package part of the Export Wizard.
Note: Make sure you have specified correct path to the jarsigner executable in the mToolkit preference page before generating the deployment package file. Otherwise, the deployment package will not be signed.
Tip: If you do not specify keystore password(s) and/or key password(s), when generating the relevant deployment package, a dialog is displayed prompting you to enter the missing password(s). Passwords entered in this way are not permanently saved in the Deployment Package Project file.
Figure 2: Specifying a signer key password at package generation.
Deployment Package Overview
Deployment Package Editor
Creating a Deployment Package Project File
Configuring Deployment Package Editor
Generating a Deployment Package
Quick Deployment Package Build