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.
Using the TM1 Replication feature, you can copy cubes and other associated objects from a remote server to your local server, or between two remote servers. This can be done by synchronizing the data bi-directionally among the copied cubes.
Replication creates a relationship between two cubes and between two servers.
Replicating cubes can offer the following advantages:
- Traveling “disconnected” users can update their local servers and then connect and have their cubes synchronized to the corporate database when it is convenient to them.
- The latest data can be synchronized to your laptop for “disconnected” presentations or training.
- Replication enhances the scalability of TM1.
Here are some points about TM1 replication based upon my experience:
- TM1 versions: All TM1 Servers in a replication process must be the identical versions.
- Remote servers: You can replicate cubes that reside on only remote servers. You cannot replicate cubes that reside on other local servers.
- Local servers: TM1 clients can replicate cubes to their local server only if they are running that server as an independent process. The machine must have a network card. To run a local server as an independent process, clients need to select the Local Server Execution Mode: Independent Process option in the TM1 Options dialog box.
- Access privileges: When you replicate a source cube on a remote server to a local server, any elements to which the local client has None access on the remote server will have a value of zero. If the client has Read (or higher) access to a consolidation which includes elements to which the client has NONE access, the consolidation will appear to be the sum of only those elements to which the client has READ (or higher) access. The consolidation, as reported to the client, will not be the sum of all elements, as in the source cube.
- Tm1s.cfg file: The Tm1s.cfg file must be configured to register the target and source servers with the same TM1 Admin Server. If your local server wants to have its data replicated to the corporate server, your local AdminHost parameter must list both the corporate server and your local servers ID (separated by a semicolon).
- Length of directory path and cube name: The total length of the path name for the target TM1 server’s data directory and the name of the cube you are replicating cannot exceed the limit of 256 characters.
- Transaction logging: Transaction logging must be enabled for the mirror cubes on the target server which are a part of the replication and synchronization process. If you are performing a bi-directional synchronization, transaction logging must be enabled for all the related cubes on both the source and target servers.
- CubeProperties control cube: The values stored in the CubeProperties control cube are specific to a TM1 Server and are not copied from the master to the target server during a replication process.
- Dimension replication: TM1 can be setup to replicate dimensions but by default, it does not.
- Rule replication: TM1 can be set up to replicate cube rules but by default, it does not.
- Multiple server replication: Depending on your access privileges, you can replicate a single cube on many different servers.
- Replication of Replicated: You can replicate a replicated cube.
- Source cubes: A source cube refers to the original cube in a replication.
- Mirror cubes: A mirror cube refers to a copy of the source cube.
- Current replications: The Server Explorer window lists the current replication connections beneath the Replications icon.
- Source servers: A source server is the remote server you log in to.
- Target servers: A target server is the server you logged in from.
- Replication connections: Before replicating a cube, you need to log on to a remote server and create a replication connection. This is done in Server Explorer by double-clicking on the Replications icon and by filling in the required information on the Create Server Replication dialog.
Replication can be a powerful feature if designed correctly but can be overwhelming the first time you set it up. Make sure to plan according!
Good Luck!
