IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Replicating the Tivoli Enterprise Portal Server database
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Understanding the Tivoli Enterprise Portal Server database
Before replicating the Tivoli Enterprise Portal Server database, be aware of what the database contains and what is required before you begin.
Tivoli Enterprise Portal customizations
Tivoli Enterprise Portal customizations are stored at the portal server in the TEPS database. This includes user IDs, Navigator views, custom queries, custom workspaces, and local terminal scripts. It does not store situations, policies, and managed system groups.During an installation upgrade to a new version of the portal server, the TEPS database is updated with any new or changed predefined Navigator views, queries and workspaces. Custom Navigator views, queries, and workspaces that you created are not affected.
The TEPS database replication is required for moving from a test environment to a production environment. You can also use the procedure for backing up the database as a precautionary measure before applying a fix pack or upgrading to a new version.
All workspaces previously created in the destination environment are replaced with those that were created in the source environment. Any existing user changes in the destination environment are also replaced.
Requirements for replication
Before migrating the Tivoli Enterprise Portal Server, make sure your environment fulfills these requirements:
- The portal servers on the source and target computers must be configured to connect to the same hub monitoring server.
- The portal servers on the source and target computers must be at Version 6.2.1 or later and, ideally, both have been installed from the same Tivoli Monitoring Base DVD.
- The portal servers on the source and target computers must have been installed the same way:
- The selected applications are the same. For example, if the source portal server has support for the UNIX, Windows Servers, and MQ Series applications installed, then the target portal server must have the same application support.
- The same database program is used for the portal server database. For example, IBM DB2 UDB.
CLI tacmds for selective replication
The command line interface has tacmds for exporting and importing specific IBM Tivoli Monitoring objects. See the Command Reference for a description of each of these commands and their syntax.
- tacmd exportworkspaces
- tacmd importworkspaces
- Selectively copy workspaces from one portal server to another.
- tacmd exportQueries
- tacmd importQueries
- Export custom queries to an XML file; then import them into a portal server.
- tacmd bulkExportSit
- tacmd bulkImportSit
- Export all Tivoli Monitoring enterprise situations from one hub monitoring server and importing into another.
- tacmd bulkExportPcy
- tacmd bulkImportPcy
- Export all Tivoli Monitoring policies from one hub monitoring server and importing into another.
- tacmd exportNavigator
- tacmd importNavigator
- Export custom Navigator views and their assigned workspaces, queries, and situation associations to an XML file; then import them into a portal server.
- tacmd exportSitAssociations
- tacmd importSitAssociations
- Export all the situation associations for a Navigator view or a particular Navigator item to an XML file; then import them into a portal server.
- tacmd exportSysAssignments
- tacmd importSysAssignments
- Export all managed system assignments for a Navigator view or a particular Navigator item to an XML file; then import them into a portal server.
Parent topic:
Replicating the Tivoli Enterprise Portal Server database