Attachments with non-ASCII File Names

To successfully upload an attachment with a file name containing non-ASCII characters (such as Japanese), Oracle recommends running the application server with the locale that supports those specific non-ASCII characters—for example, ja_JP.sjis. If the storage location for the attachment is an FTP site or an HTTP repository, Oracle recommends that the storage location also be running in an environment that supports the same language or locale as the file names used. The web server (which serves as an intermediary in the transfer of the file from the browser to the application server and then on to the storage location) can be running either a multi-language environment (for example, UTF-8) or a non-ASCII character language environment.

The uploading of a file attachment involves multiple tiers—for example, the browser on the client, the web server, the application server, the database server, and ultimately the file attachment storage location. To ensure the correct transfer of data and files between these tiers, Oracle recommends configuring each server tier (web server, application server, database server, and file storage location) to use the same character set as follows:

• If your PeopleSoft system operates in a multi-language environment, use a UTF-8 character set on each server tier.

• If your PeopleSoft system operates in a single language environment, use the native language character set for that language on each server tier.

The Global Technology PeopleBook provides examples of which character set to specify on which tier for three typical configurations—a multi-language environment, a single language environment (Western), and a single language environment (non-Western).