Migration from Executive Scorecard 9.50 to Business Analytics 10.10

To prepare the environment for the ITBA and the BOE instances:

1. Download and Install the ITBA 10.10 instance.

   For details, see the ..

2. Install the BOE instance.

   Download the BOE 4.1 SP3.

   For details, see the . for the supported versions of BOE.

   Install the BOE instance.

   For details about a new installation, see the ..

3. Install the Vertica Driver for the BOE instance.

   For details, see Optional - Install the Vertica Driver in the BOE Server and the BOE Client Server in the ..

4. Install BOE client 4.1 SP3 if you need to migrate the BOE reports.
5. It is recommended to install a Vertica client tool (for example DBeavor) to help you edit SQL statements.

1. Download and Install the ITBA 10.10 IDE environment from HP Live Network.
2. Backup the entire existing XS 9.50 IDE workspace directory.

3. Merge the new 10.10 IDE workspace directories and existing XS 9.50 IDE workspace directories:

   1. Find the cp-core directory under the 10.10 IDE workspace directories.

   2. Find the cp-core-architect directory under the 10.10 IDE workspace directories

   3. Copy those two directories to the XS 9.50 IDE workspace directories.

4. Launch the new 10.10 IDE.

5. Import projects from the newly merged IDE workspace directory.

   For details, see Import Existing Content .

   

1. Download the Migration Tool from HPLN (https://hpln.hpe.com//node/10214/otherfiles/?dir=29434) to the existing XS 9.50.0004 server for standalone configuration or to the Data Warehouse server in a distributed configuration, in the production environment.

2. Unzip the migrationtool.zip file.

The XS Usage Analysis Tool scans all user usage data in the XS 9.50 database and directories, and summarizes the results in the XS Usage Report. The report provides a reference to understand and plan the scope of the migration before starting the migration itself.

To run the tool:

1. Open the command window as administrator and locate the Migration Tool in the installation directory.
2. Run the UsageReport.bat command. A usage report Reports.txt is generated under %BTOA_HOME%.

The report is organized in different sections:

• Foundation. The section lists the XS version and license information, the total number of active users, the number of licenses of both types Power and Viewer, whether LDAP is enabled (true) or not (false).

  Foundation:

  =====================================

  ActivatedGroupsNum : 5

  XsBuildVersion : 9.50.350

  XsPatchVersion : no patch version

  PowerLicenseSeats : 10

  XsBuildNumber : 32182

  ActivatedUsersNum : 4

  LdapEnabled : false

  ViewerLicenseSeats : 5

• Content Pack directory. The section lists the deployed data sources and activated data source instances. The Migration Tool checks the physical difference between what the customer directories and the OOTB version contents based on the deployed and activated data sources. The report shows what needs to be migrated regarding the data source part.

  Activated ContentPacks:

  ===============================================

  [SM]-[SM] : Instance Id:1, State:ACTIVATED

  [LIB]-[LIB] : Instance Id:1, State:ACTIVATED

  [TCO]-[TCO] : Instance Id:1, State:ACTIVATED

  [AM]-[AM] : Instance Id:1, State:ACTIVATED

  [UCMDB]-[UCMDB] : Instance Id:1, State:ACTIVATED

   

  --------------------------Content Pack Folder Scan Summary------------------

  Total data source to migrate : 6

  1. Core

  2. SM

  3. LIB

  4. UCMDB

  5. AM

  6. TCO

  Total entity to migrate : 134

  1. Core, 80 entities

  2. SM, 24 entities

  3. LIB, 5 entities

  4. UCMDB, 4 entities

  5. AM, 8 entities

  6. TCO, 13 entities

  The Scan Summary has two parts:

  • Data source migration.Lists the data sources and the entities that you need to migrate from XS 9.50 to ITBA 10.1. For details, see Data Source Migration.
  • Incorrect customization. Lists data source and entities that you customized. For details, see Incorrect Customization.

The data source migration includes the migration of IDE metadata, ETL, data models, and streams.

1. Check the Data source migration section in the XS Usage report to understand which data source and entity to migrate.

   ------------- Data source migration -------------------------

   data source UCMDB , Total entity to migrate : 0, entity name = no entity

   data source LIB , Total entity to migrate : 5, entity name = PERSON, XXX_TITLE_CSTM, APPLICATION, XXX_APPLICATION_CSTM, ACTUALCOST_CSTM

   data source TCO , Total entity to migrate : 13, entity name = REF_DECOM_OS_HW_RELATIONSHIP, ACTUALCOST, XXX_ASSET_CSTM, REF_DECOM_BKUP_APP_REL, REF_DECOM_APP, NODE, XXX_CLASS_CSTM, APPLICATION, XXX_APPLICATION_CSTM, ACTUALCOST_CSTM, XXX_SLC_REL_CSTM, ORG, XXX_SLC_CSTM

   data source AM , Total entity to migrate : 3, entity name = XXX_ASSET_CSTM, XXX_ASSET_CLASS_REL_CSTM, XXX_ASSET_OS_VENDOR_CSTM

2. Launch the latest 10.10 IDE.

3. Open the Engineer context diagram for the relevant data source entity.

4. For each entity that needs to be migrated:

   1. Make sure all fields, links, and mapping are correct in the Engineer context diagram.

      

      Tip If you are mapping a customized field to a customized target entity make sure to use the _CSTM suffix for your customized target entity name so the IDE ETL Generator generates the CORE directory for the target entity.

   2. In the IDE 10.10, launch the ETL Generator to generate your Entity and Data Source in IDE.

      For details, see Generate Content Package.

      

   3. Merge the newly generated artifact to the $HPBA_Home/Content Packs/ directory.

Customized extractors cannot be migrated from XS 9.50 to ITBA 10.10. You must recreate your customized extractors by following the DCS Extractor SDK Guide. For details, see .

1. For each data source:

   1. Install the data source and entities.

   2. Apply your customized ETL logic if necessary.

      Note IDE generates the standard ETL logic for your entities. If you have any customized ETL logic in BODS such as SSI or MSI workflow, you need to create the similar logic in the new SSI step, which is a Vertica SQL based script.

      For details on how to customize the SSI step, see Customize the SSI Layer

   3. Connect to the data source.

   4. Run ETL to populate the source data into the target database.

   5. Apply your customized view logic if necessary.

      Customized view are for example: XS.CHANGE_FACT_V, XS.PROBLEM_FACT_V, XS.PROJECT_FACT_V that you might have created in XS 9.50.

      Note ITBA automatically generates the view for each fact and dimension table. If you have additional customized logic in the View, apply the changes manually.

      For details on how to customize the view logic, see Customize Views

2. Verify the data correctness in the target tables(Fact, Dimension) and views.

If a list of entities appear in the Incorrect customization section in the XS Usage report, recreate these entities using the above approach. For details, see Customize the SSI Layer.

Content Pack Folder Scan Detail.This section shows how many files the tool has scanned in the customer XS 9.50 instance. Each line shows if the scanned file is new/modified/deleted compared to the XS 9.50 CP 0004 benchmark (the tool compares the file in the customer environment with the file in the XS 9.50 CP 0004 benchmark). For example, the section shows that INCIDENT belongs to an incorrect customization (see above), and the changes were done to the file (see below).

The Application Content contains Scorecard, KPIs, Metrics, Contexts, Pages, and data files (Excel import). The current Content Acceleration Pack (CAP) mechanism supports to export application content into an XS 9.50 CAP (.zip file). An XS 9.50 CAP cannot be directly imported into ITBA 10.10. To do so, you must use the CAP Migration Tool. The tool is a command-based interface application.

1. Create a new XS 9.50 CAP that includes all your Scorecards, KPIs and Metrics, Business Contexts, and Pages.

   For details, see Create a CAP with the ITBA application data.

2. Download the new XS 9.50 CAP to the server where the migration tool is installed.

   For details, see Download a CAP to the user's local system.

3. Launch the command window and go to the migration tool installation directory.

   1. Migrate the CAP using the following command: CapMigration.bat <cap file with full path>

      where <cap file with full path> is the path and file name of the relevant CAP .ZIP file.

      Example: C:\migrationtool\CapMigration.bat c:\SM_CAP.zip

      When the jar runs, the following operations take place.

      • The type of columns in the tables are changed from nvarchar to varchar, day_time to timestamp.
      • The prefix of the schema names are changed from ext to extension.schema, dwt to target.schema, and xs to application.schema.
      • In each field, the table name is changed from ext to extension.schema, dwt to target.schema, and xs to application.schema.
      • The <target_file_name> is changed to new_<target_file_name>

   2. To apply a conversion rule, make the changes in the conversionrule.txt in the same directory as the migration tool.

      Example:

      ORGANIZATION_DIM_V to ORG_DIM_V

      ORGANIZATION_DIM_V.NAME to ORG_DIM_V.NAME

4. In the dialog box that is issued, select Generate dummy context if you want to recreate later the context in Context Designer, or Convert context if you want to convert the context directly.

   In ITBA 10.10, changes were made to some of the OOTB entities in the Target database. For details, see OOTB Target DB Table Column Changes.

5. Upload, import, and activate the new CAP into the ITBA 10.10 platform.

   For details, see Upload a CAP to the Business Analytics application and Activate a CAP

6. Check the cap.log and xs2go.log in ITBA log Portal using the following URL: linkhttp://{ITBAinstance}:10002/LogPortal. Check if the CAP was imported with errors.

   For each error:

   1. Unzip the new cap package file.

   2. Open each failed context file such as, for example: the PPM_context.xml file, with an editor tool such as Notepad++.

   3. Fix the issues for all incorrect mappings in the context .xml file according to the error logs.

   4. Save the changed context file.

   5. Repackage the new cap using the WinRAR tool.

7. Redo step #5-#6 until the new CAP is activated.

8. In the ITBA Application, click ADMIN > Semantic Layer > Semantic Layer, open the relevant context.

   1. Redesign your context if necessary in Context Designer.

   2. Validate it and save it.

9. Run the KPI and business context calculation.

   For details, see Calculation..

10. Verify the data correctness for your KPIs and Pages.

BOE provides an Upgrade management tool, a Promotion management tool, and a Universe design tool to migrate the BO Users/Groups/Permissions, BO Universe/Connections, and BO reports from one machine to another. The detailed steps are provided below.

If your BOE is a new installation, go to step 1, otherwise go directly to step 3:

1. New approach. Export the BO Users/Groups/Permissions, BO Universe/Connections and BO reports from your old BOE instance as one .biar file using the Upgrade management tool in the XS9.50 BO server.

   1. Open the Upgrade Management Tool.

      

   2. Select Incremental Upgrade and Next.

      Note If you select Complete Upgrade, all objects and files from source system will be migrated to .biar files.

   3. Select Live to BIAR, and enter the CMS name, user name, and password of the source and the location of the output file. You do not have to enter a Password in the Destination section.

      

   4. If the connection of the reports that you want to export is XS_DWH_JDBC, select the reports and universes and click Export this object.

      

   5. If not, select the reports, and click Export this object and its dependencies.

   6. Click Start, and wait for the completion of the process.

2. New approach. Import the .biar file using the BOE Promotion management tool to the ITBA10.10 BO server.

   1. Copy the output file to their destination in the BOE ITBA 10.10 server.

   2. Login to the CMC of the ITBA 10.10 system.

      

   3. Choose Promotion Management in the CMC Home in the ITBA 10.10 system.

      

   4. Click Import file under Import.

      

   5. Select the .biar file and click OK.

      

   6. Select Login to a New CMS  in Destination.

      

   7. Select the destination BOE server in the System list, and enter the user name and password of the BOE server.

      

   8. Click Create.

      

   9. Select Promote.

      

   10. Select Promote.

       

   11. The operation is successful.

       

3. Create new connections:

   1. Prerequisite: The BOE Client must be installed.

   2. Open the Universe Design Tool.

      

   3. Click Tools, and Connections….

   4. Right-click the empty item and select Add.

      

      Tip Make sure the name of new connection is not XS_DWH_JDBC.

      

   5. Select the driver HP Vertica 6.1 JDBC Drivers.

      

   6. Input the Vertica connection message.

      

   7. Click Next, and Finish.

      Tip To test this connection, make sure you have installed Vertica driver in both the BOE server and the BOE Client server.

4. Update the connection in universes:

   1. Open the Universe Design Tool.

      

   2. Click File and Import in the Universe Design Tool.

   3. Click Browse to select the universe folder

   4. Select the universe and click OK.

      

   5. Click File and Parameters….

      

   6. Select the connection you just created.

      

   7. Right click all the tables, select Rename Table…, delete the schema name  and click OK.

      

      

   8. Click Refresh Structure under View.

      

   9. Export this universe to the BOE server.

      1. Click File and Export.

      2. Click Browse to select the destination folder, and click OK.

         

This section describes how to migrate the User Management and Admin Configuration data, which include the Users, Groups, Role and Permission, LDAP, Notification, Data loader, and Data Loader Scheduler created in the XS 9.50 environment.

The Migration Tool is a command-based interface application that helps you export data from the XS 9.50 repository and then import into the ITBA 10.10 repository.

1. Go to migration tool installation directory and run DataMigration.bat. It generates a DataFromSQL.csv file in the %BTOA_HOME% directory, with the relevant data from the XS9.50.0004 application.

2. Upload the DataMigration.jar and the DataMigration.sh files located under the migration directory, and the DataFromSQL.csv file located in the %BTOA_HOME% directory to the $HPBA_HOME directory in the ITBA10.10 environment.

3. Run the DataMigration.sh to import data into ITBA 10.10.

4. In the ITBA 10.10 application, click ADMIN > Users and Roles, click the User Management, Role Management, Resource Management, LDAP Management, and Dimension Permission tabs, and verify the information.

5. In the ITBA 10.10 application, click ADMIN > Settings > Foundation and reset the password for the Notification Mail Server.

   For details, see Settings - Foundation.

6. In the ITBA 10.10 application, click ADMIN > Semantic Layer > Data Loader Scheduler and verify the data loader scheduler.

   For details, see Semantic Layer - Data Loader Scheduler .

7. In the ITBA 10.10 application, click ADMIN > Notifications > Entity Reports and verify the notification entity reports.

   For details, see Notifications - Entity Report.

License data cannot be migrated from XS 9.50 to ITBA 10.10. You can only reimport the license using the Maintenance Tool. For details, see Update ITBA Licenses.

SSO data cannot be migrated from XS 9.50 to ITBA 10.10.

In the ITBA 10.10 application, click ADMIN > Setting >Single Sign-On, and reconfigure the SSO settings.

For details, see Settings - Single Sign-On

The Target data exists in each dimension and fact tables. Each data source can be configured to extract the source data from a previous date such as 1-2 years ago. When the ETL job runs, it automatically populates the data into the dimension and fact tables.

1. In the ITBA 10.10 application, click ADMIN > Data Management > Run ETL.

2. Verify the data correctness in the target tables(Fact, Dimension) and views