Release 10.1A: OpenEdge Application Server:
Administration

> ## Code-page settings

> You can set code pages for 4GL clients and AppServers using several code page startup parameters. Each parameter allows you to specify any one of a wide variety of supported code pages for a specified data domain in the OpenEdge environment (for example, memory code page or input/output stream code page). For the AppServer, you specify code page startup parameters in the Progress Explorer as part of the `srvrStartupParam` property setting in the `ubroker.properties` file. For more information on these parameters, see the chapter on code pages in OpenEdge Development: Internationalizing Applications . Whatever the settings, the AppServer performs the necessary conversions to and from the client application.

> Note: Note that the Terminal Code Page (`-cpterm`) startup parameter has no meaning for the AppServer.

> Both .NET and Java Open Clients send requests (input) to the AppServer and receive responses (output) from the AppServer using Unicode UTF-8. The AppServer automatically converts between these open client Unicode UTF-8 requests and the particular code page that the AppServer is using.

> Note: If your AppServer application provides database services to a multi-lingual open client application, using UTF-8 for both the AppServer and the database provides the most effective data interchange across application components.

> Caution: Unicode supports text with embedded nulls. OpenEdge does not support this feature, no matter what character set it uses. Make sure that any open client applications filter character strings input to the AppServer for embedded nulls. Unfiltered input can result in unpredictable errors returned by the AppServer.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095