The Change and Configuration Management application is referred to as the CCM application.Jazz Team Server is referred to as JTS.In this topic, the following abbreviations are used: The databases are hosted on one or more servers.Īs described in Building products from applications, the IBM solution for ELM is now built around a central Jazz Team Server and several applications that share this Jazz Team Server.The context roots are /am, /gc, /rs and potentially others. Additional supporting applications such as Global Configuration Management, Reporting etc.The context roots are /jts, /ccm, /rm, /qm. For simplicity, assume that the installation is new and without a migration from prior versions.The Requirements Management (RM) application (Engineering Requirements Management DOORS Next) is installed on its own server: RM_SERVER.The Quality Management (QM) application (Engineering Test Management) is installed on its own server: QM_SERVER.The Change and Configuration Management (CCM) application (Engineering Workflow Management) is installed on its own server: CCM_SERVER.Jazz Team Server is installed on its own server for example, JTS_SERVER. This article provides specifics about what to consider when backing up the IBM solution for ELM.įor the purposes of this article, assume that the IBM solution for ELM is deployed in a fully distributed topology. Since whole development teams depend on the infrastructure, it is desirable to be able to recover it as quickly as possible. To minimize down time, you can increase the reliability of the IBM solution for ELM by using hardware that provides high reliability. The Rational solution for Collaborative Lifecycle Management Information Center contains information on how to back up the databases. Therefore, it is essential to make regular backups of the data to avoid losing it. Backing up products that were upgraded from a release of version 2Īfter you start using the IBM solution for Engineering Lifecycle Management (ELM), it will contain more and more important data.Backing up applications that were upgraded from a release of version 2.Temporal database consistency during a restore.Offline backup with reduced server downtime.Offline backup sequence for the IBM solution for ELM.Offline backup sequence for a single application on a single server.Ensuring a consistent backup of database and Fulltext index.Backing up the JFS index files in 4.0.5 and later.Backing up the JFS index files in 4.0 - 4.0.4.Backup of the JFS index files in version 3.x products.Ensuring a consistent backup of database and index files.Backing up the application server configuration.Files to include in the Jazz application configuration files backup.Backing up the Jazz application configuration files.Practicing your backup and restore procedure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |