The following describes how a user-defined exception error (when using a business process) propagates through the system when returned by a service component.

(a) When fault processing does not transform the error information into a service message

The following figure shows how a user-defined exception error returned by a service component (when using a business process) propagates (without fault processing) through the system in the context of a custom reception.

Figure A-6 Method of error propagation (without fault processing) in a custom reception when a user-defined exception error is returned from a service component (when using a business process)

Exceptions that occur in the service component reach the custom reception framework unchanged as exceptions. The custom reception framework that catches the exception throws CSCMsgServerException unmodified to the reception process.

(b) When fault processing transforms the error information into a service message

The following figure shows how a user-defined exception error returned by a service component (when using a business process) propagates through the system (without fault processing) in the context of a custom reception.

Figure A-7 Method of error propagation (with fault processing) in a custom reception when a user-defined exception error is returned from a service component (when using a business process)

Exceptions that occur in the service component are forwarded as-is to the fault processing of the business process. The error information is then transformed into a response message by the fault processing of the business process, and then passed to subsequent processes in the form of a response message containing the error information. In this scenario, the response message is returned to the custom reception framework via HCSC message delivery control. The custom reception framework returns this response message to the reception process in the same way as a normal response message.

The following describes how an error other than a user-defined exception error propagates through the system when returned by a service component (when using a business process).

(a) When fault processing does not transform the error information into a service message

The following figure shows how an error other than a user-defined exception error returned by a service component propagates through the system (without fault processing) in the context of a custom reception (when using a business process).

Figure A-8 Method of error propagation (without fault processing) in a custom reception when an error other than a user-defined exception error is returned from a service component (when using a business process)

When an unexpected error occurs in a service component, the error reaches the custom reception framework as a RuntimeException error (system exception). The custom reception framework that catches the exception throws the caught RuntimeException unmodified to the reception process.

(b) When fault processing transforms the error information into a service message

The following figure shows how an error other than a user-defined exception error returned by a service component propagates through the system (with fault processing) in the context of a custom reception (when using a business process).

Figure A-9 Method of error propagation (with fault processing) in a custom reception when an error other than a user-defined exception error is returned from a service component (when using a business process)

Exceptions that occur in the service component are forwarded as-is to the fault processing of the business process. The error information is then transformed into a response message by the fault processing of the business process, and then passed to subsequent processes in the form of a response message containing the error information. In this scenario, the response message is returned to the custom reception framework via HCSC message delivery control. The custom reception framework returns this response message to the reception process in the same way as a normal response message.

The following describes how an error returned by the HCSC server propagates through the system (when using a business process).

The following figure shows how an error returned from the HCSC server propagates through the system in the context of a custom reception (when using a business process).

Figure A-10 Propagation of errors returned by HCSC server in a custom reception

The errors that might have occurred in the illustrated scenario are as follows:

• Error 1: Invalid request parameter
• Error 2: Location not found, service adapter is inactive
• Error 3: Data transformation failed
• Error 4: Invalid location, service component is inactive, communication error
• Error 5: Exception error in business process

If any of errors 1 to 5 in the figure is detected on the HCSC server, the custom reception framework throws the error information to the reception process as a CSCMsgServerException error.