Setting Flow Properties

How to:

Reference:

Flows properties allow you to view or set properties that apply to the entire data flow. These include:

You specify flow properties in the flow properties pane, which is available by clicking the Properties button in the Data Flow or Process Flows tabs.


Top of page

x
Procedure: How to Set the Flow General Properties
  1. On the Flow tab, in the Tools group, click Properties.

    The flow properties pane opens.

  2. In the Description field, enter a description of the flow.
  3. Optionally, in the Comments field, enter comments about the flow.
  4. Click Save in the toolbar.

Top of page

x
Reference: Flow Properties Pane - General Attribute

The flow properties pane is available by clicking Properties in the Insert group on the Flow tab.

General Properties

The General attribute section of the flow properties pane has the following fields and options.

Description

Is a description of the flow. You can enter up to 150 characters.Descriptions display in the navigation pane next to the flow name.

Comment

Are comments regarding the flow.

This page also provides information on the flow name, the user who created the flow, and the date it was last modified.


Top of page

x
Procedure: How to Set the Flow Execution Properties
  1. On the Flow tab, in the Tools group, click Properties.

    The flow properties pane opens.

  2. Expand the Execution attribute.
  3. Optionally, set a stop processing option.

    You can stop processing after a specific number of DBMS errors or if no data is returned.

  4. Click Save in the toolbar.

Top of page

x
Reference: Flow Properties Pane - Execution Attribute

The flow properties pane is available by clicking Properties in the Insert group on the Flow tab.

Execution Properties

The Execution attribute section of the flow properties pane has the following fields and options:

Stop after DBMS errors

Causes the flow to fail with a non-zero return code if the number of errors specified is exceeded. Applies to relational targets when Insert/Update or Insert records from memory is used. Any rows written to the RDBMS are committed to the RDBMS. The default value is 10000000, unless this is overridden in the Run Options found in the Tools group of the Home tab.

A relational database may return an error for a constraint violation, such as a Unique Index constraint, a Not Null constraint, or a user-specified constraint.

If such errors are not expected, you may want to fix their cause without waiting for the entire flow to be processed. Using a low value, such as 10, can provide enough information to determine the cause of the problem, without running the entire job.

If such errors are expected, and you want to continue processing anyway, use a high value, one greater than the number of records in the source, or do not check the Stop processing after check box.

Note: When using the Load Type setting of Bulkload utility using a disk file, this setting is not used.

Stop if 0 rows selected

Allows you to stop processing if no data is returned.


Top of page

x
Procedure: How to Set the Flow Restart Properties
  1. On the Flow tab, in the Tools group, click Properties.

    The flow properties pane opens.

  2. Expand the Restart attribute.
  3. Choose a number of attempts and a restart point (Beginning or Last Commit). If you do not set this option, it will default to zero restart attempts.
  4. Set a value for the sched_restart_interval attribute in order to set the restart time interval. For more information, see Scheduler Configuration Window.
  5. Click Save in the toolbar.

Top of page

x
Reference: Flow Properties Pane - Restart Attribute

The flow properties pane is available by clicking Properties in the Insert group on the Flow tab.

Restart Properties

The Restart attribute section of the flow properties pane has the following fields and options.

Number of Attempts

Is the number of times a flow will be restarted if the execution fails

Note: The amount of time between restart attempts can be set for the server. The default value is 60 seconds. For more information, see Setting Up DataMigrator.

Restart From

Is the point from which the next attempt will be made. The options are Beginning or Last Commit.

Note: Last Commit cannot be used for flat file, delimited file, or XML targets. Last Commit can only be used for existing targets, and cannot be used with Prior to Load Options of Delete all rows from table, Truncate table, or Drop table.


Top of page

x
Procedure: How to Set the Flow E-mail Notification Properties

Note: Your DataMigrator Server must be configured for e-mail notification to use this option.

  1. Right-click the Start object in a process flow and select Properties.

    The flow properties pane opens.

  2. Expand the E-Mail Notification attribute.
  3. Select an option for email notification.

    The options are to send an email on:

    on start - when a flow is executed.

    on end - when a flow execution is successfully completed.

    on failure - when an error terminates a flow execution.

    Note: The email for a flow end or a failed flow will include the log file for the flow.

  4. Enter an email address in the Mail To field.
  5. Click Save in the toolbar.

Top of page

x
Reference: Flow Properties Pane - E-Mail Attribute

The flow properties pane for E-mail is available by right-clicking the Start object in a Process Flow and selecting Properties.

E-Mail Notification Attribute

E-Mail On Start, E-Mail On Completion, and E-Mail On Failure all have the following fields and options:

Mail To

The email addresses where the messages will be sent. Place each email address (or user ID configured on the server with an associated email address) on a new line with no separators.

Mail to addresses defined in procedure

You can send the messages to email addresses defined in the procedure by either typing in the location of the procedure, or clicking the ellipses and manually selecting it from the Select Procedure dialog box.

Enable

Select this to enable when an email should be sent.

Advanced

Select this option to get the following options:

  • Importance. Select the importance for the E-mail from the drop-down menu. Choices are Low, Normal or High.
  • Subject. The subject line of the message.
  • E-Mail Message. The body of the message.
  • Send HTML output as inline message. When selected, if any stored procedures called by the flow generates an output, the message is included as message text instead of as an attachment. This option is only available in the E-Mail On Completion section.

Note: Your DataMigrator Server must be configured for email notification in order to use this option. See How to Configure the Server for E-mail Notification.


Top of page

x
Procedure: How to Set the Flow Record Logging Properties
  1. On the Flow tab, in the Tools group, click Properties.

    The flow properties pane opens.

  2. Expand the Record Logging attribute.
  3. Select an option for record logging.

    The options are:

    • DBMS Errors. Transactions rejected by an RDBMS due to a constraint violation or data type error. For flat file targets, format errors are also recorded.
    • Duplicate Rejections. Transactions rejected due to a duplicate key.
    • Invalid Data. Transactions rejected for not meeting a VALIDATE condition.
    • No Match Rejections. Transactions rejected when a required key is not found.
    • Format Errors. Transactions rejected due to a format error. (Format errors only apply to Direct Load Flows.)
    • Accepted Transactions. Transactions that were accepted.
    • All Transactions.
  4. Click Save in the toolbar.

Top of page

x
Reference: Flow Properties Pane - Record Logging Attribute

The flow properties pane is available by clicking Properties in the Insert group on the Flow tab.

Record logging properties

The Record Logging attribute section of the flow properties pane has the following fields and options:

Record Logging on:
DBMS Errors

Logs transactions rejected by an RDBMS due to a constraint violation or data type error. For flat file targets, format errors are also recorded.

Duplicate Rejections

Logs transactions rejected due to a duplicate key.

Invalid Data

Logs transactions rejected for not meeting a VALIDATE condition

No Match Rejections

Logs transactions rejected when a required key is not found.

Format Errors

Logs transactions rejected due to a format error. (Format errors only apply to Direct Load Flows.)

Accepted Transactions

Logs transactions that were accepted.

All Transactions

Logs all transactions.


iWay Software