The Siebel connectivity DLL component of the Adapter for Siebel eBusiness
Applications returns an error in the following cases:
- Inability to connect to InterChange Server Express
- Inability to open log or trace files for writing
- Errors occurring when creating the WebSphere Business Integration Server
Express Plus system business object from input XML messages. This could
be the result of incorrect data formatting in the incoming XML data. In
the case of a data error in a request, the workflow does not stop processing
the batch request. To find the failed requests, the workflow log needs
to be looked at to find the failed requests. After fixing the errors,
the request must be sent again. This scenario can also occur if the
InterChange Server Express goes down while processing the request. The
user will have to look at the workflow log to check and see if a series of
requests have failed. Then, the user will have to verify that the
InterChange Server Express is up, and the failed requests will need to be
resent.
- Errors in executing the collaboration can be caused due to a wrong verb
setting, attribute values not having the correct formatting, or if the
external application or InterChange Server Express goes down. This
could also happen if the collaboration does not exist or is not up. The
user will have to ensure that the external application is up and the
InterChange Server Express is up prior to analyzing the cause of the
error. The user will have to look at the DLL log and trace files to
find the cause of the error, fix the error and send the request again.
- Unable to open log or trace files for writing.
- There are error scenarios in which the Siebel Connectivity DLL has no
control. For example, consider the scenario in which the WebSphere
Business Integration Server Express Plus system business object has been built
and sent to the collaboration for processing, the results have been returned
to the DLL and the Siebel application triggering the workflow is down.
In addition, the request has already been sent out and processed by the
external application. In this case, the user will have to check for the
requests processed prior to the application shut down. Also, the user
needs to verify that the request processing has succeeded in the external
application. If anything in the batch needs to be sent again, the same
needs to be handled on an individual request basis.
For all the above cases excluding the last one, the connectivity DLL
returns an error message in an XML message. The error message is
enclosed in the tags <Error> and </Error>. The generic
business adds the Siebel specific tags to the error message, then, converts it
to a property set by calling the XML converter service. All error
messages from the generic business service needs to be handled by the workflow
from which it was invoked.
The Siebel connectivity DLL logs the trace and error messages to the
SiebelConnectivityTrace.txt file created in the Siebel\Client\bin
folder.
