Spell Checker in Management Center

You can customize the Spell check feature within the Management Center by adding in new words to the dictionary. Please note that with WCS - new dictionary cannot be created though.

To add words to the Management Center spell check dictionary, create <word> elements as children of the root <dictionary>  element of the file     LOBTools > WebContent > WEB-INF > dictionaries >addenda.xml using the below guidelines and restart the server.
      
SAMPLE:
        <word>sampleword1</word>
        <word>sampleword2</word>
        <word locale="de-DE" >sampleword3</word>
        <word locale="en-US" >sampleword4</word>
        <word locale="en-US,fr-FR" >sampleword5</word>
        <word locale="en-US,fr-FR,it-IT,">sampleword6</word>

Specify a comma separated list of locales in the locale attribute to indicate the languages for which each word is available.

If the locale attribute is not specified, the word will be available for all languages.

The following locales can be specified:
                  
  Language - Country/Region       Locale code
        Afrikaans - South Africa        af-ZA
        Arabic                          ar-XX
        Catalan                         ca-CT
        Czech - Czech Republic          cs-CZ
        Danish - Denmark                da-DK
        German - Switzerland            de-CH
        German (Germany)                de-DE
        Greek - Greece                  el-GR
        English - Australia             en-AU
        English - United Kingdom        en-GB
        English (US)                    en-US
        Spanish (Spain)                 es-ES
        French - Canada                 fr-CA
        French (France)                 fr-FR
        Italian (Italy)                 it-IT
        Norwegian (Bokmal) - Norway     nb-NO
        Dutch - The Netherlands         nl-NL
        Norwegian (Nynorsk) - Norway    nn-NO
        Polish (Poland)                 pl-PL
        Portuguese (Brazil)             pt-BR
        Portuguese - Portugal           pt-PT
        Russian (Russia)                ru-RU
        Swedish - Sweden                sv-SE

RESOLVED : Application Failed to Install. WC

WC application does not publish in WCS 7 toolkit and you see the below error -

com.ibm.websphere.management.exception.AdminException: A composition unit with name WC already exists. Select a different application name.

Dont worry .. the following steps will help you. I have tried it myself and it works :)

Problem(Abstract)

You are unable to publish an IBM WebSphere Commerce application to the integrated test server environment.

Symptom

The following error message is received when attempting to publish the WebSphere Commerce application in WebSphere Commerce Developer 7.0:
Application Failed to Install. WC


[10/6/10 16:31:39:541 EDT] 00000025 SystemErr R com.ibm.websphere.management.exception.AdminException: A composition unit with name WC already exists. Select a different application name.
[10/6/10 16:31:39:541 EDT] 00000025 SystemErr R at com.ibm.ws.management.application.task.
ValidateBLATask._validateBLAInstall(ValidateBLATask.java:344)
[10/6/10 16:31:39:541 EDT] 00000025 SystemErr R at com.ibm.ws.management.application.task.
ValidateBLATask._performTaskAsSystem(ValidateBLATask.java:128)
[10/6/10 16:31:39:541 EDT] 00000025 SystemErr R at com.ibm.ws.management.application.task.
ValidateBLATask$1.run(ValidateBLATask.java:100)
[10/6/10 16:31:39:541 EDT] 00000025 SystemErr R at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:4389)
[10/6/10 16:31:39:541 EDT] 00000025 SystemErr R at com.ibm.ws.security.auth.ContextManagerImpl.runAsSpecified(ContextManagerImpl.java:4547)
[10/6/10 16:31:39:541 EDT] 00000025 SystemErr R at com.ibm.ws.management.application.task.ValidateBLATask.performTask(ValidateBLATask.java:97)
[10/6/10 16:31:39:541 EDT] 00000025 SystemErr R at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:284)
[10/6/10 16:31:39:541 EDT] 00000025 SystemErr R at java.lang.Thread.run(Thread.java:735)

Cause

A previous failed application update has corrupted the applications configuration information.

 Resolving the problem

Perform the following steps to resolve this issue:

1. Stop the server

2. Backup and remove the following directories:
- WCDE_installdir/wasprofile/config/cells/localhost/cus
- WCDE_installdir/wasprofile/config/cells/localhost/blas
- WCDE_installdir/wasprofile/wstemp
- WCDE_installdir/wasprofile/temp
- WCDE_installdir/wasprofile/config/temp
3. Start the server

4. Publish the WebSphere Commerce application.

The above steps clears corrupted server configurations and allows for the publish action to run properly.

Important Note 

It is important that you keep a backup of the directories listed above since you may run into issues like few applications such as WAS Admin Console may not be accessible. If you face the same issue, please refer to the steps provided in my post - RESOLVED : Unable to access WAS Admin Console 

Alternatively , try just removing the module which is causing problem during publishing - WC