Show TOC

Migrating Agentry Applications from SAP Mobile Platform 2.3 to 3.0Locate this document in the navigation structure

You can migrate SAP Mobile Platform 2.3 Agentry applications to SAP Mobile Platform 3.0.


  • Install SAP Mobile Platform SDK and SAP Mobile Platform Server.
  • Modify the file references within the Java Synchronization logic for any Agentry applications that contain a Java system connection.
  • Ensure you have access to the previous Agentry Editor version and Eclipse workspace in which the Agentry application project exists.
  • Install the Agentry Editor plug-in as provided in the SAP Mobile Platform SDK to Eclipse.


  1. In an Agentry perspective in the SAP Mobile Platform 2.3 Agentry Editor, export the entire Agentry application project.
    The resulting file name contains the extension .agx or .agxz.
  2. In an Agentry perspective in the SAP Mobile Platform 3.0 Agentry Editor, right-click in Project Explorer view and select Import.
  3. Follow the wizard to complete the import process.
    During the import process, you can associate the project with the development server.
    Once the import process is complete, the new Agentry application project for the mobile application exists in the Eclipse workspace and is listed in the Project Explorer view.
  4. Make sure the Network Connect Type is WebSockets over HTTPS for all transmit configurations.
  5. (Optional) Migrate the associated Java back-end project to the Eclipse workspace.
  6. Publish the application as a Production version.
    1. Click the Publish button, then browse to the location where you want to publish (save) the ZIP file.
    2. (Optional) Right-click within Publish Folder Structure to add auxiliary project files, which may include Java resource files, application-specific DLL files, JAR files for the back end, and other back-end configuration files.
    3. Click Next, then Finish.
  7. In the cockpit, create an Agentry application definition.
    1. Under Quick Links, select Configure Application.
    2. In Applications, click New, enter the information for the application definition.
      Select Agentry for the type, then click Save.
    3. In App Specific Settings, under Publish, browse to the Agentry application zip file, then click Open.
    4. In Back End, enter the back-end connection information for the back-end connection type.
      It may be helpful to have the previous Agentry.ini file as a reference when entering the back-end information.
    5. In Authentication, indicate the security profile or create a new one.
    6. Set any other applicable configuration options.
    7. Click Save.
      Once you save the application definition, if you change any application-specific configuration options preceded with an i, stop and restart the SAP Mobile Platform Server.
  8. For applications using the Java back end and the JavaBE.ini file, such as the Work Manager and Service Manager products, copy JavaBE.ini from the Agentry server root directory to SMP_HOME\Server.
  9. For Java System connections, add the directory to the system path.
    • On Windows, edit Server/bin/setenv.bat. At the end of the file, add set PATH=%SMP_HOME%\configuration\;%PATH%
    • On UNIX, edit Server/bin/ At the end of the file, add LD_LIBRARY_PATH=$SMP_HOME/configuration/$LD_LIBRARY_PATH export LD_LIBRARY_PATH
  10. Perform full end-to-end testing.
    When this is complete, upgrade the client installations within the implementation environment to migrate all mobile users to the new environment.
    1. Have all users perform a final transmit to verify all information stored on the device has been updated to the back end system.
    2. All users should shut down their clients prior to upgrading them.
    3. Install the Agentry Client provided with the SAP Mobile Platform for the client device type.
    4. Each user should start the new client, login, and perform an initial transmit.

Next Steps

At some point after the completion of fully migrating all mobile users to the new environment, you can uninstall the previous version of the client from the mobile devices, provided there are two separate versions. For platforms, the client can be upgraded in place, resulting in only one client executable existing on the device at any given time.