Table 4. Siebel Unicode Architecture Data Flow
|
|
1 |
User input is URL-encoded by JavaScript or browser. |
2 |
JavaScript code and style sheets are in ASCII. NOTE: Style sheet files can be saved as UTF-8 in order to be able to specify font names that contain non-ASCII characters.
|
3 |
HTML pages are in ASCII, or UTF-8 if hard-coded non-ASCII content is required. |
4 |
Web server passes URL-encoded input to Siebel Web Server Extension (SWSE). |
5 |
SWSE configuration file (eapps.cfg) is in ASCII. |
6 |
SWSE sends input (still in URL encoding) to the Siebel Server. The Siebel Server decodes input immediately to the Siebel internal encoding (UTF-16). |
7 |
Application configuration file (CFG) is UTF-8. (Some parameter values may specify non-ASCII text for elements such as font names or splash screen text.) |
8 |
Web templates are in ASCII and are language-independent. |
9 |
Most C++ code uses the Siebel internal encoding (UTF-16). |
10 |
Application Object Manager uses UTF-16 to communicate with the database. The internal encoding of the database can be UTF-8, UTF-16, or a code page. |
11 |
Siebel Web Engine (SWE) sends the HTML page (in UTF-16) to SWSE. |
12 |
SWSE transcodes, or converts, the HTML page to UTF-8 for the World Wide Web. |
13 |
Web server passes the HTML page (in UTF-8) to the browser. |
14 |
Browser code (JavaScript or Java) reads the HTML page in UTF-16. |
15 |
Resource dynamic-link libraries (DLLs) store content in UTF-16. |
16 |
Siebel repository file (SRF) stores content in UTF-16. |