Openwave SDK 6.2
How to Install and Use

Table of Contents
What's New in the SDK
Installing the SDK
Using the SDK
Using the Commmand-Line Arguments
Arguments and Parameters
Known Problems

OpenwaveTM SDK 6.2 is a Windows-based application that you can use to test how your wireless applications work Openwave Mobile Browser 6.2. The SDK features a mobile device simulator, which includes the same browser code as is embedded in real mobile devices. It also includes sample code and a generic device configuration file, or "skin," that represents an idealized mobile device (for details about the generic skin, see "About the Openwave SDK 6.2 Generic Configuration File."

Openwave SDK 6.2 is distributed as a set of packages, available from the Openwave Developer Program Web site:

Openwave Mobile Browser 6.2 can display content delivered in XHTML Mobile Profile 1.0 (XHTML-MP) with Cascading Style Sheets (CSS), the Wireless Markup Language (WML), MMS-SMIL, and a number of other formats.

The Openwave SDK 6.2 includes sample code for XHTML-MP and CSS and sample messages in MMS format. For more information, choose Start > Programs > Openwave SDK 6.2 > Samples > Readme.

Important: There are practical limits to how perfectly a Windows-based application can simulate a real mobile device. For example, the SDK's Windows-based simulator relies on Windows fonts and type-handling code, whereas real devices use their own fonts and code. The character fit of Windows fonts can be very close to a real device's fonts, but it's rarely identical. In addition, the CSS properties that adjust the space between words and characters are not supported by Windows, so they are ignored by the simulator. You can specify any font, size, or style available in Windows and the simulator will display it, even though the real device may support only a handful of font sizes and styles. It's a good idea to obtain details about the features of mobile devices before you design your applications. And it's essential that after you develop and test your wireless applications using a device simulator, you then test your applications on the actual devices and networks where they will be deployed.

For more information about the Openwave Mobile Browser 6.2, for documentation on XHTML-MP, CSS, WML, MMS, and for a broad range of other information about developing content for Openwave Mobile Browsers, visit the Openwave Developer Program Web site. Please also visit this site for further information about this release of the Openwave SDK and to tell us what you think.


What's New in the SDK

Openwave SDK 6.2 introduces a number of new features since SDK 6.1:


Installing the SDK

You can install Openwave SDK 6.2 on any computer running:

To install Openwave SDK 6.2, download its InstallShield package from the Openwave Developer Program Web site, start it, and follow its on-screen instructions.

Once you've installed the SDK, you can install additional components.

To install the Openwave SDK 6.2 WAP simulator plug-in, download its InstallShield package from the Openwave Developer Program Web site and install it in the same directory as you installed the Openwave SDK 6.2 package. The first time you start the SDK after you install it, the SDK sends your IP address and SDK version to Openwave to register the successful installation.


Using the SDK

Important: These release notes describe how to use the HTTP version of the Openwave Mobile Browser 6.2 simulator. If you've installed and are using the Openwave SDK 6.2 WAP simulator plug-in, be sure to read the release notes for the WAP version of the simulator: The file names, arguments, and parameters supported by the WAP version are different than those supported by the HTTP version.

When you install the SDK with the default installation options, the installer creates an Openwave SDK 6.2 HTTP menu item in the Start > Programs > Openwave SDK 6.2 menu. This menu item is in fact a link to a batch file:

C:\Program Files\Openwave\SDK 6.2\program\http\OSDK62http.cmd

You can choose this menu item to start the SDK in its default configuration.

However, to take full advantage of Openwave SDK, you can change the default configuration and control the SDK at startup or after it's running by:

When you install the SDK with the default installation options, the HTTP version of the Openwave Mobile Browser 6.2 simulator is installed in:

C:\Program Files\Openwave\SDK 6.2\program\http\OSDK62http.exe

When you start the SDK, the Openwave SDK 6.2 window opens, with a simulation of a mobile device featuring keys you can click and a display for content, useful menu commands, and so on.

The simulator's View menu includes commands that open windows with additional information: The Phone Information window and the Network Information window. You can use the -showphoneinfo and -shownetworkinfo command-line arguments to make the SDK open one or both of these windows at start-up.

The Phone Information window displays a wide variety of information about the commands you execute and their results, including debugging information. The information displayed in the Phone Info window is also written to a log file, named sim.log, which is stored in the same directory as the SDK application file. Each time you start the SDK, a new sim.log file is created, and the log file from the last session is renamed sim.bck.

The Network Information window is a new feature in Openwave SDK 6.2. This window displays information about each HTTP protocol transaction between the simulator and a web server.

You open the Network Information window by choosing the simulator’s View > Network Info command. You can also use the –shownetworkinfo argument to start the SDK with the Network Information window open.

The Network Info window has two sections: An upper section that lists summary information about each HTTP transaction, and a lower section that displays details about the transaction selected in the summary list.

The transaction details are displayed in three sections:

The information displayed in the Network Info window is also written to a log file, named network.log, which is stored in the same directory as the SDK application file. Each time you start the SDK, it creates a new network.log file, and renames the log file from the last session Network.bck.

To control memory use, the SDK only displays the 200 most recent HTTP transactions in the Network Information window. However, all transactions are retained in the log file (until the log file is replaced when you restart the SDK).


Using the Command-Line Arguments

Keep the following in mind as you use the command-line tools to control the SDK.


Arguments and Parameters

The following arguments to OSDK62http.exe are supported by the SDK.

Argument -help
Description Displays a summary of SDK command-line arguments in the SDK's Phone Information window.
Example OSDK62http.exe -help


Argument -exit
Description Causes the SDK to exit.
Example OSDK62http.exe -exit
Notes Equivalent to choosing the SDK's File > Exit command.


Argument -shownetworkinfo
Description Starts the SDK with the Network Information window open.
Example OSDK62http.exe -shownetworkinfo


Argument -showphoneinfo
Description Starts the SDK with the Phone Information window open.
Example OSDK62http.exe -showphoneinfo
Notes This argument replaces the -noconsole argument from previous SDKs.


Argument <URL>
Description If the first string after the SDK executable does not start with a dash ( - ), the SDK tries to load that string as a URL, as if it were parameter of the -reload argument.
Example OSDK62http.exe file://c:/mydecks/index.html

OSDK62http.exe http://developer.openwave.com/dhome5.cgi


Argument -reload [<URL>]
Description When used without the optional URL, reloads the current URL in the SDK's simulator window.

When used with a URL, marks that URL as invalid in the SDK's cache and then opens the specified URL.
Example OSDK62http.exe -reload

OSDK62http.exe -reload file://c:/mydecks/index.html
Notes When used without a URL, equivalent to the SDK's Edit > Reload menu command (F9).


Argument -go <URL>
Description Opens the URL in the SDK's simulator window.
Example OSDK62http.exe -go http://developer.openwave.com/dhome5.cgi

OSDK62http.exe -go developer.openwave.com/dhome5.cgi

OSDK62http.exe -go file://c:/myapplications/demo/index.html
Notes Equivalent to entering a URL or path in the SDK's Go field.

For URLs, you can omit http://.

For files, you must include file://. You can enter an absolute path name or a path name relative to the location of OSDK62http.exe.


Argument -gohome
Description Opens the current home deck in the SDK's simulator window.
Example OSDK62http.exe -gohome
Notes Equivalent to choosing the SDK simulator's Tools > Go Home command.

This argument is ignored if used when starting the SDK.


Argument -sethome <URL>
Description Sets the SDK's home deck when connecting with the -direct argument.
Example OSDK62http.exe -sethome http://developer.openwave.com/dhome5.cgi

OSDK62http.exe -sethome developer.openwave.com/dhome5.cgi

OSDK62http.exe -sethome file://c:/myapplications/demo/index.html
Notes For URLs, you can omit http://.

For files, you must include file://. You can enter an absolute path name or a path name relative to the location of OSDK62http.exe.

This argument only sets the home deck, it does not instruct the SDK to open it as well.

You can also use the SDK simulator's Tools > Set as Home command to set the page currently displayed in the browser as it's home.


Argument -pho <.pho file>
Description Changes the device configuration file used by the SDK's simulator.
Example OSDK62http.exe -pho OPWV-SDK-62.pho
Notes Equivalent to using the SDK's File > Change Device command to choose a device configuration file.

You can enter an absolute path for the device configuration file. Or if the .pho file is in the C:\Program Files\Openwave\SDK 6.2\program\devices directory, you can just enter its file name.


Argument -clearcache
Description Clears the SDK's cache and then opens the home deck.
Example OSDK62http.exe -clearcache
Notes Equivalent to using the SDK's Edit > Clear Cache command (F12).


Argument -direct
Description Configures the SDK to connect directly to wireless content on a Web server or in your file system, rather than through a gateway or other proxy.
Example OSDK62http.exe -direct
Notes This argument is ignored if the SDK is already running.


Argument -g <gateway>
Description Specifies the gateway or other proxy the SDK uses to connect to Web servers hosting wireless applications.
Example OSDK62http.exe -g proxy.mydomain.com -clearcache
Notes You can only specify a gateway or other proxy (such as the Openwave ESF) that can accept an HTTP connection.

This argument is ignored if the SDK is already running.

You can specify a host name or IP address, but in either case it must be for a host that your computer's DNS server can resolve.

Important: When changing gateways with the -g argument, always use the -clearcache argument at the same time.


Argument -pg <port>
Description Specifies the nonsecure (HTTP) port on the gateway or other proxy the SDK uses to connect to Web servers hosting wireless applications.
Example OSDK62http.exe -g proxy.mydomain.com -pg 80 -clearcache
Notes This argument is ignored if the SDK is already running.


Argument -pgs <port>
Description Specifies the secure port on the gateway or other proxy the SDK uses to connect to Web servers hosting wireless applications, with link-by-link security.
Example OSDK62http.exe -g proxy.mydomain.com -pgs 443 -clearcache
Notes You specify this port if the proxy supports link-by-link security, that is, the browser establishes a secure connection with the proxy and then when the browser requests a URL from the proxy, the proxy establishes a separate secure connection with the Web site hosting the URL.

This argument is ignored if the SDK is already running.


Argument -pgt <port>
Description Specifies the port on the gateway or other proxy the SDK uses to tunnel through to connect to Web servers hosting wireless applications, using end-to-end security.
Example OSDK62http.exe -g proxy.mydomain.com -pgt 8080 -clearcache
Notes You specify this port if the proxy supports link-by-link security, that is, when the browser requests a URL from the proxy, the browser establishes a secure connection directly with the web server that hosts the URL, using the proxy port as a tunnel.

This argument is ignored if the SDK is already running.


Argument -user <username>
Description Specifies the user name the browser uses when establishing a connection with a gateway or other proxy that requires authorization, such as the Openwave ESF.
Example OSDK62http.exe -user myname -pass password
Notes You can use backslash-escaped characters in the user name and you can surround it with double quotes.

Ignored if the SDK is already running.


Argument -pass <password>
Description Specifies the password for the user name the browser uses when establishing a connection with a gateway or other proxy that requires authorization, such as the Openwave ESF.
Example OSDK62http.exe -user myname -pass password
Notes You can use backslash-escaped characters in the password and you can surround it with double quotes.

Ignored if the SDK is already running.


Argument -charset utf8
Description Overrides just the character set portion of the language and script settings you establish with the -lang argument, setting the character set advertised in the simulator's accept header to UTF8.
Example OSDK62http.exe -lang ru-ru -charset utf8
Notes This argument must follow a correct use of the -lang argument.

Ignored if the SDK is already running.


Argument -lang <language code>
Description Specifies the language and character set ("Script") that the SDK tells content servers it prefers to receive, for servers that can deliver content in more than one language or character set. The SDK's browser declares these preferences in HTTP accept headers, which it sends to content servers when it connects to them. The -lang argument also sets the font used to display content in the simulator.
Example OSDK62http.exe -lang zh-hk
Notes The SDK only accepts the -lang argument parameters from the following table, which lists the character set, font, and related settings included with each parameter.

The text in the SDK browser simulator's UI (softkeys, menus, the status bar, error messages, and so on) are presented in English, regardless of the language you specify.

You can also use the SDK simulator's Tools > Language menu to set the preferred language.
-lang
parameter
Language Charset Font Style Size Script
ar-sa Arabic iso-8859-6 Set by .pho file (Arial) Regular Set by .pho file Arabic
zh-cn Chinese
(Simplified)
gb-2312 MSHei, SimSun, or similar Regular Set by .pho file Chinese_GB2312
zh-hk Chinese
(Traditional)
big5 MingLiU, PMingLiU, or similar Regular Set by .pho file Chinese_BIG5
cs-cz Czech iso-8859-2 Set by .pho file (Arial) Regular Set by .pho file Latin2
da-dk Danish iso-8859-1 Set by .pho file (Arial) Regular Set by .pho file Western
nl-nl Dutch iso-8859-1 Set by .pho file (Arial) Regular Set by .pho file Western
en English iso-8859-1 Set by .pho file (Arial) Regular Set by .pho file Western
fi-fi Finnish iso-8859-1 Set by .pho file (Arial) Regular Set by .pho file Western
fr-fr French iso-8859-1 Set by .pho file (Arial) Regular Set by .pho file Western
de-de German iso-8859-1 Set by .pho file (Arial) Regular Set by .pho file Western
el-gr Greek iso-8859-7 Set by .pho file (Arial) Regular Set by .pho file Greek
iw-il Hebrew iso-8859-8 Set by .pho file (Arial) Regular Set by .pho file Hebrew
hu-hu Hungarian iso-8859-2 Set by .pho file (Arial) Regular Set by .pho file Latin2
it-it Italian iso-8859-1 Set by .pho file (Arial) Regular Set by .pho file Western
ja-jp Japanese Shift-JIS MS Gothic, MS UI Gothic, or similar Regular Set by .pho file Japanese
ko-kr Korean ks_c_5601 GulimChe, Batang, or similar Regular Set by .pho file Hangul
no-no Norwegian iso-8859-1 Set by .pho file (Arial) Regular Set by .pho file Western
pl-pl Polish iso-8859-2 Set by .pho file (Arial) Regular Set by .pho file Latin2
pt-pt Portuguese iso-8859-1 Set by .pho file (Arial) Regular Set by .pho file Western
ru-ru Russian windows-1251 Set by .pho file (Arial) Regular Set by .pho file Cyrillic
es-sp Spanish iso-8859-1 Set by .pho file (Arial) Regular Set by .pho file Western
sv-se Swedish iso-8859-1 Set by .pho file (Arial) Regular Set by .pho file Western
tr-tr Turkish iso-8859-9 Set by .pho file (Arial) Regular Set by .pho file Latin5


Known Problems

The following problems have not been fixed in this release of the Openwave SDK.