How to Reinstall Damaged Software Components (prodreg)

If other software depends on a damaged software component, you might want to reinstall the damaged component, rather than uninstall the component and the other dependent software. You can use the -f option with the prodreg unregister to perform a forced unregister of the damaged component, and then reinstall the component.

1. Become superuser or assume an equivalent role.

2. View the information on the software you want to reinstall.

   # prodreg browse -m "name" BROWSE # +/-/. UUID # NAME ======== ===== ==================================== = ============ 1 - root 1 System Registry 2 + a01ee8dd-1dd1-11b2-a3f2-0800209a5b6b 1 Solaris 9 8/03 System Software 3 + 8f64eabf-1dd2-11b2-a3f1-0800209a5b6b 1 Unclassified Software 4 . UUID 1 name

   
   

   -m "name"	Displays information on the name software component you want to reinstall.
   UUID	Specifies the UUID of the software component you want to reinstall.

3. Identify the software that depends on the software you want to reinstall.

   # prodreg info -m "name" -a "Dependent Components" Dependent Components: Name UUID # --------------------------- ------------------------------------ - component-a component-a-UUID 1

   
   

   -m "name"	Specifies the name of the software component you want to reinstall.
   -a "Dependent Components"	Displays the components that depend on name software.
   component-a	Specifies the name of a software component that depends on name software.
   component-a-UUID	Specifies the UUID of the component-a software component.

   The component-a software component depends on the software you want to reinstall. To reinstall name software and not unregister component-a, you must perform a forced unregister of name software, then reinstall name software.

4. Unregister only the software component you want to reinstall.

   # prodreg unregister -f -u UUID

   
   

5. Reinstall the software component.

   # /usr/bin/java -cp /usr/installers/installer

   
   

   installer

   Specifies the name of the installer program for name software.

Example--Reinstalling Damaged Software Components (prodreg)

The following example shows how to reinstall the damaged software component ComponentSoft without unregistering or uninstalling the dependent component ExampleSoft.

# prodreg browse -m "ComponentSoft"
BROWSE #  +/-/.  UUID                                  #  NAME
========  =====  ====================================  =  ============
1         -      root                                  1  System 
                                                          Registry
2          +     a01ee8dd-1dd1-11b2-a3f2-0800209a5b6b  1   Solaris 9 8/03
                                                          System
                                                          Software
3          +     8f64eabf-1dd2-11b2-a3f1-0800209a5b6b  1  Unclassified 
                                                          Software
4           .    86758449-554a-6531-fe90-4352678362fe  1  ComponentSoft

# prodreg info -m "ComponentSoft" -a "Dependent Components"
Dependent Components:
Name                         UUID                                  #
---------------------------  ------------------------------------  -
ExampleSoft                  95842091-725a-8501-ef29-0472985982be  1

# prodreg unregister -f -u 86758449-554a-6531-fe90-4352678362fe -i 1

# /usr/bin/java -cp /usr/installers/org.example.componentsoft

Adding and Removing Signed Packages (Task Map)

The following task map describes the tasks for adding and removing signed packages.

How to Import a Trusted Certificate into the Package Keystore (pkgadm addcert)

1. Become superuser or assume an equivalent role.

2. Verify that the Root CA certificate exists in the Java keystore.

   # keytool -storepass storepass -list -keystore certfile

   
   

   keytool	Manages a Java keystore (database) of private keys and their associated X.509 certificate chains that authenticate the corresponding public keys. Also manages certificates from trusted entities. For more information on the keytool command, see keytool-Key and Certificate Management Tool.
   -storepass storepass	Specifies the password that protects the integrity of the Java keystore.
   -list	By default, prints the MD5 fingerprint of a certificate.
   -keystore certfile	Specifies the name and location of the persistent Java keystore file.

3. Export the Root CA certificate from the Java keystore to a temporary file.

   # keytool -export -storepass storepass -alias gtecybertrustca -keystore gtecybertrustca -keystore /usr/j2se/jre/lib/security/cacerts -file filename

   
   

   -export	Exports the trusted certificate.
   -storepass storepass	Specifies the password that protects the integrity of the Java keystore.
   -alias gtecybertrustca	Identifies the alias of the trusted certificate.
   -keystore certfile	Specifies the name and location of the keystore file.
   -file filename	Identifies the file to hold the exported certificate.

4. Import a trusted certificate to the package keystore.

   # pkgadm addcert -t -f format certfile

   
   

   -t	Indicates that the certificate is a trusted CA certificate. The command output includes the details of the certificate, which the user is asked to verify.
   -f format	Specifies the format of the certificates or private key. When importing a certificate, it must be encoded using either the PEM (pem) or binary DER (der) format.
   certfile	Specifies the file that contains the certificate.

   For more information, see the pkgadm man page.

5. Remove the temporary file.