Character Sets Across the Tiers of the PeopleSoft Architecture
PeopleSoft installations include multiple components, each of which must be able to handle differing character sets.
PeopleSoft application servers and clients (for example, the PeopleTools development environment and PeopleSoft Pure Internet Architecture pages) use Unicode exclusively and do not rely on other character sets to represent and process data. However, depending on your environment, not all system components support Unicode-encoded data. Therefore, you might not be able to run all parts of your system in Unicode. For example, some database platforms and third-party products do not support Unicode. The following table illustrates support for Unicode in the PeopleSoft system.
| Tier | Component | Unicode Support |
|---|---|---|
|
Client |
|
|
|
Web server |
Web server |
Yes |
|
Application server |
Application server |
Yes |
|
Database |
|
|
|
File attachment storage |
|
|
Examples of how to configure these tiers are provided in this topic.
See Understanding Character Set Selection.
In addition to the tiers listed in the previous table, PeopleTools enables you to configure these system components to use other character sets:
-
COBOL.
The character set that is used for PeopleSoft COBOL processing must match the character set of the database. If you created a Unicode database for the PeopleSoft implementation, you must also run COBOL in Unicode.
-
Direct file I/O operations.
All direct file I/O operations in PeopleTools, including file layout objects, trace and log files, and file operations from Structured Query Report (SQR) programs can be performed in Unicode or any supported non-Unicode character set. This is useful in situations in which you must interface with an external system that does not support Unicode.
Some applications refer to the ANSI encoding that inherits the encoding of the OS. For example, applications running on Windows OS inherits the active codepage. Application running on Unix OS inherits the encoding portion of the shell locale.
-
Third-party products that are non-Unicode compliant.
Some third-party products that are supported by PeopleTools do not yet support Unicode. In this case, PeopleTools converts application data to a specific, non-Unicode character set before communicating with these tools. Check the product documentation for your third-party application regarding Unicode compliance before determining how the application and the PeopleSoft system will interoperate.
When Unicode is not used for any of these types of operations or data storage, the PeopleSoft system transparently handles the conversion from Unicode to a non-Unicode character set. The non-Unicode character set that is used depends on several settings, which are discussed in detail later in this topic.
PSCHARSETS Table
The character sets that the PeopleSoft system supports are defined in the PSCHARSETS table. The following table lists these character sets and the names by which they may be referred to in PeopleSoft applications. You may need to know the correct character set name to use in several situations including:
-
In PeopleCode programs for manipulating file layout objects.
-
In the Unix/Linux application server configuration to determine the default, non-Unicode character set for log files, trace files, and operating system interfaces.
-
When creating your database.
Refer to your hardware and software requirements guide for details about the character sets that are supported for your database platform.
| PSCHARSETS Character Set Name | Description and Comments | Character Set Type |
|---|---|---|
|
ANSI |
Current ANSI-based code page. Not really a character set, but causes the system to use the default non-Unicode character set of the host operating system. |
SBCS or DBCS, depending on the host operating system. |
|
ASCII |
7–bit US-ASCII |
SBCS |
|
Big5 |
Big5 (Traditional Chinese) |
Nonshifting DBCS |
|
CCSID1027 |
IBM EBCDIC 1027 (Japanese-Latin) |
SBCS |
|
CCSID1047 |
IBM EBCDIC 1047 (Latin1) |
SBCS |
|
CCSID2901 |
IBM EBCDIC 290 (Katakana) |
SBCS |
|
CCSID3001 |
IBM EBCDIC 300 (Kanji) |
Nonshifting DBCS |
|
CCSID9302 |
IBM EBCDIC 930 (Kana-Kanji) |
Shifting DBCS |
|
CCSID9352 |
IBM EBCDIC 935 (Simplified Chinese) |
Shifting DBCS |
|
CCSID9372 |
IBM EBCDIC 937 (Traditional Chinese) |
Shifting DBCS |
|
CCSID9392 |
IBM EBCDIC 939 (Latin-Kanji) |
Shifting DBCS |
|
CCSID942 |
IBM EBCDIC 942 (Japanese PC) |
Nonshifting DBCS |
|
CP1026 |
Windows 1026 (EBCDIC) |
SBCS |
|
CP1250 |
Windows 1250 (Eastern Europe) |
SBCS |
|
CP1251 |
Windows 1251 (Cyrillic) |
SBCS |
|
CP1252 |
Windows 1252 (Western Europe) |
SBCS |
|
CP1253 |
Windows 1253 (Greek) |
SBCS |
|
CP1254 |
Windows 1254 (Turkish) |
SBCS |
|
CP1255 |
Windows 1255 (Hebrew) |
SBCS |
|
CP1256 |
Windows 1256 (Arabic) |
SBCS |
|
CP1257 |
Windows 1257 (Baltic) |
SBCS |
|
CP1258 |
Windows 1258 (Vietnamese) |
SBCS |
|
CP1361 |
Windows 1361 (Korean Johab) |
SBCS |
|
CP437 |
MS-DOS 437 (U.S.) |
SBCS |
|
CP500 |
Windows 500 (EBCDIC 500V1) |
SBCS |
|
CP708 |
Windows 708 (Arabic - ASMO708) |
SBCS |
|
CP720 |
Windows 720 (Arabic - ASMO) |
SBCS |
|
CP737 |
Windows 737 (Greek - 437G) |
SBCS |
|
CP775 |
Windows 775 (Baltic) |
SBCS |
|
CP850 |
MS-DOS 850 (Western Europe) |
SBCS |
|
CP852 |
MS-DOS 852 (Eastern Europe) |
SBCS |
|
CP855 |
MS-DOS 855 (IBM Cyrillic) |
SBCS |
|
CP857 |
MS-DOS 857 (IBM Turkish) |
SBCS |
|
CP860 |
MS-DOS 860 (IBM Portuguese) |
SBCS |
|
CP861 |
MS-DOS 861 (Icelandic) |
SBCS |
|
CP862 |
MS-DOS 862 (Hebrew) |
SBCS |
|
CP863 |
MS-DOS 863 (Canadian French) |
SBCS |
|
CP864 |
MS-DOS 864 (Arabic) |
SBCS |
|
CP865 |
MS-DOS 865 (Nordic) |
SBCS |
|
CP866 |
MS-DOS 866 (Russian) |
SBCS |
|
CP869 |
MS-DOS 869 (Modern Greek) |
SBCS |
|
CP870 |
Windows 870 |
SBCS |
|
CP874 |
Windows 874 (Thai) |
SBCS |
|
CP875 |
Windows 875 (EBCDIC) |
SBCS |
|
CP932 |
Windows 932 (Japanese) |
Nonshifting DBCS |
|
CP936 |
Windows 936 (Simplified Chinese) |
Nonshifting DBCS |
|
CP949 |
Windows 949 (Korean) |
Nonshifting DBCS |
|
CP950 |
Windows 950 (Traditional Chinese) |
Nonshifting DBCS |
|
EBCDIC |
IBM EBCDIC CCSID37 (USA) |
SBCS |
|
EUC-JP |
Extended UNIX code (Japanese) |
Nonshifting DBCS |
|
EUC-KR |
Extended UNIX code (Korean) |
Nonshifting DBCS |
|
EUC-TW |
Extended UNIX code (Taiwan) |
Nonshifting DBCS |
|
EUC-TW-1986 |
Extended UNIX code (TW-1986) |
Nonshifting DBCS |
|
GB12345 |
GB 2312 (Simplified Chinese) |
Nonshifting DBCS |
|
GB18030 |
GB18030 (Simplified Chinese) |
Nonshifting DBCS |
|
GB2312 |
GB 2312 (Simplified Chinese) |
Nonshifting DBCS |
|
HKSCS |
Hong Kong Supplementary Character Set |
Nonshifting DBCS |
|
ISO-2022-JP2, 3 |
ISO-2022-JP Japanese |
Shifting DBCS |
|
ISO-2022-KR2 |
ISO-2022-JP Korean |
Shifting DBCS |
|
ISO_8859-1 |
ISO 8859-1 (Latin1) |
SBCS |
|
ISO_8859-10 |
ISO 8859-10 (Latin6) |
SBCS |
|
ISO_8859-11 |
ISO 8859-11 (Thai) |
SBCS |
|
ISO_8859-14 |
ISO 8859-14 (Latin8) |
SBCS |
|
ISO_8859-15 |
ISO 8859-15 (Latin9/Latin0) |
SBCS |
|
ISO_8859-2 |
ISO 8859-2 (Latin2) |
SBCS |
|
ISO_8859-3 |
ISO 8859-3 (Latin3) |
SBCS |
|
ISO_8859-4 |
ISO 8859-4 (Latin4) |
SBCS |
|
ISO_8859-5 |
ISO 8859-5 (Cyrillic) |
SBCS |
|
ISO_8859-6 |
ISO 8859-6 (Arabic) |
SBCS |
|
ISO_8859-7 |
ISO 8859-7 (Greek) |
SBCS |
|
ISO_8859-8 |
ISO 8859-8 (Hebrew) |
SBCS |
|
ISO_8859-9 |
ISO 8859-9 (Latin5) |
SBCS |
|
JIS_X02011 |
Japanese Half-width Katakana |
Nonshifting DBCS |
|
JIS_X_0208 |
Japanese Kanji |
Nonshifting DBCS |
|
Java |
Java (Unicode encoding) |
Unicode |
|
Johab |
Johab (Korean) |
Nonshifting DBCS |
|
Shift_JIS |
Shift-JIS (Japanese) |
Nonshifting DBCS |
|
UCS2 |
Unicode UCS-2 |
Unicode |
|
UTF-8 |
Unicode UTF-8 |
Unicode |
|
UTF71 |
Unicode UTF-7. (An outdated Unicode 7-bit clean transformation that is sometimes used for email that must pass through gateways that do not support 8-bit characters.) |
Unicode |
|
UTF8 |
Unicode UTF-8 |
Unicode |
|
UTF8BOM |
Unicode UTF-8 with BOM (byte-order mark) |
Unicode |
1 Not commonly used.
2 In the PeopleSoft system, shifting DBCSs have limited usage, such as for file I/O, and are not supported for use as a database character set.
3 To use certain Windows-31J (also known as Microsoft CP932) characters in incoming or outgoing email messages, you must complete additional configuration of your web server (incoming email) and application server or PeopleSoft Process Scheduler (outgoing email).
See Selecting Email Character Sets.
This PeopleBook also contains information about supported character set encodings for globalization when using SQR for PeopleSoft.
See SQR for PeopleSoft-Supported Character Set Encodings.
See, Certifications tab on My Oracle Support.
Related Topics