A new development archetype for Agentry applications is now integrated
with SAP Mobile Platform. Developers use the Agentry Editor to
create and modify applications, then deploy them to SAP Mobile Server. System administrators deploy, manage, and monitor applications
using SAP Control Center.
Agentry applications provide the ability to:
- Support one or more client device types, and one or more enterprise
information systems (EISs) of varying types, from a single application
project.
- Configure and modify applications with minimal user impact.
- Develop simple or complex multi-screen workflows.
- Store high data volumes on client devices.
Each Agentry application has its own Agentry Server instance that runs on a
SAP Mobile Server node.
Note:
- End-to-End Trace, Solution Manager, and LoadRunner are
not currently supported for Agentry.
- Native
push is supported for Apple Push Notification Service (APNS) and Google
Cloud Messaging (GCM).
- The current SAP Mobile Platform scale-out node
architecture supports the Agentry Server.
- Agentry
applications are now included under the SAP Mobile Platform license; you can no longer use the Syclo
licensing method.
Quick Start: Agentry Documentation
Agentry information is now incorporated in the SAP Mobile Platform documentation set. In Fundamentals, see Agentry Applications for an overview of the
Agentry development archetype.
Install
Core Agentry components are installed as part of SAP Mobile Platform 2.3.
- Installation Guide for
SAP Mobile SDK
- Installation Guide
for Runtime
Configure
Use SAP Control Center to
configure the Agentry Server and back-end system connection, and the Agentry Server
and application client security connections. Setting up these configurations
modifies the agentry.ini file.
Each Agentry application server instance is configured based on the
information that is loaded from the Agentry Server configuration files that are
installed with the SAP Mobile Server. You can modify
the configuration for individual Agentry applications using the SAP Control Center. To modify the Agentry Server
configuration files installed with the SAP Mobile Server, you must edit the files directly.
- Landscape Design and
Integration, see Agentry Server Host System
Connectivity to identify EIS connectivity requirements. [In
SAP Mobile Platform documentation,
enterprise information system (EIS) is equivalent to "back end"].
- System Administration, see:
- Agentry Server Configuration
Overview
- Configuring Back End
Communications
- Configuring Client-Server
Communications
Migrate
Migrate your existing Agentry Mobile Platform development environment
to SAP Mobile Platform. In Developer Guide: Migrating to
SAP Mobile SDK,
see Migrate Agentry Applications, and follow the steps
in the order presented to set up your environment, and deploy your existing
applications.
Develop
Install a standalone version of
Eclipse, separate from SAP Mobile WorkSpace, and the
Agentry Editor plug-in. Use the Agentry Editor to design applications, define
authentication and security settings, and define EIS connections and operations. Use
the Branding SDK to modify the client application package (for example, icons,
application name, and so forth).
- Installation Guide for
SAP Mobile SDK, see Installing the Agentry
Editor Plug-In and Eclipse Platform
- Developer Guide: Agentry
Applications
- Developer Guide:
Agentry Language Reference
- Developer Guide: Agentry
Device Client Branding SDK
Deploy
Use the SAP Control Center
application creation wizard to create an application definition. Specify the
application file, import the Agentry application, and configure the Agentry Server
instance associated with the application. You can manage multiple Agentry
application versions. Security settings are autogenerated, picking up configuration
settings from Agentry Editor.
In
SAP Control Center
for SAP Mobile Platform, see:
- Agentry Applications
- Creating Agentry Application Definitions
Manage
Use SAP Control Center to manage
applications and the application life cycle. Create application definitions, deploy
them immediately or later, and update definitions over time.
Monitor
Use SAP Control Center
domain-level event and message application logs, and server log files to monitor
end-to-end communications from client applications to the EIS.
- System Administration, see:
- Agentry Server Logs
- Agentry Application Logs
- SAP Control Center
for SAP Mobile Platform, see
Retrieving Application Logs