Home : Tools & SDK : Ide Integration : Ibm : IBM
 

IBM Websphere Studio

 

You do this by configuring Websphere Studio to take advantage of the command-line arguments supported by Openwave SDKs 4.1.1, 6.1, and 6.2.x. (These Openwave SDKs are available for download on the Phone Simulator page.)

Openwave SDK 4.1.1 contains a simulator for Openwave mobile browser 4.1, which adheres to the WAP 1.1 standard and renders content in WML. SDK 6.1 and 6.2.x contain Openwave mobile browser 6.1 and 6.2.x respectively, which adhere to the WAP 2.0 standard and render content in XHTML Mobile Profile and CSS. You can use any combination of simulators, depending on your needs and the target devices for your market. For details on browser capabilities and device deployments, see Supported Phones.

On the Openwave side, this document describes integrating and working with SDK 6.1, but you can easily substitute the paths and names for SDK 4.1.1 or SDK 6.2.x to work with those simulators instead.

On the IBM side, the rest of this document describes Websphere Studio Application Developer (WSAD), but similar steps can be taken with the other tools in the Websphere Studio family, including Eclipse.

Requirements

• Websphere Studio Application Developer (WSAD) V5, or similar
• Openwave SDK 4.1.1, SDK 6.1, and/or SDK 6.2.x

Integrating an Openwave simulator with WSAD

Configure the Openwave simulator as the Web Browser in WSAD.

1. Start WSAD.
   
   
2. Open or create a web project, HTML/XHTML File, JSP File, Servlet or any other project/file that will target mobile devices.
   
   
3. From the Window menu, select Preferences.
   
   
4. In the  Preferences dialog box, click Web Browser on the left pane and then click on the Use external Web Browser radio button.
   
   
5. In the Location field, enter the SDK simulator's application path name, or click Browse... to browse to it.
   
   If you installed the SDK in the default location, the path name is:
   
   "C:\Program Files\Openwave\SDK 6.1\program\http\OSDK61http.exe"
   
   
6. In the  Parameters field, enter -reload %URL%.
   
   
   
   
7. Click OK.
   

Testing with the Openwave simulator

To test your applications with the Openwave simulator in WSAD, select Run on Server or Debug on Server .  These options are available in the toolbar or by right-clicking your content page.

The Openwave simulator starts with two windows:  the phone information window and the main simulator window.  Either window may launch minimized or in the background, so you may have to bring it to the foreground.

As you debug and make changes, you can again select Run on Server to update the running simulator and pass it the URL you are currently working on. This way you can test your current page or move between pages.

You can also navigate using the Openwave simulator itself, selecting links or entering URLs in the simulator's "Go" field.

Controlling a running simulator with WSAD

You can create menu items in WSAD that send command-line arguments to a running Openwave simulator.

The simulator features a number of command-line arguments, such as -clearcache to clear the simulator's cache, -pho to change the simulator's configuration file (or "skin"), and -lang for changing the language, character set, and related localization settings the simulator sends in ACCEPT headers to web servers. For a complete list and description of simulator command-line arguments, see the Openwave SDK release notes.

1. Select Run > External Tools > Configure... and in the External Tools Configuration dialog box, click New....
   
   
2. In the Name field, enter a name for the new menu item.
   
   
3. In the Tool Location field, enter the SDK simulator's application path name, or click the Browse File System...button to browse to it.
   
   If you installed the SDK in the default location, the path name is:
   
   C:\Program Files\Openwave\SDK 6.1\program\http\OSDK61http.exe
   
   
4. In the Tool Arguments field, enter an Openwave simulator command-line argument.
   
   Because the simulator accepts only one argument at a time when it's running, you need to create separate menu items for each command-line argument you want to pass to the simulator.
   
   
5. The rest of the fields in this dialog page are not important and you can leave them blank or enter an appropriate value.
   
   
   
   
6. Click OK.  Click OK again to close the External Tools Configuration dialog box. 
   
   The menu item is added to the Run > External Tools menu.

Notes

In SDK 6.1, you can optionally start the simulator without the Phone Information window by adding the -noconsole command-line argument to the end of the Parameters field in the Preferences dialog box. 

In SDK 4.1.1, because of an issue with the phone information window, you have to launch the simulator outside of WSAD and then use the Run on Server command to refresh content.

The integration instructions use the -reload %URL% command-line argument, not -go %URL%, because -reload invalidates the URL in the simulator's cache before loading it, forcing the simulator to get the latest version. This is useful when you are debugging and want to load the latest content. If you would rather always start from the home page (or your start page), then just use -reload without %URL% .

There are some Openwave simulator command-line arguments that you can only use when you start the simulator, and there may be some that you want to set as defaults (for example, the default language or default simulator configuration file, or "skin"). In these cases, you can start the simulator using a batch file with all the arguments you need. One way to to this is to edit the batch file called when you start the simulator using its Start menu item, C:\Program Files\Openwave\SDK 6.1\program\OSDK61http.cmd .  For details, see the Openwave SDK release notes.