IM InfoSphere Identity Insight, Version 8.0

Starting Web services pipelines

To send and process data sent through a Web service, start the pipelines using the bi-directional HTTP transport. Typically, pipelines used with Web services remain constantly running in the background, listening to the assigned ports for data to process. Use these steps to start a Web services pipeline.

Before you begin

About this task

There are three steps to starting a pipeline:

Procedure

  1. Verify that there are no other pipelines currently running on the pipeline node which have the same name as the pipeline you want to start. Each pipeline must have a name unique to its pipeline node. (The default pipeline name is pipeline.) There are two ways to verify this:
    1. If you are using the application monitor to check the status of pipelines or route the results to other systems, look at the Pipeline Status tab to see if there is another pipeline running that has the same name you want to use.
    2. Or at a command prompt, type the following command:
    pipeline -n pipelinename -l

    where pipelinename is the name you want to use to start the new pipeline. Make sure that this name matches the name registered in the Configuration Console for this pipeline.

  2. At a command prompt, start one or more pipelines by specifying the type the appropriate pipeline command options and parameters using this format:

    pipeline -option parameter

    Note: If you are using the application monitor for this pipeline and it has been registered in the Configuration Console for monitoring or routing, be sure to use the -n option as part of the pipeline start command and specify the registered pipeline name. If the pipeline name specified does not exactly match the registered pipeline name (including case), the pipeline status will not display correctly on the Configuration Console Pipeline Status tab and any routing configured for this pipeline will not be successful.
    Note: Typically, you use either the -s or the -d pipeline option to start the pipeline in either service/daemon or debug mode, as appropriate.
  3. Verify that the command worked, and the pipeline is started and active.
    1. If you are using the application monitor and this pipeline has been registered in the Configuration Console, check the Pipeline Status tab. If the pipeline is active, the status displays as Active.
    2. If your system is running on a Microsoft Windows platform and you are using the services pipeline option, you can see the status of the pipeline in the Microsoft Windows Services control panel.
    3. If your system is running on a UNIX platform and you are using the daemons pipeline option, you can type the following command to check for running processes:

      ps -fu userid

      where userid is the identification of the user starting the pipeline.

    4. Or at a command prompt, type the following command:
    pipeline -npipelinename -l

    where pipelinename is the name of the pipeline you just started.

    If the pipeline is active, the command prompt returns Running.

What to do next

This pipeline command starts the number of pipeline processing threads equal to the concurrency parameter in the pipeline configuration file. The number of records processed simultaneously is determined by the concurrency parameter included in the HTTP transport option.


Feedback

Last updated: 2011