Entering content frame

Background documentation Mobilizing Business Processes Locate the document in its SAP Library structure

Before the end user can work with SAP Mobile Infrastructure (SAP MI), you as consultant or system administrator must configure various technical components, upload data from the back-end system, and edit master data.

The IT scenario Structure linkMobilizing Business Processes consists of the following IT scenario variants:

IT Scenario Variant

Configurations to Be Performed

IMGs to Be Executed

Structure linkEnabling Mobile Applications for Occasional Connection

Yes

(see next section)

Yes

(see SAP Solution Manager)

Structure linkRunning Mobile Applications with an Online Connection

No

No

SAP Notes

Read the SAP Notes about configuration before beginning the installation. These SAP Notes contain the most recent information regarding the installation and configuration, as well as corrections to the configuration documentation.

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

List of Related SAP Notes

SAP Note Number

Description

925569

SAP Mobile Infrastruct. 7.0 SP07 - Composite Note

Overview of Configuration Steps

The following configuration steps are necessary for the IT scenario variant Enabling Mobile Applications for Occasional Connection:

     Configuration of SAP NetWeaver (Once Only)

After the SAP NetWeaver Application Server has been installed, you configure it and prepare the installation of the mobile devices. You configure the following areas:

     General Settings (for example, setting up background jobs, role editing)

     Configuration of Mobile Administrator

     Configuration of Smart Synchronization

     Configuration of the Computing Center Management System

     Configuration of Mobile Applications (for Each Mobile Application)

You must carry out additional configuration steps for each mobile application. You can find general information on these configuration steps under Configuration of Mobile Applications. For detailed information, see the installation instructions for the respective mobile application.

     Administration of Mobile Components

The files for the mobile components have to exist on the server so that the system can deploy them on the mobile device. For more information about the different types of mobile components and about the procedure involved, see Administration of Mobile Components.

     Test Installation of Single Mobile Device

You can install and configure an individual mobile device for test purposes. For more information about the process, see Test Installation of Single Mobile Device. Use this process to install single mobile devices for test purposes only. If you want to install devices for other users, use the other installation methods (see Installing SAP MI on the Mobile Device).

     Assignment of Mobile Components to Users

When assigning mobile components to users you have various options. The option you choose to use depends on your administration concept. For more information, see Assignment of Mobile Components to Users.

     Configuration of Mobile Devices

You can configure mobile devices, the behavior of SAP MI on the mobile device and the drivers installed there. For more information about the various methods, see Configuration of Mobile Devices.

     Installation of SAP MI on the Mobile Device (for Each Mobile Device)

Either you or the user of the mobile device install the client (SAP MI Client Component) on each mobile device using one of the described methods. After the installation has been completed, the device has to be synchronized twice to download the mobile applications and the application data for the user. For more information, see Installing SAP MI on the Mobile Device.

     Configuration of Security Functions

You can adjust the security settings to meet your requirements. For more information about the different security functions, see Configuration of Security Functions (Optional).

 

Leaving content frame