IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Upgrade from a previous installation > IBM Tivoli Monitoring coexistence and interoperability
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Tivoli Enterprise Portal Server
Coexistence and interoperability statements for the Tivoli Enterprise Portal Server.
- The V6.3 Tivoli Enterprise Portal Server can interoperate with older hub Tivoli Enterprise Monitoring Servers back to V6.1. However, it is recommended best practice that the portal server match the version of the hub Tivoli Enterprise Monitoring Server.
- The V6.3 Tivoli Enterprise Portal Server supports an upgrade-in-place from IBM Tivoli Monitoring V6.2, V6.2.1, V6.2.2, or V6.2.3 portal server on the same platform.
- The V6.3 Tivoli Enterprise Portal Server supports an upgrade from IBM Tivoli Monitoring V6.1 portal server on the same platform by importing an IBM Tivoli Monitoring V6.1 database and then upgrading it by running buildpresentation.bat (for Windows platforms) or InstallPresentation.sh (for Linux/UNIX platforms).
- Migrate a Tivoli Enterprise Portal server to a new platform, including switching from a 32-bit installation to a 64-bit installation on the same operating system, is accomplished with database export and import. For information about migrating the database, see the description of the migrate-export and migrate-import scripts in the IBM Tivoli Monitoring Administrator's Guide.
- When upgrading from a prior portal server to the current version, it is important that your system's temporary directory has sufficient space to accommodate the download of the eWAS server code and the Eclipse server code. See the memory and disk space requirements documented in Table 1.
- The Tivoli Enterprise Portal clients must be at the same release level as the portal server.
- If you are using MS SQL Server as your portal server database, the portal server database schema name must match the portal server user ID. Otherwise the Tivoli Enterprise Portal Server will fail to start and an error message is displayed. This is not an issue for a pristine installation of IBM Tivoli Monitoring. However, if you are upgrading your environment from V6.2.2 or earlier, it is possible that the database schema name and user ID do not match. If this is the case, change the portal server database schema name to match the portal server user ID.
Parent topic:
IBM Tivoli Monitoring coexistence and interoperability