Bookshelf v7.7: Siebel Unicode Architecture

The Siebel software architecture has been designed to fully support Unicode, including internal processing. There are many benefits to using Unicode, such as the ability to show multilingual data in the same session. Figure 2 provides a graphical representation of the architecture, while Table 9 describes the flow of data through the Siebel Unicode architecture.

Table 9. Siebel Unicode Architecture Data Flow
Step Number	Text Encoding
1	User input is URL-encoded by JavaScript or browser.
2	JavaScript code and style sheets are in ASCII.
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	Application 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	Configuration file (CFG) is 8-bit, presumably in ASCII.
8	Web templates are in ASCII and are language independent.
9	Most C++ code uses the Siebel internal encoding (UTF-16).
10	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.