Understanding Client Detection

Client detection determines the capabilities and characteristics of each mobile device that is used to access the portal site. To do this, it uses the composite capability and preference profiles (CC/PP) specification, UAProf, or preconfigured data. Mobile Access software requires that three properties be defined for every client. They are:

• clientType—A name that provides a unique index for the client data. Nokia6310i_1.0 is the clientType value for the Nokia 6310i mobile phone.

• parentId—ID of the immediate parent for a device. (For an object with no parent, the value is the same as clientType.) Nokia is the parentId value for the Nokia 6310i mobile phone.

• userAgent—The HTTP user-agent string. This value can be empty for base and style information. Nokia6310/1.0 is the userAgent value for the Nokia 6310i mobile phone.

Mobile Access software also uses conditional properties to store and retrieve specific property values for client types. One example is the desktopContainer conditional property. The wireless desktop dispatcher reads this property to determine what the desktop container is for the requested client type.

Mobile Access software imports client type data from the file /var/opt/SUNWam/config/ldif/sunAMClient_data.ldif into the LDAP directory and uses Access Manager software APIs to identify clientType property matches. Matches are determined in the following order:

1. An exactmatch

2. A partialmatch

3. A keywordmatch

You can also dynamically apply UAProf profile against your base profile. Users need to retain FEDIClientDetector and do one of the following:

• configure your firewall to allow access from Mobile Access system to the public internet or selective handset vendor sites

• configure the Mobile Access system JVM to use a proxy server to access the public internet or selective handset vendor sites.

• publish the UAProf profiles (RDF files) on an internal web server accessible to the Mobile Access system and configure DNS on the Mobile Access system to use the internal web server instead of the public internet for all UAProf requests.

To configure the proxy server to selectively access the public internet:

The JVM provides an option to specify proxy server details for an external connection from the web container using an external proxy. The JVM also allows you to specify the hosts that should not use the specified proxy. You can configure the Mobile Access system JVM to use a proxy server to access the public Internet.

Use the following JVM options in the web container:

Dhttp.proxyHost=your-proxy-server-host

Dhttp.proxyPort=your-proxy-server-port

Use the following option for bypassing proxy server for certain domains and hosts: Dhttp.nonProxyHosts="*.domain-name|hostname|localhost"