Importing legacy documents - Data360_Analyze - 3.12

Data360 Analyze Server Help

Data360 Analyze
Product family
Product name
Data360 Analyze
Data360 Analyze Server Help
First publish date
Note: Only graphs created in LAE version 6.1 or later can be imported to Data360 Analyze. Graphs created prior to version 6.1 are not supported in Data360 Analyze. Data flows and library nodes that were created in LAE are stored as BRG files, rather than LNA files. Legacy BRG files can be imported, but BRX files are not supported.
Tip: "Data flow" is the new name for "graph" in Data360 Analyze. See Terminology changes for a full list of updated terminology.

The process of transferring your graphs from LAE to Data360 Analyze is outlined below:

  1. Open your graphs and dependent libraries in BRE. Save the libraries by selecting Save from the File menu, then repeat this step to save your graphs with the latest libraries. It is important to complete this step even if you have previously saved your graphs and libraries.
  2. Choose where to install Data360 Analyze. You can install Data360 Analyze on a new machine, or on the same machine as an existing LAE installation. The installer will suggest alternative ports if it detects an existing installation is running.
  3. Install the latest version of Data360 Analyze:
  4. Read What's changed? for an overview of the changes between LAE and Data360 Analyze in preparation for transferring your graphs.
  5. Read Supported nodes for a list of nodes that have been superseded or deprecated.
    Note: The basic.brg and simple.brg node libraries are no longer available. If your graphs contain nodes from these libraries, you should replace these nodes with nodes from the core library prior to importing.
  6. Migrate graphs from LAE to Data360 Analyze:
    1. Locate the BRG files for your production graphs (version 6.1 or higher — graphs created prior to version 6.1 are no longer supported).
    2. If the graphs that you are migrating are dependent on one or more custom libraries, you must first import the custom libraries into your new Data360 Analyze installation by selecting import > Legacy Node Libraries from the Directory. In BRE, you can check if there are any dependencies by selecting Dependent Libraries from the View menu.
    3. When you open a document in Data360 Analyze, library paths are used to populate the Nodes panel. Ensure that the default list of library paths includes the folder that you have imported any legacy node libraries into. You can check this in the Directory by clicking Settings, then selecting Library Paths.
      Note: Changes to the list of default library paths will apply to all new documents that you create. Once you have imported your document, you may want to remove the folder from the default list and instead manage library paths at a document level. See the "Library paths" topic in the integrated help for more information.
    4. Import your production graphs into your new Data360 Analyze installation by selecting Import > Legacy Data Flow or Legacy Node Libraries from the Directory.

      When prompted, select the BRG file to import and then select the folder to which you would like to import the legacy document.

      Note: If you are using the server product and want to share documents with other users, ensure that the permissions set on the document gives users the required level of access.

      If the import is successful, the imported documents will be listed in your chosen folder in the Directory.

      If there are any errors in the document that is being imported, an import Issues dialog will notify you, giving you the option to continue or cancel the import. A common reason for seeing the import Issues dialog is if the data flows or library nodes cannot locate all of their dependencies.

      If the import fails, an import Failed dialog will inform you that the process has not completed successfully. An import will most commonly fail if the BRG was not created in LAE version 6.1 or later.

      If you want to import a legacy data flow into multiple instances of Data360 Analyze, it is recommended that you only import the BRG into one environment, then export the data flow in the new LNA format. You can then use the LNA for importing into other environments. This ensures that the data flow is recognized by the same unique ID across multiple environments.
  7. Select a number of graphs for testing. Run the graphs in both LAE and Data360 Analyze to confirm that they execute as expected and that there are no adverse effects as a result of the migration. While testing, you should be aware of the following changes:
    • If your graphs contain superseded nodes, although these are still available for backwards compatibility, we recommend that you begin replacing these nodes with the new Python-based nodes, see Supported nodes and BRAINscript to Python.
    • If you are still using some superseded nodes in your graphs while you transition to use the new Python-based nodes, it is important to be aware of a number of BRAINscript changes in Data360 Analyze compared to LAE, see BRAINscript changes.
    • Make a note of any run properties as these are not stored in the BRG files and you will need to populate the corresponding run properties in Data360 Analyze.
    • As password properties are encrypted, you will need to know the cleartext passwords in order to populate the corresponding properties in Data360 Analyze.
  8. When you are happy that you have successfully transferred your graphs, shut down LAE and begin working in Data360 Analyze.