SAP Inventory Manager on the SAP Mobile Platform

Runtime Environment

The runtime environment is a production server system. Within this component, you can define one or more applications of different archetypes. An archetype refers to the different types of mobile applications, including the development paradigms, under which mobile applications are developed and deployed. The SAP Inventory Manager application is developed and deployed under the Agentry archetype. Therefore, it requires the definition of an Agentry application within the runtime environment into which it is deployed. You can modify the application by configuring options within the administration interface, the SAP Mobile Platform Cockpit.

Additionally, you can develop changes to out-of-the-box behavior of the application by using components of the Agentry toolkit within the SAP EAM and service mobile SDK.

SAP Mobile Platform Server

The server is provided within the SAP EAM and service mobile app SDK. It provides the same runtime functionality as the Agentry server component within the SAP mobile runtime environment. It is provided in the Agentry toolkit to allow you to install the server without the need to install the entire runtime environment for development work. The development server is not intended for production use.

Agentry Plug-in to Eclipse

The Agentry plug-in to Eclipse provides a 4GL, point-and-click interface that allows developers to modify the SAP Inventory Manager application. The Agentry is provided in the SAP EAM and service mobile app SDK as a part of the Agentry toolkit. Agentry applications are stored within the Agentry in the Eclipse workspace as Agentry application projects.

Both the Agentry application project and the Java packages and projects are all managed within a single Eclipse workspace. The developer is presented with a single IDE in which the mobile application as a whole can be maintained and modified. See the document Agentry App Development in the SAP Mobile Platform documentation for details on working within this toolset.

SAP Inventory Manager Client

The SAP Inventory Manager client is provided for each of the client device types supported by the SAP Inventory Manager application. An installer for the SAP Inventory Manager client build is provided for Windows operating systems. For devices running iOS, the application is installed from the App store, or from your Apple Enterprise Server site. For Android devices, the .apk file is provided. You can install the .apk file from a Web server by navigating to its location within the local network of your environment.

The SAP Inventory Manager client is an executable run on the client device by the end user. The overall architecture of the Agentry toolkit allows for the development of a single application project, which can be deployed on multiple device types. The client processes the business logic developed in the Agentry and is deployed to the runtime environment. The client displays the user interface according to the native operating system of the device on which the SAP Inventory Manager is running.

The Agentry Test Environment

The Agentry Test Environment (ATE) is among the development tools provided in the Agentry Toolkit within theSAP EAM and service mobile app SDK. It is a highly useful tool for developers during the development cycle used for testing the client-side behavior and functionality of your mobile application. It includes numerous debugging and inspection tools to provide insight into the data, action execution, rule evaluation, and other aspects of the behavior of the client at runtime.

The ATE is not an emulator. However, it does posses the capability to mimic the behavior of all the supported client device types. Within the ATE is a full Agentry client. Part of the features of the ATE is the ability to select from a list of supported client platforms from within the Agentry archetype development paradigm. Once you select a platform, the Agentry client tells the SAP Inventory Manager server that it is a client of that type. The client then receives the user interface components for that platform.