Modifying the pipeline object’s definition

By default, you can execute a pipeline in an application, but you cannot modify the pipeline object’s definition.

If you are deploying your application to advanced users, however, you may want to give users the ability to modify the pipeline object from the application. Allowing users to modify pipelines means that you do not have to modify the pipeline object in InfoMaker, recreate the application, and deploy it immediately. However, since the pipeline object definition is not saved when you modify a pipeline in an application, you should redeploy the application later.

What you can allow users to modify

To modify a pipeline definition, either you or your users must add a new section to the application’s initialization file. Users can change the type of pipeline operation and the Commit and Max Errors values. Depending on the quality of the network connection (particularly if users are connecting by telephone from laptops), lowering the Commit and Max Errors values could result in more efficient committing of rows to the database. For example, committing all rows when the database connection is through a 28.8 Kb/sec modem could take a long time and your phone connection could fail. It may be better to change the Commit value to 10.

StepsTo enable users to modify the pipeline’s definition:

  1. Open the application’s initialization file and create a Pipe section by adding the following line:

    [Pipe]
    

  2. Include these lines in the Pipe section:

    [Pipe]
    AllowTypeChange = 1
    AllowRunTimeChange = 1
    

    This keyword

    Allows the user to change the

    AllowTypeChange

    Type of pipeline operation: Create, Refresh, Replace, Append, and Update

    AllowRunTimeChange

    Commit value, Max Errors value, and whether to pipe extended attributes

    NoteOmitting lines in the [Pipe] section If you do not want users to change the pipeline type, you can omit the AllowTypeChange line in the [Pipe] section. You cannot omit the AllowRunTimeChange line.

  3. Save the initialization file.

    Now when you select the Actions menu in a pipeline, you see new menu items that enable you to change the pipeline type, the Commit value, the Max Errors value, and whether the pipeline copies extended attributes:

    Shown is the Actions menu with options for Execute, Repair, Cancel, Reset Pipeline Log, Pipeline Type, Pipeline Commit After, Pipeline Max Errors Allowed, Pipeline Copy Extended Attributes, which is checked, and Delayed Execution. Repair and Cancel are grayed and right arrows appear next to Pipeline Type, Pipeline Commit After, and Pipeline Max Errors Allowed.

Modifying the pipeline definition

After a user’s application initialization file has been modified to include the [Pipe] section, the user can use items on the Actions menu to modify the pipeline definition.

For complete information about pipeline types, the Commit value, and the Max Errors value, see Chapter 4, “Working with Data Pipelines.”

StepsTo modify the pipeline type:

  1. Select Actions>Pipeline Type from the menu bar.

    A menu of pipeline types displays.

  2. Select the pipeline type:

    Shown is the Actions menu with the Pipeline Type option highlighted and its submenu displayed. The Pipeline Type options include Create - Add Table, Replace - Drop / Add Table, which is checked, Refresh - Delete / Insert Rows, Append - Insert Rows, and Update - Update / Insert Rows.

StepsTo modify the Commit value:

  1. Select Actions>Pipeline Commit After from the menu bar.

    A menu of Commit values displays.

  2. Select the Commit value:

    Shown is the Actions menu with the Pipeline Commit option highlighted and its submenu displayed. The Pipeline Commit options include All Rows and None and the choices 1, 10, 100, 1,000. Under them is the checked value Default : 100.

StepsTo modify the Max Errors value:

  1. Select Actions>Pipeline Max Errors Allowed from the menu bar.

    A menu of Max Errors values displays.

  2. Select the Max Errors value:

    Shown is the Actions menu with the Pipeline Max Errors Allowed option highlighted and its submenu displayed. The Pipeline max Errors Allowed vlues are No Limit, 1, 10, 100, 1,000. Under these is the checked value Default: 100.

StepsTo specify whether or not to pipe extended attributes:

  1. Select or clear the Actions>Pipeline Copy Extended Attributes menu item:

    Shown is the Actions menu with options for Execute, Repair, Cancel, Reset Pipeline Log, Pipeline Commit After, Pipeline Max Errors Allowed, Pipeline Copy Extended Attributes, which is checked, and Delayed Execution. Repair and Cancel are grayed and right arrows appear next to Pipeline Commit After and Pipeline Max Errors Allowed.