For information on upgrading Tetra Agents, see this topic: https://developers.tetrascience.com/docs/upgrade.
This guide describes how an IT Administrator can install and configure the Tetra Chromeleon Agent (version 1.x.x). It describes how to:
- Select and set up a data connection
- Install the Tetra Chromeleon Agent
- Configure the Tetra Chromeleon Agent
- Select the Data Vault
- Monitor Tetra Chromeleon Agent progress and server system metrics
Before you begin, ensure that your environment meets the prerequisites listed here.
The Tetra Chromeleon Agent generates RAW files which are uploaded to the Tetra Data Platform (TDP) through a Data Connector.
To enable secure file transfers, TetraScience provides two available data connectors:
- [Generic Data Connector (GDC)] (https://developers.tetrascience.com/docs/agent-common-behavior#generic-data-connector-aka-gdc)
- [Cloud Data Connector (CDC)] (https://developers.tetrascience.com/docs/agent-common-behavior#user-defined-integration-aka-udi) (Note that the UDI was renamed the Cloud Data Connector (CDC) in version 3.1 of the TDP software.)
Before you install the Tetra Chromeleon Agent, you must set up one of these data connectors. To determine which data connector to select, click this [link] (https://developers.tetrascience.com/docs/agent-common-behavior#agent-tetrascience-platform-integration-summary) for details.
TetraScience provides a Microsoft Installation Package (.msi) file to install the Chromeleon Agent in the host server. To access the server and run the installation package, you must log in as an Administrator.
- To obtain the link to the .msi installation package, please contact your TetraScience Customer Success Manager (CSM).
- Once you have the link, download the Tetra Chromeleon Agent to a machine
that runs a supported version of Thermo Fisher Chromeleon.
- Double-click the Tetra Agent installation file to start the installation wizard. The installation wizard guides you through the prompts. The default Tetra Chromeleon Agent installation path is:
- After the Tetra Chromeleon Agent is successfully installed on the server, you can access its Windows-based Management Console under the TetraScience folder from the Windows Programs. Select TetraScience Agent Chromeleon from the Windows Programs list to open the Agent.
After you have successfully installed the Tetra Chromeleon Agent, use the Windows-based Management Console to continue the Agent configuration.
Click Configuration from the menu on the left. The Management Console is divided into four sections:
- Agent Status
- Agent Configuration
- Agent Group User
- Service Settings
This section indicates the current state of the Agent's processing status:
- Agent Service Not Installed
- To save the Chromeleon Agent configuration, click Save.
- To start the Chromeleon Agent with the new configuration settings, click Start. When the Chromeleon Agent starts, the status indicator shows Running for an Agent that is successfully up and running.
- When the Chromeleon Agent starts, the Stop button is enabled. To stop the Chromeleon Agent, click Stop.
- You can increase the Agent's reliability by ensuring that it remains online without having to manually check it each day. If you enable this option, the Agent creates a Windows Task that checks the status of Agent service daily (at the run time you specify). Enter the time in the Run Time field.
- If the Agent is stopped, then the scheduled Windows Task automatically restarts the Agent service.
- If the Agent is running, nothing further happens.
- If you manually stop the Agent, then the Windows task is removed, and the Windows Task that you create runs under the LocalSystem account.
Use this section to configure the Agent connection the Tetra Data Platform. TetraScience provides several options to connect the Tetra Data Platform. Click this link to select the best option for your company's needs.
To have the Tetra Chromeleon Agent directly upload files to the AWS S3 bucket bypassing GDC or CDC, set the S3 Direct Upload option to Yes. When you set this option to Yes, you can upload a maximum file size of one TB. No is the default setting.
- If you use the S3 Direct Upload option with GDC, you must add an L7 Proxy Data Connector in the same Data Hub where you set up the GDC. Additionally, the port of the L7 Proxy Data Connector is open. To learn more about GDC, see this link.
- To learn more about CDC, see this link.
To enable the Agent to receive commands from the Tetra Data Platform, set the Enable Queue option to Yes. When you set this option to Yes, the Agent keeps polling the queue messages sent from the Tetra Data Platform. The messages provides instructions to the Agent. In version 1.2.0, only the Sequence Creation Command can be received. No is the default setting.
TDP Commands and Queue Security
Although queues enable TDP to send commands to the Tetra Agent, the command execution request process is secured.
- TDP does not send actual commands, but rather messages that request commands for execution.
- The Tetra Agent has its own queue to receive messages from TDP and is not shared by any other agent.
- When queues are enabled, the Tetra Agent proactively reads the queue for messages containing command execution requests and determines whether to initiate the command execution. You can control whether to enable local command execution by toggling the Enable Queue option for the Tetra Agent.
- The Tetra Chromeleon Agent can only execute certain a limit set of pre-built commands. As of version 1.2.0, the Tetra Chromeleon Agent can only execute the Sequence Creation Command.
For more information on how to initiate the Sequence Creation Command, see this topic.
Click Advanced Settings to open the Agent Configuration Advanced Settings pane.
You can specify the time intervals for these fields (default value for each field is 30 seconds):
- Data Connection status check every - Indicates how often the software checks the status of the connection (heartbeat) between the Tetra Data Platform and the Agent. If the Tetra Data Platform does not receive a message indicating that the Agent is "alive" for more than 5 minutes, it assumes that the Agent is offline.
- File Upload Job runs every - Indicates how often to upload files to the Tetra Lake.
- Agent log files upload every - Indicates how often to upload log files to the Tetra Lake.
SQLite Database File Backups
To enable the Tetra Chromeleon Agent to automatically perform regular backups of the SQLite database file, set the S3 Direct Upload option to Yes. When you enable this option, the SQLite database file (which stores agent configuration data) is uploaded to the backup bucket in the Data Lake. If a Tetra Chromeleon Agent failure occurs, you can restore the database file from the backup bucket and continue processing.
If you do not use not use the S3 Direct Upload option, then we recommend that you create periodic backups of the Tetra Agent database, which is typically stored in the installation folder under C:\TetraScience<agent>\Bin\Database. In the event of a failure (for example, if the host server drive is lost), this would enable the data extraction to continue from where it left off without having to re-upload all of the data.
Before you set up a Tetra Chromeleon Agent from GDC or CDC, you must enter:
- (Required) An Agent ID. The Agent ID (a UUID) is used to connect the Tetra Data Platform. You can retrieve Agent ID from the Tetra Data Platform when you set up GDC or CDC.
- A full connection URL from GDC or CDC (as shown in these URL examples):
- GDC URL is
- CDC URL is
- GDC URL is
Verify the Agent ID and Connection URL
- Agent ID is required. The Connection URL is required if you are uploading RAW files to the Tetra Data Platform; optional, if you are not.
- Before you use the Agent ID and URL with the Tetra Data Platform, we strongly suggest that you verify both with your TetraScience Customer Success Team.
If you use the CDC Connector, then you must:
- When using the JWT token, the Org Slug field is required. Enter the Org Slug to attach it to the header.
- Enter the JWT token in the Authorization field to attach it to the header. To learn how to get the JWT token, see CDC.
- Click Add/Edit to open a dialog and enter the JWT token.
- Click Save to close the dialog and encrypt and save the JWT token. The Agent validates the connection immediately and displays the updated connection status next to the Connection URL field.
Beareris optional. If you do not provide it, then the Tetra Chromeleon Agent adds it automatically.
The Agent Group User is the service account that runs the Tetra Chromeleon Agent.
- If Chromeleon enables LDAP, then this User Name and Password must be a valid Chromeleon user account.
- If Chromeleon does not enable LDAP, then this User Name and Password can be any valid Windows account.
Group user tip
If you are having trouble signing in with your Chromeleon user account, try adding
.\at the front of your user name. For example, if you user name is "Tetra", try using ".\Tetra"
When the you enter the Chromeleon Group User Name and Password, the Agent validates the account immediately. If the user name and password are correct, then the Tetra Chromeleon Agent displays a Valid status next to the field.
Use this section to configure the Tetra Chromeleon Agent's settings at run time.
- Set the Processing Interval (Seconds) field to indicate how often the Tetra Chromeleon Agent runs the Injection extract task in the specified time interval. The extract task includes scanning Chromeleon to detect new or modified injections, and the generation of the RAW injection file.
- Select the Injection Service Output Folder to where you want to temporarily store the generated RAW file. After the files have been uploaded to the Tetra Data Platform successfully, the RAW file is deleted from the temporary folder to save disk space.
- Set the Chromeleon LDAP Setting to match the LDAP setting in Chromeleon. If Chromeleon enables LDAP, select Yes; otherwise, select No.
- If LDAP is not enabled (Chromeleon LDAP Setting = No), then you must enter information in the User Name, Password, and Role fields so that the Tetra Agent can access Chromeleon based on that specific user account.
Daily Agent Run Schedule
After you complete the initial installation and configuration, you can use a Windows Task script to re-start the Tetra Chromeleon Agent (for example, you can set it to run at 1:00 AM) and ensure that it runs constantly. For details, see [link] (https://developers.tetrascience.com/docs/using-windows-schedule-task-to-schedule-agent-services).
The Tetra Chromeleon Agent can access all of the Data Vaults that the user has permission to access. Instead of generating the injections from all of the Data Vaults, you can select individual ones from the Data Vault list.
To select individual Data Vaults:
- From the Management Console, verify that the Tetra Chromeleon Agent has been started and has a status of Running.
- Select Data Vault from the left of the Management Console to open the Data Vault dialog. The Data Vault list takes a minute or two to populate.
- Select the Data Vaults from which you want the Tetra Chromeleon Agent to extract injections.
To review the Tetra Chromeleon Agent's run time progress and host server's system metrics:
- Select Summary from the left of the Management Console to open the Summary dashboard:
From the summary page, you can review see how many total injections have been scanned in a given Data Vault, and how many injections have been generated and uploaded. If any failure occurs, the numbers display here. If there are any errors, the error message, and related injection URL displays on the right.
In addition to the Injection processing summary, the Agent includes system metrics on the host server as well. That information is uploaded to the Tetra Data Platform.
The Processing Summary dashboard displays this information:
- Total Scanned - Number of files scanned by the agent
- Total Generated - Number of files generated
- Failed to Generate - Number of files that failed to generate
- Pending To Generate - A pending state. When the Tetra Chromeleon Agent stops, the Pending To Generate state is reset to zero. Any file that was not completely generated is removed from the Tetra Chromeleon Agent's database and resets the counter. When the Tetra Chromeleon Agent restarts, it calculates how may files it needs to generate and starts from the beginning instead of resuming from where the file generation left off.
- Pending For Upload - A pending state. When the Tetra Chromeleon Agent stops, the Pending For Upload state is reset to zero. Any file that was not completely uploaded is removed from the Tetra Chromeleon Agent's database and resets the counter. When the Tetra Chromeleon Agent restarts, it calculates how may files it needs to upload and starts from the beginning instead of resuming from where the file upload left off.
- Uploaded - Number of files that have been uploaded to the agent successfully
- Failed To Upload - Number of files that failed to upload to the agent
This section displays any detailed error messages.
This section displays the host server system metrics and messages every minute and provides these metrics:
- Data Connection (connection status between the Agent and the Tetra Data Platform)
- Available Disk Space (in GB)
- Disk Usage (as a % of the total)
- CPU Usage (as a % of the total)
- Memory Usage (in MB)
- Available Memory (in MB)
Updated about 1 year ago