Publishing to Development
- Verify the Windows user for the Agentry Editor host system has read-write and network access (where applicable) to the installation location of the Agentry Development Server.
- Confirm the application project is in a state for which a publish is reasonable and ready for testing.
- During the publish process checks will be made as to the overall integrity of the application project. Errors or warnings will be 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 with errors.
- Verify the version number of the Agentry Development 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.
This procedure describes the steps necessary to perform a development publish from the Agentry Editor to the Agentry Development Server. When this process is complete, the application project will exist on the Server and will be deployed to any Agentry Clients that perform a transmit with that Server. This process is performed whenever it is desired to publish an application project for the purposes of development or unit testing in advance of eventual deployment to a production environment.
- Begin the publish 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 development publish the
following options are set:
- The Publish As option is set to Development Version.
- The To Server option lists the most recently selected Development Server, or the Development Server specified when the application project was created. Any other Development Servers to which a publish has been performed will be listed in this drop down. Select the Development Server in this field by selecting it from the drop down or by navigating to the Server’s installation location using the [Browse] button.
- The Create override base files option can be set to generate the files used in support of localization. These files will contain all the display strings within the application project, with each display string including an identifier. The contents of these files can be translated and reincorporated in the Server to localize the application. See available information on localizing an Agentry application on the next steps after these override base files have been generated.
Once these options are set click the [Next >] button to begin the publish. The publish status screen will be displayed:
Performing a development publish results in the business logic encapsulated in the definitions being transferred to the Agentry Development Server where they can be deployed to clients connecting to that server instance. Any previous version of the application published to the same server instance is overwritten by subsequent publishes.