MicroPipe Object
.gif "Ee799248.c++_off(en-US,CS.10).gif")
.gif "Ee799248.vb_on(en-US,CS.10).gif")
Use this object to run a single pipeline component from an Active Server Page (ASP) file without using a pipeline configuration file (.pcf).
| ProgID: | Commerce.MicroPipe (Externally creatable) |
| COM Class Name: | CMicroPipeline |
| COM Interface Name: | IMicroPipeline |
| Interface ID Constant: | None |
| Header File: | None |
| Type Library Name: | Microsoft Commerce 2000 MicroPipe Type Library |
| DLL Name: | micropipe.dll |
| Threading Model: | Both |
In C++, use the IMicroPipeline interface to access the properties and methods of the MicroPipe object.
Because this object is primarily intended for use within ASP script, access from C++ will not be common.
The methods of the MicroPipe object are shown in the following table.
| Method | Description |
| Execute | Runs the component indicated in the SetComponent method. |
| SetComponent | Indicates the pipeline component to load and execute. |
| SetLogFile | Identifies the file in which to log pipeline events. |
Remarks
The MicroPipe object does not explicitly use Microsoft Transaction Server (MTS). To use transactions, mark the page as transacted or use the standard MtsTxPipline object. Distributed transactions have no meaning in the MicroPipe object because the object contains a single component.
Many pipeline components use configuration information in addition to the Context and Order dictionaries. Two common ways of passing this information to the component are:
To create a dictionary and pass the dictionary to the component.
To set individual or multiple properties directly.
The first method applies only to pipeline components that implement the IPipelineComponentAdmin interface. The second is common for components written in Microsoft Visual Basic, which usually do not implement the IPipelineComponentAdmin interface.