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.
Customizing WebSphere Commerce
You can extend the WebSphere Commerce product to fit your business needs. This topic describes the prerequisite skills and required knowledge that you need to customize business logic. After you have the required knowledge, use WebSphere Commerce Developer to take tutorials that guide you step-by-step through various customization scenarios.
Supporting globalization
The WebSphere Commerce architecture is designed to support globalization. Globalization is the proper design and execution of systems, software, services, and procedures so that one instance of software, running on a single server or end-user machine, can process multilingual data and present culturally correct data in a multicultural environment such as the Internet.
Globalization in the messaging system
The WebSphere Commerce messaging system gives WebSphere Commerce the ability to communicate with its external environment (back-end and external systems), as well as send notification to customers and administrators that events have occurred within WebSphere Commerce. This is accomplished through two subsystems: an inbound system that manages inbound messages coming from back-end and external systems, and an outbound messaging system that allows you to send notification to users (such as sending e-mail messages notifying a customer about a password reset).

Globalization in the messaging system

The WebSphere Commerce messaging system gives WebSphere Commerce the ability to communicate with its external environment (back-end and external systems), as well as send notification to customers and administrators that events have occurred within WebSphere Commerce. This is accomplished through two subsystems: an inbound system that manages inbound messages coming from back-end and external systems, and an outbound messaging system that allows you to send notification to users (such as sending e-mail messages notifying a customer about a password reset).

The character encoding used for MIME messaging is usually different from that used by browsers. For example, the de-facto character encoding for MIME messaging in Japan is iso-2022-jp, while the most commonly used character encoding in all other applications is Shift_JIS. As a result, a unique field is added to the WebSphere Commerce schema to enable the messaging system for multilingual support. This field is the MIMECHARSET column in the LANGUAGE table.