Publishing to Production

When you are ready to deploy an application to users, perform a production publish in the Agentry Editor.


  • An application project that is ready for production use, or user acceptance and quality assurance testing.
  • The location to which to publish the project, from the system administrator. Verify that you have read-write access to the location.


The production publish process produces a ZIP file. You can select all associated auxiliary project files to include in the ZIP file, such Java resource files, application-specific DLL files, JAR files for the back end, and other back-end configuration files.

The publishing process checks the overall integrity of the application project. Agentry Editor list errors or warnings in the Problems view. You can publish an application with warnings, but not with errors; therefore, to successfully publish, you must first correct any errors. Ideally, correct warnings as well, before deploying to end users.


  1. In Management Cockpit, create an Agentry application definition. This step may need to be completed by the system administrator in a production system. See Defining Applications in Administrator > Application Administration.

    This step creates an empty placeholder for the application definition, and a corresponding configuration folder for the Agentry mobile application: configuration/<app_id>. In this example, the application ID is SAPWM.

  2. In Agentry Editor, click Publish .
  3. Select Production Version, then click Next.
  4. In Production Publish Details, browse to the folder location provided by your system administrator.
  5. Select the production version.
    An Agentry project’s version number contains three components: major, minor, and modification numbers. For example, in the publish version 3.2 mod 1, 3 is the major version, 2 is the minor version, and mod 1 is the modification number.
    • New Major Version: the only choice when performing the first production publish for an application. To avoid version incompatibilities between the same transactions, when you select a new major version, the server processes each transaction sent by a client using the old version of the application. Once the server has processed all pending transactions, it provides the updated application to Agentry Clients.
    • Minor Version: indicates minor updates or bug fixes that do not affect transaction processing.
    • Modification: a modification to a major or minor version that does not affect transaction processing.
  6. (Optional) To include auxiliary project files with the application project, right-click in the field under Publish Folder Structure. For example, if you customize a configuration file, or use alternate scripts for the application.
    For the first production publish, this field is blank unless you indicated a default publishing folder structure in the Agentry Editor preferences. Subsequent publishing shows preselected folders and files. To remove an object from the list, right-click it, and select Delete.

    Agentry Editor Production Publish Folder Structure

    • Add Folder Structure enables you to browse to an existing folder, which includes all sub-folders and their contents.
    • Add Folder enables you to create a new folder. Drag and drop to add files to this folder.
    • Add File enables you to add individual files to the Agentry application zip. Once added, you can drag and drop files to a new or existing folder.
    For example, to use a custom SQLBe.ini file and custom query files for an application, create the sqldirectory structure for the application, and include your custom files. During production, the server detects the custom files for the application, based on your configuration settings, and performs processing based on the custom files rather than the standard configuration files.
    • Use Add File to add the custom SqlBE.ini file to SMP_HOME\Server\Configuration\<app_id>.

    • Use Add Folder to create a sql folder for custom configuration files: SMP_HOME\Server\Configuration\<app_id>\sql.

    • Use Add File to add custom *.sql configuration files to the application's sql folder.

  7. Make the application available to clients immediately, or specify a future date and time for deployment, and then click Next.
    The application definition is published to the specified production location.
  8. Click Finish. This produces the Agentry application ZIP file to be used in the Management Cockpit, for example: All the mobility files and connection information should be contained in the ZIP file (for example, *.sql files, Java files, javaBE.ini, with back-end connection information, and others), before it is uploaded to Management Cockpit.
  9. In Management Cockpit, use the ZIP file as the Publish Agentry App to populate the Agentry application logic. This adds the application definition to the placeholder you created in step 1. In a production system, this step may need to be completed by the system administrator. See Publishing Agentry Apps in Administrator > Application Administration.

  10. Click Save.