Migrating variables using a directory with template.xml files as input

bin/migration.sh nifi migrate-variables \
-i /etc/migration-tool-input \
-od /etc/migration-tool-output/variables \
--sourceCompatibleOutput

This generates a sourceVersion folder that contains the output files of the Stage 1 migration.

variables
└── sourceVersion
    ├── activity_log.json
    └── migrated_output
        ├── migrated_Elastic_template.json
        └── migrated_TCP_Listener_template.json

activity_log.json

• A new parameter context was created with a new parameter called TCP Listener Port, which replaces the corresponding variable.

• The TCP Listener Port variable was removed.

• A new parameter context was created with a new parameter called Elasticsearch Index, which replaces the corresponding variable of the same name.

• The new parameter is referenced from the PutElasticsearchJson processor.

• The Elasticsearch Index variable was removed.

migrated_TCP_Listener_template.json

• A modified NiFi 1 flow, which is not compatible with NiFi 2 yet.

• It contains everything the original flow did, except the TCP Listener process group now references a parameter instead of the removed variable.

• This is still a NiFi 1 flow definition, so do not load this file directly into NiFi 2. Use an empty NiFi 1 instance to review the modification made by the tool. The flow definition will appear unchanged, but variables will be replaced with parameters of the same name, which are now referenced by the processor instead.

• Changes in the syntax: Variables were previously referenced using ${}, whereas parameters are now referenced using #{}.

  • NiFi 1 variables: ${variable_name}

  • NiFi 2 parameters: #{parameter_name}

migrated_Elastic_template.json

• A modified NiFi 1 flow definition, which is not compatible with NiFi 2 yet.

• It contains everything the original flow definition did, but the Elastic process group now references a parameter instead of the removed variable.

At this stage, the flow definition no longer contains variables and uses parameters instead. If the flow meets your expectations, you can either run a full variable migration to validate your flow in NiFi 2 or proceed with migrating the components.

At this stage, both flow definitions no longer contain variables and use parameters instead. If the flow meets your expectations, you can either run a full variable migration to validate your flow in NiFi 2 or proceed with migrating the components.

bin/migration.sh nifi migrate-variables \
-i /etc/migration-tool-input \
-od /etc/migration-tool-output/variables

This generates a sourceVersion and targetVersion folders that contain the output files of the migration.

variables
└── sourceVersion
│    ├── activity_log.json
│    └── migrated_output
│        ├── migrated_Elastic_template.json
│        └── migrated_TCP_Listener_template.json
└──targetVersion
    ├── activity_log.json
    └── migrated_output
        ├── migrated_Elastic_template.json
        └── migrated_TCP_Listener_template.json

The contents of the previously generated sourceVersion folder will be overwritten, but this is not a concern as the tool generates the same sourceVersion output as before.

Additionally, a targetVersion directory is created, containing the output files of the Stage 2 part of the migration.

migrated_Elastic_template.json

• NiFi 2-compatible flow in terms of variables

• You can load it into NiFi 2 and validate it

migrated_TCP_Listener_template.json

• NiFi 2-compatible flow in terms of variables

• You can load it into NiFi 2 and validate it

activity_log.json

• List of all actions performed during this stage of the migration.