Notes & Domino FP10 – Some Suggested Steps Before And After
Just a reminder as you prepare for installing FP10, there are some areas worth backing up (thanks to those who’ve mentioned some on Twitter or chats).
On the server:
- java.policy file, if you’ve made changes
- java.pol file if you’ve made one
- Any additional JAR files in jvm\lib\ext
- osgi-dots folder, if you’ve added DOTS changes
You can then replace them, as required, after the upgrade.
On the client:
I blogged a few years ago about being able to back up Java preferences. It’s always worthwhile. You can then re-apply them after upgrade, if required.
With the new Java 8 JVM I’ve heard people mention getting “Access Restriction” errors when building. I can’t remember if I got that during the beta, but it’s tied to a Java compiler setting that I always need to set each time I install Eclipse for plpugin development. By default, Eclipse sets it as at “Error” level. Maybe it’s something that’s changed since the Eclipse version DDE was originally built on, but it’s set to “Warning” in my FP9 installation. If applying preferences doesn’t fix it, go to Preferences > Java > Compiler > Errors/Warnings. In the “Deprecated and restricted API” section change the settings to “Warning” (or “Ignore” if you don’t want to see them at all).
The other area that tends to get quirky around installs is plugins. With standard Eclipse there’s no such thing as an upgrade and workspace is separate from everything else, so typically you install the new Eclipse version, add in all plugins from scratch and migrate your workspace. Notes and Domino Designer includes everything and upgrades it all. Sometimes they get disabled, sometimes they get removed. If there are problems, File > Application > Application Management… is the place to go. Ensure it’s set to show disabled plugins (there’s an icon to turn on / off on the icon bar under File. Then, if the relevant plugin is showing disabled, just right-click and enable it. If it’s not there, check Help > Support > View Trace or View Log for any errors enabling it. If nothing, re-install it. If it’s there and not working correctly (e.g. not showing in Xsp Properties as a library), uninstalling and re-installing it may be the required solution. Eclipse has a lot of files around plugins, other than just the plugin itself. Upgrades may often make changes to these files, so something might have gone wrong.
In an upcoming blog post I’ll show one of the benefits you can take advantage of with Java 8 in FP10.