Rolling Out Devices by Using Setup Packages 

Use

You can roll out client devices (Laptops and Handhelds) by using setup packages if the users of client devices need initial data to perform their activities immediately after the device setup is complete. 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

·        Data

○       You must use setup packages to rollout only SAP Applications.

○       You must use setup packages for initial rollout of devices only and not for upgrade scenarios.

○       You can execute batch files by using setup packages.

Prerequisites

You have:

·        Identified the attributes that must be used to register devices with the Data Orchestration Engine (DOE).

More information: Identifying Attributes for Device Registration

·        Uploaded the required mobile components such as database, framework, JRE, and applications to the Data Orchestration Engine (DOE).

More information: Uploading Mobile Client Archive to DOE

·        Tested the mobile components by deploying them on a test device and changed their state to tested.

More information: Changing the State of a Mobile Component

●      You have installed NSICom CrEme 4.1 on the Handheld device. (applicable for Handhelds only)

More information: Downloading Mobile-Specific Software Units

Procedure

       1.      To deploy mobile components, such as database, framework, JRE, and applications on multiple devices, you can create a device profile of type Application and assign the mobile components to it. As a result, you are not required to deploy these mobile components to individual devices.

More information: Creating a Device Profile

       2.      The configuration information related to the database and framework is available as part of the device profile of type Framework. Therefore, you must create a device profile of type Framework to ensure that this information is transferred to devices. This step is applicable only for laptops.

More information: Creating a Device Profile of Type Framework

       3.      Optional: Based on your requirements, you can install the setup package on a different partition, such as D:\ or E:\. This step is applicable only for laptops.

More information: Installing the Package on a Different Disk Partition

       4.      Optional: Based on your requirements, you can configure the setup properties of mobile components. This step is applicable only for laptops.

More information: Maintaining Properties of a Mobile Component for Device Setup

       5.      Assign the mobile components: database, framework, JRE (applicable for laptops only), and the applications that must be deployed on devices to the device profile of type APPLICATION.

If you are rolling out laptops, then you must assign the SETUP_WIN32 mobile component as the framework.

If you are rolling out handheld devices, you require the following mobile components:..

...

...

                                                  i.       JVM - You need to manually install the CrEme 4.1 on all the handheld devices.

The installable for the CrEme JVM is available from NSIcom's web site.

Assign the following mobile components to the device profile of type application:

                                                ii.       Database IBM DB2e 9.1

For information on how to download DB2e, refer to the section on downloading mobile-specific software units mentioned above.

To upload IBM DB2e to the Data Orchestration Engine (DOE), you must extract the zip file that you downloaded from the service marketplace, navigate through the folders, and upload the two .SDA files.

Note: When you are uploading the SDA files by using transaction SDOE_UPLOAD_ARCHIVE, do not use the Switch Screen to Upload Non SDAs option. After you upload the .SDA files, the corresponding mobile component is assigned the name DB2E_PPC. To assign the IBM DB2e to the device profile, you must search for this mobile component.

                                               iii.       PDA_CORE 71XXYY

The significance of the digits in the version of the PDA_CORE framework is as follows:

■       First two digits – indicate the release number of the SAP NetWeaver release

■       Next two digits – indicate the support package level

■       Last two digits – indicate the patch level (if any)

                                               iv.       Search and assign one of the following containers to the device profile:

■       AWT container skeleton for AWT applications

■       JSP container skeleton for JSP applications

To do this, you must search for mobile components of type SKELETON.

■       For eSWT applications, you must assign the following components, OCA_RT, WDLContainerUI, and eSWT_PPC.

                                                 v.       Search and assign mobile components of type APPLICATION to the device profile.

You must assign an AWT application for an AWT container, a JSP application for a JSP container, and an eSWT application for an eSWT container.

More information: Assigning Mobile Components To a Device Profile of Type Application

       6.      Create an agent configuration.

More information: Creating an Agent Configuration

       7.      Add the required agents to the agent configuration. You must add the CONFIG agent with values for the following parameters:

○       com.sap.tc.mobile.sync.http.host

○       com.sap.tc.mobile.sync.http.port

○       com.sap.tc.mobile.sync.client

○       com.sap.tc.mobile.sync.protocol

For the above-mentioned parameters, you must set the values of both the SET and GET parameters to TRUE.

More information: Adding Agents to an Agent Configuration

       8.      Assign the configuration template you created to the device profile of type Application.

More information: Assigning Agent Configurations to a Device Profile

○       You can update the device profile details in the back-end system. As a result, when you create the devices in the next step, the device profile is assigned to all the devices.

○       The attributes related to data distribution can be assigned to devices in the back-end system.

       9.      Create the required devices by extracting information related to devices from the back-end system.

More information: Creating Mass Devices

   10.      Optional: If you have not assigned both the device profiles to the devices in the back-end system, then you must manually assign the device profiles to all the devices that are created in step 9.

More information: Assigning Devices to a Device Profile

   11.      Optional: If you have not assigned the attributes related to data distribution in the back-end system, then you can manually assign them to all the devices that are created in step 9.

More information: Modifying the Attributes of a Device

   12.      Set up devices by downloading the setup package to the client devices.

More information: Setting up Devices by Using Setup Packages

   13.      Start and logon to the SAP NetWeaver mobile client after the setup as explained below:

Device	Activity
Laptop	Logging On to Mobile Client for Laptops
Handheld	Logging On to Mobile Client for Handhelds

   14.      Specify values for registration relevant attributes and register the device with the DOE. This step is applicable only for Laptops.

More information: Registering the Client Device