Skip to main content

Application import

To run the Discovery or Testing process via Apptimized TO GO the application must be imported to the project.

The option to start the import is called “Classic import”. It is available under Import in project menu > Start Import section > Classic import option.

to_go_08_2.png

The initial preparation process may take a while. In case of success, Apptimized shows the Upload sources and discovery document step.

to_go_09.png

Three options to upload Installation Source are available:

  • Upload application file from customer's PC;

to_go_10_1.png

  • Upload application file from the Internet;

to_go_10_2.png

  • Upload application file from the file storage.

to_go_10_3.png

The Installation Source uploading progress is shown as follows:

to_go_11.png

The uploading time depends on the application's size. When the download of the application is completed, the customer can start uploading another application. Five application uploads are available for one session.

Uploading Discovery Document is optional. A discovery document can be generated in previous sessions.

One discovery document upload is available for one session.

The Upload sources and discovery document step finalizes by clicking on the Next button.

Apptimized shows the Metadata step when successful.

to_go_12.png

The process reverts to the previous step by clicking on the Upload sources and discovery document button.

to_go_13.png

To extract the application metadata automatically a customer can select the main installer from the list on the left or can enter the metadata manually into the fields on the right. All required fields have * in front of their label.

The following metadata will be provided:

Table 1. Application metadata

Metadata

Details

Application ID

The application ID is a unique identifier generated automatically for every application during its upload.

Application ID provides application identification.

Reference

This field is optional and can stay blank.

This field provides additional comments from a customer to the Apptimized portal (i.e. internal application ID).

Vendor

This field defines the vendor name (i.e. Tim Kosse).

This is a required field.

Software

This field defines the application name (i.e. FileZilla).

This is a required field.

Version

This field defines the application version (i.e. 3.46.3).

This is a required field.

Language

This field defines the application language (i.e. English (United States)).

This is a required field.

A previous version of an application

This field defines if the previous version of the application is available in the portfolio.

The default value is None, it is the first version of the application in the portfolio.

A click opens a dropdown list to select the previous version of the application from the list.

Enable Echo

This option defines if Echo is needed to be enabled.

The Echo is enabled by default.

Learn more about Echo.

The prerequisites can be added by clicking on the Add prerequisites button.

 A prerequisite may be a specific application that must be installed before the target application.

A field "Select media type for …" is filled automatically can be changed if needed.

A prerequisite is added by clicking on the Save button. Apptimized shows the following notification when successful:

to_go_16.png

Current prerequisites can be changed by clicking on the Edit prerequisites button and by following the same set of operations as for adding a prerequisite.

to_go_15.png

The Metadata step finalizes by clicking on the Finish button.

A Transition screen for application immediately appears where the Workflow scheme and modalities for interaction with the application (namely discovery, packaging, testing) are available.

to_go_17.png

Apptimized TO GO can be used only for Discovery and Testing.