Start of Content Area

Procedure documentation Uploading Mobile Applications Locate the document in its SAP Library structure

Use

This procedure enables you to upload the installation files for mobile applications that are not yet available in the SAP MI Web Console. The uploaded files can be edited there. 

Prerequisites

      You have obtained the installation files required for the mobile application and saved these to a folder of your choice in Windows Explorer. For more information about the storage location of the installation files, see the respective mobile application documentation on the SAP Service Marketplace at service.sap.com/instguides.

      The Mobile Component Descriptor (MCD) is available in your system. If the MCD is not yet available and you have a suitable transport file, you can transport it to your system using transaction STMS. You can find information about transports in the documentation for the Transport Management System.

If there is no transport file for the MCD, you might have to create an MCD yourself (see Mobile Component Descriptor).

      The name of the mobile components can only contain the following characters: a-z, A-Z, 0-9, _. The version description can also include a period (.).

      You started the SAP MI Web Console (see Starting the SAP MI Web Console).

Procedure

...

       1.      Choose This graphic is explained in the accompanying text Change for the mobile component you want to upload.

Note

If the list does not contain an entry for the mobile component, first create an MCD for the component (see Mobile Component Descriptor).

       2.      Enter the following data:

Field

Meaning

Version for Role-Based Assignment

If there are different versions of an application, you can select one here. The system then automatically uses this version when processing roles (see Assigning Mobile Components to a Role). There is no input field for the version in the role editor.

Build Number

You can specify the build number of the application to establish at a later date which build of a mobile application you uploaded.

Use IP Instead of Host Name

Access to the host using the IP address.

If the mobile devices cannot access the host on which the installation files are stored using the host name, set this indicator. In this case, the IP address is used for the download link instead of the host name.

Domain in URL

If the mobile devices can only reach the host on which the installation files are stored using their fully qualified name in the network, enter the network domain in this field.

Protocol

Enter the protocol to be used when the files are downloaded to the mobile device, for example, http or https.

Application File

Use the Explorer to navigate to the storage location of the required file and select it.

The selected operating system and language are of no importance since there is a file for each operating system and each language.

Caution

If the SAP MI Web Console is run in a J2EE cluster, the mobile components are stored on only a single node of the cluster. In this case you must manually copy the mobile components to all the other nodes of the cluster (see Copying Mobile Components to All Nodes of the J2EE Cluster).

For more information about the other fields, see Mobile Component Descriptor. You should only change these fields using the procedure described.

       3.      Choose Change.

Note

If you want to upload a new version of the application, you do not need to create a new entry. You can simply change the existing entry.

Choose This graphic is explained in the accompanying text in the line with the entry to be changed. Change the version, enter the corresponding runtime environment and select the installation file. Choose Change.

Result

The application files have been uploaded. You now need to deploy the uploaded files to the mobile device (see Assigning Mobile Components To Users ).

 

End of Content Area