Deploying Mobile Components Using Archive Upload Tool

Use

This procedure allows you to deploy Mobile components from the development workstation to the SAP NetWeaver AS.

The Mobile components exist in the development workstation.

Uploading Mobile Components of the SCA/SDA format

Log on to the SAP NetWeaver AS and start transaction S DOE _UPLOAD _ARCHIVE .
Enter the name of the Mobile component that you want to upload to the DOE.
Enter the destination data object.
Choose Upload .

Uploading Mobile Components of a different format

Log on to the SAP NetWeaver AS and start transaction SDOE_UPLOAD_ARCHIVE .
Choose Switch Screen to Upload non SDAs .
Enter the details depending on the mobile component that you want to upload. You can upload mobile components of the types db, jvm, addon, patch, dbconfig, and dbindex. If you upload the dbconfig and dbindex mobile components, you need to enter the name of the dependant mobile component of the type application.
Choose Upload .

Note

If you get the error: Not enough memory for Data Provider , common reasons are:
- SAP GUI that you have installed in the system (the system from which you are uploading the archive file) is not the latest version.
- The RAM memory of the system is not sufficient.
  
  Refer to SAP Notes: 875700 , 875871
Note

If you upload an MCD that corresponds to an older version of the application (that uses older versions of data objects or package variants) to the DOE, you need to regenerate the objects before assigning the MCD to devices. This is because the generated outbound service handles only those versions that are currently in the system. It does not handle older versions unless an application uses them.

However, the outbound service does not handle old versions that have never been generated in a system, irrespective of whether they are used in an application or not.