Copyright © TIBCO Software Inc. All Rights Reserved

> Troubleshooting the Services Plug-in
> ORIG_FILE_NAME and ORIG_FILE_PATH are not populated when using outbound File poller to send files from private processes
> When using outbound File poller to send files from private processes, the file slots ORIG_FILE_NAME and ORIG_FILE_PATH may not be populated. The ORIG_FILE_NAME and ORIG_FILE_PATH properties are populated by the protocol to indicate the original source of data, if any. When you use outbound File poller in EZComm, these properties are not set but the location of the source file is set on the OUTPUT_SOURCE_DIR and SRC_FILE_NAME properties instead.
> Outbound transactions for HTTP are not entered in the non-repudiation log
> Non-repudiation logs, in general, are used for signed messages to avoid disputes between trading partners. When using HTTP with the the Services Plug-in, there are two types of signed messages that can be exchanged:

> • | Inbound signed messages These messages are posted to the non-repudiation log. Since the trading partner already signed such message and the signature can be verified, there can be no dispute that the message came from this specific trading partner.

> • | Outbound signed messages When a signed message is sent using HTTP outbound, there is no ability to request a receipt. The trading partner’s HTTP server can officially acknowledge that the message was received, but it cannot verify the signature on the message. The acknowledgement from the HTTP server about the message arrival is not the same as the acknowledgement from the trading partner who actually received and processed the message.

> Therefore, if TIBCO BusinessConnect would post such outbound signed message into the non-repudiation log, the other trading partner could still dispute that they received the message. For that reason, HTTP transport in the the Services Plug-in does not enter outbound signed messages in the non-repudiation log.
> When I import the whole configuration, the operation is not imported
> When an operation in a .csx file already exists in the BusinessConnect system, upon importing the .csx file this operation is not imported.
> For example, if you try to import the operation BC/version/operation, which exists by default, you need to rename the existing BC/version/operation (such as BC/6.0/operation1) in order to import a new operation with the same name. The exception is the default operation BC/1.0/Notify, which cannot be renamed or deleted: this operation has to be updated manually.

Copyright © TIBCO Software Inc. All Rights Reserved