The Openwave® SDK 6.1 WAP simulator plug-in is a package that 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.
These release notes describe how to install the Openwave SDK 6.1 WAP simulator plug-in and how to use the WAP version of the Openwave Mobile Browser 6.1 simulator.
For more information about the Openwave SDK 6.1, see the Openwave SDK 6.1 Release Notes.
Once you have downloaded and installed the Openwave SDK 6.1, as described in its Release Notes, you can install the WAP simulator plug-in.
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.
Important: These release notes describe how to use the WAP version of the Openwave Mobile Browser 6.1 simulator. If you're using the HTTP version of the Openwave Mobile Browser 6.1 simulator, be sure to read the release notes for the HTTP version of the simulator: The file names, arguments, and parameters supported by the HTTP version are different than those supported by the WAP version.
When you install the Openwave SDK 6.1 WAP simulator plug-in, the installer creates an Openwave SDK 6.1 WAP 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 OSDK61wap.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 Openwave SDK 6.1 WAP simulator plug-in with the default installation options, the WAP 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 OSDK61wap.exe file (C:\Program Files\Openwave\SDK 6.1\program\wap\ 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 OSDK61wap.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:
osdk61wap.exe -g devgate2.openwave.com -anon -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 OSDK61wap.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
OSDK61wap.exe -help
Argument
-noconsole
Description
Starts the SDK without opening the Phone Information window.
Example
OSDK61wap.exe -noconsole
Notes
This argument is ignored if the SDK is already running.
Argument
-exit
Description
Causes the SDK to exit.
Example
OSDK61wap.exe -exit
Notes
Equivalent to choosing the SDK's File > Exit command.
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.
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.
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 OSDK61wap.exe.
Argument
-gohome
Description
Opens the current home deck in the SDK's simulator window.
Example
OSDK61wap.exe -gohome
Notes
Equivalent to entering device:home in the SDK's Go field.
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.
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 OSDK61wap.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
OSDK61wap.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
OSDK61wap.exe -clearcache
Notes
Equivalent to using the SDK's Edit > Clear Cache command (F12).
Argument
-g <gateway>
Description
Specifies the gateway or other proxy the SDK uses to connect to Web servers hosting wireless applications.
Example
OSDK61wap.exe -g proxy.mydomain.com -clearcache
Notes
You can only specify a gateway or other proxy that can accept a WAP connection, such as an Openwave Mobile Access Gateway (MAG).
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 WAP gateway port the SDK uses to make remote TCP/IP network requests.
The port is secure or nonsecure depending on whether you use the -secure or -nonsecure argument when you start the SDK. The default secure port is 9203; the default nonsecure port is 9201.
Only use the -pg argument to change the port if the WAP gateway is configured to use nonstandard ports. Otherwise, the SDK will not be able to connect to the gateway.
This argument is ignored if the SDK is already running.
Argument
-p <local port>
Description
The port on your computer that the MAG or other gateway uses to communicate with the SDK. The default is port 8502.
This is the client ID in hexadecimal format, obtained when an administrator provisions a subscriber. The ID is available in the MAG administrative UI, except that you need to eliminate the first four digits from the ID displayed in the MAG administrative UI.
This argument is ignored if the SDK is already running.
Argument
-lang <language code>
Description
Specifies the language and character set (or "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
OSDK61wap.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.
293950: If you do not use the -clearcache argument when you change gateways with the -g argument, the SDK can fail to connect to the gateway due to a secure key-exchange problem. Restarting the SDK with the -clearcache argument should correct this problem. If not, exit the SDK, delete the C:\Program Files\Openwave\SDK 6.1\program\wap\.wapconfig file, set your key state on the MAG to Force, and restart the SDK.
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.
