Skip to main content

WebSphere Software not installed properly - .nfiregistry and vpd.properties

The installer program for WebSphere® Products use the InstallShield MultiPlatform (ISMP) program to install code. The .nifregistry and vpd.properties files list program components that are currently installed. The file helps ISMP and the installer programs of WebSphere products recognize previous installations of WebSphere products and control options for new installations.
Inorder to successfully install a websphere product after uninstalling another version of the same websphere product, you need to remove the .nfiregistry and vpd.properties files(vpd.properties). Without doing this the ISMP assumes that the same version of the websphere product exists and does not install the product and completes the process.

Location of the .nfiregistry fils on various platforms isThe location of the .nifregistry file varies per operating platform:
On AIX® platforms: The root directory /usr/.ibm/.nif/.nifregistry or the non-root directory /.ibm/.nif/.nifregistry

On HP-UX platforms: The root directory /opt/.ibm/.nif/.nifregistry or the non-root directory /.ibm/.nif/.nifregistry

On i5/OS® platforms: The root directory /QIBM/WAS/.ibm/.nif/.nifregistry

On Linux® platforms: The root directory /opt/.ibm/.nif/.nifregistry

On Solaris platforms: The root directory /opt/.ibm/.nif/.nifregistry or the non-root directory /.ibm/.nif/.nifregistry

On Windows® platforms: The root directory C:\Windows\.nifregistry

Delete this .nfiregistry file manually and the reinstallation of the websphere software works.

Comments

Popular posts from this blog

HashMap in Java

1) Implement HashMap in Java, with the put and get operations   HashMap can be implemented in Java Using Arrays. Use the same logic that the Out of the Box   HashMap follows, for resizing, and load factor, when ever the HashMap reaches the size of the   resize with the load factor a new Array is created, and the previous array contents are copied over   to the new Array.  HashMap is Not Synchronized by default. We can synchronize the whole map by using Synchronization, or by using collection.synchronizedmap(map), which synchronizes all the operations on the map. Alternatively We can use the CocurrentHashMap which does not lock the read operations, rather locks the segments that are being written. 2) HashMap vs LinkedHashMap vs IdentityHashMap 3) HashMap vs ConcurrentHashMap 4) Implement a Cache using LinkedHashMap