Creating Patches for a Mobile Component

Context

You can create patches for mobile components that are deployed on the client. This section explains how the patches are processed by the client, and how you can create your own patches.

Procedure


  1. Understand how the mobile client processes a patch.

    Client installer is a piece of software included in the mobile client that enables a more flexible update mechanism on the client. The client installer processes the patches that it receives from the Data Orchestration Engine (DOE).

    More information: Client Installer and Archives

  2. Understand the structure of a patch.

    The software deployment archive (SDA) is the delivery format for SAP applications in programming languages other than ABAP, for example applications of the Java EE Engine.

    More information: Structure of an .SDA file

  3. Create the inner archive of a patch.

    This is the archive that is downloaded and deployed on the mobile client. The inner archive is recognized only by the mobile client, the DOE does not process the inner archive.

    More information: Creating the Inner Archive for Patches (.ZIP file)

  4. Create the outer archive of a patch.

    The outer archive is the archive deployed in the mobile container of Java EE engine. The outer archive conforms to the standard SDA format.

    More information: Creating the Outer Archive for Patches (.SDA file)