Show TOC Start of Content Area

Procedure documentation Composing and Testing the Application  Locate the document in its SAP Library structure

Use

To deploy your mobile application, you can choose to deploy the Mobile UI Component directly or to first explicitly compose the mobile application from the components and then to deploy the composed result.

Prerequisites

You have created components:

      Mobile Service Component

      Mobile UI Component

Procedure

1. Create a Development Component and Define its Dependencies (Optional)

...

       1.      Create a new Mobile Application by choosing New Mobile Application.

This opens the Application Explorer. Use order_app as name of the development component.

       2.      Define the dependencies to the Mobile UI and Mobile Service Components (order_ui and order_srv). by selecting the mobile application and choosing Define Dependencies on the context menu.

2. Define the Start-Up Application (Optional)

...

       1.      In the Application Explorer, choose Manage Startup Applications from the Startup Application context menu.

       2.      In the Select UI Component dialog box, choose the application OrderApp, which is to be started on the launch pad of the client.

3. Build, Deploy, and Run the Application

...

       1.      If you are using a mobile application for composition, open the Application Explorer and select application order_app.

If you are not using a mobile application for composition, open the UI Explorer and select the mobile UI component order_ui.

       2.      Open the context menu and choose Development Component Build.

       3.      In the context menu, choose Deploy.

       4.      In the context menu, choose Run as Mobile Application.

4. Use the Application

...

       1.      In the new Java window showing the desktop installation of the Mobile Client for Handhelds, choose Menu New User.

       2.      Create a new user by adding a user name and password.

Note

If you intend to synchronize with the Data Orchestration Engine, the user name needs to be identical to the user name on the DOE. The password can differ though since you are entering a local logon password here. Only during synchronization, will you be prompted for your synchronization password, which is your real DOE password.

       3.      In the application launcher, start the application by clicking its icon.

The application appears, but shows no data. This is because the query is executed with “” as a longtext parameter.

       4.      Enter % and choose the search button to show the complete table, then enter another text, such as repair and choose the search button to show a filtered list.

       5.      In the table control, drag the right delimiter of column longtext to the right to display more text. In the upper right corner of the table, choose the triangular arrows and then created at to display alternative columns that cannot be displayed due to limited screen size.

       6.      To synchronize with the DOE, maintain the sync settings that you can access in the menu by choosing Manage Device Settings Sync Settings (optional).

The host and port information is identical to that maintained as DOE settings in the IDE configuration at the beginning of the tutorial. After maintaining the sync settings, you can choose Sync on the menu. However, this will only succeed, if a device has been created on the DOE.

5. Debug the Application

...

       1.      Open the Service Explorer and choose service orderService.

       2.      In the context menu, choose Open with Java Editor.

       3.      Scroll to the implementation of query getOrdersByLongtext() and set a break-point by double-clicking to the left of any line.

A blue circle appears.

       4.      Choose Run Debug.

Result

You have completed the tutorial by creating a Mobile Application for Handhelds, which youhave deployed, run, and debugged.

Recommendation

We recommend that you examine the code in detail and add a secondary page.

To do so, you simply use standard Web Dynpro tools and concepts – no mobile-specific development is involved. These are the required steps:

...

                                                  i.       Add a new view orderDetails.

                                                ii.       Create its context through context mapping with the component controller.

                                               iii.       Apply the form template to the view, using the output structure of getOrderByLongtextnode of the context as data binding source.

                                               iv.       Use the window editor to:

        Add the view to window orderWindow.

        Create inbound plugs fromOrderList in view orderDetails and outbound plugs toOrderDetails in orderList view.

        Create a navigation link between the views from outbound plug to inbound plug.

                                                 v.       In the view editor of orderList, add button to Details and create a new action for it in the properties pane.

When the button is clicked, it should fire the outbound plug.

 

End of Content Area