Transfer

Overview

• eMite Transfer is an application to copy/transfer pages from one system to another with a simple user interface.
• eMite Transfer is available and compatible with eMite version 6.0.2 and above.
• The transfer happens over three modules.
  • Reports/Pages Transfer.
  • RTBI Transfer (Includes fact queries and underlying schema).
  • KPI Transfer (Includes TransactionKPIs, TransactionKPIGroups, TransactionKPITemplates, TransactionKPIRanges, TransactionKPITemplateSets, TransactionKPISets, TransactionKPIVariables, TransactionKPITemplateVariables).
• eMite Transfer is available on the dashboard UI only for the admin users.
• eMite Transfer tool can only work if there is at least one page available for the admin to transfer RTBI  (this helps in initializing the configurations).
  The export basically copies pages and its entire hierarchy including RTBI schema and KPIs schema.
                  E.g: The system has 3 fact queries (cubes) and KPIs and if the selected export page has only one fact query, transfer tool only transfers just one fact query and its hierarchy of RTBI schema and KPIs.
• Extremely bulky import cannot be handled at the moment (example: 109 pages). Once the pages are exported via the dashboard, on the Import screen a few pages can be selected at a time to complete the import properly.
• The transfer process starts by performing Export which gives the transfer pack JSON file bundling the pages, fast queries, and KPIs.
• The exported file can then be downloaded/saved onto the desired location.
• The second part of the transfer is Import, which allows the user to browse to the exported file and perform Import.
• The Import basically adds missing schema in the new system or simply updates the existing schema.

Export 

This feature allows you to export selected pages including its hierarchy of RTBI and KPI schema. 

1. Select the pages from the left pane and click on the right arrow button to transfer pages to the selection panel, which is on the right.
2. Page Groups can also be selected for Export instead of individual pages, and by doing so all the pages belongs to that group will be transferred to the right panel. Example below.
3. The page selection can be altered by using left and right arrows in the middle.
4. Once the pages are selected, Click on 'Export' button
5. The exported JSON file will be downloaded in the user's default “Download folder” of user’s computer.

Import

The TransferPack.json file exported from one system can be imported into another system by browsing the TransferPack.json file and uploading in the Import section of the Transfer.

1. Click on 'Select Files' icon to browse the TransferPack.json file 
2. Click on 'Import Options' tab for more options
3. Click on 'Import' button to start the Import process
4. A confirmation message 'Done' will be displayed if the transfer is successful

Import Options

This section provides the following options:

Import All Modules - Transfers all pages, fact queries, and KPI 

Import Pages Only - Only transfers pages. By expanding 'Pages' on the right hand, you can select all or a few pages. 

Import Fact Queries Only - Only transfers fact queries. By expanding 'FactQueries' on the right, you can select all or a few fact queries. 

Import KPIs Only - Only transfers KPIs. By expanding 'KPIs' on the right hand, you can select all or a few KPIs. 

'Allow Update' will give you an option to update or not update existing schema if the pages/fact queries/KPIs already exist with the same name.

NOTE: 

If the "Allow Update" checkbox is not checked, then fact query is only inserted if it does not exist, but no updates are made to the fact queries or its dependent tables.

If the "Allow Update" checkbox is checked:

• The fact query will be inserted if fact query does not exist in the destination system.
• The fact query will be updated if fact query exists in the destination system. All its dependent tables also will be updated/new record added, whichever is relevant.

Additional Requirements

1. Use Transfer Tool during the time when the system is not too busy as it might impact the speed.
2. It's advisable to take a back up of the destination database before you perform import. 
3. MSDTC must be enabled on Application Server, Database Server, and Web Server in case if you want to revert back the changes. Transaction support (transactionscope) feature can only be enabled by selecting the "Allow MSDTC" on the Import screen and needs enabling MSDTC on user's machine.
4. Steps to enable MSDTC can be found in below link [https://wiki.emite.com/wiki/Enable_MSDTC]

Limitations

• This tool can be used to import only a few pages at one time [Beta version]. You can import all the pages in multiple JSON files by selection fewer pages in one file. 
• eMite Transfer tool can only work if there is at least one page available for the admin to transfer RTBI.
• MSDTC should be installed in all servers in case if you want to revert back all the changes. If MSDTC is not enabled you will not be able to revert back the export changes. You can still restore the database backup in case if you want to revert back changes. 
• Any error messages can be found in the logs instead of UI [Beta version]. Logs for Transfer tool are found in the location [Emite Installation folder]\logs\Dashboard\EmiteTransfer]

Logs

• If there is an exception on the Import process, the import will stop with a red colored warning. More details about the errors can be found in the installation log. eMite Transfer logs can be found in: [EmiteInstallationDirectory]\eMite\[EmiteVersion]\logs\Dashboard\EmiteTransfer.txt]