Siebel Portal Framework Guide > Delivering Content to External Web Applications >

Siebel Object Manager and Web Server Configuration and Markup Determination

The Siebel Web Engine (SWE) can be configured to produce output in HTML, WML, and XML markup languages. The default markup is set using the SWEMarkup parameter for the Application Object Manager. Based on browser or device detection or parameters set on the inbound request, this default markup might be overridden.

NOTE:  The Siebel Open UI client supports HTML markup only. For more information, see Overview of the XML Web Interface.

The following is a summary of how the markup is determined for a given request. The following three steps are used in the markup determination process for a given request. They are listed by priority.

1. SWESetMarkup parameter. This is an optional inbound request parameter that can be used to override the User Agent Service and Server configuration. Valid values for this are XML, WML, or HTML. The User Agent Service and server configuration are not used to determine the markup when the SWESetMarkup parameter is defined on the inbound request.
2. User agent service. This service is used to determine the markup based on the device or browser that generated the request. The service takes information from the request header and look up the designated markup in the device table. The resulting markup is passed to the next step. If no match is found in the device table, then the default markup is HTML.
3. Dynamic markup comparison. Assuming that no markup is specified by the inbound request SWESetMarkup parameter, the markup from the user agent service is compared to the server default configuration to determine what markup is generated. The server default markup is designated by the SWEMarkup parameter the Application Object Manager.

Table 18 shows a summary of the markup that is generated for a given request based on the intersection of the server configuration markup and the markup from the user agent service.

Accessing Specialized WML Behavior

When you use the XML interface in conjunction with the Siebel Wireless WML-based application, the Wireless parameter must be set to TRUE (the default value) for the Application Object Manager for the Siebel Wireless application.

For more information about using the XML interface with the Siebel Wireless application, see Siebel Wireless Administration Guide.