After perfoming the upgrade, there are some additional tasks you may need to perform.
Log in to Mobile Web Studio and change the action type of linked applications you upgraded from 7.0 to 8.0 to Update.
If you have created or changed the following files or applications, either re-create them or manually merge them:
If you have any customized .jsp files from onepage\fw\baseApps, manually merge them.
If you change the location of the installation, manually copy custom .jsp files to the same subdirectory in the new installation directory.
If you modified the main index.jsp file from the onepage directory, manually merge them.
If you have created a cobrand directory, verify the installer retained the directory.
If you have customized images, check them, and if necessary, copy them from your backup.
Verify that any advanced applications you created, such as server-side click-across linked applications with update, charting, offline BlackBerry, and so on are working correctly. If they are not, you must re-create them.
Check the DefaultResourceID in the global.properties.xml file to verify that it is 21. If it is not 21, change the property manually to duplicate the same UA look and feel when you create new resources.
If you use the CellularModemController (CMC), after performing the upgrade, run:
run -logLevel FINEST -initDatabase true
Check the tomcat.old/webapps directory created by the installer. If you need the files contained in the directory, you must manually deploy them into the new version of Tomcat. You may need to modify these files, as UA 8.0 uses version 5.5 of Tomcat as opposed to version 4.0 used by UA 7.0
Check the templates associated with any applications you imported from version 7.0 and verify the associated template is appropriate for version 8.0 to avoid execution failures. For example, the BlackBerry Online template has changed with 8.0, the Nokia Online template is new, and applications created in 7.0 may use XSL templates that no longer work with 8.0.
To fix the templates, either edit the application so that each device type points to the correct template; or edit the template itself so that it is correct. If you edit the template, there is no need to edit the application. Decide which method to use based on whether the problem is with the template definition, or with the application pointing to the wrong template.
