You can create custom merchandising association
types or semantics, depending on your business needs. For example,
may create a custom merchandising association type called replacement.
After creating a custom merchandising association type or semantic,
you can add national language-translated versions of that type or
semantic. These national language-translated types or semantics display
in WebSphere Commerce Accelerator. If national language-translated
versions are not provided, the value in the database will display.
To
add national language-translated versions of your new merchandising
association type or semantic:
Procedure
- Find the identifier of the custom semantic or type inserted
in the database.
- Connect to the database
- Run one of the following SQL statements:
- For custom merchandising association types, run:
select
MASSOCTYPE_ID from MASSOCTYPE
.
- For custom merchandising association semantics, run:
select
MASSOC_ID from MASSOC
.
- Find your merchandising association type or semantic
identifier in the resulting list.
- Create a new properties file with the translated information
- Navigate to the WC_eardir/xml/tools directory.
- Create directories until you have the following directory
tree: WC_eardir/xml/tools/custom/properties.
- Create a new properties file, for example, myCustomMA_locale.properties,
using the locale for which you want to add translated text.
- Add the following information to the file:
# These are translated versions of custom merchandising association identifiers.
identifier_found_in_step_1=Translated_text
for example, if in step 1, you found the identifier
for your new type was DOWNSELL, add the following text to your properties
file:
DOWNSELL=translated_text_for_downsell
- Update the appropriate resources.xml file to include your
new properties file:
- Navgiate to WC_eardirxml/tools/catalog
- Open resources.xml in a text editor.
- Edit the file to include the new properties file. Between
<resourceBundle
name="MAssociationNLS">
and </resourceBundle>
,
add the following text: <bundle>com.ibm.commerce.tools.custom.properties.
yourCustomMA </bundle>
.
For example, if your properties file is called myCustomMA_fr_FR.properties
,
your resulting text will be similar to this:
<resourceBundle name="MAssociationNLS">
<bundle>com.ibm.commerce.tools.catalog.properties.MAssociationNLS</bundle>
<bundle>com.ibm.commerce.tools.catalog.properties.MAssociationIdentifiersNLS</bundle>
<bundle>com.ibm.commerce.tools.custom.properties.myCustomMA</bundle>
</resourceBundle>
- Restart
the WebSphere Commerce within the development environment.
- Test that the change displays as expected in the WebSphere
Commerce Accelerator. Remember to log in using the correct locale.
- If the changes are satisfactory, propagate these changes
to the production system:
- Update WebSphere Commerce with your new properties file.
For more information, see the topic Updating enterprise application files. Ensure that you follow
the instructions for updating a single file.
You will
need the following information:
- Update WebSphere Commerce with the updated resources.xml file
new properties file. For more information, see Updating enterprise application files. Ensure that you follow
the instructions for updating a single file.
You will
need the following information:
- Enterprise application name
- WCServer_enterprise_archive
- Relative path to file
- xml/tools/catalog/resources.xml
- Restart
WebSphere Commerce within the production environment.
Results
If you delete a custom merchandising association semantic or type,
you can remove these changes from your system.