Customizing pipeline processing

In addition to providing your own message handlers, you can also use a set of global user exit points (GLUEs) to customize the processing that occurs for inbound and outbound web services in the pipeline.

Before you begin

You must understand the best practices for writing global user exit programs before customizing the pipeline. If you are customizing a service provider pipeline, you must be using the supplied DFHPITP or Axis2 application handler in your pipeline.

About this task

You can use the pipeline domain exits to access containers on a web services provider pipeline, a web services requester pipeline, or a web services requester pipeline that contains a security handler. The pipeline global user exits are described in detail in Pipeline domain exits.

Procedure

  1. Select which global user exit points to use:
    • Use XWSPRRWI, XWSPRROI, XWSPRROO, or XWSPRRWO GLUEs to access containers in a web services provider pipeline.
    • Use XWSRQRWO, XWSRQROO, XWSROROI, or XWSRQRWI GLUEs to access containers in a web services requester pipeline.
    • Use XWSSRRWO, XWSSRROO, XWSSRROI, or XWSSRRWI GLUEs to access containers in a secured web services requester pipeline.
  2. Use the DFH$PIEX sample exit program to write your own global user exit program.
    DFH$PIEX is in the SDFHSAMP library. You are recommended to make the program threadsafe.
  3. Enable the global user exit program.
  4. Test your global user exit program to ensure it works correctly.