PipeToPipeTransfer

The PipeToPipeTransfer component initializes and executes a remote pipeline to receive the Transport Dictionary from the current pipeline. Control then returns to the initial pipeline.

• υCalling Pipeline Object. Specifies the type of object that is to be passed to the remote pipeline.
  • υRoot Object. Specifies that the object that is to be transferred is a root object. This means that the object is either an order form (being transferred from an order processing pipeline) or a Transport Dictionary (being transferred from a Commerce Interchange Pipeline).
  • υChild Object. Specifies that the object being transferred is a child object. This means that the object is a Commerce Interchange Pipeline business data object, which is a child object of the Transport Dictionary.
• υReceiving Pipeline Object. Specifies the type of object that the receiving pipeline will create to store the received data.
  • υRoot Object. Specifies that the object is a root object; either an order form (for use in an order processing pipeline) or a Transport Dictionary (for use in a Commerce Interchange Pipeline).
  • υChild Object. Specifies that the object is a child object; a business data object, which is a child object of the Transport Dictionary (for use in a Commerce Interchange Pipeline).
  • υChild’s Parent Data Type. Specifies whether the data type of the parent object is a Dictionary or an OrderForm.
• υReceiving Pipeline Information. Specifies the pipeline configuration file and the type of pipeline object.
  • υPipeline Configuration Filename. Specifies the full path to the .pcf file used for initializing the receiving pipeline. To locate the .pcf file, click Browse.
  • υPipeline Type. Specifies the type of pipeline object used for the receiving pipeline.
  • υOrderPipeline. Specifies that the receiving pipeline is to be an OrderPipeline object, which is not registered under Microsoft® Transaction Server (MTS), and is generally used only for backward compatibility with sites created in Commerce Server 2.0.
  • υMtsPipeline. Specifies that the receiving pipeline is to be an MtsPipeline object, which is registered under MTS as transactions not supported. This pipeline is used in situations where transactions are not desired.
  • υMtsTxPipeline. Specifies that the receiving pipeline is to be an MtsTxPipeline object, which is registered under MTS as transactions required. This pipeline holds a transaction across all components in the pipeline configuration.

Example

Suppose that you want to pass an OrderForm from an OPP to a CIP, so that the Transport Dictionary that is passed through the CIP will have an Object name/value pair that references the OrderForm.

To do this, you would select Root Object as the Calling Pipeline Object (indicating that the entire OrderForm is to be transferred), Child Object as the Receiving Pipeline Object (indicating that the OrderForm will be the child of the object to which it is transferred. Next, you would type Object into the into the Child Object textbox, and select Dictionary as the Child’s Parent Data Type.

This combination of options results in the creation of a Dictionary with an Object name/value pair. This name/value pair references the OrderForm.