(iSeries)

Configure application servers for other language environments

We can configure individual application servers to run with different globalization settings to support different language environments. The following topics discuss how we can configure the application server to run with the language environment attributes which you require, and how we can configure the application server to use a specific language.

We 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 Information Center.

• 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 WAS 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 based on CCSID 420 is not supported by WAS. The QEJB and QEJBSVR user profiles default to the system CCSID setting. If the QCCSID system value is set to 420, 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 WAS 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. Create the locale using the create locale command. We must have option 21 installed so that WAS 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 we can either modify the QEJBSVR profile and set the attributes specifically or we can create a new profile which has QJEBSVR as its group profile and which has the appropriate language environment settings. If we choose to create a new profile, we must also register it for use with WAS. See Run application servers under specific user profiles.

A second consideration is the language setting for the WAS 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 WAS runtime.

Multiple language settings can be configured at the same time. If the language version to use is the same as the primary language of the system, no additional configuration is needed. If the language version we want to use is a secondary language, perform the following steps to set the os400.websphere.nlv property.

Tasks

1. In the administrative console, click...

           Servers > Server Types > WebSphere application servers.

2. Click the name of the server for which you wish to change language version.

3. Click Java and process management > Process definition > Java virtual machine > Custom properties > New.

4. Specify os400.websphere.nlv in the Name field and the code number for the language feature we want to use to display messages in the Value field.

   For example, to specify the Japanese language, specify 2962 in the Value field. We can also specify a description for this property.

5. Click OK, and then click Save to save the changes.

When an application server has the os400.websphere.nlv property set, the corresponding QSYS29xx library is added to the beginning of the library list and iSeries messages sent by the application server to the joblog are used accordingly.

Running application servers under specific user profiles