IPipeline::SetLogFile Method [pooled transacted]
Use this method to identify the file in which to log the operations of the pipeline component.
Note
This method is for use by developers who want to analyze pipeline configuration file information. Logging should never be enabled in a production environment: it degrades performance and could compromise the security of credit card numbers in non-set transactions. File systems must be configured to allow the process running the pipeline to have write access to the specified path.
HRESULT IPipeline::SetLogFile(
BSTR pszFileName
);
Sub SetLogFile(
pszFileName As String
)
Parameters
pszFileName
[C++][in] A BSTR containing the name of the file in which to log events.
[Visual Basic]
A String containing the name of the file in which to log events.
Return Value
[C++]
This method returns an HRESULT indicating whether it completed successfully. See the Error Values section for more details.
[Visual Basic]
None.
Error Values
[C++]
This method returns S_OK (0x00000000) to indicate success and standard COM HRESULT error values to indicate failure. For more information about standard COM errors, see Standard COM Errors. Additional information may be available using the global Err object, which can be accessed using the API function GetErrorInfo. In particular, the GetDescription method of the IErrorInfo interface may return a text description of the error.
[Visual Basic]
This method sets the Number property of the global Err object to S_OK (&H00000000) to indicate success and to standard COM error values to indicate failure. For more information about standard COM errors, see Standard COM Errors. Additional information may be available using the global Err object. In particular, the Description property may contain a text description of the error.
Remarks
When logging is set, the pipeline logs the pipeline components that are called and the error values each component returns. The pipeline also logs all Dictionary and SimpleList object read and write operations.
The SetLogFile method should be called immediately before executing a pipeline.
Calling this method with an empty string turns off logging.
Example
' pPooledTxPipeline is a PooledTxPipeline object.
errVal = pPooledTxPipeline.SetLogFile("CustomShipping.log")