Rolling Out Devices by Using Software
Packages
Use
You can roll out client devices (Laptops and handhelds) by using software packages if the users of client devices do not need initial data to perform their activities immediately after the device setup is complete. In addition, rolling out devices by using software packages is less time consuming compared to rolling out devices by using setup packages. This is because a setup package also contains the data that must be deployed on devices.
¡ You must use software packages to rollout only SAP Applications.
¡ You must use software packages for initial rollout of devices only and not for upgrade scenarios.
¡ You can execute batch files by using software packages.
Prerequisites
You have:
· Identified the attributes that must be used to register devices with the Data Orchestration Engine (DOE).
More information:
Identifying Device
Attributes for 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. (applicable for handhelds only)
More information:
Downloading
Mobile-Specific Software Units
Procedure
1. Create a software package.
More information: Creating a Software Package
2. 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
3. Assign the mobile components: database, framework, JRE, and the applications that must be deployed on devices to the software package.
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 software package:
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:
■ 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 software package.
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 Software Package
4. Optional: You can assign devices to a software package if required. You can perform this step for administrative purposes based on your requirements. This step is not mandatory.
More information: Assigning Devices to a Software Package
5. Create the installable file using which you can set up devices. After you have created the installable file for a software package, you cannot modify that software package. This means that you cannot assign mobile components, devices, or DM software component versions to the software package.
More information: Creating the Software Package Installable File
6. Create a device profile of type Framework. This step is applicable only for laptops.
More information: Creating a Device Profile of Type Framework
7. Based on your requirements, you can install the software 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
8. Assign the device profile of type Framework to the software package. This step is applicable only for laptops.
More information: Assigning Software Packages to a Device Profile
9. Create the required devices by extracting information related to devices from the back-end system.
More information: Creating Mass Devices
10. Set up devices by downloading the software package to the client devices.
More information: Setting up Devices by Using the Software Package
11. Start and logon to the SAP NetWeaver mobile client after the setup as explained below:
Device |
Activity |
Laptop |
|
Handheld |
12. 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