Complete Contents
About This Guide
Chapter 1 Introduction to iPlanet Web Server
Chapter 2 Administrating iPlanet Web Servers
Chapter 3 Setting Administration Preferences
Chapter 4 Managing Users and Groups
Chapter 5 Working with Server Security
Chapter 6 Managing Server Clusters
Chapter 7 Configuring Server Preferences
Chapter 8 Understanding Log Files
Chapter 9 Using SNMP to Monitor Servers
Chapter 10 Configuring the Server for Performance
Chapter 11 Extending Your Server with Programs
Chapter 12 Working with Configuration Styles
Chapter 13 Managing Server Content
Chapter 14 Controlling Access to Your Server
Chapter 15 Configuring Web Publishing
Chapter 16 Using Search
Appendix A HyperText Transfer Protocol
Appendix B ACL File Syntax
Appendix C Internationalized iPlanet Web Server
Appendix D Server Extensions for Microsoft FrontPage
Appendix E iPlanet Web Server User Interface
Glossary
Index
Previous Next Contents Index Bookshelf


Appendix C Internationalized iPlanet Web Server

The internationalized version of the iPlanet Web Server contains special features tailored for the non-U.S. environment. These features include a choice of user-interface language (Japanese, French, or German) and a choice of search engines that allow you to use text search on a variety of languages.

This appendix contains the following sections:


General Information
The following information covers the international considerations for general server capabilities.

This section includes the following topics:

Installing the Server
When you install the server, you choose what user-interface language to use, as well as what search engines to install.

For information on installing the international version of the server, see the iPlanet Web Server, Enterprise Edition 4.1 Release Notes. You can access the Release Notes online via the link provided in the README file.

Entering 8-bit Text
If you want to type 8-bit data into the Server Manager or the administration server forms, you need to be aware of the issues in this section.

File or Directory Names
If a file or directory name is to appear in a URL, it cannot contain 8-bit or multi-byte characters.

LDAP Users and Groups
For email addresses, use only those characters permitted in RFC 822
(ftp://ds.internic.net/rfc/rfc822.txt). User ID and password information must be stored in ASCII.

If you use a local database, you can enter 8-bit and multi-byte characters, but you should standardize on one character set. If you use more than one character set in the same database, it can cause display and search problems.

If you must use 8-bit or multi-byte characters in your directory database, you should store them in UTF-8 for future compatibility with the Netscape Directory Server version 4.x. To make sure you enter characters in the correct format, use a UTF-8 form-capable client (such as Netscape Communicator) to input 8-bit or double-byte data.

If you let users access their own user and group information, they will need to use a UTF-8 form-capable client.

Note. iPlanet Web Server 4.x no longer packages the ldapsearch and ldapmodify utilities. Earlier versions of Enterprise Server included them, since those versions employed local LDAP database support. iPlanet Web Server 4.x now uses an LDAP server all the time which includes these utilities.

Note. The default maximum number of parallel LDAP sessions is now set to 8. There is a way to override this limitation. In addition to the binddn and bindpw properties that a LDAP connection listed in dbswitch.conf may have, iPlanet Web Server 4.x now includes a sessions property. The value is numeric and this property sets the maximum number of parallel connections in the LDAP session pool.

Using the Accept Language Header
When clients contact a server using HTTP 1.1, they can send header information that describes the various languages they accept. You can configure your server to parse this language information.

For example, suppose this feature is set to on, and a client configured to send the accept language header sends it with the value en,fr. Now suppose that the client requests the following URL:

The server first looks for:

If it does not find that, it looks for:

If that is not available either, and a ClientLanguage (call it xx) is defined in the magnus.conf file, the server tries:

If none of these exist, the server tries:

Language Settings in Configuration Files
The following directives in the magnus.conf file affect languages:

Table C.1 International settings in magnus.conf
Directive
Values
Description
ClientLanguage
en, fr, de, ja
Specifies the language in which client messages, such as "Not Found" or "Access denied" are to be expressed. This value is used to identify a directory containing ns-https.db.
DefaultLanguage
en, fr, de, ja
Specifies the language used if a resource cannot be found for the client language or the administration language.
AcceptLanguage
on, off
Enables or disables the Accept language header parsing.

The following directives in the ns-admin.conf file affect languages:

Table C.2 International settings in ns-admin.conf
Directive
Values
Description
ClientLanguage
en, fr, de, ja
If the client does not send an accept language header, ClientLanguage defines the language of the Directory Server User Information and Password pages. The two-letter value code is used to find the directory containing ns-admin.db.
AdminLanguage
en, fr, de, ja
Sets the language used for administrative pages that are accessed through the administration server.
DefaultLanguage
en, fr, de, ja
The language used if a value cannot be found for the client or admin languages.


Server-side JavaScript Information
When you use server-side JavaScript with the international version of the server, you have additional things to consider when compiling applications and using databases. For example, you can specify the language of the JavaScript application one of two ways: using the compiler, or using the HTML <META> tag.

Specifying the Character Set for the Compiler
For the international version, the server-side JavaScript compiler (jsac) has a -l option called charSet. This option specifies the character set being used in the input HTML files. The value for charSet is one of the following character set names.

Table C.3 Valid values for charSet
Language
Value for charSet
Western European
iso-8859-1
Central European
iso-8859-2
Cyrillic
iso-8859-5
Japanese
iso-2022-jp, x-sjis, x-euc-jp
Korean
iso-2022-kr, x-euc-kr
Simplified Chinese
x-gb2312
Traditional Chinese
x-big5, x-euc-ch
Greek
iso-8859-7
Turkish
iso-8859-9

Usage
To use this option, use the following format:

jsac [-cdv] [-l charSet] -o binaryFile [-i] inputFile1 [-i] inputFile2 ...

jsac [-cdv] -o binaryFile -f includeFile

jsac -h

Options
The following table shows the options for the compiler.

Table C.4 Options for the jsac compiler
Option
Usage
-c
Check only; do not generate binaryFile
-v
Enable verbose output
-d
Enable debug output
-o
Name of binaryFile (output file).
-i
Name of inputFile (use if the input filename starts with a switch character)
-f
Name of includeFile (has input filenames, separated by white space)
-l
Name of charSet (for example, iso-8859-1, x-sjis, euc-kr)
-h
Display this help

The possible filename extensions are summarized in the following table:.

Table C.5 File extensions
Extension
File type
.html or .htm
HTML source file (may include JavaScript)
.js
JavaScript source file
.web
Binary output file

When you specify the language using the compiler option, you can only specify one language. If you want to specify multiple languages, you can use the <META> tag in the individual files.

Specifying the Character Set With the <META> Tag
You can also use the <META> tag to specify the character set information. For example, if you put the following statement into the header (between <HEAD> and </HEAD>) in a JavaScript program, the server-side JavaScript compiler (jsac) considers the file to be written in x-sjis.

If the character set specified in the <META> tag is different from the character set specified by the compiler's charSet option, the character set specified by the compiler option is used.

Using Server-side Javascript With Oracle's Japanese Database
To use server-side JavaScript with Oracle's Japanese database, you need to install Oracle and set up your environment, verify the connection, and verify the language setup. follow these overall steps. This section discusses these topics:

Installing Oracle and Setting Up Your Environment
You must first install the Japanese Oracle database. For instructions, see the documentation that came with your database. Next, you must set up your environment variables using the following information. Note that the environment variable syntax assumes C Shell.

Server-side JavaScript library:

Environment variables for Oracle:

Environment variable for NLS (National Language Support) in Oracle:

Environment variable for the path:

Restart the web server from the command line.

Verifying the Connection

  1. At the Application Manager, select and run dbadmin.

  2. Click Connect to Database Server.

  1. Enter the following information in the window, and click Connect. If your server identifier, user ID, or password is different from these default values, enter your actual values here.
Table C.6
Field
Value
Server Type
ORACLE
Server Identifier
WG73
User ID
system
Password
manager
Database

Unless you see an error indicating otherwise, you are now connected.

Verifying the Language Setup
Use the videoapp sample application to verify the language setup.

  1. If your ORACLE installation has a server identifier, user ID, or password that is different from the default values shown in the previous table, be sure to specify the actual values in the start.htm file at the following line:

  2. Run the build script in the directory to recompile the JavaScript code.

  3. At the Application Manager, select and run vidoeapp.

  4. Click Add New Customer and enter data in the character set you specified.

  5. Click Home to go back to the videoapp home page, and then click Save Changes.

  6. Click Delete a Customer.

  7. Check to see if the data you entered appears in the table. If the data appears in the database in the correct language, you've set up the languages correctly.
Putting the Oracle Client and Database Server On Separate Hosts
To put the Oracle client (with server-side JavaScript database service) and the Oracle database server on separate hosts, follow these steps:

  1. On the client side, define the SERVER SID alias to refer to the server in tnsnames.ora.

  2. Set the TWO_TASK environment variable to the SERVER SID alias defined in the tsnames.ora file. For example:

  3. Set the NLS_LANG environment variable to the correct client language and character set information.

  4. Using the sample application videoapp, edit the start.htm file as shown below. (In this example, assume that the SERVER SID alias is remoteDB.)

  5. Click Add New Customer and enter data in the character set you specified.

  6. Click Home to go back to the videoapp home page, and then click Save Changes.

  7. Click Delete a Customer.

  8. Check to see if the data you entered appears in the table. If the data appears in the database correctly, you've configured your system properly.
Search Information
Search capabilities are supported for the following languages:

You choose which search engines to install when you install the international version of the server.

International Search and Auto Catalog
If your server contains documents in various character set encodings, the search collections and/or auto catalog for the documents will inherit the same encodings as the originals. To view documents in different character set encodings, users must change the character set encoding for their browsers. In addition, since the text search and auto catalog features work with one character set encoding at a time, you might receive inaccurate results when using those features. Netscape recommends using one specific character set for all documents.

Searching in Chinese, Japanese, and Korean
The following information is specific to searching in Japanese, Korean, and Chinese.

Query Operators
This release supports the following query operators for Japanese, Korean and Chinese languages:

Table C.7 Query operators for Japanese
Operator
J/C/K Character
AND
Yes
CONTAINS
No
ENDS
Yes
MATCHES
Yes
NEAR
Yes
NEAR/N
Yes
NOT
Yes
OR
Yes
PHRASE
Yes
STARTS
Yes
STEM
English only
SUBSTRING
Yes
WILDCARD *
Yes
WILDCARD ?
Yes
WILDCARD {}
No
WILDCARD []
No
WILDCARD ^
No
WILDCARD -
No
WORD
Yes

Document Formats
This release supports the following document formats for the Japanese, Korean, and Chinese languages:

Searching in Japanese
The following sections give additional information about searching in the Japanese character set.

Document Codes

This release supports the following document codes for the Japanese language:

Search Words

This release supports the following search words:

The search engine translates half-width katakana to full-width katakana, and translates full-width ascii-string to half-width ascii-string. Users can use full-width and half-width as the same characters.

This release also supports phrase and sentence search.


Getting Support for Accented Characters in Filenames
If the filenames on your server contain accented characters, for instance elninõ.html, you can get support for them by specifying the 8859 character set as the internal coding for search collections. To specify 8859, you need to modify the file language.conf in the directory <serverRoot>\plugins\search\admin. This file is used by the Search Engine, Web Publishing, and the document indexing features of the server.

The language.conf file contains the following lines for the English language. These lines direct the server to configuration files that use 8859 as the default character set. The configuration files are located in the directory <serverRoot>\plugins\search\common.

To specify 8859, you need to activate these lines in language.conf by removing the comment characters (#).

If you make this change to the language.conf file after a collection has been created, to support accented characters in filenames for that collection you need to delete the collection, make this change to the file, recreate the collection choosing "English NS 8859 (ISO-8859-1" from the "Documents are in" drop-down list, and reindex all the documents in the collection.

 

© Copyright © 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © 2000 Netscape Communications Corp. All rights reserved.