Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Developing
The topics in the Developing section describe tasks performed by an application developer.
Controller layer
The Controller layer is the conductor of operations for a request. It controls the transaction scope and manages the session related information for the request. The controller first dispatches to a command and then calls the appropriate view processing logic to render the response.
Integrating with back-end systems and external applications
External systems integration is a key feature of the WebSphere Commerce solution. In WebSphere Commerce business logic is enabled for integration and built-in adapters and interfaces are provided for common integration points. Additionally, the WebSphere Commerce integration solution leverages integration standards by using various IBM connectivity solutions.
Inbound services
WebSphere Commerce provides inbound web services to retrieve information for WebSphere Commerce business operations. You can use the code and documentation that is provided with WebSphere Commerce to enable inbound web services to integrate backend systems and external system with WebSphere Commerce operations.
Generic application and system error XML messages
In WebSphere Commerce, generic application and system errors can occur. XML messages are generated if a command, invoked by an inbound message through WebSphere MQ, encounters a generic application or a generic system exception.

Generic application and system error XML messages

In WebSphere Commerce, generic application and system errors can occur. XML messages are generated if a command, invoked by an inbound message through WebSphere MQ, encounters a generic application or a generic system exception.

A generic application error message is sent to the outbound queue if the error is related to the user. When a user enters an invalid parameter in an XML message, an ECApplicationException is thrown. The message is then sent to the outbound queue and the exception is documented in a log file.

Note: When an exception of this type is thrown, the Web controller will not retry the command, even if it is specified as a command that could be retried.

A generic system error message is sent to the outbound queue if a runtime exception or a WebSphere Commerce configuration error is detected, such as null-pointer exceptions and transaction rollback exceptions.

The contents of generic XML messages vary depending on the contents of inbound XML messages however, the format is similar to the following:


<?xml version="1.0" encoding="UTF-8"?>
<WCS_Error type="GenericApplicationError"> (or <WCS_Error type="GenericSystemError">)
<RequestAttributes> 
...(Error parameters and data of inbound XML message)
<excMsg>(Error message key, e.g. _ERR_REMOTE_EXCEPTION)</excMsg> 
... 
</RequestAttributes> 
</WCS_Error>