Aquafold Licensing

[Timmy Tatel]

Thankyou for considering Aqua Data Studio.

If you have any technical questions, or are in need of support, please visit our support page.

For licensing questions, please visit our licensing page.

To activate a valid license, select Commercial and enter the

company name and license key EXACTLY as you received it from

AquaFold, Inc. in your registration email. Do NOT include extra

spaces in front of or after your company name or license key.

Click Activate.

A key administrative aspect of managing Aqua Data Server is ensuring that you have sufficient licenses to cover all activity in the system. License enforcement in Aqua Data Server is based on thread count and is not based on user or processor count. The License Management interface provides a central place to view and manage all of your licensing information. If you have any questions regarding licensing or would like to purchase a license, please contact lic...@aquafold.com.

Since licensing is thread based, when you purchase a license key, the key is embed with the number of threads for which the license is valid. After you activate the license in Aqua Data Server, the system enforces the maximum number of threads that can execute simultaneously. e.g. if you purchased a 10 thread license, Aqua Data Server will only allow up to 10 threads from executing simultaneously within the application. Most actions such as accessing the GUI or executing a script in Aqua Data Server require a thread license. To increase the number of simultaneously executing threads, you must purchase additional thread licenses. Aqua Data Server calculates the total number of threads available by summing up the licensed units across all active licenses.

You might want to remove a license from Aqua Data Server if your evaluation has expired or if you have incorrectly entered the license information. In case of incorrect entry, you can also edit the license information directly instead of deleting and then re-adding it. However, you will need to deactivate the license first prior to editing. Similar to adding a license, removing a license is a two step process: deactivating the license key and then deleting it.

Welcome to Aqua Data Studio Documentation - Below you will find 6 quick steps to getting you started with Aqua Data Studio. Once you have your database query tool up and running, you may continue into the documentation to understand the different features of Aqua Data Studio.

1 Downloading - You can download the appropriate package for your operating system by logging into the Customer Support Portal or registering for a free trial. If you experience any download problems or just slow download speeds, please send an email to arch...@aquafold.com so that we may upgrade our servers and bandwidth.

3 Connecting to a database - Ready to connect? View the sample registration screenshots provided in the gallery for help with your specific database (registration/screenshots). If you still experience problems connecting to your database you should review the JDBC driver and the registration section of the documentation.

Our Enterprise License is meant to minimize the cost of license key management and order processing. The Enterprise License offers companies with larger deployments of AquaFold products a single Enterprise License Key for frictionless distribution with license usage true-up. This minimizes operational and processing costs on both ends, allowing us to offer cumulative (versus per order) pricing to Enterprise License customers.

In addition to lowering the operational and licensing costs in standard desktop environments, our Aqua Data Studio Enterprise License has been specifically designed for ease of use in Terminal Server and Citrix environments.

In appreciation for the great effort and contribution that is put forward by the Open Source Software community, AquaFold provides no-cost licensing to qualified individual OSS developers. If you qualify, email us at lic...@aquafold.com for more information.

1. In order to enable the scanner to gather the inventory information directly from the host ESX(i) device, the VMWare SNMP agent needs to be enabled on the host device and the SNMP community needs be enabled, that the SNMP scan will use.

There are various types of B2B connectors in Data Analytics and they implement different technology depending on the use case. This document will attempt to give you some basic troubleshooting techniques for each type of connector and also supply other documentation to review for deeper information on a particular topic, if necessary. If you're wondering about what type of connector we're troubleshooting, there are specific behaviors that you can look out for to figure out which type of b2b connector you're troubleshooting.

There are several connectors that use web scraping to gather data from vendors and import it into your Inventory. If you've already set up some of these and are wondering where you can find the data in inventory you can use the B2B column set that is in your list of public column sets (Administration > Column Sets > All Column Sets). This will show you a list of the most common columns used for B2B connectors and is an easy way to see if you have data imported for your devices.

Several Web services online now offer two-factor authentication. Please be aware that if you have two-factor authentication enabled that these web scraping technologies will not be able to log into the respective websites until one of the following happens:

During this time, when the rule is running it will save log information in the MP_Log folder. Usually, if you run these rules by hand it will have a log with the appropriate name based on the name of the rule you created. However, when scheduling these things the log is written to a generic file name like "MPRunSched_DATE.log". So with this in mind, it's generally best to run these rules by hand when troubleshooting the issue, by right-clicking on the rule name and selecting "Run Now".

Also, if you have a report that matches the format expected for rule your troubleshooting you can always place a copy of the report (usually a CSV or XLSX file) in the MP_Temp folder for the rule you're working with. Then all you'd need to do is run the rule and kill the ManagedPlanet WebPull process from task manager and it should attempt to import the file for you. However, you'd only do this if the website we were attempting to gather data wasn't working as expected.

Additionally, there are issues where you may not be able to log in to certain websites without taking additional steps. Unfortunately, the scripting does not detect if it was able to log in successfully, but you can verify this by using the debugging window mentioned in this document. As usual, you'll want to double check your log in details you've provided as well as if you have Two-Factor Authentication or not.

There are several Web API rules that are in place, these generally don't take a whole lot of manual troubleshooting as a result. First, you'll want to make sure that you use the previously mentioned B2B column set to ensure that data is being imported for your devices. If not, you can run the rule manually and inspect the log located in your MP_Log and MP_Temp folder. Usually, if you run these rules by hand it will have a log with the appropriate name based on the name of the rule you created. However, when scheduling these things the log is written to a generic file name like "MPRunSched_DATE.log". So with this in mind, it's generally best to run these rules by hand when troubleshooting the issue, by right-clicking on the rule name and selecting "Run Now".

In your log, we will generally leave the type of error occurred during the process. Most commonly you may see something like a 401 error, or something like that, in your log. These are usually responses received from the vendor's public API that was used. Sometimes you may run into situations where you are getting 401 messages stating that you've been prohibited access from their server. When you run into this error there are a number of possibilities as to why you would have gotten that error at that time here's a quick list of a few:

The Universal B2B connector uses the same UI as the Import Data data rule and there is some documentation on that. I'd recommend reviewing the following documentation to get assistance with setting up one of these rules:

When running the "Archive to Asset Control" option from the right click menu for device(s) in the Core Console, the job will start then fail with an "All link attributes are blank for source device." error as seen in the diagram below:

The un-modeled serial number data needs to be removed from the database. This is done using the DBRepair tool. Instructions for this tool are found here: Database Repair Utility (DBRepair.exe download)

There may be an instance in which you may want to import date's into your LDMS Inventory. Let's say for instance if you were importing this data into a new attribute in inventory all you'd have to do is simply name the new attribute in your import rule and you're done. Unfortunately when importing DATE types it doesn't work the same way. In order to import a date you will need to first model the inventory attribute.

IMPORTANT: After making these changes to the Database, make sure to restart the LANDESK Inventory Server Service. It would not be a bad idea to stop the inventory service first and start it back up again once you've made the changes.

Vendors sometimes implement changes to their websites that interfere with LDDA's ability to gather data. However, there are steps that can be done manually to temporarily get past some of these changes..

There are times when there may have been changes on a vendor's website that may interfere with the automated process of retrieving information. In this case it can sometimes be done manually through the Managed Planet Webpull window if the website is accessible.

3a8082e126