WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  locale / language settings

    Posted Wed April 18, 2012 05:22 AM
    We have implemented our WebSphere Application Servers on HPUX/IA64 (migration to Linux/x86_64 planned). 

    HPUX-Server language/region settings are default (which should be en_us, configured on operating system level). 
    Due to our applications (not I18N), our WebSphere Application Servers need to run using de_DE.iso88591. At the moment, we configure this setting in .profile of our "was" user on HPUX (non-root - export LANG="de_DE.iso88591"), but this does not seem to be ideal as from time to time, we still have language problems with our WebSphere Application Servers.

    What are the best practices for configuring locale / language settings (de_DE.iso88591)?


  • 2.  locale / language settings

    Posted Wed April 18, 2012 05:42 AM
    Hi Christoph,

      What do you want to know? how to change language to WebSphere?

      I have do in several ways, putting in JVM process the locale


          -Duser.language=en -Duser.locale=US

      or changing file encoding

          -Dfile.encoding=de_DE.iso88591

     

      I don't change the .profile, I do at JVM process level

    regards,


  • 3.  locale / language settings

    Posted Wed April 18, 2012 06:11 AM
    [quote author=91692909 post=518739791]Hi Christoph,

      What do you want to know? how to change language to WebSphere?

      I have do in several ways, putting in JVM process the locale


          -Duser.language=en -Duser.locale=US

      or changing file encoding

          -Dfile.encoding=de_DE.iso88591

     

      I don't change the .profile, I do at JVM process level

    regards,[/quote]


    Thanks for your quick response, Gabriel.
    I will check these settings using a dummy applications to see if it will work for our applications.

    What I wanted to know is what the best practices are. Our solution (.profile configuration) was set a long time ago (when we were using JBoss with java1.4). I am just checking whether we should continue with our "old" solution or if we should change anything
     


  • 4.  locale / language settings

    Posted Wed April 18, 2012 06:38 AM
    Ok Christoph,

      A long time ago with WAS 6.0.2 in SuSe I took a similar approach changing and exporting  LANG_LD in the start script.

      Tell us your conclusions

    regards,


  • 5.  locale / language settings

    Posted Wed April 18, 2012 07:09 AM
    [quote author=91692909 post=518740399]Ok Christoph,

      A long time ago with WAS 6.0.2 in SuSe I took a similar approach changing and exporting  LANG_LD in the start script.

      Tell us your conclusions

    regards,[/quote]

    Will do so, but it will take some time (other projects are more important at this time, perhaps I will need to wait until we migrate to linux)


  • 6.  locale / language settings

    Posted Wed April 18, 2012 08:23 AM
    Ok Christoph,

    only FYI.

    DMGR with -Duser.language=en -Duser.locale=US
    ====================================

    [4/18/12 12:00:52:464 CEST] 0000002a MbuRmmAdapter I   DCSV1032I: DCS Stack DefaultCoreGroup at Member GABICell01\GABICellManager01\dmgr: Connected a defined member GABICell01\GABINode01\server1.
    [4/18/12 12:01:16:227 CEST] 0000002b RoleMergeLead I   DCSV8054I: DCS Stack DefaultCoreGroup at Member GABICell01\GABICellManager01\dmgr: View change in process.
    [4/18/12 12:01:16:304 CEST] 0000002a VSyncAlgo1    I   DCSV2004I: DCS Stack DefaultCoreGroup at Member GABICell01\GABICellManager01\dmgr: View synchronization completed successfully. The View Identifier is (6:0.GABICell01\GABICellManager01\dmgr). The internal details are None.



    Node Agent with nothing (machine locale spanish)
    ==================
    [18/04/12 12:00:04:612 CEST] 00000061 NodeSyncTask  A   ADMS0003I: La sincronización de la configuración ha finalizado satisfactoriamente.
    [18/04/12 12:00:47:677 CEST] 00000020 MbuRmmAdapter I   DCSV1032I: Pila DCS DefaultCoreGroup en miembro GABICell01\GABINode01\nodeagent: Se ha conectado un miembro definido GABICell01\GABINode01\server1.
    [18/04/12 12:01:04:612 CEST] 00000063 NodeSyncTask  A   ADMS0003I: La sincronización de la configuración ha finalizado satisfactoriamente.
    [18/04/12 12:01:16:318 CEST] 00000020 VSyncAlgo1    I   DCSV2004I: Pila DCS DefaultCoreGroup en miembro GABICell01\GABINode01\nodeagent: La sincronización de vistas se ha completado correctamente. El identificador de vista es (6:0.GABICell01\GABICellManager01\dmgr). Los detalles internos son None.
    [18/04/12 12:01:16:442 CEST] 00000025 CoordinatorIm I   HMGR0228I: El coordinador no es un coordinador activo para el grupo principal DefaultCoreGroup. El coordinado activo establecido es [GABICell01\GABICellManager01\dmgr].



    Server with -Duser.language=de -Duser.locale=DE  I guess is german
    ====================================
    [18.04.12 12:00:12:300 CEST] 0000000a ManagerAdmin  I   CWTRA0017I: Der Status des Start-Trace ist *=info.
    [18.04.12 12:00:13:206 CEST] 0000000a AdminInitiali A   CWWMN0015I: Der Administration Service wurde initialisiert.
    [18.04.12 12:00:14:400 CEST] 0000000a PluginConfigS I   CWPLC0057I: Der Plug-in-Konfigurationsservice wurde ordnungsgemäß gestartet.
    [18.04.12 12:00:14:507 CEST] 0000000a SSLComponentI I   CWPKI0001I: Der SSL-Service initialisiert die Konfiguration.

    It's on windows environment but I think that is the same in Linux ( I'm starting virtual machine with RHEL 6.2 , I tell you)

    best regards,


  • 7.  locale / language settings

    Posted Wed April 18, 2012 08:32 AM
    Thanks for your support! :-)
    The language is OK, so now I will only have to check the codepage settings 


  • 8.  locale / language settings

    Posted Wed April 18, 2012 08:55 AM
    You can see the codepage in the next file:

    \AppServer\properties\encoding.properties

    and to change for whatever purpose

    \AppServer\properties\converter.properties

    In my case "de" has the next codepage

    \AppServer\properties\encoding.properties

    de=ISO-8859-1


  • 9.  locale / language settings

    Posted Thu April 19, 2012 05:18 AM
    Then it should be enough to set these JVM Custom Properties.

    Thanks for your great support, Gabriel! :-)