Server Identity File

A server identity file is a special file that helps a store recover from a hard-drive failure or other catastrophic server failure. The server identity file contains the necessary SID information to re-install Prism using the same controller, store, subsidiary as before. Using the identify server file, the Prism install program will do the work needed so that the machine can claim its former node in the enterprise. If you do not reference the server identity file during the reinstall, the controller will not be able to claim its former node in the enterprise.
The rest of this topic explains how to 1) export the server identity file and 2) reference the file during a reinstall of Prism.
Export Server Identity File
Because of the crucial role it plays in restoring a system, you should create the server identity file at the first opportunity.

1. Launch Tech Toolkit and log in.  The Tech Toolkit is accessed via web browser by appending /TTK to the Prism server FQDN or hostname. Example: myserver.mycompany.com/TTK 
2. Click the desired server. 
3.Click the hamburger icon and select Export Identity (Oracle) or Export Identity (MySQL).
    

4. The file is generated. A modal displays a link to the file.

Reference Server Identity File during Prism Reinstall
During the Prism server install, the wizard will ask if you have a server identity file. This file is for a specific use case that must be handled at the beginning of the install process. Specifically, if a server crashes and needs to be rebuilt, referencing the file will ensure that the SIDs 4. generated during the install will be consistent between the old install and the new install. Without the server identity file, mismatching SIDs will result.
When installing the Prism server, click the check box and then click the Select File button. Navigate to the file and then click Next to proceed with the install using the selected server identity file.

If a POA will be down indefinitely
1. Export the identity of the downed system.
2. Remove the children of the downed system
3. Remove subordinate from the downed system's POA.
4. If desired, re-add the children to a temporary POA
5. Re-install Prism with the identity file of the downed system
7. Re-add the new system to it's POA
8. Remove children from temporary POA
9. Re-add the children to the new system that had crashed

Situations when it may not be possible to reinstall Prism using an identity file

• The user has removed Prism from a system at one location and re purposes it to another location (for example from an HQ to a Store) and needs to reinstall Prism as a new system *(new hostname and IP) 
• The database has become corrupted, and the user does not have a backup and needs to reinstall Prism completely using an identity file.
• The customer wishes to change the database type (due to the overhead differences between Oracle and MySQL ) and will need to remove Prism from the server and re install it using the identity file for the new database type on the same hostname.