Apptimized TO GO infrastructure
Infrastructure components
The figure below shows the scheme of the Apptimized TO GO infrastructure.
The infrastructure components details are described in Table 1.
Table 1. Infrastructure components
|
Component |
Details |
|
1. Apptimized Portal |
The platform where Apptimized customer manages projects portfolios.
Technical requirement for working in Apptimized: 1. Browsers:
2. Enabled Java-script in browser; 3. Speed of internet connections – min 50 Mb/s. 4. Enabled firewall white list: 195.201.82.88; 195.201.170.90; https://app.apptimized.com/; https://rdproxy.apptimized.com/; https://cdn.apptimized.com; *.zoho.eu; *.chatlio.com |
|
2. Customer Environment |
Information technology environment, including software, hardware, and systems (e.g., endpoint PCs, VMs, servers, networks).
The access of endpoint PC or VM to the 80 and 443 port of the app.apptimized.com host is a prerequisite. |
|
2.1. Proxy server |
This component is optional. A proxy server is a third party between the customer and the service (the Apptimized Portal). A proxy server manages the requests sent by the customer and completes them depending on the system's preferences. |
|
2.2. Apptimized TO GO agent |
Apptimized TO GO agent allows a customer to turn a local machine, PC's or VM's into Apptimized VM so that they can be used for discovery and testing. The Apptimized TO GO agent must be installed and launched on a local PC by the local administrator. |
Communication process and methods
The Apptimized Portal communicates to the Customer environment via API.
To integrate the Apptimized Portal, the Apptimized TO GO agent must be installed to the endpoint PC.
To identify the customer, a deployment code (i.e. 3D6-111DC-1) or TO GO file (i.e. 11321.Apptimized.togo) from Apptimized is used. Any other identifications from the customer will not be requested.
When data is received from the Apptimized Portal, the Apptimized TO GO agent mounts a network share with source files and prerequisites using Command Promt commands.
UI automation is used for capturing user interactions while discovery and testing. Screenshots are sent every 500 milliseconds.
UI automation is used to playback the recorded actions in Echo.
The TO GO agent is configured to communicate with the Apptimized Portal using HTTPS protocol. The text box below provides the certificate details:
Issued by – K Software certificate Authority (DV) 2 https://sectigo.com/legal
Version – V3
Signature algorithm – sha256RSA
Signature hash algorithm – sha256
Public key – RSA (2048 Bits)
TLS – 1.2
The information flow content depends on the type of customer activity (see Cases 1-2).
Case 1. A customer discovers/ tests TimKosse_FileZilla_3.46.3_English(United States) via Apptimized TO GO agent. To run the Apptimized TO GO agent a deployment code is used.
Outbound information - a data sent from the Apptimized Portal:
- an application metadata;
Application vendor - Tim Kosse;
Application name - FileZilla;
Application version - 3.46.3;
Application language - English(United States)
- an action mode metadata;
Echo enabled - True;
Mode - Discovery;
Self service mode - No.
Inbound information - a data sent to the Apptimized Portal:
- a request to receive the manifest;
- records of the customer's actions.
"Type": 10,
"HasKeyboardFocus": true,
"Text": "hello",
"InitialText": null,
"Id": "7167ac61f40342d89cf061f61cab6d49",
"ProducerId": null,
"Window": {
"Title": "*new 2 - Notepad++",
"Screenshot": in base64 string format
Case 2. A customer discovers/ tests TimKosse_FileZilla_3.46.3_English(United States) via Apptimized TO GO agent. To run the Apptimized TO GO agent a TO GO file is used.
Outbound information - a data sent from the Apptimized Portal:
- TO GO file - Apptimized.togo.
Inbound information - a data sent to the Apptimized Portal:
- records of the customer's actions.
"Type": 10,
"HasKeyboardFocus": true,
"Text": "hello",
"InitialText": null,
"Id": "7167ac61f40342d89cf061f61cab6d49",
"ProducerId": null,
"Window": {
"Title": "*new 2 - Notepad++",
"Screenshot": in base64 string format