Bookshelf Home | Contents | Index | Search | PDF

Siebel Wireless Administration Guide For Financial Services > Configuring Siebel Wireless >

Supporting Wireless Requests with Multiple Markup Languages

---

If your users are using different browsers, you may need to configure Siebel Wireless applications to handle multiple markup languages. Siebel Wireless applications can be configured to handle all wireless requests through the XML Web Interface, or to handle only certain wireless requests through the XML Web Interface and to handle others through the WML Interface.

To make sure that Wireless requests are handled as desired, first determine whether Siebel software will need to support:

Requests from WML browsers only
Requests from both WML and non-WML browsers
Requests from only non-WML browsers

If Siebel Wireless will need to handle requests for WML browsers only or for both WML and non-WML browsers (the first two cases above), the following configuration must be performed.

To configure for WML and non-WML browsers

Make sure that the MarkupLanguage parameter in the SWE section of relevant Siebel Wireless server configuration files is set as follows:

[SWE]

MarkupLanguage = WML

NOTE:  WML is the default value for this parameter when Siebel software is installed.

Create the following Web Browser entries using the Web Browser Administration screen in the Siebel Web Client for each wireless browser for which requests will be handled by the XML Web Interface:
Define a Browser Group entry with capabilities as follows:

Capability Name	Capability Value
Browser	<Browser Name>
DefaultMarkup	XML

Define child browsers with capabilities as follows:

Capability Name	Capability Value
Default Markup	XML
User-Agent	<Browser User Agent>
Parent	<Browser Name Defined Above>

Create the following Web browser entries using the Web Browser Administration capability in the Siebel Web Client for each wireless browser for which requests will be handled by the WML Interface:
Define a Browser Group entry with capabilities as follows:

Capability Name	Capability Value
Browser	<Browser Name>
Default Markup	WML

Define child browsers with capabilities as follows:

Capability Name	Capability Value
Default Markup	WML
User-Agent	<Browser User Agent>
Parent	<Browser Name Defined Above>

User agents must be defined for both WML and non-WML browsers to make sure that the correct interface is applied.

If MarkupLanguage is set to WML as described above, any wireless request for which no user agent is recognized is treated as an XML request. Additionally, any wireless request from a user agent which has HTML defined as its default markup is treated as an XML request.

See Siebel Web Client Administration Guide for additional details on defining Web browsers and user agents using Web Browser Administration.

If Siebel Wireless will need to handle requests only through the XML Web Interface, the following configuration must be performed:

Make sure that the MarkupLanguage parameter in the SWE section of relevant Siebel Wireless server configuration files is set as follows:

[SWE]

MarkupLanguage = XML

NOTE:  If the MarkupLanguage parameter is set to XML for a particular Siebel Wireless application, the XML Web Interface is used to handle all wireless requests from all browsers regardless of the DefaultMarkup value defined for their user agent.

This process of determining a markup language for a particular request described above can be overridden by setting the SWESetMarkup parameter for inbound wireless requests. Valid values for this SWESetMarkup parameter are XML or HTML (not WML).

For example, this parameter can be set as follows to force a particular wireless request to be rendered in XML, regardless of the MarkupLanguage defined in the wireless configuration file or the DefaultMarkup defined for that browser:

SWESetMarkup="XML"

Bookshelf Home | Contents | Index | Search | PDF