Developer

Importing a New Agentry Project Into the Eclipse Workspace

This procedure describes the steps involved in importing an application project into the current Eclipse workspace.

Prerequisites

Address the following items prior to performing this procedure:
  • Determine the source of the application project you are importing in this procedure and that you have access to that source.
  • Verify that the application project source was created with the same or earlier version of the Agentry Mobile Platform. You cannot import projects, export files, or published applications created with a later version into an earlier version.
  • Verify the workspace in which you are importing the project is the currently opened workspace in Eclipse.
  • Determine a name for the project as it will be listed in the Eclipse workspace, as this is required information entered in the import process.
  • Determine a value for the Name attribute of the application definition. This is information required during the import process.
  • Though not required, it is strongly recommended that the Agentry Development Server to which development publishes are performed is installed. While the location of this Server instance is optional during the import, it is necessary information when defining any of the synchronization logic within the project after it is created.

Context

When the procedure of importing an application project into the current Eclipse workspace is complete, a new Agentry application project is created in the current Eclipse workspace. This project contains the definitions and application components found in the import source.

Note that this process excludes any related projects for the source application that may reside in that source project’s workspace, such as Java development projects and related packages. Import these related projects and components according to the process that matches that project type, using tools found in Eclipse. Whether the Agentry application project is imported before or after other related projects is unimportant. However, all items must be imported and/or configured before modifications are made.

This procedure accomplishes the following:
  • Checks out an Agentry application project from an Agentry share repository and creates a new local project based on the top revision within that repository.
  • Migrates an application project from one workspace to another.
  • Upgrades an application project or application export file created in a previous release of the Agentry Mobile Platform.
  • Restores or recovers an application project from an archived project or export file.
  • Creates, restores, or recovers an application project from a mobile application published to the Agentry Server.

Procedure

  1. If not already open, open or create the Eclipse workspace in which to import the new project. Opening or creating a workspace in Eclipse begins by selecting the menu item File | Switch Workspace and following the on-screen instructions.
  2. Right-click an empty area in the Project Explorer View and select the menu item Import.... Alternately, select the menu item File | Import... in the Eclipse main menu.

    The Select Import Source screen displays.



  3. On this screen are the different import sources for Eclipse. Two of these pertain to Agentry application projects: Agentry Project and Agentry Share. Select the desired source by expanding one of these nodes and selecting the appropriate item under it. Click [Next] to continue.

    The Select Source screen displays. This screen will be slightly different depending on the selected import source type. The following example is for a source type of Agentry Server application:



  4. In this screen the information entered is dependent on the source type selected in the previous step. Enter the information according to the following:
    1. The specific item selected for the source is different based on the type. Select the source by clicking the [Browse] button.
    2. The Source Application box is only displayed when the source type is an Agentry Server. This lists the name of the application published to that Server instance. If the selected server instance is a production Server, each published version currently residing on that Server is listed and you can import any one of those versions.
    3. The Application Name is the name given to the mobile application that is created by the import. This is set as the value of the Name attribute within the application definition and can contain no white space. This field is read-only if the selected import source is an Agentry share repository.
    4. The Project Name is the name for the project within the Eclipse workspace. This must be a unique project name for the workspace and white space is allowed.
    5. The Development Server (optional) is the Agentry Development Server for the application project being created. Any script files contained in the source project are copied to this Server. By default, this field is set to the Server from which the project is imported, if that Server instance is a development Server. Leave the option set as-is if this is the development Server for the new project, or change to a different development Sever if necessary.
  5. Verify the information entered is accurate and complete. Click [Finish] to perform the project import.

    A new project is created by importing the definitions from the selected import source. The project is listed in the Project Explorer View and is automatically opened.

Results

After this process is complete, the new project is added to the Eclipse workspace. The project is opened and displayed in the Agentry Perspective within Eclipse. The application name and project name match those values entered in the Import wizard. If the application project source was created using a previous version of the Agentry Mobile Platform, the new project was upgraded during the import to the version of the current Agentry Editor.

If the selected import source was an Agentry share repository, the new project contains the definitions found in the top revision of that repository. The revision is checked out to the current user. Subsequent changes made to the application project are tagged with that user ID. The project is connected to the selected share repository and you can update from it. Commit changes made locally to this repository.