Step 4: Verify JAR Creation

After you have created the JAR, click "Verify" to see if your SmartUpdate JAR was created successfully. Your SmartUpdate Builder JAR contains the items you added, the install script, and a digital signature. Remember to re-sign the JAR with a CA-issued signing certificate if you signed the JAR with a test certificate.

After you click Verify, you are notified that your SmartUpdate Builder JAR was built correctly. If the JAR was not built correctly, SmartUpdate Builder will give you possible reasons for the failure. You may click More Info to see a complete log of the activities performed by Netscape Signing Tool.

Saving the SmartUpdate Information File

You can save all of the settings pertaining to the current SmartUpdate JAR. Saving a settings file is convenient if you’re going to create a new SmartUpdate JAR on a regular basis and do not want to re-enter the information every time.

  1. Click Save on any SmartUpdate Builder screen.
  2. The Saving SmartUpdate JAR Information dialog box appears.

  3. Type a name for the SmartUpdate JAR information file, including the path, and click Save.
  4. The extension .sbi is used to identify SmartUpdate JAR information files.

Opening a SmartUpdate Information File

You can use SmartUpdate Builder settings from a previous session so you don’t have to re-type all of the information when you create a new JAR.

  • Click Open on any SmartUpdate Builder screen.
  • The Opening SmartUpdate JAR Information dialog box appears.

  • Click Browse to find the SmartUpdate Builder information file that you want to open.
  • Click Open.
  • Deploying a SmartUpdate Builder JAR

    You can deploy a SmartUpdate Builder JAR in a web page on your corporate intranet, via the AutoConfig URL, or in an email message. You must create your own triggers when deploying a SmartUpdate Builder JAR. See SmartUpdate Developer's Guide for information on how to create triggers and deploy your JARs.