Installing an Agentry Application in SMP (Differences from Agentry 6.x)
Agentry in SMP 3.x Vs Agentry 6.x
The Agentry component of SAP Mobile Platform (SMP) is a tool for designing, deploying and managing the lifecycle of mobile projects. Previously a standalone platform, Agentry is now integrated into SMP 2.3 and SMP 3.0. As such, the installation and configuration has changed in several key areas.
This document is intended to help experienced developers quickly get up to speed on the components of the new platform, as well as provide an explanation of what has changed. For detailed installation and setup instructions, please see the product documentation.
The installation files used set up an application running on SMP differ from the files used to set up an Agentry 6.x or earlier based system. The installation files needed to set up an SMP 3.0 Agentry environment are as follows:
- SMP Mobile Platform installer
- SMP Mobile Platform SDK installer
- Product Installers
All installers are located in the Software Downloads | SAP Support Portal > Installation and Upgrades -> A-Z index
- The SMP installers are under the letter M
- Please see the Agentry apps for SAP backends Agentry apps for IBM backends pages for details on the product installers
On a very high level, the installation process now consists of the following steps:
- Install the SMP Mobile Platform
- Create an Agentry application in the SMP Management Cockpit
- Run the Application Installers to configure the Application and create the Zip file
- Deploy the application zip file to the SMP Mobile Platform through the Administration Cockpit
- Install the SMP Mobile Platform SDK to access the Agentry development tools and Client Installers
Details on the SMP components, as well as the differences between the Agentry 6.x landscape and SMP Agentry landscape are explained below.
The Agentry server is no longer a stand-alone server. It is installed as a component of the SMP Mobile Platform. Starting with SP04, you can run multiple Agentry applications from a single SMP server. The SMP server itself is not Agentry specific, in addition to the Agentry server component, it also contains the servers for Hybrid and Native applications. These are not used in Agentry deployments, but can be used to develop additional applications that are running on the same SMP server.
When you run a product installer, like SAP Work Manager, SAP CRM Service Manager, etc, you are not installing a server. You are populating the ini and configuration files for the product with installation specific information (such as the backend connection information, java paths, etc.) and creating a zip file that is used to deploy the application definitions to the application definition created in SMP Mobile Platform.
- The production definitions are deployed through the SMP Management Cockpit
- The development server must be manually set up. Detailed instructions are here:Setting up an SMP Agentry Development Environment
- Each Agentry application that you create will have its own directory in the \MobilePlatform3\Server\configuration\ directory.
- The configuration and SQL files in the application instance directory above will override the generic Agentry files in the \com.sap.mobile.platform.server.agentry directory.
SMP Mobile Platform SDK
The Agentry Clients, Test Environment, Editor plug-in and development SDKs are now distributed via the AgentryToolkit component in the SMP Mobile Platform SDK. This SDK also includes the development tools for Kapsule, Native Development, SMS and the other SMP components. These are not used for Agentry, but can be used to develop additional mobile applications.
The Agentry toolkit is found in the \MobileSDK3\AgentryToolkit directory and includes the following development tools:
- AgentryClients – These are the standard client installers for Windows, Android, WPF and WinCE devices. The iOS clients must be downloaded from the Apple App store, as they were in previous versions of Agentry.
- AgentryEditors – This contains the Eclipse plug in for Agentry that is used to develop Agentry Applications, as well as the Jar file containing the Agentry Class files and the docs file that contains the Agentry JavaDocs. The Editor now requires a 64-bit environment.
- AgentrySDK – This is the development kit used to create Active X controls for win32 and Windows Mobile clients only. The newer Agentry clients (Android, iOS and WPF) utilize the Open UI SDK to provide similar functionality.
- AgentryTestEnvironment – This is client used for development and troubleshooting. It provides debugging and data inspection tools as well as the ability to mimic supported client platforms. Starting with SP06, the Agentry Test Environment is included with the Agentry Editor plugin and is based on the WPF Agentry client. You no longer need to install the ATE separately.
- BrandingSDK – The Agentry Clients as provided with the SAP® Mobile Platform are branded based on SAP standards. Customers can re-brand the client to match their needs. This directory contains the branding SDK for the Windows Mobile (WinCE) clients.
OpenUI SDK – The OpenUI API components allow development of custom controls for the Agentry client. It is provided for Android, iOS and WPF cleint devices and the controls are built using the native language of the target device client. The OpenUI SDK also contains the Agentry client frameworks for Android and iOS that can be used to provide branded clients for these platforms.