Publishing to Production
- Confirm the application project is in a state for which a publish is reasonable and ready for production use or user acceptance and quality assurance testing.
- Verify the Windows user for the Agentry Editor host system has read-write and network access to the installation location of the Agentry Production Server.
- During the publish process checks will be made as to the overall integrity of the application project. Errors or warnings are listed in the Problems View in Eclipse. Prepare for the possibility of needing to correct these issues in order to perform a successful publish. An application can be published with warnings, but not when any errors are found. It is recommended that any warnings are corrected prior to performing a production publish, especially when deploying to end users.
- Verify the version number of the Agentry Production Server and the Agentry Editor are the same, excluding any patch or point releases. Publishing from an Editor from one major or minor release to a Server from another release is not supported.
- The Agentry Application Project must be open in the Agentry Perspective.
- Determine which of the major, minor, or modification number of the publish version should be changed, based on the desired transaction processing behavior related to Client transmits.
- Determine if the application should be immediately available, or if deployment to the Clients should be delayed to a future date and time.
This procedure describes the steps necessary to perform a production publish from the Agentry Editor to the Agentry Production Server. When this process is complete, the application project will exist on the Agentry Server. From here it can be packaged, along with other resources, for deployment to the SAP Mobile Platform runtime environment.
In addition, Agentry Clients can also synchronize with this server instance for testing purposes, if desired.
- Begin by clicking the toolbar Publish
button in Eclipse.This displays the first screen of the Publish Wizard:
- All options affecting the publish, including the type
of publish, are set on this screen. For a production publish the
following options are set:
- The Publish As option is set to Production Version.
- The To Server option lists the most recently selected production server. Any other production servers to which a publish has been performed are listed in this drop down. Select the production server in this field from this drop down, or by navigating to the Server’s installation location using the [Browse] button.
- The Publish Version is specific to a production publish. The option selected here increments one of the Major, Minor, or Modification numbers of the publish version on the Server. Increment the Major version when it is necessary to process transactions using the previous published version before providing Clients with the new version. Increment the Minor or Modification number when this processing is unnecessary.
- The Make Available option is specific to a production publish. This option can specify whether to make this published version of the application available to Clients immediately, or at a future date and time. When a date and time is specified, the application is published immediately, but will not be deployed to Clients until after the specified date and time.
- The Create override base files is set to generate the files used in support of localization. These files contain all the display strings within the application project. The contents of these files can be translated and reincorporated in the Server to localize the application.
Once these options are set click the [Next >] button to begin the publish. The publish status screen is displayed:
Performing a production publish results in the transfer of the application logic to the Agentry Production Server. The publish version of the application on that server instance is changed according to the selection made in the Publish wizard. The business logic contained in the .agp or .agpz file, along with the accompanying .ini file, can now be bundled with the ZIP archive for deployment to the SAP Mobile Platform runtime environment.