Resolution:
Description:

= = = = = =

1). If referring to a schema in the “Error Schemas” tab of an activity, say, “End” activity, the content of the “Error Output” tab is empty.

2). We can get the content of the “Error output” tab, but how to make the information sent to a SOAP client if creating a service agent from a process?

Environment:

= = = = = = 

TIBCO BusinessWorks - All.

Symptoms:

= = = = = 

For the send problem, without getting the “Error Output” content, the SOAP client receives an "Internal Server Error" instead.

Resolution:

= = = = = 

The design is not correct.

1). If using a custom error schema in the End Activity of a process, the "Error Output" tab of the End activity is expected to be blank. Only when the above process is called from another main process, the actual error schema structure gets loaded to the "Error Output" of the "Call Process" activity in the main process. A project named “TestErrorOutputBlank” is attached.

2). If you want the custom error message generated by the Webservice to be propagated to the SOAP client, design the service a differently from the project “TestErrorOutputBlank”.

Remove the "Catch" and "Generate Error" activity from the service subprocess (Concat process) and include them in the actual service process, the Main Process which is calling the Concat process. The custom error from this process will then propagate to the SOAP Client calling the Webservice.

Steps:
1). Remove the "Catch" and "Generate Error" activity from the Concat Process.
2). Create a webservice from the Concat process. Add the "Catch" and "Generate Error" activity in the wsConcat process for the webservice, which is calling the actual Concat process.
3). Call the WebService using a simple SOAP client using SOAP RR activity. When the SOAP RR activity fails, it will receive the custom error message thrown by the Webservice.

The “Error Output” tab is blank after referring to a schema in the “Error Schemas” tab.