Skyone
English
English
  • Home
  • Skyone Platform
    • Overview
    • Access and Registration
      • Password recovery for the platform
    • Settings and Preferences
      • My Profile
      • User Management
        • How to invite a user to the platform?
        • Options for User Management
        • Types of User Permissions
      • Invitations
      • My Company
      • Support Case Configuration
      • Companies Management
      • Billing
      • Settings
      • Security
      • Feedback
      • Logs
      • Cancellation
      • Partner-Clients
        • My Clients
        • My Partner
    • Notification
    • Health: Platform status check
    • Support Cases
      • How to track and respond to support cases?
      • Guide for opening ABO Tickets
  • Cloud Computer
    • Overview
    • Autosky
      • Login and Password Registration
        • Password RecoveryPassword Registration
      • Profile and Preferences
      • Skyone Autosky Platform
        • Dashboard
        • Accounts
          • Servers
            • Server Options
        • Environments
          • Micro environment
            • Micro environment instance
            • Micro environment servers
          • Scaling environment
            • Scaling environment instances
            • Scaling environment servers
          • Other features of the environments
        • Clients
          • Edit and Clone
          • Users
          • Applications
          • Sessions
          • Manage Access Restrictions
          • Maintenance
            • Maintenance history
        • Users
    • Cloud Server
      • Cloud Server Options
      • Backup Audit
  • Studio
    • Overview
      • Create an account
      • Recover Password
      • Quick Platform Guide
      • How to test the platform for free
      • Workspace
        • Creating a new Workspace
        • Find a Workspace
        • Sending an invitation to a Workspace
        • Editing a Workspace
      • Organizations
        • Creating an Organization
        • Organization Overview
        • Organization Management
        • Organization Monitoring
      • Settings and Preferences
        • Profile
        • Notifications
        • Usage and Billing
        • Users and Permissions
    • Integrations
      • Integration Management
        • Create integration
        • Import Integration
        • Edit Integration
        • Integration Options
        • Flows of this integration
      • Flows
        • Flow management
          • Creating a flow
          • Flow options
          • Flow Canva: configuring and editing the flow
            • Flow Canva: overview
            • Exception Handler
              • Exception Handler - Configuration
              • Exception Handler - Cases
            • Multicontext Flows
              • Example: Multicontext with an API Gateway
              • Example: Multicontext with a Time Trigger
            • Flow Settings
        • Triggers of a flow
          • API Gateway Triggers: Adding and Setting
          • AS2 Triggers: Adding and Setting
          • Queue Triggers: Adding and Setting
          • Flow Triggers: Adding and Setting
          • Time Triggers: Adding and Setting
          • Webhook Triggers: Adding and Setting
        • Tool Modules
          • AS2 Module
          • CSV Module
          • Data Transform Module
          • Data Balancer Module
          • EDI Module
          • Flow Call Module
          • IF Module
          • JavaScript Module
          • Log Module
          • Loop Do While Module
          • Loop For Module
          • Return Module
          • XML Module
          • Other Tool Modules
        • Module Header
        • Connecting components of a flow
        • Editing triggers and modules
        • Data Operations
          • Object Handling
            • Practical example: Handling variables
          • SMOP (Small Operations)
          • Parameterization rules
    • Modules
      • Module management
        • Creating a Module
        • Importing a Module
          • IAC Files - Integration as Code
        • Editing a module
        • Module Options
      • Settings and Operations
        • Module settings
          • Connectivity: Database
          • Connectivity: Email
          • Connectivity: REST
          • Connectivity: SOAP
          • Connectivity: File
          • Connectivity: RFC
          • Connected Account Management
        • Operations
          • Importing operations into REST Modules
          • Operation Management
        • Flows Using This Module
    • API Gateway
    • Terminals & Agent
      • Agent
        • Versions supported by Agent
        • How to Update the Agent Version
        • How to back up Agent files
      • Terminals
    • Data Management
      • Engine
        • How to use the Data Engine Proxy
      • Parameters
      • File filters
      • File templates
      • File Jobs
      • JSONata Jobs
    • Data Lake
    • Data Warehouse
      • Data Jobs
      • Databases
    • Artificial Intelligence
    • How to
      • Insert JSON into databases
      • Flattening: Data transformation using JSONata
      • How to use Form Data
      • Understanding recursion in JSONata
      • REST Module Output Consolidation
      • How to configure a component timeout?
      • Isolated in execution: concept and application in variables
      • URL Parameters in API Gateway
      • Use case: API Gateway trigger parameters
      • Use case: Exception Handler in financial transactions
      • Use case: using Groups to manage access to flows
      • How to create a download endpoint and integrate with Power BI
      • Is it possible to use two triggers in a single flow?
    • FAQ
    • GIGS: The complete guide
    • Glossary
  • Cybersecurity
    • Overview
    • Threat Analysis
      • Security Panel
      • Targets
      • Schedules
      • Target Resolution
      • Threat Group
      • Report
    • How to install Bitdefender security agents
Powered by GitBook
On this page

Last updated 3 days ago

Concept

A terminal is a logical entity that represents the connection of a single "Agent", installed on a machine and linked to a user, to that user's "Workspace" on the platform.

A "Workspace" can contain multiple terminals, as long as each terminal is connected to an Agent.

On a computer where an "Agent" is installed, the application can access a company's Database or the REST interface of an ERP, and therefore one terminal can intermediate the execution of several integrations, without the need for a public API. This way, several distinct flows within a "Workspace" can reference the same terminal through one or more user accounts.

After installing and configuring an "Agent" in a local environment (On Premises), a terminal is automatically created on the Skyone Studio platform. From then on, you can choose and use this terminal on the platform to configure REST or Database accounts. When you select a terminal in the configuration of these accounts, the account credentials are sent to the Agent to be used locally.

Multiple connected accounts can be associated with the same terminal. This way, you can create multiple users in a database to be used by different integrations. Each user can be configured under a different account, but all accounts will point to the same terminal.

An "Agent's" terminal is permanently monitored, so the platform always knows when it is connected and operational. On the other hand, the collapse of a terminal, noticed through the disconnection of the "Agent" connected to it, implies the collapse of all the accounts connected to it.

You can install as many "Agents" as you like, for the same user or "Workspace", as long as they are installed on different devices and have different names and locations. Each one will appear as a different terminal on the platform.

Connected Accounts

By default, the "Terminal" field of a REST or Database account is left blank, which means that the "Agent" is not used during the connection. To use a previously installed "Agent", you must select one of the terminals (active or not) that are configured in the system:

When you use a "Terminal" on an account, the execution of operations on a module (tests) or on a flow (tests or execution) will only occur if the "Agent" is running and the "Terminal" status is active (green).

Terminal Management

In the "Terminals" tab you will see all the terminals connected to the selected "Workspace". If you have not yet installed and configured an agent, you can download the "Agent" by clicking "Download Agent".

Once one or more "Agents" have been configured, the list of available terminals and their respective details and status will be displayed on the screen:

Each line corresponds to an "Agents" entry with its basic information. The information on this screen is dynamic, updating automatically in a few seconds.

Fields:

  • ID: unique "Agent" identifier

  • Agent Name: name assigned in the "Agent" configuration

  • Username: name of the user who configured the "Agent"

  • Connected at: last time the "Agent" connected

  • Agent IP: IP address of the computer where the "Agent" was installed; displayed only when it is connected

  • Host ID: host signature that uniquely identifies the machine where the "Agent" is installed

  • Status: "Agent" connection status

Terminal Information

To view detailed information on a terminal:

  1. At "Terminals", choose the Agent that you want to view and click the "More Options" icon;

  2. Select "View";

  1. The Terminal Information window will be displayed an you will view the following fields:

  • Host ID: host signature, which uniquely identifies the machine where the "Agent" is installed

  • Agent Name: name provided in the "Agent" configuration

  • Agent localization: localization provided in the "Agent" configuration

  • Agent IP: IP address of the machine where the "Agent" is installed

  • Connected at: date of last connection, in the format DD/MM/YYYY HH:MM:SS

  • Last APC control: the last time Integra.Sky sent an APC (Agent Procedure Call)

  • Last APC data: last time Integra.Sky received messages

  • Controls delivered by the APC: number of messages sent

  • Data received by the APC: number of messages received

  • Connected accounts: accounts that point to the "Terminal"

Testing the Connection

The connection status ensures that there is an established connection, but does not guarantee full operation. The connection test performs a complete test involving the Agent.

To test the connection:

  1. At "Terminals", choose the "Agent" whose connection you want to test and click "More Options" (three-dot icon).

  2. Select "Test Connection"

  1. Wait for the connection to be tested and the result.

Terminal Logs

To view the logs of a terminal:

  1. At "Terminals", choose the "Agent" you want to view the logs for and click on the "More Options" icon;

  2. Select "Logs";

  1. The Terminal logs will be displayed (if any).

Deleting an Agent

If you delete an "Agent" from the "Terminals" tab and then want to use the application again, you will need to uninstall and reinstall the application. This is also necessary if you want to change the initial installation settings (Workspace, Skyone Studio account, Agent Name and Location).

To delete an "Agent", follow these steps:

  1. At "Terminals", choose the Agent you want to delete and click on the "More Options" icon;

  2. Select "Delete Agent";

  1. Enter the name of the terminal you want to delete and then confirm the action by clicking "Delete";

  1. Back to the "Agent", the connection to the Server will be broken. To set up the "Agent" again, you’ll have to uninstall and reinstall it.

  1. Studio
  2. Terminals & Agent

Terminals

PreviousHow to back up Agent filesNextData Management
  • Concept
  • Connected Accounts
  • Terminal Management
Concept
Connected Accounts
Terminal Management
Terminal Information
Testing the Connection
Terminal Logs
Deleting an Agent
Example of connected account configuration