Before creating or modifying an instance with Configuration Manager

Before creating or modifying an instance with Configuration Manager

+
Search Tips | Advanced Search

Before you start the Configuration Manager server or before you create or modify an instance with Configuration Manager:

Install any fixes mentioned in the README file.
Apply the most recent WebSphere Commerce Payments fix pack.
To use a 64-bit DB2 Universal Database for iSeries database as the WebSphere Commerce Payments database, complete the instructions in FORM='TEXTONLY'.
(i5/OS) Install the Remote WebSphere Commerce Management Utilities on a Windows PC.
Ensure that you meet the prerequisites for starting Configuration Manager.
Start the Configuration Manager. Refer to
(i5/OS)
Start the Configuration Manager
(Windows)
Start the Configuration Manager
(Solaris)
(AIX)
(Linux)
Start the Configuration Manager.

Important
You should only modify the following Web server properties, as well as any WebSphere Commerce-related properties, through the Configuration Manager GUI (and not through the Web server GUI nor the WAS Administrative Console):

SSL (enabling or disabling)
Web server instance name or port number
SSL port number
System IP address (Payments server host)
This will ensure that all configuration files, not just the Web server configuration files, are updated properly with the correct information.

Install the Configuration Manager client

(i5/OS)
Before you create or modify a WebSphere Commerce Payments instance with Configuration Manager, install the Remote WebSphere Commerce Management Utilities on a Windows PC.

Ensure that the Windows machine you will be using to install the Remote WebSphere Commerce Management Utilities code has 150 MB of free space available on the drive where you want to install the Remote WebSphere Commerce Management Utilities code.

Install the Configuration Manager client as follows:

Insert the WebSphere Commerce CD 1 into the CD-ROM drive on your remote Windows system.
The WebSphere Commerce Launch pad starts. Select the language for the launch pad and click OK to continue.
If the launch pad does not stop, start the launch pad by double clicking on the autorun.exe file under the root directory of the WebSphere Commerce CD 1.
The Install Product option of the launch pad is used for installation of Server, and Remote WebSphere Commerce Management Utilities on the remote Windows machine.
Once the WebSphere Commerce installer has started, minimize or close the launch pad.

Depending on your Windows system, the starting of the launch pad might take up to 3 minutes. Ensure you minimize all your windows sessions so that the initial window, for the language selection, is not missed.

If you do not want to install the Remote WebSphere Commerce Management Utilities using the launch pad, or if the launch pad does not start, then do the following steps:

Navigate to the CD-ROM drive into which the WebSphere Commerce CD 1 was inserted and double click on setup.exe to start the InstallShield Wizard.
Select the language for the installer and click OK to continue.
The Welcome screen is displayed. Click Next.
Read the license agreement. If you accept the terms of the agreement, select that you accept the terms and click Next.

The Installation prerequisite warning screen may display. Review the information on the screen. If a memory size warning is reported, click Next to continue.

Choose Custom Installation and click Next.

A warning message may display indicating that a previous version of WebSphere Commerce is installed. Click Yes to proceed with the installation. Click No to cancel.

Select Remote WebSphere Commerce Management Utilities and click Next.
You can choose to select the default destination path or select Browse for another destination path. A new directory can be specified, and the installation wizard will create that directory for you. Once you have selected your destination path, click Next to continue.
If you want to create a WebSphere Commerce response file based on your custom install options, select the Create a response file check box and specify a filename and location. Select Next.
Confirm your installation choices.
To start the installation, click Next.
To modify your choices, click Back.
After you click Next, the installation begins. The window displays the progression of the installation.
Insert the CDs as prompted and, if required, enter the location of the CDs.
On the Installation Complete panel, click Finish.
The installation is complete and the wizard closes.

The directory on the Windows PC where the Configuration Manager Client code is installed will be denoted by: WC_rmtMgt_installdir in the remaining sections of this Guide.

To verify that the Remote WebSphere Commerce Management Utilities are installed properly on your Windows machine, refer to the following log files:
WC_rmtMgt_installdir/logs/install.log
WC_rmtMgt_installdir/logs/wctrace_timestamp.log 
Configuration Manager prerequisites

(Solaris)(AIX)(Linux)(Windows) Before starting the WebSphere Commerce Configuration Manager, complete the following checklist to ensure that you meet all the prerequisites:

(Solaris)(AIX)(Linux) The systems on which you are starting the Configuration Manager server and the Configuration Manager client use a supported locale.
You have started your WebSphere Commerce database server.
(Solaris)(AIX)(Linux) The user ID you are logged on as has its umask set to 027.
Ensure that the DB2 Fenced user group is assigned to the DB2 user ID.
If you are using a remote Configuration Manager client, it must be at the same level as the Configuration Manager server.
Refer to Verify remote Configuration Manager client level.
(i5/OS) Before starting the WebSphere Commerce Configuration Manager, complete the following:
Ensure the DDM server is running on your iSeries system. To start this server issue the following OS/400 command:
STRTCPSVR SERVER(*DDM)
Ensure that you start the WebSphere Commerce Configuration Manager under a user profile that has the required CCSID for the language in which you want your instance created. Valid CCSIDs are listed in Create an OS/400 or i5/OS user profile.
Verify remote Configuration Manager client level

The Configuration Manager client and the Configuration Manager must be at the same level. If you have applied any WebSphere Commerce fix packs on the WebSphere Commerce node, apply the same fix pack level to the Configuration Manager client node.
To verify if the remote Configuration Manager client and the Configuration Manager server are at the same level:
On the Configuration Manager server node (WebSphere Commerce or WebSphere Commerce Payments node):
Open the following file in a text editor:
WC_installdir/properties/version/COMMERCE.product
Check the value in the <version> tags. For example,
<version>6.0.0.0</version>
Check the value in the <build-info> tag. For example,
<build-info date="12/05/06" level="120506dev"/>
Check the value in the <id> tag. For example,
<id>wc.server.express</id>
On the Configuration Manager client node:
(Solaris)(AIX)(Linux)(Windows) Open the following file in a text editor:
WC_installdir/properties/version/COMMERCE.product
(i5/OS) Open the following file in a text editor:
WC_rmtMgt_installdir/properties/version/COMMERCE.product
Check the value in the <version> tags. For example,
<version>6.0.0.0</version>
Check the value in the <build-info> tag. For example,
<build-info date="12/05/06" level="120506dev"/>
Check the value in the <id> tag. For example,
<id>wc.server.express</id>
If the values for both tags on both nodes match, the Configuration Manager client and server are at the same level.
Instance creation requirements using a remote Web server
If your Web server is remote from your WebSphere Commerce Payments server, complete the following steps on your Web server machine:
Create a directory on your Web server machine that is dedicated to your WebSphere Commerce Payments instance and a directory dedicated to the WAS profile for your WebSphere Commerce Payments instance. These directories must match the directories that you will create on your WebSphere Commerce machine. For example, the following directories should be created:
(Windows)
WAS_installdir\profiles\profile\config
\cells\cell\nodes\node\servers\web_servername
C:\Program Files\IBM\WebSphere\CommerceServer60\instances\instance
(Solaris)(Linux)(AIX)
WC_installdir/instances/instance
WAS_installdir/profiles/profile/config/cells/
cell/nodes/node/servers/web_servername
(i5/OS)
WC_userdir/instances/instance
WAS_userdir/profiles/profile/config/
cells/cell/nodes/node/servers/
web_servername
Your FTP and NFS users must have "write" permissions for this location.
(i5/OS)Instance creation requirements using a remote database for iSeries

If you are using a relational database other than *LOCAL, set up the database for remote access.
To configure your iSeries system to use a remote database:
Start the DDM TCP/IP server on the remote iSeries system using either of the following:
The Network option under your remote iSeries system in iSeries Navigator
The following OS/400 command:
STRTCPSVR SERVER(*DDM)
To check if the DDM server job is running on your iSeries, check for job QRWTLSTN in subsystem QSYSWRK.
On the iSeries system where WebSphere Commerce v6 is installed, use the WRKRDBDIRE command to ensure that there is an entry for the remote database where your instance's schema will be created.
On the iSeries system where WebSphere Commerce v6 is installed, run the following command on one line:
RUNJVA CLASS(com.ibm.db2.jdbc.app.DB2PackageCreator) 
PARM('database_name' 'user' 'password')
where the variables are defined as follows:

database_name

The name of the database where the instance's schema will be created. On this remote system, use the WRKRDBDIRE command and record the Relational Database value defined as *LOCAL.

user

A profile with authority to create new objects on the remote iSeries system.

password

The password associated with the user.

The command opens up a Java Shell Display. The following message should be displayed after the command has completed: Java program completed
Create a user profile on the remote iSeries system. The user profile must have the same name as the WebSphere Commerce instance name (instance) that you are creating. Configure the user profile so that it's language settings match the language you intend to choose as the default language for your WebSphere Commerce instance.
The password for this user profile must be the same as on the *LOCAL system (the machine where WebSphere Commerce is installed). This is the password that will be entered in the Instance Logon Password and Confirm Password fields on the Schema page while configuring the instance in the Configuration Manager.
For information in creating an iSeries user profile, refer to Create an OS/400 or i5/OS user profile.
Ensure that the instance user profile, you just created on the remote iSeries system, has authority to the *SQLPKG objects in library QGPL by running the following command on one line:
GRTOBJAUT OBJ(QGPL/*ALL) OBJTYPE(*SQLPKG) USER(instance) 
AUT(*CHANGE) 
During instance creation, IBM recommends that Use iSeries Toolbox driver is selected in the WebSphere panel.
Modifying your iSeries user profile

(i5/OS)
Use the DSPUSRPRF command to determine the Home Directory (HOMEDIR) of your *SECOFR user profile. Ensure that the HOMEDIR exists. If the HOMEDIR does not exist, create it using the OS/400 command: MKDIR.
Ensure that the user profile uses the localized settings for the language as listed below.

Localized settings for iSeries user profiles

Language CCSID LangID CountryID
English 37 ENU US
French 297 FRA FR
German 273 DEU DE
Italian 280 ITA IT
Spanish 284 ESP ES
Brazilian Portuguese 37 PTB BR
Japanese 5035 JPN JP
Korean 933 KOR KR
Traditional Chinese 937 CHT TW
Simplified Chinese 935 CHS CN

Using localized settings for an iSeries user profile other than those defined above might work, but has not been tested.
The HOMEDIR must contain a file named SystemDefault.properties, with a Coded character set ID of 819 and containing ASCII data. This file must specify the file.encoding property that matches your user profile. The file.encoding property must be specified on one line, must contain no spaces, and is case sensitive. If this file already exists, use the EDTF command to set the file.encoding property to one of the following values:
Japanese:
file.encoding=SJIS
Korean:
file.encoding=KSC5601
Simplified Chinese:
file.encoding=Cp1381
Traditional Chinese:
file.encoding=Cp950
All other languages:
file.encoding=ISO8859_1
If this file does not exist, copy it to your HOMEDIR using one of the commands below:

The HOMEDIR will be denoted as home_directory below.
Simplified Chinese:
COPY OBJ('/QIBM/ProdData/CommerceServer60/config/SystemDefault_CN.properties') 
 TOOBJ('home_directory/SystemDefault.properties')
 TOCCSID(819) 
Korean:
COPY OBJ('/QIBM/ProdData/CommerceServer60/config/SystemDefault_KR.properties') 
      TOOBJ('home_directory/SystemDefault.properties')
      TOCCSID(819)
Traditional Chinese:
COPY OBJ('/QIBM/ProdData/CommerceServer60/config/SystemDefault_TW.properties') 
     TOOBJ('home_directory/SystemDefault.properties')
     TOCCSID(819)
Japanese:
COPY OBJ('/QIBM/ProdData/CommerceServer60/config/SystemDefault_JP.properties') 
     TOOBJ('home_directory/SystemDefault.properties')
     TOCCSID(819)
All other languages:
 COPY OBJ('/QIBM/ProdData/CommerceServer60/config/SystemDefault.properties')
      TOOBJ('home_directory/SystemDefault.properties')
      TOCCSID(819)
Once the new file is created, ensure that it contains the proper ASCII data.

Start the Configuration Manager

(i5/OS)
To start the WebSphere Commerce Configuration Manager on iSeries:
Start the Configuration Manager server by doing the following:
Log on to the iSeries machine ensuring that the profile has a *SECOFR user class, and is set up with the language specific settings of either English, or the language that you will choose as the default language for your instance.
Start a QShell session by entering the following command:
STRQSH
and do the following in the QShell session:
Navigate to the WebSphere Commerce Server bin directory by issuing the following command:
cd WC_installdir/bin
Start the Configuration Manager server program by issuing the following command:
config_server.sh [-port server_port_number]
The port server_port_number parameter is optional. If you do not specify this parameter, the default port of 1099 is used. The Configuration Manager server will listen using this port number. If you specify the server_port_number, the value must be between 1024 and 65535 and not currently in use on the iSeries system.
If you are using a system where your primary language is not the same as the language in which you are creating your instance, then add the QSYSlanguage_feature_number library into your user profile's library list. Otherwise the profile will try to locate it under QSYS. To add the language feature library, use the EDTLIBL command.
If this is the first time that Configuration Manager is run on the system, you will see the following messages:
 +----------------------------------------------------------------------------------------------------+
 |Attaching Java program to /QIBM/ProdData/CommerceServer60/lib/ConfigManager.jar. 
                    |
 |Attaching Java program to /QIBM/ProdData/CommerceServer60/lib/Utilities.jar.                        |
 |Attaching Java program to /QIBM/ProdData/CommerceServer60/lib/Enablement-                           |
 |BaseComponentsLogic.jar.                                                                            |
 |Attaching Java program to /QIBM/ProdData/CommerceServer60/lib/jtopen.jar.                           |
 +----------------------------------------------------------------------------------------------------+
When the following messages are posted:
 Registry created.
 CMServer bound in registry.
proceed to the next step.
Start the Configuration Manager client on the Windows machine where the Configuration Manager client code was installed.
Use a command prompt on the Configuration Manager client machine, change to the WC_rmtMgt_installdir/bin directory.
Start the Configuration Manager client by running the following command:
configClient.bat -hostname iSeries_Host_name [-port server_port_number]
where

iSeries_Host_name

Is the fully qualified host name of the server.
The fully qualified host name of the server must exactly match the host name (HOSTNAME) and the domain name (DMNNAME) values displayed when viewing the CFGTCP command, option 12, on the system where the Configuration Manager server is running. This parameter is case-sensitive.

server_port_number

Is the port number on the iSeries server on which the Configuration Manager is listening. You only need to specify this value if the server is listening on a non-default port. The port parameter is optional, but if it was specified in the config_server.sh command, it needs to be specified here.
Log in to Configuration Manager. The initial ID is configadmin and the initial password is defined during the installation process.
Continue with the instructions in Create a WebSphere Commerce Payments instance.
Stopping the Configuration Manager

To end Configuration Manager:

In the Configuration Manager GUI, click on Console and Exit.
Click OK when the message 'For Security reasons, the Config Manager Server will now be stopped.' is posted.
Exit from the DOS window where the Configuration Manager client was started.
Exit from the QSHELL session, on your iSeries system, where the Configuration Manager server was started.

Start the Configuration Manager

(Windows) To start WebSphere Commerce Configuration Manager on Windows:
Ensure that the Configuration Manager server is running by opening the Windows Services panel and checking that the IBM WC 6.0 Configuration Manager service has a status of Started.
Open the Windows Services panel as follows, depending on the version of Windows you are using:

(2000) Select Start > Settings > Control Panel > Administrative Tools > Services
(2003) Select Start > Settings > Administrative Tools > Services
If the IBM WebSphereCommerce 6.0 Configuration Manager service has a status of Stopped, right-click the service name and select Start from the pop-up menu.

Important
Leaving the IBM WC 6.0 Configuration Manager service running could potentially pose a security problem. Stop the IBM WC 6.0 Configuration Manager service when you are not using the Configuration Manager.
To prevent potential security problems, you should also ensure that the IBM WC 6.0 Configuration Manager service is set for manual startup, not automatic.

When you start the Configuration Manager server as a service, it listens on port 1099 for a connection. To have the Configuration Manager server listen on a different port:
Ensure that the IBM WC 6.0 Configuration Manager service is stopped.
Start a command prompt session and issue the following command:
WC_installdir/bin/config_server -port port_number
where port_number is the port on which the Configuration Manager server will listen for a connection.
Closing the command prompt session will shut down the Configuration Manager server.
Do one of the following sets of steps, depending on whether you are using a local or remote WebSphere Commerce Configuration Manager client:

For a local WebSphere Commerce Configuration Manager client:

(2000) Select Start > Programs > IBM WebSphere > Commerce Server v6.0 > ConfigurationManager
(2003) Select Start > All Programs > IBM WebSphere > Commerce Server v6.0 > ConfigurationManager
For a remote WebSphere Commerce Configuration Manager client:

On the Configuration Manager client machine, enter the following command from a command prompt session:
WC_installdir/bin/configClient -hostname cm_hostname [-port cm_port]

where the variables are defined as follows:

cm_hostname

The host name of the Configuration Manager server machine.
To obtain the host name of the Configuration Manager server machine, issue the hostname command from a command prompt session on the Configuration Manager server machine.

cm_port

The port specified when starting the Configuration Manager server.
The -port parameter is optional. If you do not specify the -port parameter, the Configuration Manager client attempts to connect to the Configuration Manager server using port 1099.

Log in to Configuration Manager. The initial ID is configadmin and the initial password is defined during the installation process.
Continue with the instructions in Create a WebSphere Commerce Payments instance.
Start the Configuration Manager

(Solaris)(AIX)(Linux)
To start WebSphere Commerce Configuration Manager:
Log in as the WebSphere Commerce non-root user ID. This ID was created before installing WebSphere Commerce.
Depending on the instance you are creating or modifying, start the server by doing the following on the WebSphere Commerce node:
Open a terminal window.
Ensure that you have exported your display and that you have access to your X server. Refer to your operating system documentation for more information.
Issue the following commands:
cd WC_installdir/bin
./config_server.sh
Notes:
Do not close the terminal window you entered the config_server command in or the Configuration Manager server will stop.
Do not run the Configuration Manager server as a background process - this is a potential security risk.
The Configuration Manager server is now listening on port 1099 for a connection. To have the Configuration Manager server listen on a different port, issue the following command instead of the ./config_server.sh command:
./config_server.sh -port port_number
where port_number is the port on which the Configuration Manager server will listen for a connection.
Once the following messages are displayed, proceed to the next step:
Registry created
CMServer bound in registry
Do one of the following sets of steps, depending on whether you are using a local or remote WebSphere Commerce Configuration Manager client:
For a local WebSphere Commerce Configuration Manager client:
Open another terminal window.
Ensure that you have exported your display and that you have access to your X server. Refer to your operating system documentation for more information.
As the non-root user ID created before installing WebSphere Commerce, issue the following commands:
cd WC_installdir/bin
./config_client.sh [-port cm_port]
Do not use configClient.sh to connect to a local Configuration Manager server.The variables are defined as follows:

cm_port

The port specified when starting the Configuration Manager server.
The -port parameter is optional. If you do not specify the -port parameter, the Configuration Manager client attempts to connect to the Configuration Manager server using port 1099.
For a remote WebSphere Commerce Configuration Manager client:
Log on to the remote machine as the non-root user ID created before installing WebSphere Commerce.
Open a terminal window.
Ensure that you have exported your display and that you have access to your X server. Refer to your operating system documentation for more information.
Issue the following commands:
cd WC_installdir/bin
./configClient.sh -hostname cm_hostname [-port cm_port]
Do not use config_client.sh when connecting to a remote Configuration Manager server.
The variables are defined as follows:

cm_hostname

The short host name of the Configuration Manager server machine.
To obtain the short host name of the Configuration Manager server machine, issue the hostname command from a command line on the Configuration Manager server machine

cm_port

The port specified when starting the Configuration Manager server.
The -port parameter is optional. If you do not specify the -port parameter, the Configuration Manager client attempts to connect to the Configuration Manager server using port 1099.
Log in to Configuration Manager. The initial ID is configadmin and the password is set during the installation of the product.
Continue with the instructions in Create a WebSphere Commerce Payments instance.
Reviewing the README file
Reviewing the README file is an important prerequisite for installing WebSphere Commerce. The README file contains information about last-minute changes to the product. Last-minute changes can include additional fixes that must be installed before using WebSphere Commerce.
Failure to install any last minute fixes listed in the README file will result in WebSphere Commerce not functioning correctly.
The README file can be found in the readme directory of WebSphere Commerce CD 1. The README file name is:
readme_language_code.htm
where language_code is one of the following values:

Language Language code
German de_DE
English en_US
Spanish es_ES
French fr_FR
Italian it_IT
Japanese ja_JP
Korean ko_KR
Brazilian Portuguese pt_BR
Simplified Chinese zh_CN
Traditional Chinese zh_TW

Install the most recent WebSphere Commerce Payments fix pack

After installing WebSphere Commerce, you should install the most recent WebSphere Commerce fix pack available if one exists.
WebSphere Commerce fix packs are cumulative, so the most recent fix pack for a version of WebSphere Commerce will contain all of the fixes and updates found in previous fix packs for that version.
Fix packs and the instructions for installing the fix packs are available from the WebSphere Commerce support Web site at the following URL:

http://www.ibm.com/software/webservers/commerce/support/

From this Web site, select the edition of WebSphere Commerce you are using to get to the correct support Web site for your edition and click the link for the newest fix pack for your version of WebSphere Commerce under the Self Help > Download section of this Web page.

Important
If you also use WebSphere Commerce Developer, ensure that WebSphere Commerce Developer and WebSphere Commerce are at the same fix pack level. If you apply a WebSphere Commerce fix pack to WebSphere Commerce, apply the WebSphere Commerce Developer fix pack of the same level to WebSphere Commerce Developer. For example, if you apply WebSphere Commerce fix pack 6.0.0.1 to WebSphere Commerce, apply WebSphere Commerce Developer fix pack 6.0.0.1 to WebSphere Commerce Developer.

Create an OS/400 or i5/OS user profile

(i5/OS)
To create an OS/400 or i5/OS user profile, you can either use the OS/400 or i5/OS command line or use iSeries Access.
To create an OS/400 or i5/OS user profile using the OS/400 or i5/OS command line:

Enter CRTUSRPRF.
Press F4 for a prompt.
Complete the necessary parameters, and then press Enter to create the user profile.
Ensure that USRCLS is set to *SECOFR and SPCAUT is set to *USRCLS for this profile.
The iSeries user profile should be created with the following localized settings:

Localized settings for iSeries user profiles

Language CCSID LangID CountryID
English 37 ENU US
French 297 FRA FR
German 273 DEU DE
Italian 280 ITA IT
Spanish 284 ESP ES
Brazilian Portuguese 37 PTB BR
Japanese 5035 JPN JP
Korean 933 KOR KR
Traditional Chinese 937 CHT TW
Simplified Chinese 935 CHS CN

Using localized settings for an iSeries user profile other than those defined above might work, but has not been tested.
After the iSeries user profile has been created, use the DSPUSRPRF command to determine the Home Directory (HOMEDIR). Ensure that the HOMEDIR exists on your iSeries system. If the HOMEDIR does not exist, create it using the OS/400 or i5/OS command: MKDIR. (The HOMEDIR will be denoted as home_directory below.)
The HOMEDIR must contain a file named SystemDefault.properties, with a coded character set ID of 819 and containing ASCII data. This file must specify the file.encoding property that matches your iSeries user profile. The file.encoding property must be specified on one line, must contain no spaces, and is case sensitive. The file.encoding property can be one of the following values:
Simplified Chinese:
file.encoding=Cp1381
Korean:
file.encoding=KSC5601
Traditional Chinese:
file.encoding=Cp950
Japanese:
file.encoding=SJIS
All other languages:
file.encoding=ISO8859_1
To create the
SystemDefault.properties
file do the following:
On a PC, using a text editor, create a file named
 SYSDFT.FILE
In this file, enter the appropriate
file.encoding
line for you language (as shown above). For example:
file.encoding=ISO8859_1
Save this file and copy it to your iSeries system in the /QIBM directory.
From an OS/400 command line, enter the following:
COPY OBJ('/QIBM/SYSDFT.FILE')
      TOOBJ('/home_directory/SystemDefault.properties')
      TOCCSID(819) 
where home_directory is your
HOMEDIR
Once the new file is created, ensure that it contains the proper ASCII data.
Related tasks

Opening the Configuration Manager
Create a WebSphere Commerce Payments instance
Modifying a WebSphere Commerce Payments instance

Related concepts

Configuration Manager
WebSphere Commerce configuration file

Language	CCSID	LangID	CountryID
English	37	ENU	US
French	297	FRA	FR
German	273	DEU	DE
Italian	280	ITA	IT
Spanish	284	ESP	ES
Brazilian Portuguese	37	PTB	BR
Japanese	5035	JPN	JP
Korean	933	KOR	KR
Traditional Chinese	937	CHT	TW
Simplified Chinese	935	CHS	CN

Language	Language code
German	de_DE
English	en_US
Spanish	es_ES
French	fr_FR
Italian	it_IT
Japanese	ja_JP
Korean	ko_KR
Brazilian Portuguese	pt_BR
Simplified Chinese	zh_CN
Traditional Chinese	zh_TW