Mobile Component Descriptor

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. The information from the MCD is displayed in the Mobile Administrator. This information is used to assign mobile components using device configurations.

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).

The MCD is usually created during the development of a mobile application or generated when converting a mobile component in the Mobile Administrator. The MCD is imported during deployment and then used for the mobile component display in the Mobile Administrator.

If there is no corresponding MCD, you as a customer or consultant can also create it. To do this, use either the archive converter in the Mobile Administrator or the transaction MCD.

Administrators can also edit an MCD using the MCD transaction. This is useful, for example, in the following cases:

?     If you use Smart Synchronization and want to assign SyncBOs to the application.

?     If you assign mobile components using roles and you want to define which version is to be used as the standard version when assigning in this way.

The MCD contains the following required information:

Required Fields

Field

Meaning

Mobile Component

Technical name of the mobile component

Version

Version of the mobile component. The version has between 1 and 6 figures, is of type Character, and can be freely selected.

Version for Role-Based Assignment

If there are different versions of the applications, the administrator can mark one version. The system then automatically uses this version when processing roles (see Assigning Mobile Components to Roles). There is no input field for the version in the role editor.

Make this setting here. You cannot do this in the Mobile Administrator.

Description

Description of the mobile component.

Component Type

?     Application: Mobile application

?     Framework: Runtime environment for mobile applications

?     Add-On: Generic additional functions, for example, a DLL or driver

?     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.

Runtime Environment

?     JSP: For web-based applications

?     AWT: For Abstract Window Toolkit (AWT)-based applications

?     MicroITS: For 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.

You can also make the following (optional) settings:

Optional Settings

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. The system enters the path when the mobile component is deployed.

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.

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.

See also:

For more information on assignment options, see Assignment of Mobile Components to User.

For more information on the various mobile components:

?     Framework Files

?     Database Files

?     Driver Files

?     Mobile Applications

For more information on the installation sequence, see Defining the Installation Sequence (Optional)