Migrating From Agentry Mobile Platform to SAP Mobile Platform

Prerequisites

The following items must be addressed prior to performing this procedure:

The SAP Mobile Platform 2.3 is assumed to be installed and properly configured.
If implementing an SAP Mobile Platform clustered environment, this should be established, and the Agentry application defined in each node, prior to beginning the migration process. The migration should then be performed with deployment to the primary node in the cluster.
For mobile applications which make use of a Java system connection, the Java Runtime Environment (JRE) should be installed to the host system for the SAP Mobile Platform prior to performing this procedure. Note that installation of the JRE requires the update of the system’s PATH environment variable with the location of the bin and lib directories of the JRE installation.
If the mobile application is one provided by SAP built on Agentry 6.0.x, review and have available the Implementation and Administration guide for the application being migrated. This manual can be found on the SAP Marketplace page for the mobile application. Items related to server configuration and environment setup, as well as system requirements, are applicable to the migration and implementation of the mobile application in SAP Mobile Platform 2.3.
The person performing this procedure must have detailed, development-level knowledge concerning the application to be upgraded from Agentry Mobile Platform 6.0.x. This includes the following items, though this list may not be comprehensive and the requirements will vary from one application to the next:
- Java resources, such as application specific .jar files
- Application-specific configuration files
- Application-specific resource files such as dynamic link libraries (DLL’s)
- Administration scripts typically stored within the sql directory of the Agentry Server
The SAP Mobile SDK 2.3 should already have been retrieved and its contents extracted.
The person performing this procedure must have access to and the proper permissions for the SAP Control Center to allow for the import of ZIP archives into Agentry Applications and to start and stop services within the SAP Mobile Platform.

Task

The purpose of this procedure is to upgrade or migrate a mobile application built and deployed on Agentry Mobile Platform 6.0.x, a.k.a. “Agentry Standalone” to the SAP Mobile Platform 2.3. This process can be performed to upgrade a current production implementation, or to upgrade a new implementation using an out-of-the-box mobile application provided by SAP and built on Agentry Mobile platform 6.0.x. Those familiar with the process for upgrading mobile applications from one version of Agentry to another will find this procedure to be similar, though with some key differences in the execution.

From a high level, this procedure accomplishes the following main tasks in order to migrate the mobile application:

All application-specific resources stored on the Agentry 6.0.x Server are bundled together in a ZIP archive, with the exception of the business logic itself
The business logic is imported from the Agentry 6.0.x Server as a new project in the Eclipse workspace for the Agentry Editor for SAP Mobile Platform 2.3. This upgrades the business logic to the latest format.
The application is published to the Agentry Server running with the SAP Mobile Platform 2.3. This updates the configuration sections for the application related to the defined system connections.
The ZIP archive containing the non-Agentry application-specific resources is imported using the SAP Control Center into the Agentry Server for the application within the SAP Mobile Platform 2.3.

The end result of this process is a merging of the new Agentry Server resources within the SAP Mobile Platform with the mobile application-specific resources as implemented in the Agentry 6.0.x Server. The following instructions provide the steps necessary to accomplish this migration.

This procedure is applicable to any application built and deployed on Agentry Mobile Platform 6.0.x, whether it be a product from SAP, or a custom application built by the customer.

If the mobile application to be migrated is not yet installed in the implementation environment, the server component for the mobile application should be installed to a separate, but accessible location in order to provide the mobile application business logic and application-specific resources. This must be a production server installation of the mobile application.
Install the Agentry Server for production as provided in the SAP Mobile SDK 2.3 according to the instructions provided in the Install SAP Mobile SDK 2.3 guide.
Install and configure the Agentry Editor for SAP Mobile Platform 2.3 as provided in the SAP Mobile SDK 2.3 according to the instructions provided in the Install SAP Mobile SDK 2.3 guide.
Within the Agentry Editor for SAP Mobile Platform 2.3, import the application from the Agentry 6.0.x Server, creating a new Agentry application project within the Eclipse workspace.
Publish the application project from the Agentry Editor to the Agentry Server installed from the SAP Mobile SDK 2.3.
Create a ZIP archive, preserving the directory structure, containing the following items found in the Agentry 6.0.x Server installation:
- Application-specific configuration files, which does not include configuration files provided with standard Agentry Server installations
- Application-specific Java resources, including .jar files, but do not include the Agentry-v5.jar or Agentry-v4.jar (if present) files found in the Java folder of the Server’s installation. Any other resources found here should be included as they are likely to be application-specific.
- Application-specific DLL files, but do not include DLL’s provided with a standard Agentry Server installation.
- The contents of the sql directory under the Agentry Server’s installation location. All files in this directory can be safely added to the ZIP archive.
- Any other files know to be a part of the mobile application but not provided with a standard Agentry Server installation.
Add to the ZIP archive the folder Application found in the Agentry Server installation from the SAP Mobile SDK 2.3, as well as the Agentry.ini configuration file.
Using the SAP Control Center, define a new Agentry application according to the procedure found in the SAP Control Center for SAP Mobile Platform guide, in the section Creating Agentry Application Definition.
Within the SAP Control Center, stop the Agentry Server instance just created if it is currently running.
Import the ZIP archive containing the application-specific resources and the Application folder according to the procedure in the SAP Control Center for SAP Mobile Platform, in the section Deploying Agentry Application Files to an Exiting Application.
Start the Agentry Server instance for the application using the SAP Control Center.
Configure the Agentry Server within the SAP Mobile Platform using the SAP Control Center, including system connections, client-server communications, and other standard configuration tasks. For applications provided by SAP see the Implementation and Administration guide for the product for information on configuring the Server for the application. Note that instructions may reference the Agentry Administration Client as provided with Agentry 6.0.x and prior releases. The SAP control Center is now used to perform the configuration, but the appropriate settings and options are the same.

With the completion of this procedure, the mobile application originally built and deployed on the Agentry Mobile Platform version 6.0.x has been upgraded and migrated to the SAP Mobile Platform 2.3. Application-specific resources have been moved to the Agentry Server instance within the SAP Mobile Platform and the business logic for the application has been upgrade and imported.

Next

The next steps should be to thoroughly test the updated application with standard testing procedures, including end-to-end synchronization tests involving the Agentry Clients.