h3. Introduction The Mobile Infrastructure (MI) framework holds a registry of all the deployed components like mobile applications and addons; as well as the info of the framework itself. The next figure shows an example of an MI Info page where all the installed components information are being displayed. This registry of information is also used in creating the application links made available on the MI main page. In some cases, there's a need to retrieve this information and use them within your application. However, at the time of writing this article, there's no public API available to retrieve this information. So how do we access them? This article describes a way how to retrieve installed component information from the MI registry with the use of the implementation classes. 
h3. The Mobile Component Descriptor (MCD) Every mobile component (framework, addon, and application) has a corresponding Mobile Component Descriptor (MCD). MI framework uses the MCD to manage the mobile components that spans over the separated systems: the client and the Web AS. An MCD contains the following information: ** Header information (namespace, name, version) ** ** Properties (Runtime type, application type, build no. etc.) ** ** Dependencies (required SyncBOs and MCDs, relevant authorization objects etc.) ** ** Customizing (Download location on the virtual file system, flag for role-based deployment) ** The MCD informations are kept on the client in the form of registry database. Specifically in the +mobileengine.registry+ file.
h3. Accessing MCDs Currently, MI does not have any public APIs for accessing the registry information. Here, we will use the implementation class called MobileSolutionDescriptor (fyi, Mobile SolutionDescriptor was the former name for Mobile Component Descriptor) in the com.sap.ip.me.core package which is included in the +meg.jar+ file. The next figure shows some of the public methods of the MobileSolutionDescriptor. (+ I will just show you the methods used for retrieving the MCD attributes+).
h3. The Mobile Component Descriptor (MCD) Every mobile component (framework, addon, and application) has a corresponding Mobile Component Descriptor (MCD). MI framework uses the MCD to manage the mobile components that spans over the separated systems: the client and the Web AS. An MCD contains the following information: ** Header information (namespace, name, version) ** ** Properties (Runtime type, application type, build no. etc.) ** ** Dependencies (required SyncBOs and MCDs, relevant authorization objects etc.) ** ** Customizing (Download location on the virtual file system, flag for role-based deployment) ** The MCD informations are kept on the client in the form of registry database. Specifically in the +mobileengine.registry+ file. h3. Accessing MCDs Currently, MI does not have any public APIs for accessing the registry information. Here, we will use the implementation class called MobileSolutionDescriptor (fyi, Mobile SolutionDescriptor was the former name for Mobile Component Descriptor) in the com.sap.ip.me.core package which is included in the +meg.jar+ file. The next figure shows some of the public methods of the MobileSolutionDescriptor. (+ I will just show you the methods used for retrieving the MCD attributes+).
