Agentry System Landscape and Publish Mechanism

8/10/2019 Agentry System Landscape and Publish Mechanism

1/15

Agentry System Landscape and PublishMechanism

Provided by SAP Mobile - Rapid Innovation Group

Applicable Releases:

Agentry 5.X and 6.X - which Includes all SAP based mobile

products running on Agentry 5.X and 6.X.

Version 1.0


2/15

Agentry System Landscape and Publish Mechanism

TABLE OF CONTENTS

SECTION 1: AGENTRY SERVER LANDSCAPE OVERVIEW ........................................................................ 3

SECTION 2: PUBLISHING APPLICATIONS OVERVIEW .............................................................................. 4

SECTION 3: DEVELOPMENT PUBLISH ......................................................................................................... 5

SECTION 4: PRODUCTION PUBLISH ........................................................................................................... 6

SECTION 5: AGENTRY DEVELOPMENT VS. PRODUCTION SERVER ....................................................... 8

SECTION 6: AGENTRY FILE TYPES .............................................................................................................. 9

SECTION 7: APPLICATION DEPLOYMENT PROCESS .............................................................................. 13

SECTION 8: PUBLISH PROCESS ................................................................................................................. 14


3/15


SECTION 1: AGENTRY SERVER LANDSCAPE OVERVIEW

When we install Work Manager Server it needs connection to the SAP backend system. Typically we set-upthree tier landscape development, quantity and production server for Agentry development.

SAP system landscape dictates Agentry Server landscape set-up as shown in figure 3.

Production landscape

Production landscape

Quality landscape

Development landscape


4/15


SECTION 2: PUBLISHING APPLICATIONS OVERVIEW

There are two types of publishes that can be performed, Development and Production. When

publishing an application from the Agentry Editor, there are various aspects that will affect the type ofpublish performed and which options to select during the process. Additionally, the first time anapplication project is published there is some initial configuration performed by the publish processthat will affect the Agentry Server.

Other options exist for the publish process, including the creation of files used for localization of theapplication. When performing a production publish, the publish version of the application must beset. Also during a production publish the option exists to delay the deployment from the AgentryServer to Agentry Clients until a specified date and time.

For all publish operations the application data is copied to the Agentry Server, with transformation ofthe application data into the format for the Agentry Server. This format will vary depending onwhether the target Agentry Server is configured for development or production. The location of theapplication data will be in the Agentry Servers configuration directory, in either the subdirectoryApplication\Development for a development publish, or Application\Production\Version for aproduction publish. To perform a publish it is necessary to have read-write access to this location.


5/15


SECTION 3: DEVELOPMENT PUBLISH

A development publish will transfer the definition files in the application project from the Agentry Editor tothe Agentry Development Server. The files are stored on the file system at the installation location of theSAP Mobile Server; specifically within the configuration directory of the Agentry Server in the sub-directory Application\Development. A development server has no concept of application versions. Whena development publishes is performed, the previous version of the application on the Server isoverwritten.

Note: - A development publish should only be performed to an Agentry Development Server.

Begin the publish by clicking the toolbar Publish button in Eclipse.


6/15


SECTION 4: PRODUCTION PUBLISH

During production publishes, the version number for the application must be specified. The first time aproduction publish is performed to the Agentry Server, the version number will be 1.0. During

subsequent production publishes to the same Agentry Server instance, the version number is changedbased on the selection made in the Publish Wizard.

An Agentry projects publish version contains the three components major, minor, and modificationnumber. In the publish version SAPWM-v1-0-2-app, the 1 is the major version, 0 is the minor version,and mod 2 is the modification number. The Publish Wizard will contain a section where the developer willspecify which of these should be changed. This selection impacts the behavior of the application duringthe next synchronization by the Agentry Clients.

The specific difference is related to the processing of transactions sent from the Agentry Client to theAgentry Server. Depending on the nature of the change made to the application, it is possible thatchanges captured on the Agentry Client in transactions using the previous application version will beincompatible with the new version of those same transactions. When the synchronization definitions ofthe transaction (server data state or update steps) perform processing that will not work with the

previous version of the application, it is necessary to process the pending transactions with the previousapplication version. To force this behavior, change the production publish version by incrementing themajor version number.

When a new major version is specified, the Agentry Server will process each transaction sent by a Clientusing the old version of the application. Once all transactions have been processed, the new version ofthe application will be sent to the Agentry Client and dictate any subsequent synchronization behaviors.When either the minor or modification numbers are changed, the new version of the application takeseffect immediately, before the pending transactions on the Agentry Client are processed.

Because of this behavior, it is the responsibility of the developer performing the publish to determinewhich behavior is desired, and to then select the proper change to the publish version of the application.

Note: - A production publish is performed to an instance of the Agentry Production Server

Begin the publish by clicking the toolbar Publish button in Eclipse.


7/15



8/15


SECTION 5: AGENTRY DEVELOPMENT VS. PRODUCTION SERVER

An Agentry server is identified as type Development or Production during installation. Importantdistinctions of an Agentry Development Server is only a single, latest version of an application is kepton the server. Agentry application definitions stored in multiple files not intended for large, concurrentusers (because of logging and other parameters tuned for development purposes). Importantdistinctions of an Agentry Production Server, Application versions are stored on the server.Application versions consist of three part naming components.

MajorMinorModificationFor example - SAPWM-v1-0-2-app


9/15


SECTION 6: AGENTRY FILE TYPES

Agentry File Types

Agentry Project File - .apjAgentry Development File - .agdAgentry Development File Compressed - .agdzAgentry Production File - .agpAgentry Production File Compressed - .agpzAgentry Export File - .agxAgentry Export File Compressed - .agxz


10/15


Figure 1: Agentry Architecture


11/15


Figure 2: Agentry Server in DMZ zone


12/15


Figure 3: Agentry Server Technical landscape (Logical)


13/15

www sap com

SECTION 7: APPLICATION DEPLOYMENT PROCESS

The movement of the mobile application through the customer landscape requires the coordinationof following activities:

1. The movement of the ECC transports for the project, including both workbench requests andcustomizing requests.

2. The movement of the mobile application to the target Agentry Server.3. The movement of any custom Java code to the target Agentry Server.


14/15


SECTION 8: PUBLISH PROCESS

1 Develop and unit test by publishing to a development serverCheck exports and Java into dailyversion control.

2 Publish production mode application to staging server or unit test development server and perform

end-to-end testing. When a version of the application is ready to be released, the development teamwill create an archive (.agdz) of the application definition, and a JAR file for the custom Java code.

3 To move the Java, the JAR file will be manually saved to the Java folder of the target AgentryServer. Note that any new JAR files will need to be added to the classpath in the Agentry.ini file.

4 Agentry application definition, the project (.agdz file) will be moved to the Application folder of thetarget Agentry Server.

5 Modify classpath in JavaBE.ini file for the new jar file.


15/15

www sap com

2013 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP

BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP

products and services mentioned herein as well as their respective

logos are trademarks or registered trademarks of SAP AG in Germany

and other countries.

Business Objects and the Business Objects logo, BusinessObjects,

Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and

other Business Objects products and services mentioned herein as

well as their respective logos are trademarks or registered trademarks

of Business Objects Software Ltd. Business Objects is an SAP

company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL

Anywhere, and other Sybase products and services mentioned herein

as well as their respective logos are trademarks or registered

trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are

registered trademarks of Crossgate AG in Germany and other

countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of

their respective companies. Data contained in this document serves

informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials

are provided by SAP AG and its affiliated companies ("SAP Group")

for informational purposes only, without representation or warranty of

any kind, and SAP Group shall not be liable for errors or omissions

with respect to the materials. The only warranties for SAP Group

products and services are those that are set forth in the express

warranty statements accompanying such products and services, if

any. Nothing herein should be construed as constituting an additional

warranty.

Agentry System Landscape and Publish Mechanism

Documents

Transcript of Agentry System Landscape and Publish Mechanism