SolutionsTools & SDKSupport  



Quick Links
 
WAP Push Quickstart (continued)
 
 
  1. Launch the Push Initiator Tool (PushIT)

    Select Openwave WAP Push Library Java 1.0 --> Push Initiator Tool from the Windows Programs menu to launch the PushIT tool. When the tool launches, a black console window appears before the GUI is displayed. You can minimize the console window since all data is entered via the GUI.

    The PushIT tool GUI launches with the Push Submission screen displayed. The Push Submission screen provides everything you need to send a Push Submission with any payload type. For complete usage guidelines, refer to Chapter 8 of the WAP Push Library Developer's Guide (.pdf).

    To push an Service Indication (aka "Alert") to the simulator, complete the following steps:


  2. Specify the PPG Address

    Select View --> Options from the PushIT pull-down menu to display the Options dialog. Make sure the PPG address field value includes the domain of the Openwave Developer MAG (the default value), as shown here:



    Click on the OK button to confirm.


  3. Specify the Recipient / Subscriber

    Click on the Select button on the Push Submission screen to display the Select Recipients dialog. Click on the New Recipient button to display the Add Recipient dialog.

    Enter your Subscriber ID (see step 3, previous page) in the Recipient field. Click on the Subscriber id radio button to specify the client ID format. When you are done, the Add Recipient dialog should look like this:



    Click on the OK button to confirm. Click on the ">" button to add the new recipient to the recipient list. When you are done, the Select Recipient dialog should look like this:



    Click on the OK button to confirm.


  4. Specify the Push Content Type

    Click on the Add button on the Push Submission screen to display the first page of the Add Content Type wizard. Click on the Service Indication radio button as shown below:



    NOTE: Openwave WAP Push Library supports four types of content, each which can be composed by clicking on the associated radio button:
    • Service Load -- Push a WML deck
    • Service Indication -- Push an alert that links to a WML deck
    • Cache Operation -- Push a WAP cache operation
    • Custom -- Carrier-defined custom content
    For more information on the above content types, refer to Chapter 3 of the WAP Push Library Developer's Guide (.pdf).


  5. Specify the Alert Text and URL

    Click on the Next button to display the next page in the Add Content Type wizard.

    In the Alert text field, enter the text you want to display to the end user when the alert appears on the phone. This should be a short string that identifies the WAP service, e.g. "Openwave News Flash". For more information on how to create user-friendly alerts, refer to the WAP Push Application Style Guide.

    In the Href field, enter a public URL that you know will return a valid WML deck. This could be your own WAP service home page or the Openwave corporate home page as shown below:



    Click on the Finish button to confirm.


  6. Send the Push Submission

    Click on the Preview button on the Push Submission screen to display the Message Preview window. This window contains the actual XML content that will be posted to the PPG when you send the push submission.



    Click on the Close button to dismiss the Message Preview dialog.

    Select View --> PPG Response Window to display the PPG Response window. This window will display the response from the PPG after you send the push submission.

    Click on the Send button on the Push Submission screen to send the push submission.

    If the push submission is successful, the PPG Response window will display a successful response from the PPG. If the PPG does not respond, see the Appendix on troubleshooting.


  7. View the Alert

    Re-launch SDK 5.1 if it isn't already running. If the alert was successfully delivered by the PPG to the phone simulator, Mobile Browser displays the following message containing the alert text:



    If you select View, the browser fetches the alert URL (e.g. the Openwave home page).

    If the alert does not appear, see the Appendix on troubleshooting. Otherwise, congratulations on successfully sending and receiving WAP Push content using Openwave SDK and WAP Push Library!




Appendix: Troubleshooting



This section provides troubleshooting tips for the most common problems encountered with the WAP Push development environment. If you still cannot resolve your problem after reading this section, visit the WAP Push FAQ and Discussion Area on the Openwave Developer Forum.
  • No response from the PPG

    If the PPG does not respond, make sure that your PC is connected to the Internet and can access the PPG address. Try entering the PPG address using a conventional Web browser (Netscape or IE):


    http://devgate2.openwave.com:9001/pap

    If you can access the URL, the web browser will display either a blank page or the error message:


    Bad Request. Not understood due to malformed syntax. Error 0x3 : HTTP Syntax Error, Service only provides support for HTTP POST methods.

    The above message is normal, since the PPG rejects anything other than a well-formed WAP push request.

    If you get a 404 Not Found error, then you need to contact your network administrator and make sure that your firewall is configured to allow outgoing HTTP requests to port 9001.


  • Alert not delivered from the PPG to the phone simulator

    If the alert does not appear on the phone simulator, first try restarting the simulator by selecting Simulator -> New Session from the SDK pull-down menu. If the alert does not immediately appear, click on the Status Query button in the PushIT tool icon menu to display the Status Query screen. Send a Status Query to the PPG using the same Push ID that was generated for the previous Push Submission. For instructions on how to interpret the Status Query response, refer to Chapter 7 of the WAP Push Library Developer's Guide (.pdf) under the section: Examining the PPG Response Message.
<< Previous

 
Copyright © 2000-2008 Openwave Systems Inc.    Openwave  |  Terms & Conditions  |  Privacy Policy