PUBLIC

Migration Guide

SAP NetWeaver
Mobile 7.1
Target Audience
System administrators
Technology consultants
Software Developers

Document version: 4.00 March, 2009

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 24
F +49/18 05/34 34 20
www.sap.com

Copyright 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any

SAP, R/3, mySAP, mySAP.com, SAP NetWeaver, xApps, xApp, and

form or for any purpose without the express permission of SAP AG.

other SAP products and services mentioned herein as well as their

The information contained herein may be changed without prior

respective logos are trademarks or registered trademarks of SAP AG

notice.

in Germany and in several other countries all over the world. All other
product and service names mentioned are the trademarks of their

Some software products marketed by SAP AG and its distributors

respective companies. Data contained in this document serves

contain proprietary software components of other software vendors.

information purposes only. National product specifications may vary.

Microsoft, Windows, Outlook, PowerPoint, and SQL Server are

These materials are subject to change without notice. These materials

registered trademarks of Microsoft Corporation.

are provided by SAP AG and its affiliated companies (SAP Group)

for informational purposes only, without representation or warranty of

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,

any kind, and SAP Group shall not be liable for errors or omissions

MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,

with respect to the materials. The only warranties for SAP Group

xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity,

products and services are those that are set forth in the express

Tivoli, and Informix are trademarks of IBM Corporation in the United

warranty statements accompanying such products and services, if any.

States and/or other countries.

Nothing herein should be construed as constituting an additional

warranty.

ORACLE is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the
Open Group.

Disclaimer
Some components of this product are based on Java. Any code

Citrix, ICA, Program Neighborhood , MetaFrame, WinFrame,

change in these components may cause unpredictable and severe

VideoFrame, and MultiWin are trademarks of Citrix Systems, Inc.

malfunctions and is therefore expressively prohibited, as is any

decompilation of these components.

HTML, XML, XHTML and W3Care trademarks or registered

trademarks of W3C, World Wide Web Consortium, Massachusetts

Any Java Source Code delivered with this product is only to be used

Institute of Technology.

by SAPs Support Services and may not be modified or altered in any

way.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used

Documentation in the SAP Service Marketplace

under license for technology invented and implemented by Netscape.

You can find this documentation at the following address:

http://service.sap.com/instguidesnw

Typographic Conventions

Icons

Type Style

Description

Icon

Example Text

Words or characters quoted from

the screen. These include field
names, screen titles,
pushbuttons labels, menu
names, menu paths, and menu
options.

Caution

Cross-references to other
documentation

Recommendation

Example text

Emphasized words or phrases in

body text, graphic titles, and
table titles

Syntax

EXAMPLE TEXT

Technical names of system

objects. These include report
names, program names,
transaction codes, table names,
and key concepts of a
programming language when
they are surrounded by body
text, for example, SELECT and
INCLUDE.

Example text

Output on the screen. This

includes file and directory names
and their paths, messages,
names of variables and
parameters, source text, and
names of installation, upgrade
and database tools.

Example text

Exact user entry. These are

words or characters that you
enter in the system exactly as
they appear in the
documentation.

<Example text>

Variable user entry. Angle

brackets indicate that you
replace these words and
characters with appropriate
entries to make entries in the
system.

EXAMPLE TEXT

Keys on the keyboard, for

example, F2 or ENTER.

Meaning

Example
Note

Additional icons are used in SAP Library

documentation to help you identify different
types of information at a glance. For more
information, see Help on Help
General
Information Classes and Information Classes
for Business Information Warehouse on the first
page of any version of SAP Library.

Migration Guide: SAP NetWeaver Mobile 7.1

Contents
1 Introduction .........................................................................................5
1.1 Backward Compatibility for SAP NetWeaver 2004 and 7.0 ....................................... 5
Backward compatibility on the Data Orchestration Engine (DOE) ...................................... 5
Backward compatibility on the mobile client....................................................................... 6
1.2 About this Document.................................................................................................. 6
1.3 Before You Start ......................................................................................................... 7
1.3.1 Naming Conventions ............................................................................................... 7
1.3.2 SAP Notes for the Migration .................................................................................... 7

2 Migration Step by Step ...................................................................9

3 Preparation .......................................................................................11
4 Installation Process .........................................................................12
5 Migration Process .............................................................................12
5.1 Migrating Application-Specific Information............................................................. 12
5.1 a Migrating Smart Sync Applications ...................................................................... 13
5.1 a.1 Downloading SyncBOs from the NetWeaver 2004 / NetWeaver 2004s Server .... 13
5.1 a.2 Performing Migration Activities in NetWeaver AS 7.1 .......................................... 13
5.1 a.3 Creating Distribution Rules for SyncBOs............................................................. 15
5.1 a.4 Activate the Rules............................................................................................... 19
5.1 b Migrating Generic Sync Applications ................................................................... 19
5.2 Verifying the Migration of the Device Definitions.................................................... 20
5.3 Uploading the Application to the DOE..................................................................... 20
5.3.1 Creating an .SDA file............................................................................................. 20
5.3.2 Uploading the Application to the DOE.................................................................... 24
5.4 Rolling Out Devices .................................................................................................. 24
5.4.1 Assigning Mobile Components to Devices ............................................................. 25
5.4.2 Assigning Mobile Components to a Device Profile ................................................. 26
5.4.3 Assigning Devices to a Device Profile.................................................................... 26
5.4.4 Preparing Setup Packages for Devices.................................................................. 27
5.5 Setting Up Physical Devices .................................................................................... 28
5.5.1 Setup Using the Mass Device Setup Package ....................................................... 28
5.5.2 Setup on a Manual Installation of the SAP NetWeaver Mobile Client...................... 29

6 Reference ..........................................................................................31
6.1 Example: Converting Filters into Rules................................................................... 31
6.2 Example: Web.xml File for MAM 2.5......................................................................... 32

1 Introduction

1 Introduction
This guide provides instruction for upgrading your mobile client solution that runs on
NetWeaver 2004/ 2004s to SAP NetWeaver 7.1 Mobile. Since the system landscape and
software architecture changed, you need to migrate the device definitions to work in the new
environment.
This release includes a new message-oriented system to enable communication between
back-end systems and various mobile devices. Additionally, SAP NetWeaver Mobile
Administrator provides support for deployment of applications to and monitoring of mobile
devices.

1.1 Backward Compatibility for SAP NetWeaver 2004 and 7.0

SAP NetWeaver Mobile 7.1 allows backward compatibility for applications built on SAP
NetWeaver 2004 or SAP NetWeaver 7.0. When you migrate to SAP NetWeaver Mobile 7.1,
you need to make only minor modifications to the application design, but you do not need to
modify the application logic. Migrating to SAP NetWeaver Mobile 7.1, has the following
advantages:
Higher scalability
Support for large data volumes compared to pre
Support for large number of devices
Better performance
SAP NetWeaver Mobile uses qRFCs for data processing. this results in
improved:
Data flow within the NetWeaver AS
Connectivity with the back-end system
Stability and reliability of data transfer
Tools for monitoring
Simplified system landscape as only AS ABAP is required

Backward compatibility on the Data Orchestration Engine (DOE)

As part of migration, the SyncBO definitions are imported to NetWeaver 7.1 as data objects.
Post migration, there is only one form of synchronization (equivalent to Smart Sync in MI).
However, if your application uses generic sync, then you can enable the same behavior in the
DOE.

1 Introduction

Backward compatibility on the mobile client

On the SAP NetWeaver 7.1 mobile client, there is a compatibility layer that enables the MI
applications to run. This layer contains the list of MI application relevant APIs. When there is
call from the application, this layer converts the old APIs accordingly. This is explained in the
following graphic:

Mobile Device
App1

Application still uses

old APIs

App2
Smart
Sync

Persistence

Generic
Sync

Gen/Smart Sync/Pers

Converts API calls

Mobile Client
Data base contains data
objects

JVM

DB
Data Object

1.2 About this Document

Purpose
This document includes information for migrating your applications from SAP NetWeaver
2004 and SAP NetWeaver 2004s. Instructions are provided for migrating both Generic Sync
applications and Smart Sync applications.
Integration
To perform the migration of your existing mobile applications, you need to use the SAP
NetWeaver Mobile Master Guide, the SAP NetWeaver Mobile Migration Guide, and the
Solution Manager for configuration information.
Constraints
For migrating an existing Mobile Infrastructure usage type, you must perform all required
planning and preparation steps before beginning the migration process.

1 Introduction

1.3 Before You Start

In order to migrate your existing mobile clients to SAP NetWeaver Mobile, you must ensure
that you have installed SAP NetWeaver Mobile 7.1 on new hosts and that you have
configured these systems.
More information: SAP NetWeaver Mobile 7.1 Installation Guide and Solution Manager

1.3.1 Naming Conventions

With this release of SAP NetWeaver Mobile 7.1, there are many new terms and names.
These are listed below:
SAP NetWeaver Mobile
With SAP NetWeaver Mobile 7.1, the usage type Mobile replaces the usage type Mobile
Infrastructure.
SAP NetWeaver Mobile defines the mobile-specific tools and software of the Mobile usage
type.
Data Orchestration Engine
The Data Orchestration Engine (DOE) comprises the message oriented middleware
information and data objects and their associated data. It includes the tools for defining the
dependencies and distribution rules for each object before the objects are used in an
application.
Data Orchestration Engine Workbench
The Data Orchestration Engine Workbench is the development area in which you can model
your data objects, apply the flow definition and back-end adapters, create associations and
dependencies, and define distribution rules.
Data object
Data object represents a business object that allows you to stage data relevant for mobile
applications in the NetWeaver AS. A data object comprises:
The processing information in the form of a flow definition
A back-end adapter to exchange data with the back-end systems
A distribution model that ensures data distribution to various receivers
This term replaces SyncBO.
SAP NetWeaver Mobile Administrator
This is a new tool that provides administrators access to the administrator-related functions.
This tool can be accessed through the DOE or through a portal.
The tool provides functions for deploying applications, monitoring client and back end
synchronization activity, and much more.

1.3.2 SAP Notes for the Migration

Read the SAP Notes about migrating before you start to migrate your mobile
solution that resides on NetWeaver 2004/ 2004s. SAP Notes contain the latest
information about the migration as well as corrections to the migration
documentation.

1 Introduction

Make sure that you have the latest version of each SAP Note. You can find the
SAP Notes on the SAP Service Marketplace at service.sap.com/notes or
in SAPNet - R/3 Front End.

SAP Note Number

Description

1040073

SAP NetWeaver Mobile 7.1 composite note for migration

1148756

If you are migrating to SAP NetWeaver Mobile SP03 and want

to avoid backend downtime during intial load, you must
implement this note.

1153702

If you are migrating to SP04 or SP05 and want to avoid

backend downtime during intial load, you must implement this
note.

If you are migrating to SAP NetWeaver Mobile SP06, then there will be no backend downtime
and you do not need to implement any SAP note.

2 Migration Step by Step

2 Migration Step by Step

This section includes a checklist with all actions you have to perform in order to migrate to
SAP NetWeaver Mobile 7.1 and keep your mobile clients running. The actions are in
chronological order, so that you can work through them as a checklist. For more information,
use the links to the descriptions of the actions.
Preparation
Activity
Prepare a new host for installation of the NetWeaver AS ABAP.
More information: SAP NetWeaver Mobile Installation Guide on the SAP Service
Marketplace at service.sap.com/instguidesnw
Prepare a new host (it can be a server or a laptop) for installation of the NetWeaver CE
Developer Studio.
More information: SAP NetWeaver Mobile Installation Guide on the SAP Service
Marketplace at service.sap.com/instguidesnw
Installation Process
Activity
From the SAP Service Marketplace, install the Mobile Plug-Ins on the Developer Studio.
Follow-Up Activities for SAP NetWeaver Mobile Installation
Activity
Configure the Data Orchestration Engine and the NetWeaver Mobile Administrator.
More information: Solution Manager
Migration Process
Activity
Migrate application-specific data from NetWeaver 2004/ 2004s server to the new NetWeaver
AS.
More information: Migration Process
Migrate user details from NetWeaver 2004/ 2004s server to the new NetWeaver AS using
the Central User Administration tool.
More information: Migrating User Details
Migrate the device definitions from NetWeaver 2004/ 2004s server to the new NetWeaver
AS.
More information: Migrating Device Definitions
Upload the application to the DOE.
More information: Uploading the Application to the DOE
Rollout the devices.
More information: Rolling Out Devices
Set up the physical devices.
More information: Setting Up Physical Devices

2 Migration Step by Step

Follow-Up Activities
Activity
Complete the migration of devices.
Stop the connection between the back end and the NetWeaver 2004 / NetWeaver 2004s
servers for mobile applications.

10

3 Preparation

3 Preparation
To prepare for your migration to SAP NetWeaver Mobile, you must ensure that you have
installed and configured the SAP NetWeaver Mobile hosts. When that is complete, you can
begin the migration process from your current NetWeaver AS to the new one.

Back end
Portal

AS ABAP
(MI)

AS ABAP
(Mobile)

Development
Workstation
Mobile Device
Mobile Device
Mobile Device

Diagram: Installation of the Systems

Back end
Portal

AS ABAP
(MI)

AS ABAP
(Mobile)

Development
Workstation
Mobile Device
Mobile Device
Mobile Device

Diagram: Configuration of the Landscape

11

4 Installation Process

4 Installation Process
You must install the necessary hosts for your new landscape, before you start the migration
process.
Install SAP NetWeaver 7.1 AS ABAP.
Refer to the SAP NetWeaver Mobile 7.1 Installation Guide.
Install SAP NetWeaver Developer Studio on a development workstation.
Refer to the Technology Consultants Guide.
Optionally, you can install the following hosts for your landscape:
SAP NetWeaver 7.0 (2004s) AS JAVA
Enterprise Portal 7.0 (2004s)
Following the installation, you must configure the system. Use the Solution Manager to
configure the NetWeaver AS and the SAP NetWeaver Mobile systems.
Refer to SAP Note 1047566 for up-to-date information.

5 Migration Process
Following the configuration, use the migration process to start moving, activating, and
generating the data objects you require for your mobile applications. You also migrate the
devices to the SAP NetWeaver Mobile 7.1 environment in the migration process.

5.1 Migrating Application-Specific Information

Back end
Portal

AS ABAP
(MI)

AS ABAP
(Mobile)

Development
Workstation
Mobile Device
Mobile Device
Mobile Device

Diagram: Migration of Application-Specific Information

12

5 Migration Process

You have to migrate application-specific data based on the type of the application. The
procedures for Generic Sync are different from Smart Sync.
If you are using Generic Sync on your mobile clients, refer to Migrating Generic Sync
Applications section.
If you are using Smart Sync on your mobile clients, refer to Migrating Smart Sync
Applications section.
Prerequisites
You have performed all tasks in the Solution Manager.

5.1 a Migrating Smart Sync Applications

Smart Sync applications are based on the SyncBOs. For migrating the mobile solution that is
based on the Smart Sync applications, you must migrate the SyncBO definitions.
Relationships between SyncBOs are converted into dependencies automatically. Filters used
by the SyncBOs however, must be converted into rules.

The attachments are only supported for 7.1 Mobile applications. The backword
compatible applications cannot make use of this feature.

5.1 a.1 Downloading SyncBOs from the NetWeaver 2004 / NetWeaver

2004s Server
...

1. Log on to the NetWeaver AS 7.0 (2004/ 2004s) server and start transaction
MEREP_MIG.
2. Select Download to File.
3. Specify the SyncBO IDs to be downloaded.

To select more than one SyncBO ID, choose

Multiple Selection in the
SyncBO line. On the Multiple Selection screen, select Multiple selection again.
4. In the displayed list of SyncBOs, select all SyncBOs that you want to include in the
download, and choose
Copy.
5. In the Multiple Selection screen, choose

Copy.

6. Choose Advanced Selection, and select the All Objects indicator.

7. Choose

Execute to start downloading the selected SyncBOs to a file.

8. In the Settings for RFC Destination/Publish field, do not enter any RFC destination and
choose Confirm.
9. In the File Type field, select text files (.txt), and specify the location.

5.1 a.2 Performing Migration Activities in NetWeaver AS 7.1

...

1. Log on to the NetWeaver AS 7.1 and start transaction SDOE_MIGRATION.

2. Under Application Type, select Smart Sync.
3. Under Activities, select the following activities as explained in the table below:
Activity

Description

13

5 Migration Process

Pre-Requisites

The system performs the following checks

whether :
All SAP standard data objects in the SAP
Basis 7.10 SWCV are generated and are
in a consistent state.
The Mobile receiver meta model (RMM)
is generated and the generated classes
are consistent. Use transaction
SDOE_RMM01 to identify the generated
class name and activating / generating
the RMM.
All roles defined in the configuration
guide are available in the system.
All the necessary configuration
parameters have been set up per your
requirements.
All users are available in the DOE.
All the rules in SAP Basis 7.1 SWCV are
active.
The mandatory registration parameters
that are required from the devices at the
time of registration have been setup.
For example, you can set device name and
equipment number as the mandatory
parameters for registration. When mobile
devices synchronize with the DOE for the first
time, they are registered against these
parameters.

User Migration

Transfers the user details from the SAP

NetWeaver AS 7.0 system to the SAP
NetWeaver AS 7.1.
After transferring the user details, you must set
the synchronization role
(SAP_DOE_SYNC_ROLE) to these users. For
detailed information on setting up the users in
the Data Orchestration Engine, refer to the
following information in the help portal:
SAP NetWeaver Mobile Library
Administrators Guide
Configuration
Configuration of SAP NetWeaver Systems
Mobile
Setting Up Users in Data
Orchestration Engine

Device Migration

Transfers the device details from the MI system

to the SAP NetWeaver Mobile 7.1 system.

Trigger initial download

Triggers the initial download for all the data

objects that are created based on the SyncBO
definitions in the MEREP text file

14

5 Migration Process

Activate rules

Activates the rules that are generated for the

software component version that you specify.

4. Under Text File and Software Component Version Details:

a. In the Text File field, enter the path of the MEREP text file.
b. To import the contents of the text file into a new software component version,
select Import into New Software Component Version and enter the name,
vendor, and version for the software component version.
In this case, you also need to specify RFC destination that connects to the
back-end system. You can specify an existing RFC destination or create a new
one. To create a new RFC destination, choose Create New Destination and
enter the required details.
5. Under MI Destination, enter the RFC destination name that connects to the MI system.
You can specify an existing RFC destination or create a new one. To create a new
RFC destination, choose Create New Destination and enter the required details.
6. Choose

Execute.

All SyncBOs and their association information are converted to data objects. The imported
SyncBOs appear on the Data Orchestration Engine Workbench screen. The DOE converts
the filters into distribution rules for SyncBOs that are filtered by only one field. FOR syncBOs
that are filtered by more than one field you need to manually create the distribution rules.
The Synckeys in the DOE are maintained as 32 bit GUIDs.

5.1 a.3 Creating Distribution Rules for SyncBOs

For SyncBOs that are filtered by only one field, the DOE converts the
filters into distribution rules automatically. If the SyncBO is filtered by two or
more fields, you must convert the filters of that SyncBO into rules manually.
As the first step, you must ensure that all SyncBOs that are filtered by only one field have
been converted into rules automatically.
In MI, the distribution of the SyncBOs was maintained by the filters. In the DOE, the
distribution is maintained by distribution models comprised of rules and dependencies. You
create the distribution rules for the data objects. If the application that you are migrating has
SyncBOs that are filtered by two or more fields, you must convert the filters into distribution
rules manually.
In MI, you could create references between the Sync BOs. In DOE, these references are
maintained as distribution dependencies between the data objects.

For the migration process, you must not convert the references to
dependencies. They are generated automatically by the DOE when importing
the SyncBOs
The following steps describe how to set up the Distribution Rules so that distribution of the
data objects behaves in the same way as in the former scenario.
Prerequisites
To create distribution rules you need to be assigned to the role SAP_DOE_DEVELOPER.
You can check this and add the role to your profile, if required, using transaction SU01.

15

5 Migration Process

SyncBOs with filters

Depending on the type of filters used, the steps for converting the filters to rules vary. The
following table provides an overview of the steps that are required to be performed on the
DOE, depending on the filter used. The detail steps are listed later.
Filter

Actions

Referencing SyncBOs

You do not have to create the rules manually.

In the DOE, the Filter by Referencing SyncBOs
relationship is converted into a dependency
automatically.
...

SyncBO ID

1. Create the rule.

2. Select constant type of mapping.
3. Bind the devices to all the attributes in
the Mobile RMM.
...

Mobile ID

1. Create the rule.

2. Select constant type of mapping.
3. Bind the rule to all the Receiver ID
attribute of the Mobile RMM.
...

Mobile Group

1. Customize the Mobile RMM by creating a

Group attribute.
2. Create the rule.
3. Select constant type of mapping.
4. Bind the rule to all the Group attribute of
the Mobile RMM.
...

User-specfic

1. Create the rule.

2. Select device attribute type of mapping.
3. Bind the devices to all the User attribute
of the Mobile RMM.

SyncBO ID + Mobile ID

Perform the actions based on the Mobile ID

filter.

SyncBO ID + Mobile Group

Perform the actions based on the Mobile Group

filter.

Mobile ID + Mobile Group

Perform the actions based on the Mobile ID

and the Mobile Group filters.
That is, when you select the attributes from the
Mobile RMM, you must select both the
Receiver ID attribute and the Group attribute
from the list.

SyncBO ID + Mobile ID + Mobile

Group

Perform the actions based on the Mobile Group

filter and the Mobile ID filter.
That is, when you select the attributes from the
Mobile RMM, you must select both the
Receiver ID attribute and the Group attribute
from the list. This step is same for the Mobile
ID + Mobile Group based filters.

16

5 Migration Process

The fields used in filters are referred to as criteria fields in the DOE. In DOE, when you create
filters for the data object, you must use the Distribution Rule wizard.
...

SyncBO ID Filter
...
...

1. Log on to the NetWeaver AS 7.1 and start transaction SDOE_WB

2. Expand the data object node and navigate to the distribution model.
3. Click the distribution model with the secondary mouse button and choose Add
Rule.

Bulk

The Distribution Rule wizard starts.

4. Enter the rule name and description and choose Continue.
5. Select the fields used in filters and specify the operator.
6. For Device mapping, select none and choose Continue.
7. Select the fields you require, choose Constant mapping, and then choose Continue.
8. Enter the values for each of the criteria fields and choose Continue.
9. For Device binding, select All and choose Continue.
10. Select the Mobile receiver category.
The related events appear.
11. Choose Continue.
12. Choose Finish to create the rule.
The distribution model is shown with the added rule.
Mobile ID Filter
...
...

1. Log on to the NetWeaver AS 7.1 and start transaction SDOE_WB.

2. Expand the data object node and navigate to the distribution model.
3. Click the distribution model with the secondary mouse button and select Add
from the context menu.

Rule

The Distribution Rule wizard starts.

4. Enter the rule name and description, and then choose Next.
5. Select the fields used in filters and specify the operator.
6. In Device mapping, select none, and then choose Next.
7. Select the relevant fields, in Mapping type, select constant, and then choose Next.
8. Enter the values for each of the criteria fields and choose Next.
9. Select the device binding as Device Binding.
10. Choose Device search criteria.
11. Enter a name for the device binding.
12. Select the Mobile RMM and choose Fetch attributes.
13. Select the attribute Receiver ID and use > to move it to the adjacent table.
14. Enter the value for the receiver ID and choose Save.
15. Choose Continue.
The related events appear.

17

5 Migration Process

16. Choose Continue.

17. Choose Finish to create the rule.
The distribution model is shown with the added rule.
Mobile Group Filter
...

Customize the Mobile RMM

...

1. Log on to the NetWeaver AS 7.1 and start transaction SDOE_RMM01.

2. Click the Mobile RMM with the secondary mouse button and choose Create
Customizing Group for RMM.
3. In the Group field, create an attribute called GROUP.
4. In the NetWeaver Mobile Administrator, enter the appropriate values to this group for
the various devices.
Create the Rules
...
...

1. In the NetWeaver AS, 7.1 and start transaction SDOE_WB, expand the data object node
and locate the distribution model.
2. Click the distribution model with the secondary mouse button and choose Add

Rule.

The Distribution Rule wizard starts.

3. Enter the rule name and description, and then choose Next.
4. Select the fields used in filters and specify the operator.
5. In Device Mapping, select none and choose Next.
6. Select the relevant fields.
7. In Mapping type, select constant and choose Next.
8. Enter the values for each of the criteria fields and choose Next.
9. In Device binding, select Device Binding.
10. Choose Device search criteria.
11. Enter a name for the device binding.
12. Select the Mobile RMM and choose Fetch Attributes.
13. Select the attribute GROUP and choose > to move it to the adjacent table.
14. Enter the value for the group and choose Save.
15. Choose Next.
The related events appear.
16. Choose Next.
17. Choose Complete to create the rule.
The distribution model appears with the added rule.
User-Specific Filter
...
...

1. Log on to the new NetWeaver AS, start transaction SDOE_WB

2. Expand the data object node and navigate to the distribution model.
3. Click the distribution model with the secondary mouse button and choose Add
Rule.

Bulk

18

5 Migration Process

The Distribution Rule wizard starts.

4. Enter the rule name and description and choose Continue.
5. Select the fields used in the filters and specify the operator.
In this case, it is the user field present in the data object, and the operator is EQ.
6. In Device mapping, select Device attribute mapping and choose Continue.
7. Select the Mobile receiver category.
8. Select the relevant fields and choose Device attribute mapping.
9. Map the field to the device attribute USER.
The related events appear.
10. Choose Continue.
11. Choose Finish to create the rule.
The distribution model appears with the added rule.
12. Activate the distribution model.

5.1 a.4 Activate the Rules

After you create the rules for the SyncBOs that are filtered by more than one field, you need
to activate these rules.
...

1. Log on to the NetWeaver AS 7.1 and start transaction SDOE_RSM.

2. Select the rules generated for the newly created software component version.
3. Choose Activate.

5.1 b Migrating Generic Sync Applications

To migrate Generic Sync applications, you must create new table entries in the NetWeaver
AS 7.1 system.
The following tables are relevant for generic synchronization applications:
MMWMAPPDEST
This table stores the information about the RFC destination that is used by the DOE to
call the remote function modules present on the back-end system.
MMW_MAPPING
This table stores the mapping between the class method that is called by the Generic
Sync application and the Remote Function Module to be executed on the back-end
system corresponding to this class method.
In the NetWeaver 2004/ 2004s system, if there are entries in the BWAFMAPP and
MEMAPPDEST tables, you must create the same entries in the in the appropriate tables in
the NetWeaver AS 7.1 system. To do this:
...

1. Log on to the NetWeaver AS 7.1 and start transaction SDOE_MIGRATION.

2. Under Application Type, select Generic Sync.
3. Under Activities, select the following activities:
Pre-requisites
User migration
Device migration

19

5 Migration Process

For information on the above mentioned activities, refer to Performing Migration Activities in
NetWeaver AS 7.1
4. Under MI Destination, enter the RFC destination name that connects to the MI system.
You can specify an existing RFC destination or create a new one. To create a new
RFC destination, choose Create New Destination and enter the required details.
5. Choose

Execute.

5.2 Verifying the Migration of the Device Definitions

...

1. Log on to SAP NetWeaver Mobile Administrator and choose Administration

Management
Device Migration.

Device

2. Choose Device Administration and search for all migrated devices.

3. Select all devices and choose Enable.
You can check a device using Device Administration in SAP NetWeaver Mobile
Administrator by searching for the devices by their names. All successfully migrated
devices have the following attribute set:
Attribute Name

Attribute Value

CLIENT_FRAMEWORK_TYPE

JSC

CLIENT_FRAMEWORK_VERSION

7.1

DEVICE_TYPE

LAPTOP

OSVERSION

Taken from the MI device

OSVERSIONVENDOR

Taken from the MI device

QUEUE_NAME

Generated for each new device as

MMW_000***

The name of the device remains as it was in the previous MI system

unless you explicitly renamed it during the migration.
The device status is Initial because it has not yet been registered by the
physical device.

5.3 Uploading the Application to the DOE

Uploading the application to the DOE enables you to distribute the application to multiple
devices. Applications created using SAP MI however, are in a .WAR format. The DOE only
recognizes .SDA format. To upload these applications, you must first convert them to an
.SDA format.

5.3.1 Creating an .SDA file

To create an .SDA file from a .WAR application, you must use the Mobile Developers Kit
(MDK). This plug-in is available with the SAP NetWeaver Developer Studio.
Prerequisites
You are using the MDK in the new NetWeaver environment.

20

5 Migration Process

You have installed the SAP NetWeaver Mobile client on the same SAP NetWeaver
Developer Studio host.
The project archive is available in the local system.
You have configured the settings for connecting to the DOE (Window
MDK).
You have configured the MDK perspective in the IDE. (Window
Other Mobile Infrastructure).

Preferences

Open Perspective

You have applied all the required patches to the application.

If patches for the MI application exist and you want to apply them on the
application, you must apply the patch to the existing format (.WAR) of the
application and then covert it to the .SDA format. You cannot apply patches to
the .SDA format of the application.
Procedure for Generic Sync Applications
1. To import the project archive, start the MDK and choose File

Import.

2. Select Import a MI archive into a new project and choose Next.

3. Select the .WAR file from your file system.
4. Enter a project name and location for storing the project and choose Finish.
5. To change the Mobile Component name and version, choose
general properties for MI project.

Adjust classpath and

6. Select the project and choose Next.

7. In the Create a MI Archive File screen, ensure that only the following indicators are
selected:
Uppercase for MI archive name
Package .class files in the application .jar file
Link on Mobile Webdynpro Client Home Page
Auto Accept Server on Rejection (valid till Support Package 02)
If you are on Support Package 03, then you must select the following options:
Auto Resolve Conflict
Auto Resolve Error

Deselect all other options on the screen.

8. To create the SDA file, choose File

Export.

9. Select Export project into a MI archive and choose Next.

10. In the Create a MI Archive File screen, ensure that only the following indicators are
selected:
Add JSP as compiled classes
Create an SDA archive

21

5 Migration Process

Deselect all other options on the screen.

11. Enter a destination folder for storing the .SDA file.
12. Choose Finish.
The .SDA file is created at the location you specified.
Procedure for Smart Sync Applications
...

1. To import the project archive, start the MDK and choose File

Import.

2. Select Import a MI archive into a new project and choose Next.

3. Select the .WAR file from your file system.
4. Enter a project name and location for storing the project and choose Finish.
The project name ought to match one of the names in the Java folder.
5. To change the Mobile Component name and version, choose
general properties for MI project.

Adjust classpath and

6. Select the project and choose Next.

7. In the Create a MI Archive File window, ensure that only the following indicators are
selected:
Uppercase for MI archive name
Package .class files in the application .jar file
Link on Mobile Webdynpro Client Home Page
Auto Accept Server on Rejection (valid till Support Package 02)
If you are on Support Package 03, then you must select the following options:
Auto Resolve Conflict
Auto Resolve Error

Deselect all other options on the screen.

8. To import the data objects, choose

Import.

The MBO Model Import Page appears.

9. Select a model package and a model name for storing the data objects.

The model package must be included in a package that exists for the
application.
For example, if the package for an MI application is included in com.sap.app,
then you need to select this as the model package.
10. Enter the SWCV that contains the data objects and its version number.
11. Choose List MBOs.
The data objects in the SWCV appear in a list.
12. Choose Import.

22

5 Migration Process

13. Choose Finish.

14. To create the .SDA file, choose File

Export.

15. Select Export project into a MI archive and choose Next.

16. In the Create a MI Archive File screen, ensure that only the following indicators are
selected:
Add JSP as compiled classes
Create an SDA archive

Deselect all other options on the screen.

17. Enter a destination folder for storing the .SDA file.
18. Choose Finish.
The .SDA file is created at the location you specified.
Ensuring correctness in the Web.xml file of the application
The starting page for an MDK application is called by a specific servlet. It is possible for this
servlet to have a user-defined name, and it is possible that this name is different from the one
that is generated by the MDK compiler.
When you deploy this type of application to the SAP NetWeaver Mobile client, the application
does not start. This is because the SAP NetWeaver Mobile client recognizes only the servlet
name generated by the MDK.
You must ensure that the servlet name for the starting page matches the name generated by
the MDK. You can verify this in the Web.xml file of the application following these steps:
...

1. Open the Web.xml file of the application.

The file is located in the path: app_name.sda
app_name.sda
app_name.war
WEB-INF, where app_name is the name of the .SDA application that you just
created.
2. Locate the servlet mapping for the start URL pattern.
The start URL pattern defines the starting page for the application and is in the format
shown below. Here, gen_name refers to the servlet name that is generated by the
MDK.
<servlet-mapping>
<servlet-name>gen_name</servlet-name>
<url-pattern>start</URL-pattern>
</servlet-mapping>
3. Locate the servlet element that defines the starting page element and its usage.
The format for the servlet element is shown below, where cust_name refers to the
name of the servlet and app_start.jsp refers to the starting page JSP. Both of these can
be user-defined.
<servlet>
<servlet-name>cust_name</servlet-name>
<jsp-file> app_start.jsp</jsp-file>
</servlet>

23

5 Migration Process

4. If cust_name differs from gen_name, you must replace cust_name with gen_name.
5. Save the contents of the Web.xml file.
Ensuring getApplicationName() returns the name of the JSP/AWT application
For Backward compatible applications, the value returned by getApplicationName() is
the same as the name of the war/jar file (war file for JSP applications and jar file for AWT
applications).
For JSP applications, getApplicationName() is the method found in the class that
extends com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.
For AWT applications, getApplicationName() is the method found in the class that
implements com.sap.ip.me.api.runtime.Application.
For example:
If the application war file name is MyApplication_PDA.war then the
getApplicationName() must return "MyApplication_PDA".

5.3.2 Uploading the Application to the DOE

After creating the .SDA version of the application, you must deploy it to the DOE. The DOE
defines a state for the mobile component. When you deploy the application, the state is
untested. You have to change the state to tested.
Procedure
...

1. Log on to the new NetWeaver AS and start transaction SDOE_UPLOAD_ARCHIVE.

2. Select the file you want to upload and choose Upload.
3. Log on to SAP NetWeaver Mobile Administrator and choose Administration
Software Package Management
Mobile Component Administration.
4. Choose the newly uploaded application with the correct version.
5. In the Operations screen area, choose Change State.
The Change MCD State popup appears.
6. Select Testing Succeeded and choose Change State.

5.4 Rolling Out Devices

You can roll out client devices (Laptops and PDAs) using setup packages or by installing the
SAP NetWeaver Mobile client on each device manually.

If you are installing the SAP NetWeaver Mobile client on the device, you must
refer to the Solution Manager or the SAP Library Admin Guide for information
on the installation procedure and the configuration steps required.
Setup packages also include the initial data for the users of the client devices. This is
because in a setup package, you can also include data along with all the relevant mobile
components that are required for the devices to be productive. These include:
Database
Framework
JRE (applicable for laptops only)
Mobile applications

24

5 Migration Process

Data

5.4.1 Assigning Mobile Components to Devices

Assignment of mobile components to the devices ensures that the setup packages for the
devices include the mobile components.
If SAP NetWeaver Mobile client is installed on the device directly, then the devices receive
their assigned mobile components on synchronization.
This assignment can be done in one of the following ways:
Direct assignment
Allows you to assign the mobile components and DMSWCVs to each device
separately.
Device profile
Allows you to manage multiple devices simultaneously. A device profile acts as a
template for a set of devices that require the same set of mobile devices, distribution
model software component versions (DMSWCVs), and so on, to be assigned.
Direct Assignment of Mobile Components to Devices
...

1. Log on to SAP NetWeaver Mobile Administrator and choose Device Administration.

2. Search for the device to which you want to assign the mobile component.
3. Choose the device link.
4. In the Operations screen area, choose Manage Mobile Components.
5. In the Search Mobile Components screen area, enter the appropriate mobile
component information.
6. In the Mobile Components Assignment area, select the mobile component and choose
Assign.

Assigning the MCD to the device also assigns the DMSWCVs assigned to that
MCD to that device. If you want to assign additional DMSWCVs to this device,
use the Manage DMSWCVs link on the device details page.
7. Choose Done.
You are prompted for the DMSWCV name that you used while creating the .SDA file.
8. Select the DMSWCV and choose Save.

If you are not prompted for the name, you can assign it explicitly by selecting
Manage DMSWCV on the Device Administration page.
Creating a Device Profile
...

1. Log on to SAP NetWeaver Mobile Administrator and choose Administration.

2. In the Device Management screen area, choose Device Profile Administration
3. In the Search Results screen area, choose

Create Device Profile.

4. In the Device Profile Name field, enter a name for the device profile.
5. In the Description field, enter a description for the device profile.

25

5 Migration Process

6. Select the required device profile type.

7. Choose Create.

5.4.2 Assigning Mobile Components to a Device Profile

...

1. Log on to SAP NetWeaver Mobile Administrator and choose Administration.

2. In the Device Management screen area, choose Device Profile Administration.
3. In the Search Device Profiles screen area, enter the required search criteria and
choose Go.
4. From the Search Results screen area, choose the required device profile.
5. In the Device Profile Operations screen area, choose Manage Mobile Component.
6. In the Mobile Component Assignment screen area, enter the required search criteria
and choose Go.

You can search based on the mobile component name, type, or status. You can
also use the advanced search that provides you with additional parameters for
your search.
7. In the Search Results screen area, select the required mobile components and choose
Assign.

To remove existing mobile components, in the Assigned Mobile Components

screen area, select the required mobile components and choose Remove.
8. Choose Done.
9. If the DMSWCVs are assigned to the assigned mobile component already, then you
are prompted to assign the DMSWCVs to the device profile.
10. Select the Assign option next to the required DMSWCV.
11. Choose Save.
The selected DM SWCVs are assigned to the device profile.

5.4.3 Assigning Devices to a Device Profile

...

1. Log on to SAP NetWeaver Mobile Administrator and choose Administration.

2. In the Device Management screen area, choose Device Profile Administration.
3. In the Search Device Profiles screen area, enter the required search criteria and
choose Go.
4. In the Search Results screen area, choose the required device profile.
The details of the assigned devices, mobile components, DM software component
versions, configuration templates, and client configuration appear.
5. In the Device Profile Operations screen area, choose Manage Devices.
6. In the Assign Devices to Device Profile screen area, enter the required search criteria
and choose Go.
7. From the Search Results screen area, select the required devices and choose Assign.

26

5 Migration Process

To remove existing devices, in the Assigned Devices screen area, select the
required devices and choose Remove.
8. Choose Done.

5.4.4 Preparing Setup Packages for Devices

This procedure describes the final tasks that you need to perform to prepare the setup
packages for each device.
At this stage all your logical devices are present in the SAP NetWeaver Mobile system and
each device has been assigned the software that it requires. The following steps describe
how to trigger the DOE to evaluate the data for each of the devices and associate this data
with the designated devices. Finally, it describes how to create setup packages that have to
be installed on the physical devices to make them functional for SAP NetWeaver Mobile.
...

1. Log on to SAP NetWeaver Mobile Administrator and choose Administration

Distribution Rule Administration.
2. In the Content screen area, specify the filter criteria to search for all the distribution
rules that you created and choose Go.
All rules and the current status for each appear in the table.
3. Select the rules and choose Activate.
When the processing of the rules is finished, the activated rules appear with green
indicators in the Status column.
You now need to extract data to be distributed to the devices.
4. Continuing in the SAP NetWeaver Administrator, choose Operations Handbook.
5. In the Content screen area, choose the Trigger Extract link.
6. On the next screen, provide the search criteria required to search for your devices and
choose Search.
7. In the Search Results screen area, select all the devices and choose Next.
8. On the next screen, choose Trigger Extract
The data extract starts for your devices.

In order to identify the status of the extract, in the SAP NetWeaver

Mobile Administrator start transaction SMQ2 and monitor the queues with
names containing the pattern, /EXTRACT/. These are the queues that
are executing the extract process you triggered. When all the queues are
processed, the data is extracted to the devices.
To view the data to be sent to the device as part of the initial setup, in the
SAP NetWeaver Mobile Administrator, choose Device Administration.
Search for the device and view the details by selecting it. The Device
Status screen area contains a link called View Outbound Queue Details.
When you choose this link, a screen appears displaying all data objects
that have been extracted to the device.

27

5 Migration Process

5.5 Setting Up Physical Devices

Back end
Portal

AS ABAP
(MI)

AS ABAP
(Mobile)

Development
Workstation
Mobile Device
Mobile Device
Mobile Device

Diagram: Migrating the Device to the New System

You start setting up the physical devices in preparation for the device migration. Thereafter,
the devices work in SAP NetWeaver Mobile.
The procedure for setting up the device varies depending how you install the SAP NetWeaver
Mobile client. You can install the client using one of the following methods:
Executing the file that is created using the Mass Device Setup feature of the DOE
Performing a manual installation of the client

5.5.1 Setup Using the Mass Device Setup Package

Prerequisites
Your devices must synchronize with the NetWeaver 2004 / NetWeaver 2004s system
one final time to update their local changes in the back-end system. Once the devices
are consistent with the back-end system, the device owner must not perform any local
changes. Otherwise, data loss can occur.
After meeting the first prerequisite, the devices ought to be reformatted to provide a
completely new system for the installation of the new framework and applications. If
reformatting is not possible, then ensure that all the MI related components are
uninstalled.
Procedure
...

1. Copy the setup for the specific device in the local system to any location.
2. On the mobile device, locate and double-click the MassDeviceSetup.exe file.
The install shield performs the installation in the following sequence:
JRE

28

5 Migration Process

Database
Framework
3. Launch the SAP NetWeaver Mobile Client application from the installed location.
The first screen prompts you for the user name. The user of the device must have the
necessary details and use them for this registration.
4. Enter the details required for login.
If you log on successfully, you are prompted to supply the registration parameters.
These parameters were defined by the administrator and provided to you.
5. Enter the mandatory parameters and choose Register Device.
The next screen prompts you to install the applications that were assigned to the
device.
6. Install these applications.
You can now use the applications offline and later synchronize data with the DOE.
7. Choose the Settings link to specify the synchronization settings.
8. Add the required information:
Host and port for the new system
Client
Proxy settings (if applicable)
9. Save the settings.
The device is now ready to synchronize with the new system.
10. Synchronize the client again to receive the data.

If you have difficulty accessing the application in the SAP NetWeaver Mobile
client, refer to SAP Note 1047324.

5.5.2 Setup on a Manual Installation of the SAP NetWeaver Mobile Client

Prerequisites
Your devices must synchronize with the NetWeaver 2004 / NetWeaver 2004s system
one final time to update their local changes in the back-end system. Once the devices
are consistent with the back-end system, the device owner must not perform any local
changes. Otherwise, data loss can occur.
After meeting the first prerequisite, the devices ought to be reformatted to provide a
completely new system for the installation of the new framework and applications. If
reformatting is not possible, then ensure that all the MI related components are
uninstalled.
You have configured the SAP NetWeaver Mobile client.
You have registered the SAP NetWeaver Mobile client.
Procedure
...

1. Log on to the SAP NetWeaver Mobile client.

2. To install the application, on the Home page, choose Synchronize.
3. After successful synchronization, exit the SAP NetWeaver Mobile client.

29

5 Migration Process

4. Restart the SAP NetWeaver Mobile client.

The SAP NetWeaver Mobile client can take several minutes to start, depending
on the size of the application that is deployed to the client. Do not exit the client
during this time. If you exit, you must reinstall the client and repeat this
procedure.
5. On the Home page of the client, start the application by clicking on the link.
This ensures that the SAP NetWeaver Mobile client creates a request for the
application data. On the next synchronization, the client sends this request to the DOE.
6. To obtain the data, synchronize the client with the DOE.

If you have difficulty accessing the application in the SAP NetWeaver Mobile
client, refer to SAP Note 1047324.

30

6 Reference

6 Reference
6.1 Example: Converting Filters into Rules
The following expression must be realized in the DOE.
Field 1 eq 10 and (field 2 eq 20 or field 3 eq 30)
You realize this expression in the following ways:
...

1. Ignore the operator and values and take the fields alone.
Field 1 and (field2 or field3)
2. Formulate the expression by separating it in terms of the or operator.
Field 1 and (field2 or field3) = (field1 and field 2) or (field1
and field3)
3. Each expression separated by the or operator becomes a rule. So, to realize this
expression you have to create two rules for the data object.
Rule 1: With field 1 and field 2
Rule 2: With field 1 and field 3
4. In the Data Orchestration Engine Workbench, when you create the rules using the
distribution wizard, the wizard prompts you to enter operators and values for the criteria
fields. The operators that you can use are:
Operator

Description

EQ

Equal to

LT

Less than

LE

Less than or Equal to

GT

Greater than

GE

Greater than or Equal to

BT

Between

31

6 Reference

6.2 Example: Web.xml File for MAM 2.5

If you have downloaded the MAM 2.5 application from the SAP Service Marketplace and
created the .SDA version of the application, you obtain the following format of the
application's Web.xml file.
...

1. Open the Web.xml file of the application.

2. Locate the servlet mapping for the start URL pattern, as shown below:

3. Locate the servlet element that defines the starting page element and its usage, as
shown below:

4. The servlet name is different for the two definitions. Therefore, you must replace
MAMStart with mam_0005fstart.

32