![[IBM i]](../images/ngibmi.svg)
Configuring application servers for other language environments
You can configure individual application servers to run with different globalization settings to support different language environments. The following topics discuss how you can configure the application server to run with the language environment attributes which you require, and how you can configure the application server to use a specific language.
About this task
You can configure the application server to run with the appropriate language environment attributes, such as the coded character set identifier (CCSID) and country or region identifier, for the environment you wish to create. The QEJBSVR user profile settings are the basis for the application server job attributes, and the job attributes determine the properties for the Java(TM) virtual machine environment. For more information on job attributes that are set based on the user profile, see the IBM® i documentation.
- The Japanese CCSID 5026 is not supported by WebSphere® Application Server. 5035 is the recommended CCSID for this environment. The QEJB and QEJBSVR user profiles default to the system CCSID setting. If the QCCSID system value is set to 5026, the CCSID attribute of the QEJB user profile must be changed. The QEJBSVR user profile, and any other user profiles used to run WebSphere Application Server instances, must also be changed. A QLOCALE value that is set to /QSYS.LIB/JA_JP_5026.LOCALE is not supported. However, a QLOCALE=/QSYS.LIB/JA_5035.LOCALE value or QLOCALE=*NONE value are the recommended choices for a Japanese system.
- An Arabic locale that is based on CCSID 420 is not supported by WebSphere Application Server. The QEJB and QEJBSVR user profiles default to the system CCSID setting. If the QCCSID system value is set to 420, you must change the CCSID attribute of the QEJB user profile. Also, you must change the QEJBSVR user profile and any other user profiles used to run WebSphere Application Server instances. A QLOCALE value that that is set to /QSYS.LIB/AR_AA.LOCALE is not supported because it is based on CCSID 420. However, either a QLOCALE value that is set to an Arabic CCSID 425-based locale or a QLOCALE=*NONE value are recommended for an Arabic system. You can create the locale by using the create locale command. You must have option 21 installed so that WebSphere Application Server can locate the locale source. The following command shows how to create the Arabic locale: CRTLOCALE LOCALE('qsys.lib/AR_AA_425.locale') SRCFILE('qsys.lib/qsyslocale.lib/qlocalesrc.file/ar_aa.mbr') CCSID(425) TEXT('my AR_AA locale in CCSID 425')
By default, each application server runs under the QEJBSVR user profile. To change the language enviroment settings you can either modify the QEJBSVR profile and set the attributes specifically or you can create a new profile which has QJEBSVR as its group profile and which has the appropriate language environment settings. If you choose to create a new profile, you must also register it for use with WebSphere Application Server. For more information, see Run application servers under specific user profiles.
A second consideration is the language setting for the WebSphere Application Server product. The language setting only causes the library list to be changed to include the appropriate QSYSxxxx library, where xxxx is the language feature for which you wish to display messages. The language setting does not affect the administrative console or any non-iSeries message logged by the WebSphere Application Server runtime.
Multiple language settings can be configured at the same time. If the language version that you want to use is the same as the primary language of the system, no additional configuration is needed. If the language version you want to use is a secondary language, perform the following steps to set the os400.websphere.nlv property.