IBM Cognos TM1 employs a distributed, client-server architecture that consists of the IBM Cognos TM1 server to which a combination of different clients can connect. The TM1 Server manages access to the Cognos TM1 data directory for Cognos TM1 clients. The data directory is where files are migrated from and to and this “migration of files” requires a strategy.
The Components of a Migration
First, it is important to understand that all software migrations will include 4 general components. These are:
- Identify,
- Isolate,
- Install and
- Insure.
Identify
All development activity should be logged to easily identify the files that need to be migrated. Currently, Cognos TM1 does not support vigorous change management or source control automation. You should therefore consider a simple, manual method for documenting development such as using a “Change Log” file or listing.
Release Guide
In addition to file identification, it is recommend that a standard TM1 Server Software Release Guide be prepared for the migration. This release guide should be saved along with the staged migration (release) files.
Isolate
Once the files to be migrated are identified, they need to be isolated (from the source environment) and labeled with a software version identifier.
The Future of Big Data
With some guidance, you can craft a data platform that is right for your organization’s needs and gets the most return from your data capital.
Software versioning is the process of assigning either unique version names or unique version numbers to unique states (or releases) of computer software. Within a given version number category (major, minor), these numbers are generally assigned in increasing order and correspond to new developments in the software. At a fine-grained level, revision control is often used for keeping track of incrementally different versions of electronic information, (different releases).
Isolation or Staging
Since it is assumed that development activities will continue (and may involve some of the files being migrated at this time), it is important to be able to audit isolated “versions” of each file that was migrated during a specific migration or release.
A best practice recommendation is to utilize a isolation or “staging” area. Typically this is a secured, backed up folder that is not located in the same location of the source TM1 server.
Install
Before you Begin
TM1 includes a collection of tools that provide logging and real-time performance monitoring of the TM1 servers in your environments. You can monitor TM1 performance and activity using these tools. It is a best practice recommendation to monitor and record these statistics on the target server before and after performing a migration. Careful statistical collection will provide:
- The effect of the latest release on server performance
- The effect of the latest release on application performance
- Overall baselines for future development efforts and performance testing
Insure
Once a migration or release is completed, a validation needs to be done to insure that the migration was completed successfully and with the expected results.
Validation Types
There are 2 types of validations to be performed:
- Validate that the destination server has not been ill-affected by the installation or migration performed
- Validate that the installed or migrated files are behaving as expected
General Recommendations
The following are several additional recommendations that should be considered prior to performing a migration:
- Developers support but do not perform migrations
- Determine migration roles and responsibilities, obtain appropriate security access – usually administrator access to target environment and services
- Perform a migration plan review and walk-through
- Perform a migration post-Morten
Conclusion
The process of model migration can become very complicated. The above thoughts should be input to building your strategy based upon your individual requirements.
Good Luck!
