This lesson shows you how to sign your components so that they
can be installed on an Openwings platform that has been configured
to accept only "trusted" or "authenticated"
components, as described in the previous lesson. This lesson assumes
that you have access to the Java jarsigner tool that
is part of the Java 2 Standard Edition installation.
Documentation for Jarsigner: Unix
| Windows
The Jarsigner tool needs to be pointed at the keystore that holds
the key used to sign the Jar file. The following example command
assumes a Windows installation in the default location (C:\openwings):
C:\openwings\openwings-1.0\demos> jarsigner -keystore
C:\openwings\openwings-1.0\system\certstore Launcher_im.jar openwings
Enter Passphrase for keystore: openwings
Enter key password for openwings: openwings
This command causes the Launcher_im.jar demo component to be
signed with the "openwings" identity. This Jar file
may now be installed.
Note that we've used a code signer that comes with Openwings
to sign the Launcher demo component. This is a simple example,
but it’s preferable to sign components with your own certificate.
The next lesson shows how to add your own certificate to the Openwings
certificate store.
Next: Configuring
Code Signers on your System
