SUP: Personalization Keys and Synchronize Parameter Applies to: Blackberry Mobile. For more information, visit the Mobile homepage. Summary This article gives a brief idea about Personalization Keys and Synchronize Parameter used while creating MBO in Sybase Unwired Platform with examples. Author: Naveen Subramani Company: Applexus Technologies (P) Ltd. Created on: 30 December 2010 Author Bio Naveen Subramani is working as SAP Technical Consultant in Applexus Technologies (P) Ltd. He has an experience in SAP ABAP, Sybase Unwired Platform and Netweaver Developer Studio 7.1. 2010 SAP AG 1
Table of Contents Business Scenario... 3 Introduction... 3 Personalization Keys... 3 Synchronize Parameter... 3 Demo Application... 4 Creating the Mobile Application Project.... 4 Creating the Mobile Business Object... 4 Creating Personalization Keys For MBO.... 7 Deploying the Mobile Business Object to the Unwired Server.... 8 Creating UI using Device Application Designer.... 9 Generating Device Application.... 10 Related Content... 13 Disclaimer and Liability Notice... 14 2010 SAP AG 2
Business Scenario Introduction Sybase Unwired Platform is a mobile enterprise application platform that enables enterprise developers to simply and quickly build applications that connect business data to mobile workers on any device, at any time. With the Sybase Unwired Platform you can create and manage multiple mobile applications that securely connect a variety of back-end data sources to all major device types. Sybase Unwired Platform Speeds mobile application development. Supports heterogeneous mobile device types. Ensures your investment in mobility is future-proof. Personalization Keys Personalization keys allow the mobile user to define (personalize) certain input field values within the mobile application, by associating a name (key) with a simple or complex data type value. Mobile development supports two types of personalization keys: User-defined you can define these when developing a mobile business object. Before using these keys in a device application, each user sets their own values. For example; name, address, zip code, Currency, location, customer list, and so on. System defined (username/password) refers to the user's login credentials used to access enterprise information system (EIS) data. Unlike preference attributes, username/password is readonly and reset each time the user logs in or changes their password. The values are typically used as personalization attributes or other data source runtime credentials. Synchronize Parameter Synchronization parameters filter consolidated database (CDB) data during device application synchronization. In other words allows the developer to limit the data that is returned to the device. It also maps to an attribute. In Simple words: Synchronization parameters control the amount of data to be sent to the mobile Device 2010 SAP AG 3
Demo Application Creating the Mobile Application Project. Start Sybase Unwired Workspace and select New then Mobile Application Project in the File menu to create a new project. Type in the project name (i.e. Flight) then clicks Finish. Creating the Mobile Business Object. 1. Right Click on the Mobile Application Diagram and Select Add Mobile Object. A mobile business object defines the domain-specific objects for a mobile application. It is used to Build relationships, and combine virtual artifacts into groupings, which contain attributes, relationships, operations and parameters. The attributes of a mobile business object can be persisted in a back-end data source. This mobile business object can be implemented using a SQL statement or a remote operation. 2010 SAP AG 4
2. Choose Next and give MBO name as FlightDetails. 3. Give the Data Source Type SAP and Connection Profile. Click Next, and this will make connection to the SAP R/3. 4. Choose the BAPI/ RFC Operation by clicking the Browse Button and give BAPI_FLIGHT_GETLIST 2010 SAP AG 5
5. Select parameters for mapping. 6. Click Next and then Finish. Now the created Mobile Business Object will be visible on the Mobile Application Diagram of the project. 2010 SAP AG 6
Creating Personalization Keys For MBO. 1. Right click on Personalization Keys in Workspace Navigator and select New-> Personalization Key. 2. Give Name and Type for Personalization Key. Click Finish. 2010 SAP AG 7
3. Assigning personalization key to Synchronization Parameter. Right-click on Mobile Business Object and Choose Show Properties View. In Properties Assign the personalization key to Synchronization Parameter. Deploying the Mobile Business Object to the Unwired Server. Right Click on the Mobile Application designer, choose Deploy Project. In this step we are deploying the Mobile Business Object to the Unwired Server as a deployment unit generated from a design-time deployment package using Sybase Unwired Workspace. When we deploy the MBO to the Unwired Server, we are deploying MBO attributes, operations, connections, role mappings, schedule groups, cache groups as defined in the package. Custom code related to this MBO will also get deployed. 2010 SAP AG 8
Creating UI using Device Application Designer. Enter the File Name as Flight.bob 2010 SAP AG 9
Generating Device Application. In order to generate the UI application, select Flight.bob, right click and select Verify to check for errors. Then choose Generate Device Application. In Generate Device Application Wizard select the Device Platform as Blackberry and click Finish. Now Blackberry Simulator got displayed. 2010 SAP AG 10
Choose the Application. Then enter the username as supadmin and password as s3padmin. Select Personalization from Tables of Content. Enter Value (eg. DL) and choose Update. 2010 SAP AG 11
Now all the details of Air-Id DL get displayed. 2010 SAP AG 12
Related Content Managing Personalization Keys Sybase Unwired Platform Mobile Enterprise For more information, visit the Mobile homepage. 2010 SAP AG 13
Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document. 2010 SAP AG 14