Skip to main content
Hitachi Vantara Lumada and Pentaho Documentation

Importing dataflows

  1. Last updated
  2. Save as PDF

Parent article

Dataflows are imported Data Transformation Editor and PDI client transformation (KTR) and job (KJB) files tagged for use in Dataflow Studio. When importing, you can also tag dataflows to assign group permissions that define user access to the dataflow file. Your tagged, imported files are then available for users to view, configure, schedule, and execute in Dataflow Studio, depending upon their permissions settings in LDOS.

When you tag in the Extended Description field of the KTR or KJB, you can identify the file as a dataflow, and can assign group permissions to it. As an LDOS administrator or data engineer, you must enter the tag #dataflow to import a file as a dataflow. Optionally, you can add the tag #group, where group is the group name, to assign permissions for the dataflow to a specific group or groups.

For example, you could have the following text in the extended description field: #dataflow #HR #Finance #Sales. In this case, the file appears in Dataflow Studio with permissions assigned to the HR, Finance, and Sales groups. If the dataflow does not include permissions tagging, then it will be available to all users in Dataflow Studio. See Managing users and permissions for details about assigning groups and users to content permissions.

Your dataflow files and permissions are initially imported into Dataflow Studio depending on the interval setting in the Dataflow Importer. Afterward, the dataflow is only reimported if a parameter has been added or removed from the associated KTR or KJB file.

You can make changes to an already imported dataflow:

The following steps outline the general workflow when importing dataflows from Data Transformation Editor and the PDI client:

First, Identify KTR and KJB files as dataflows including permissions so they successfully import as dataflows.

Then, Upload your KTR and KJB files into Lumada DataOps Suite to complete the import process.

Parent Topic
Child Topics

Identify KTR and KJB files as dataflows including permissions
You must add the text #dataflow in the extended description field of the Data Transformation Editor or PDI client KTR and KJB files to create them as dataflows in Lumada DataOps Suite. Optionally, in the extended description, you can also add the text #group for the name of each group that needs permissions for viewing, updating, or executing the dataflow.

NoteWhen using more than one KTR or KJB in your transformation or job file, only include the text #dataflow in the extended description in the main file and not on the individual KTRs or KJBs, or within any sub-transformations or sub-jobs within that file. Otherwise, each tagged occurrence creates a separate dataflow file.

Perform the following steps to identify your KTR and KJB files as dataflows.

Procedure

  1. From the Data Transformation Editor or the PDI client, click File Open.

    NoteIf your KTR and KJB files are kept in a Pentaho Repository, you must export the files from the repository to perform the following steps to identify them as dataflows. See Export content from the repository in the Pentaho documentation for details.
    The Open dialog box appears.

  2. Browse to and then double-click the KTR or KJB file that you want as a dataflow.

    Your selected file opens.

  3. Double-click the canvas.

    Depending on the selected file type, the Transformation properties dialog box appears or the Job properties dialog box appears.

  4. Proceed according to your file type.

    • KTR files: In the Transformation tab of the Transformation properties dialog box, locate the Extended description field, then enter #dataflow and click OK. To include permissions for the dataflow, add #group, where group is the group’s name, for each group that requires permissions. To add multiple permissions, separate each additional #group by a space.
    • KJB files: In the Job tab of the Job properties dialog box, locate the Extended description field, then enter #dataflow and click OK. To include permissions for the dataflow, add #group, where group is the group’s name, for each group that needs permissions. To add multiple permissions, separate each additional #group by a space.

    Transformation properties dialog box

    NoteIf your Extended description field already contains text, you can add #dataflow after the existing text. You just need to include #dataflow anywhere in the Extended description field for your KTR and KJB files to become dataflows. Add any group permissions after #dataflow.

  5. Click File Save.

Results

Your KTR or KJB file is now tagged as a dataflow, and optionally with group permissions.

Next steps

After saving your KTR and KJB file, copy the file into the dataflow import directory to upload it as a dataflow. See Upload your KTR and KJB files into Lumada DataOps Suite for instructions. If you need to make changes to the group permissions, see Manage dataflow permissions for details.
Parent Topic

Upload your KTR and KJB files into Lumada DataOps Suite
You can upload your KTR and KJB files into Lumada DataOps Suite by copying the files into a network shared file system (NFS) directory.

Procedure

  1. Check with your system administrator as to the location of the NFS directory set up to upload KTR and KJB files into Lumada DataOps Suite as dataflows.

  2. Navigate to the location of the KTR and KJB files you want to upload into as dataflows.

  3. Copy the KTR and KJB files you want to upload to Lumada DataOps Suite.

  4. Navigate to the specified NFS directory.

  5. Paste the copied files into the NFS directory.

Results

Dataflow Importer uploads any KTR or KJB files in the NFS directory within a time interval specified by your system administrator.

Next steps

See Navigating dataflows for details on how to use your new dataflows in Lumada DataOps Suite.
Parent Topic