Management
The following administration tasks are to be performed as and when required:
Task |
Further Information |
Assign device
configurations to groups/users |
The hierarchy reflects your organization structure. You assign device configurations to groups of users. The system automatically assigns the mobile devices used by the users to synchronize. You can also determine which users or roles are allowed to manage the various groups of users. |
You configure: ● The behavior of the SAP MI Client Component on mobile devices ● The mobile components that are to be installed on the mobile device ● The mobile device itself (for example, the start-up parameters and battery capacity monitoring) ● The drivers installed on the mobile device |
|
Using the device removal function, devices are identified that are
no longer used. |
|
● Deployment of mobile components on the server ● Upload of files required for mobile components on mobile device |
|
The following three options are available: ● Assignment using the device configuration (standard) ● Direct assignment to mobile device ● Assignment of user roles |
|
The following options are available: ● Installing the MI Client Component from the Internet ● Installing the MI Client Component using setup packages ● Single and mass installation of MI Client Component on Compact Flash Cards |
|
Edit configuration
data of Smart Synchronization |
Control and start of processing of messages that are exchanged between the mobile devices and the SAP MI Server Component. |
|
Synchronization of data with the back end that the user of the mobile device stored on one or more data carriers . |
Creation of short system messages and distribution to all mobile devices to provide the users with important information (for example, server maintenance times and dates). |
|
The following options are available: ● Installing the MI Client Component using the URL ● Installing the MI Client Component using setup packages ● Single and mass installation of MI Client Component on Compact Flash Cards |
|
If a mobile device no longer exists or the client is no longer used on a particular device, uninstall SAP MI on the mobile device. |
|
You can check the configuration files for the client in the Mobile Administrator. You can determine how often the files are updated and how many versions of the files are stored on the server. |
|
Checking Client and Application Version |
The following options are available in order to check the client and application version: ● On the SAP MI start page, choose Info. ● If the system is not available you can access the client version information in the buildno.txt file in the MI installation directory. |
Transport SyncBO
definitions |
With the migration tool you can transport the SyncBO definitions from one SAP Web AS to another. |
You can delete mobile IDs that are no longer required. |
|
Inconsistencies can occur with type T51SyncBOs between the middleware and back end if one of the two systems crashes. You can use the consistency check to track down and resolve inconsistencies. |
|
As part of a system upgrade, it may be necessary to transport BWAFMAPP entries to a temporary storage medium to update the entries after the upgrade. |
|
Checking SAP MI
Configuration (
|
In the configuration guide you can find all relevant SAP MI configuration information. Use this documentation as detailed configuration reference. |
The following tasks must be completed periodically:
Task |
Further Information |
Delete runtime
history data |
Deletion of obsolete runtime history data from the SAP MI Server Component (as this can have a negative impact on performance). How often this has to be done depends upon various factors, such as: ● The log level setting ● The number of mobile devices ● The frequency with which the mobile devices are synchronized |