Configuring pipelines

When a pipeline starts up, it checks for a pipeline configuration file to get its initial startup variables and configuration information necessary to process incoming data. By default, when a pipeline is installed on the pipeline node, the system also installs a default pipeline configuration file, named pipeline.ini, that can be used by all pipelines on that pipeline node. But some sections of this default file must be configured specifically to the pipelines running on the pipeline node so the pipeline has the proper connections and access to the entity database. Use these instructions to configure the pipeline configuration file.

Before you begin

You must know the exact name of the entity database and the login credentials necessary to access the entity database.
If your system connects to external address correction software, you must know the name of the address correction software host machine and be able to select the appropriate settings for this software.
For configuration file changes to take effect, you must stop any running pipelines on this pipeline node, and then restart the pipelines after completing the changes.

About this task

The pipeline.ini configuration file is a standard ASCII text file. You can use any ASCII text editor to edit the file.

Procedure

Make a copy of the default pipeline.ini configuration file and save the original file in a safe location. If you save a copy of the original file, you can revert to that file, if needed.
Open the copy of the pipeline.ini configuration file in the text editor of your choice.
Update the file to reflect the appropriate configuration for the pipelines running on this pipeline node. Typically, the default values in the default pipeline configuration file are adequate; usually, you only need to enter or update the database connection information under the [SQL] heading and any address correction information under the [OAC] section, if your system uses external address correction software.
Save the updated pipeline configuration file. The file should be saved to the directory where the pipeline executable command resides. (Otherwise, you must specify the pipeline configuration file name and full path location every time you start a pipeline on this pipeline node.)

What to do next

If you stopped all running pipelines on this pipeline node before making the changes, you can restart the pipelines. If you did not stop all running pipelines before making these changes, you should stop and restart them now. Pipelines that are running do not apply the pipeline configuration file changes until they have been restarted. Changing pipeline configuration information without stopping pipelines may cause pipeline errors, including pipeline shut down, due to incorrect pipeline configuration file values.