Mobile Component Descriptor 
Use
The Mobile
Component Descriptor (MCD) describes the properties of an application,
framework, or add-on that is to be used as a mobile component in the
SAP MI. If you are using the old technology and the
Web Console, with an MCD you can also define the order in which the mobile
components should be installed on the mobile device. See 
Defining the
Installation Sequence (Optional).
However, if you are using the Mobile Administrator, you define the order of the installation using device configuration (see Defining the Installation Sequence).
The developer of the framework, application, or add-on usually creates the corresponding MCD. It is shipped together with the installation file. If there is no corresponding MCD, you as a customer or consultant can also create it.
Existing MCDs are displayed in the SAP MI Web Console under Upload Applicationor in the Mobile Administrator under Mobile Components.
Features
The MCD contains the following required information:
Required Fields
Field |
Meaning |
Mobile Component |
Technical name of the mobile component The name of the mobile components can only contain the following characters: a-z, A-Z, 0-9, _. |
Version |
Version of the mobile component. The version has 1 – 6 positions, is of type Character and can be defined as you like. The version description can also include a period (.). |
Version for Role-Based Assignment |
Do not make the setting here, instead, do it while uploading the component. If there are different versions of the applications, the administrator can mark one version. This version is then automatically used in role editing. There is no input field for the version in the role editor. |
Description |
Description of the mobile component. |
Component Type |
Application: Mobile business application Framework: Runtime environment for mobile applications Add-On: Additional generic functions, for example, a DLL JVM: Java Virtual Machine for PDAs SSL: File for using the Secure Sockets Layer (see SAP Note 580497) INSTALL_SEQUENCE: Installation sequence defining the order for installation. Use the component type only if you are working with the old technology (Web Console). |
Runtime Environment |
JSP: If you want to upload Web-based applications. AWT: If you want to upload Abstract Window Toolkit (AWT) based applications. MicroITS: If you want to upload MicroITS-based applications. |
Link to SAP MI start page |
Choose Yes, if an application should appear as a link on the personal start page in the SAP MI. For all other component types choose No. |
If you are an application developer, you can also define other settings if required.
Optional Settings
The number of tab pages displayed depends on the component type selected.
Tab Page |
Description |
SyncBO |
SyncBOs that are needed by the mobile component and their properties. Here you can define whether application data should be visible for all users of a device and how to proceed if an error or conflict occurs. |
Deployment |
Path from which the files are downloaded at deployment. Do not make any entries here. The administrator must specify the path for the download. |
Link |
Other mobile components that are needed by this mobile component and that might need to be installed. When you define an installation sequence, you define the order in which the components should be installed on this tab. Use the definition of an installation sequence only if you are working with the old technology (Web Console). |
Languages |
Languages in which the mobile component is available. |
Framework |
Framework that must be installed in order for the mobile component to be installed. You can also define an area here. |
Environ. |
Conditions that must be satisfied for the mobile component to be installed. |
Authorizations |
Authorization objects needed by the user to allow the mobile components to be installed. |
Activities
With Transaction MI_MCD you can create new MCDs and search for MCDs by defining areas and by using * (asterisk) in order to edit these MCDs.
After you have created the new MCD, you have to upload the associated installation file and fill in various fields. All MCDs that have already been created are provided there for selection.
See also:
Web Console (Old Configuration) |
Mobile Administrator (New Configuration) |
|