Web Services no longer function after using Migration Wizard 7.1

Upgraded server from NetWare 5.1 Support Pack 6/eDirectory 8.7.3.2 to NetWare 6.1 SP1 8.7.3.2.
Typing "version" on server console shows a server license has not been acquired.
Server, via nwconfig, shows we are not listening on ports 443, 8009, 9009, 9010 or 2200.
Cannot access iManager 2.0.2 via browser.
Web Services no longer function after using Migration Wizard 7.1

When initially installing the destination server into a temporary tree either a basic or premigration server template was not used. This will cause web services to be installed on the temp server which will cause web services to fail when the restore from the source is performed. Novell recommends using the pre-migration template. This will install the absolute minimum services required to have a functioning destination server.
Post Upgrade Steps:

Below are potential problems and the post installation steps required to fix them.

1. Licensing
From the server console type "version". If the server reports that a license has not been aquired and iManager is not working map a drive to sys:public\win32 - run NWadmin and install the server license.

2. Volume Objects not created
Using DSREPAIR from the server console run a Complete Unattended Repair to re-created the volume objects. This ensures that trustees may be migrated back using the last step in Upgrade Wizard.

3. Server still has temp server's IP address
- From Console One select the NCP Server object - Right Click - Load Portal.
- Go to the IP Address Management link. If the bind statements are in the server's Autoexec.ncf allow the management utility to transfer these out. Change the IP address to the source server's then select "Reinitialize Server". This will re-create the server KMO's with the new address as well as transfer the address information to Apache.
- Now either restart all Apache and Tomcat services or restart the server.

Post Upgrade Steps:

Below are potential problems and the post installation steps required to fix them.

No Server License
From the server console type "version". If the server reports that a license has not been aquired and iManager is not working map a drive to sys:public\win32 - run NWadmin and install the server license.

Volume Objects not created
Using DSREPAIR from the server console run a Complete Unattended Repair to re-created the volume objects. This ensures that trustees may be migrated back using the last step in Upgrade Wizard.

Server's services still have temp server's IP address
During the ncf review portion of the Migration Wizard upgrade we were asked to change the destination server's ip address to that of the source. If this step was not performed the following should resolve the issue.
- From Console One select the NCP Server object - Right Click - Load Portal.
- Go to the Configure TCPIP link. If the bind statements are in the server's Autoexec.ncf allow the management utility to transfer these out. Change the IP address to the source server's then select "Reinitialize Server". This will re-create the server KMO's with the new address as well as transfer the address information to Apache.
- Now either restart all Apache and Tomcat services or restart the server.
- Go back into Portal using a web browser (https://xxx.xxx.xxx.xxx:8009) and select IP Address Management. Look for any red messages, there may be some for Apache. If so click on the Apache links, correct the addresses then select restart.

Install Web Services
Now all the Web Services can be installed on the server.
- Mount the NetWare 6.5 Products Overlay CD- Load"STARTX" on the server console then select "Install".
- Certificate Server, Console One and NMAS should already be selected. Add to this LDAP, iMonitor, all Apache and Tomcat instances, NRM, eDirectory Management Utilities, Refresh Native Access methods and iManager. If you have newer eDirectory modules than the overlay do not allow the install to overwrite newer files. Once complete reset the server. NOTE: You may see the install utility hang on closing install files - if so just close the windows and exit the GUI.

Tomcat does not have the new kmo keystore
This can be verified by not seeing Tomcat listening on 9009 either via TCPCON or in the server logger.
-Validate via Console One the Organizational CA then the server's own KMO's. If they do not validate they must be re-created.
- Once validated the RootCert.der file must be re-exported. Using Console One export the server's SSL CertificateIP kmo to a der file with the name RootCert.der.Copy this file to the server's sys:public directory after making a backup of the one that already exists there.
- Now this must be imported into Tomcat. Issue the following command at the Console: "tckeygen". Monitor the server's logger screen for progress. Make sure that the old server name does not appear in the subject name. If so the original RootCert.der file was not overwritten.
- Again, restart Apache\Tomcat or restart server. Once the server is back online look at the logger screen to see if the second instance of Tomcat is listening on 9009. If so, it was successful.

Getting a 500 error when attempting to connect to iManager via browser
This usually means that the nps directory structure needs to be created as well as the dependant eDirectory objects such as the pco object.
Using a web browser connect to "https://xxx.xxx.xxx.xxx/nps/servlet/configure".Select Start and accept all defaults. Once complete reset Apache\Tomcat services or restart the server. You should now be able to login to iManager using the URL:"https://xxx.xxx.xxx.xxx/nps/iManager.html".

.