WebSphere Commerce EnterpriseWebSphere Commerce Professional


A common customization scenario involves replacing the terminology used by the application with terminology that is more appropriate to the organization where the application is deployed. You might also want to replace application images with your own images. To ensure that this is possible, the IBM Sales Center application is designed to allow you to replace text and images that appear on the user interface.

By default, the English language IBM Sales Center resources are located in the com.ibm.commerce.telesales.resources plug-in in the resources directory in the file telesalesResources_en_US.properties. Alternative locale files are located in the com.ibm.commerce.telesales.resources.nl1 plug-in, in the resources directory.

If you are creating a custom resource bundle, you need to declare fully qualified packagename.properties in the plugin.xml. For example, for the following snippet, you should have an extendedTelesales.properties file in the MyNewExtensionsPlugin package. <extension point="com.ibm.commerce.telesales.resources.resources"> <resourceBundle baseName="MyNewExtensionsPlugin.extendedTelesales"/> </extension>

Not all modifiable and translatable text and images are in the telesalesResources file:

  • If you want to change the client branding, (banner images, and so on) this involves creating a plug-in that defines a new extension to the org.eclipse.core.runtime.products extension point, and a plugin_customization.ini file, and an about.ini file. For more information, see the WebSphere Everyplace Deployment Developer Guide.
  • To change system level text such as menu names and entries, view or application names, or preference page names (any text that appears in a plugin.xml or its companion plugin.properties) re-create the extension declaration in your own plug-in and then supply the text.
  • When adding a new translation, you can define a fragment that extends the plug-in containing the original properties file. The IBM Sales Center provides fragments with names containing nl1 that illustrate this. You can follow that pattern in these fragments to add fragments of your own, extending the same plug-ins.