Manage Analytic Data Flows

About Analytic Data Flows

Select and connect analytics from the analytics catalog to build analytic data flows.

Analytics Data Flows allow you to select analytics from the analytics catalog and place them into a specified order to run sequentially. All configuration information for the selected analytic is retrieved from the analytic template in the analytic catalog.

Each analytic added is considered a step in the analytic data flow. The inputs, constants, and outputs for the analytic are mapped on the I/O Mapping page. Each step in the data flow can contain multiple iterations of the step's I/O mapping.

When an analytic is created and added to the analytic catalog, a version is assigned to that analytic. For existing deployments which contain analytics whose version has been updated (single-step and/or within an Orchestration), and if the version has been marked as current, the deployment will then use the updated analytic version. The Analytics Data Flow section lists the version of the analytic being used for a particular analytic step in an orchestration.

When you edit or remove an analytic from the Analytic Data Flow, existing deployments for the orchestration are not affected. An existing deployment reflects the change only after you redeploy the analytic.
Note: If you do not wish to update an existing deployment with recent changes to analytics, then, consider creating an additional orchestration rather than redeploying an existing orchestration.

Determine Analytic Versions

You can determine the analytic version being used within an Analytic Data Flow.

About This Task

Determining an analytic version for an analytic step in an Analytic Data Flow allows you to make decisions about modifying the orchestration based on that analytic version.

The analytic version refers to the analytic artifacts that were loaded into the analytic catalog. You can determine the version being used by analytic orchestration, and the user who loaded it into the analytic catalog. You can change the analytic version in an analytic orchestration data flow during deployment.

Procedure

  • To determine the current analytic version in an analytic orchestration, do the following:
    1. In the module navigation menu, navigate to Analytics > Orchestrations.
    2. In the Search pane, select an existing orchestration to access its workspace.
    3. In the Orchestration section, hover over a step in the Analytic Data Flow subsection.
      The version for the analytic used in the step appears above the step.
  • To determine the analytic version of available analytic templates for use in orchestrations, do the following:
    1. In the module navigation menu, navigate to Analytics > Orchestrations.
    2. In the Search pane, select an existing orchestration to access its workspace.
    3. Select the Edit icon () in the Analytic Data Flow subsection of the Orchestration section.
      In the pane that appears, available analytic templates are listed with their version numbers beneath each analytic.

Add an Analytic to a Data Flow

You can add one or more analytics in the catalog to the data flow.

Before You Begin

Make sure at least one analytic exists in the analytic catalog.

About This Task

You can add multiple analytics to the data flow. When you add or drag an analytic to an existing data flow, the newly placed analytic links automatically to the adjacent analytics. Each added analytic is considered a step in a sequence. You cannot reorganize the items to modify the sequence of the data flow. However, you can delete analytics in the data flow and add them back in a different order.

Note: Analytics added in the available analytics list also contain template information added in the analytic catalog.
Warning: Adding, deleting, or changing the order of steps affects the current deployments. Consider creating a new orchestration rather than modifying an existing one.

Procedure

  1. In the module navigation menu, navigate to Analytics > Orchestrations.
  2. In the Search pane, select an existing orchestration to access its workspace.
  3. Do one of the following to add the analytics template to the data flow:
    OptionDescription
    To add an analytic to an empty analytic data flow
    • Select the Add icon () in the Analytic Data Flow subsection of the Orchestration section.
    • In the pane that appears, locate the analytic that you want to add as the first step in the analytic data flow. Select the Add icon () next to the analytic to insert, or drag the new analytic to the Analytics Data Flow section.
    To add an analytic next to an existing analytic step in the data flow
    • Select the Edit icon () in the Analytic Data Flow subsection of the Orchestration section.
    • Select the analytic in the data flow after which you want to insert the new step.
    • In the pane, locate the analytic that you want to add as the next step in the analytic data flow. Select the Add icon () next to the analytic to insert, or drag the new analytic below the highlighted analytic in the Analytics Data Flow section.
    To add an analytic as the last step in the data flow
    • Select the Edit icon () in the Analytic Data Flow subsection of the Orchestration section.
    • In the pane that appears, locate the analytic that you want to add as the last step in the analytic data flow. Select the Add icon () next to the analytic to insert, or drag the new analytic to the Analytics Data Flow section.

Modify an Analytic Data Flow

You can modify the analytic data flow to add existing analytic template.

About This Task

When you modify an analytics data flow, make sure that the orchestration is not deployed. Consider creating a new orchestration rather than modifying one that is in use.

In the Analytic Data Flow edit page, you can:
  • Modify the description.
  • Add analytics in the Available Analytics list.
  • Delete analytics in the Analytic Data Flow.

Make sure you add analytics in the order you want them to execute.

Procedure

  1. In the module navigation menu, navigate to Analytics > Orchestrations.
  2. In the Search pane, select an existing orchestration to access its workspace.
  3. Hover over the existing description, then select on the Description box, then make your modifications, and then press ENTER or select outside the Description box.
  4. Select the Edit icon () in the Analytic Data Flow subsection of the Orchestration section.
  5. Add analytics or delete analytics in the data flow.
  6. Select Save to save your modifications.

Delete an Analytic in a Data Flow

You can delete an analytic step in an analytic data flow.

About This Task

Warning: Adding, deleting, or modifying the order of steps affects the current deployments. Consider creating a new orchestration rather than modifying an existing one.

Procedure

  1. In the module navigation menu, navigate to Analytics > Orchestrations.
  2. In the Search pane, select an existing orchestration to access its workspace.
  3. Select the Edit icon () in the Analytic Data Flow subsection of the Orchestration section.
  4. In the Analytics Data Flow section, hover over an analytic step, and then select .
  5. In the Confirmation dialog box, select Remove.
  6. Select Done in the page header to exit the edit mode.
    The analytic step is removed in the data flow. The remaining analytic steps in the data flow automatically reconnect.

Modify the Analytic Version During Deployment

You can modify the analytic version being used within an Analytic Data Flow during deployment.

Before You Begin

You must have uploaded more than one analytic version to modify during the deployment of that analytic.

About This Task

Modifying the analytic version for an analytic step in an analytic data flow allows you to use a different version than set as current (default) in the analytic template.

The analytic version refers to the analytic artifacts that were loaded into the analytic catalog. You can determine the version that the analytic uses when deployed by itself or within an orchestration.
Tip: Map your inputs, constants, outputs, and attributes after you have modified the version of the analytic to apply during deployment. Modifying a different version post mapping may require you to perform the mapping step one more time for properly deploying it to the runtime.

Procedure

  1. In the module navigation menu, navigate to Analytics > Deployments.
  2. Select an existing deployment to access its workspace.
  3. In the page heading, select Edit to access the deployment.
  4. Select the 2. I/O Mapping tab.
  5. Select to access the Data Flow pane.
  6. Select a analytic step node. For example, if you have Analytic_Wind_Throughput as one of the analytic step in the deployment, then select that node to access Analytic_Wind_Throughput subsection of the 2. I/O Mapping section in the deployment.
  7. Select a version in the drop-down list box in the Version column, and then select Use this Version.
    The Mapping may be lost box appears with the message If there are structural changes between analytic versions, you may lose some or all of the existing mapping.
  8. In the Mapping may be lost box, select Continue to change the version or select Cancel to keep the current version.