Skip to main content

FAQs & Troubleshooting

All commonly asked questions, answers, and troubleshooting solutions are listed here.

If you have a problem we have not answered yet, please do not hesitate to push the button.


Q: Where can I find information about the MaDaM query language?

A: The MaDaM web frontend offers basic information about the query language and its capabilities in the Search & Analysis page. You can find a help button labeled with a "?" to the right of the main search bar.

Q: Is searching case sensitive?

A: Searching in the main search bar is not case sensitive, but the filtering in the individual column headers is.

Q: Can I use wildcards in the searches?

A: Generally, wildcards (such as "?" or "*") can be used in searches, but only on fields which are "wildcard-enabled". This option is disabled by default and can be enabled for select fields in the model page. Please note that simply enabling this option for all fields nets close to no benefit for a high performance cost.

Q: Can I search for any given value of a signal?

A: No, you can only search on statistical relevant metrics (maximum, minimum) of the signals. Storing each value of each signal is not possible in a sustainable environment and almost never necessary. If specific, individual values are of interest, you can execute jBEAM calculations for these values to have them added as 'virtual' signals for searching.

Q: What is the purpose of the model type 'Entity'?

A: The model is hierarchical in structure - each type contains the fields that it defines and the fields that its parents define. 'Entity' is the root type to ensure that every model type that is created has the core set of fields that are required by the system.

Q: How can I change fields for 'Test' or 'Data Object'?

A: For basic types, such as 'Test', 'Data Object' or 'Entity', users can't make manual changes. In order to maintain system integrity, changes on these predefined root elements can only be done programatically be the AMS.

Q: What does it mean if a field is 'faceted'?

A: Fields that are marked as 'faceted' have their values displayed as filter elements in the facet tree on the search page. When defining which fields should be displayed in this tree, it's sensible to only select distinguishing elements. Facetting Data Objects, for example, results in a set of facets that's too large and intertwined to be useful as filters.

Q: What does it mean if a field is 'nested'?

A: Whether a field is 'nested' or not determines the relationship between instances of the referencing type and the field content. For an example, we will call the referencing type 'container' and the referenced type 'content'. There are four distinct relationships; each container can either reference one content element or multiples, and each content can either be referenced by one container or by multiples. Therefore, we can have container to content relations as follows; 1:1, 1:n, n:1, n:m. 'Nested' reference fields lead to a 1:1 relationship while 'nested' reference list fields lead to a 1:n relationship. Similarly, 'non-nested' reference fields lead to a n:1 relationship and 'non-nested' reference list fields to a n:m relationship.

Q: How can I order the sequence of columns in the search page?

A: The order of columns can be defined in the model page. Going into the model page, it's possible to select the model type for which columns should be defined and select the 'Columns' tab.


The jBEAM Webservice contains a LicenseServer for interactive analysis. So the jBEAM Webservice needs a valid license file for the start-up.

Navigate to the /webbapps/jbeam/WEB-INF/lib directory and run the jBEAM-MaDaM-XXX-LicenseServer-X.X.X.X.jar” on the server (The correct name depending on your version.). The Execution will fail, because of the missing license, but you can create a “license.request” file. This “license.request” contains the serial number of the jBEAM version and some hardware information of the server. Sent this file to and we sent you the needed “.license” file. Copy this “.license” in the Tomcat installation directory. 

Alternatively, it’s possible to create the license request file via command line. The following command must be executed in a folder containing the “jBEAM-MaDaM-XXX-LicenseServer-X.X.X.X.jar” jar file and with writing access:

If there are issues in the frontend, ranging from elements that aren't displayed correctly to buttons not working as intended, please contact your support and include both the backend logs and the frontend logs.

If the login no longer works, it could be simply due to extreme load on the system. Please try after a few minutes. If the login repeatedly doesn't work, please contact your support and include the backend logs and include any helpful information, such as time of the last successful login.

If the Importer has an issue that affects the uploading or editing, it may be due to extreme load on the system. Please try again after a few minutes. If the process repeatedly doesn't work, please contact your support and include the importer and backend logs.

If the issue is only related to the importer (e.g. slow editing, errors during configuration) often times the importer logs themselves are sufficient.

For most issues, there are three kinds of different logs that are useful in solving the issue.

Backend and Server jBEAM logs: These are obtained from the directory of the container (usually Tomcat or Docker) and if they are requested, the standard output (usually stdout) and standard error (usually stderr) log files are most important

Importer and Client jBEAM logs:These can either be obtained from the AMS console that opens automatically for certain errors or via the java console. For most clients, the java console has to be enabled via the system settings > java.

Frontend logs:These can be obtained from the developer console of the web browser, which is commonly opened by pressing 'F12' while in the browser

Download Area