Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Migration Guide
SAP NetWeaver
Mobile 7.1
Target Audience
System administrators
Technology consultants
Software Developers
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
form or for any purpose without the express permission 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
any kind, and SAP Group shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express
Disclaimer
Some components of this product are based on Java. Any code
Any Java Source Code delivered with this product is only to be used
Institute of Technology.
Typographic Conventions
Icons
Type Style
Description
Icon
Example Text
Caution
Cross-references to other
documentation
Recommendation
Example text
Syntax
EXAMPLE TEXT
Example text
Example text
<Example text>
EXAMPLE TEXT
Meaning
Example
Note
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
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 Introduction
Mobile Device
App1
App2
Smart
Sync
Persistence
Generic
Sync
Gen/Smart Sync/Pers
Mobile Client
Data base contains data
objects
JVM
DB
Data Object
1 Introduction
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.
Description
1040073
1148756
1153702
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.
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
Back end
Portal
AS ABAP
(MI)
AS ABAP
(Mobile)
Development
Workstation
Mobile Device
Mobile Device
Mobile Device
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.
Back end
Portal
AS ABAP
(MI)
AS ABAP
(Mobile)
Development
Workstation
Mobile Device
Mobile Device
Mobile Device
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.
The attachments are only supported for 7.1 Mobile applications. The backword
compatible applications cannot make use of this feature.
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.
Copy.
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.
Description
13
5 Migration Process
Pre-Requisites
User Migration
Device Migration
14
5 Migration Process
Activate rules
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.
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
Actions
Referencing SyncBOs
SyncBO ID
Mobile ID
Mobile Group
User-specfic
SyncBO ID + Mobile ID
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
...
...
Bulk
Rule
17
5 Migration Process
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.
Bulk
18
5 Migration Process
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.
Device
Attribute Value
CLIENT_FRAMEWORK_TYPE
JSC
CLIENT_FRAMEWORK_VERSION
7.1
DEVICE_TYPE
LAPTOP
OSVERSION
OSVERSIONVENDOR
QUEUE_NAME
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
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.
Export.
21
5 Migration Process
1. To import the project archive, start the MDK and choose File
Import.
Import.
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
Export.
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".
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
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
...
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
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.
26
5 Migration Process
To remove existing devices, in the Assigned Devices screen area, select the
required devices and choose Remove.
8. Choose Done.
27
5 Migration Process
Back end
Portal
AS ABAP
(MI)
AS ABAP
(Mobile)
Development
Workstation
Mobile Device
Mobile Device
Mobile Device
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.
29
5 Migration Process
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
GT
Greater than
GE
BT
Between
31
6 Reference
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