
SPECTRUM Software Release Notice (SSRN)
For SPECTRUM 6.6 with Service Pack 5 CD release
Page 8
Document 5156
Upgrade Considerations
This section identifies product changes that should be
considered when upgrading from prior releases. Some of
these changes may require modifications to existing
SPECTRUM customizations and integrations.
Note: The SPECTRUM Application CD Version 6.6 with
Service Pack 5 may not be used to upgrade an
existing 6.6 SPECTRUM installation. Instead,
upgrade using the Service Pack 5 downloadable
version available at http://www.aprisma.com/
support/secure/download/.
• In SP5, the format of backup files created with ddm_save has been
changed. Instead of a proprietary format, the backup files produced by
ddm_save are now simply gzip'ed tar files of the key DDMDb database
data files needed to recreate a DDMDb database. This change should be
transparent to most customers. However, customers who have built
scripting dependent on the name of files created by ddm_save may
need to adapt their scripts to allow for the new default file extension
".tgz" that will be appended to the file name. Note that ddm_load
supports both the original proprietary save file format and the new file
format and automatically distinguishes between them.
• SPECTRUM now comes pre-configured with ports 14001-14005
assigned to certain SPECTRUM processes. Any firewall must be
configured to allow bi-directional UDP traffic for ports 14000 and 14001
and bi-directional TCP traffic for ports 14002-14005. If you had
previously customized your environment by changing the
OSAGENT_PORT from its default of 14000 to any of the ports in the
range 14001-14005, then a required SPECTRUM process may not run.
To correct this situation, choose a different available UDP port for the
OSAGENT_PORT setting.
•If you are using SPECTRUM Web Operator and if you have made
changes to the WebApps/tomcat/webapps/spectrum/WEB-INF/web.xml
file, your changes to that file will need to be re-applied after installing
6.6 with SP5 CD release.
• A new post-installation script has been introduced, to allow customers
to easily convert existing device models from the general GnSNMPDev
model type, to a more specific device model type appropriate for the