Openwave® SDK 6.1 is a Windows-based application that you can use to test how your wireless applications work with Openwave Mobile Browser 6.1. 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.
The Openwave SDK 6.1, distributed as an InstallShield package, which includes the HTTP version of the Openwave Mobile Browser 6.1 simulator, these release notes, sample code, the generic "Slimjim Mini Lime" phone configuration file, and supporting files. You must install this package.
The Openwave SDK 6.1 WAP simulator plug-in, distributed as an InstallShield package, includes the WAP version of the Openwave Mobile Browser 6.1 simulator, Release Notes for the WAP version of the simulator, and supporting files. You must install the Openwave SDK 6.1 before you can install the WAP simulator plug-in.
Mobile phone configuration files, or "skins," distributed as .zip files, include configuration files, release notes, and supporting files for particular models of mobile devices. Be sure to read the release notes that come with these configuration files to learn which version of the Openwave Mobile Browser (HTTP or WAP) they are designed to work with.
Openwave Mobile Browser 6.1 can display content delivered in XHTML Mobile Profile 1.0 (XHTML-MP) with Cascading Style Sheets (CSS), the Wireless Markup Language (WML), and a number of other formats.
The Openwave SDK 6.1 includes sample code for XHTML-MP and CSS. For more information, choose Start > Programs > Openwave SDK 6.1 > 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 also specify any font, size, or style available in Windows and the simulator will display them, 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.1, for documentation on XHTML-MP, CSS, WML, 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.
You can install Openwave SDK 6.1 on any computer running:
Microsoft Windows NT with Service Pack 6a
Microsoft Windows 2000 with Service Pack 2
Microsoft Windows XP
If you have Openwave SDK 6.1 Preview installed, you must uninstall it before you can install Openwave SDK 6.1.
To install Openwave SDK 6.1, 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.1 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.1 package.
To install a mobile device configuration file, or "skin," download its .zip file from the Openwave Developer Program Web site and install its contents in the C:\Program Files\Openwave\SDK 6.1\program\devices directory (or wherever you installed the SDK 6.1\program\devices directory, if you didn't install the SDK in the default directory). Then read the release notes that come with the skin to learn about its features, and which version of the Openwave SDK Mobile Browser 6.1 simulator (HTTP or WAP) is supported by the device it emulates.
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.
Important: These release notes describe how to use the HTTP version of the Openwave Mobile Browser 6.1 simulator. If you've installed and are using the Openwave SDK 6.1 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.1 HTTP menu item in the Start > Programs > Openwave SDK 6.1 menu. This menu item is in fact a link to a batch file:
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:
Editing the OSDK61http.cmd file
Creating and executing a new .cmd or other batch file
Appending arguments to the SDK application in a Command Prompt window
Sending arguments to the SDK application from another application, such as a third-party integrated development environment (IDE), using the Windows Command Processor
When you install the SDK with the default installation options, the HTTP version of the Openwave Mobile Browser 6.1 simulator is installed in:
When you start the SDK, two windows open: The Openwave SDK 6.1 window, with a simulation of a mobile device featuring keys you can click and a display for content, useful menu commands, and so on, and the Phone Information window, which 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 Phone Information window has new features in Openwave SDK 6.1: You can open and close it without exiting the SDK, by clicking its window control buttons or with the simulator's Info > Phone Info Window menu command. You can also resize the window, scroll its contents, select and copy text, in short: You can now work with it as you would with any standard Windows window.
Keep the following in mind as you use the command-line tools to control the SDK.
When using these command-line tools in the Command Prompt window, you must first change to the same directory as the OSDK61http.exe file (C:\Program Files\Openwave\SDK 6.1\program\http\ by default) or include its absolute path name.
When using these tools in batch files or scripts, use them as arguments to the Windows start command when starting the SDK: Otherwise your batch file or script will be blocked until you exit the SDK.
If you pass an invalid argument to OSDK61http.exe, the argument is ignored and an error message appears in the Phone Info window.
When starting the SDK, you can concatenate arguments. For example: osdk61http.exe -direct -clearcache -pho slimjim-mini-lime.pho -sethome http://developer.openwave.com/dhome5.cgi
However, not all combinations (particularly nonsensical combinations) have been tested.
When the SDK is running, you can only use one argument at a time.
If you open a modal dialog box in the SDK UI, such as the Open Configuration File dialog box, you can't control the SDK from the command line until you close the dialog box.
The SDK supports only HTTP-style slashes ( / ) in URLs or arguments for Web sites and local files. The SDK does not support Windows-style slashes ( \ ).
For convenience, the SDK makes it possible for you to browse files on your local file system, by entering a path that starts with file:// in the SDK's Go field, or with such arguments as -reload and -go. However, you should not rely on this method to test your wireless applications, for a number of reasons, most notably:
The SDK does not correctly cache information about the files you load using file://
The SDK ignores any gateway or proxy you specify with the -g argument and loads files directly from your file system -- without any of the modifications that typical gateways make
To more accurately test your applications, host them on a web server and load them using the http:// prefix instead.
When using -go or another command-line argument to open a URL that includes the & character, you need to enclose the URL in quotation marks.
The following arguments to osdk61http.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
OSDK61http.exe -help
Argument
-exit
Description
Causes the SDK to exit.
Example
OSDK61http.exe -exit
Notes
Equivalent to choosing the SDK's File > Exit command.
Argument
-noconsole
Description
Starts the SDK without opening the Phone Information window.
Example
OSDK61http.exe -noconsole
Notes
This argument is ignored if the SDK is already running.
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.
For files, you must include file://. You can enter an absolute path name or a path name relative to the location of OSDK61http.exe.
This argument only sets the home deck, it does not instruct the SDK to open it as well.
Argument
-pho <.pho file>
Description
Changes the device configuration file used by the SDK's simulator.
Example
OSDK61http.exe -pho Slimjim-mini-lime.pho
Notes
Equivalent to using the SDK's File > Open Configuration 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.1\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
OSDK61http.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
OSDK61http.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
OSDK61http.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.
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.
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.
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
OSDK61http.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
OSDK61http.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
-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
OSDK61http.exe -lang zh-hk
Notes
The SDK 6.1 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.
The following problems have not been fixed in this release of the Openwave SDK.
291826: If you do not use the -clearcache argument when you change gateways with the -g argument, the -sethome argument may have no effect. Restarting the SDK with the -clearcache argument should correct this problem.
293399: HTTP errors are recorded in the Phone Information window and in the log file as Request status: 200, regardless of the nature of the error.
Legal Notice
Copyright (c) 1999-2002 Openwave Systems Inc. All rights reserved.
Openwave, the Openwave logo, and Services OS are registered trademarks and/or trademarks of Openwave Systems Inc. in various jurisdictions. All other trademarks are the property of their respective owners.
This Software shall not be shipped, transferred, exported or re-exported into any country or used in any manner prohibited by the United States Export Administration Act or any other export laws, restrictions or regulations (collectively the "Export Laws"). In addition, if this Software is identified as an export controlled item under the Export Laws, you represent and warrant that you are not located within an embargoed nation (including without limitation Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria) and that you are not otherwise prohibited under the Export Laws from receiving the Software. All rights to use the Software are granted on condition that such rights are forfeited if you fail to comply with the terms of this Agreement. Export or re-export of this software to the embargoed countries, and any other countries that the Bureau of Export Administration may subsequently add to the list of embargoed countries, is forbidden. In addition, this Software may not be sold as part of any product developed for or used exclusively by government agencies.
