Implementing Mobile
Scenario
Purpose
In this process, you implement a mobile scenario. This can be either a customer-specific scenario or a standard scenario from SAP.
Use of the Process
This IT process is part of the following IT scenario:
IT Scenario |
Scenario Variant |
Prerequisites
You have installed the SAP NetWeaver Application Server and have carried out the necessary post-installation steps for NetWeaver Mobile.
Process Flow
The functional units for this process are Data Orchestration Engine and SAP NetWeaver Mobile Administrator.
...
1. Install and configure back-end content. (Back-end system)
2. Import metadata. (Mobile)
The data objects are imported into the Data Orchestration Engine (DOE) using the standard ABAP transport mechanism.
3. Configure back-end connectivity. (Mobile)
Administrators create the required RFC destinations.
4. Execute initial load of consolidated data store. (Mobile)
Administrators retrieve data from the backend systems, and store it in the consolidated data store of the DOE.
5. Configure data distribution logic. (Mobile)
In this step, the developers define the data distribution logic.
6. Activate runtime. (Mobile)
All the changes in the DOE need to be activated to take effect.
7. Import mobile component archives and define device profiles. (Mobile)
Administrators upload mobile components that are used by SAP NetWeaver Mobile client to the DOE. Different mobile components are grouped together into device profiles. This makes the assignment easier. The distribution model software components also need to be assigned to the device profiles.
Result
You have implemented a mobile scenario into your landscape. You must now complete the Executing Device Rollout process.