In this step, you will provide SmartUpdate Builder with security and naming information so that it can create the SmartUpdate JAR. To distribute software through SmartUpdate, you must have an object-signing certificate, which authenticates your identity as the creator of a SmartUpdate JAR.
If you are creating SmartUpdate JARs on your corporate intranet, you can get a certificate from your company’s own certificate authority (CA). If you want to distribute software through the Internet, get a certificate from an independent CA, such as VeriSign Corporation. If you do not have a certificate, use Signing Tool to create a test certificate while you wait for the CA to issue a certificate.
This database is usually located in the current Navigator user’s directory. Normally, this is one of the subdirectories located under C:\Program Files\Netscape\Communicator\Users and contains the database files (cert7.db,
The nickname can be found in Communicator’s Security dialog box. Click the Security button in any Communicator window and then click Yours under Certificates. You will view the database of the Communicator user currently logged in. To make sure your certificate hasn’t expired, select it and click View to see the expiration date.
You must leave the file extension as .jar.
SmartUpdate Builder safely creates and deletes temporary files while it assembles your SmartUpdate JAR. For example, you could specify C:\temp as the location.
SmartUpdate Builder creates the install script for your SmartUpdate JAR, compresses all the deliverables into a single SmartUpdate JAR file, and signs it.