Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

@arvand-owji
I'm going to recommend a hybrid approach. Use a userModule.js file like this, you can add it from the UI settings page. We are going to add a parent state which you can then nest custom pages inside of. The myApp.home state etc will be nested inside the <div ui-view> element of the myApp state. The "page" that is linked to from the myApp state is the menu,

define(['angular', 'require'], function(angular, require) { 'use strict'; var userModule = angular.module('userModule', ['maUiApp']); userModule.config(['maUiMenuProvider', (maUiMenuProvider) => { maUiMenuProvider.registerMenuItems([{ name: 'myApp', url: '/my-app', template: '<ma-ui-page-view xid="d012dd15-0b4e-4539-8e8a-e0235c08411d"></ma-ui-page-view><div ui-view></div>', menuText: 'My app base', //menuHidden: true, abstract: true }]); }]); return userModule; }); // define

Menu "page":

<div class="ma-designer-root" id="cd40a324-2725-42fa-9778-12255ebb5a62" style="width: 1024px; height: 48px; position: relative;"> <ma-button id="54f9db80-3064-4c61-8db4-59380f86df6e" style="position: absolute; left: 104px; top: 0px;" icon="android" label="Page 1" raised="true" palette="accent" ui-sref="myApp.page1"></ma-button> <ma-button id="7bd73a7c-6923-4e3d-93e2-85c2d4cf3f25" style="position: absolute; left: 0px; top: 0px;" icon="home" label="Home" raised="true" palette="primary" ui-sref="myApp.home"></ma-button> </div>

Home page, page 1 etc.. Create pages as desired then add menu icons for them, making sure to choose "My app base" as their parent.

The easiest way is to click on Data Sources under Adminitration. This will open up the legacy UI and then you can select System Settings from the top menu.

Something like....

import java.text.SimpleDateFormat; import java.util.HashMap; import java.util.Map; import org.apache.commons.lang3.StringUtils; import com.infiniteautomation.datafilesource.contexts.AbstractCSVDataSource; import com.infiniteautomation.datafilesource.dataimage.NumericImportPoint; public class JergForumCsvQuestion extends AbstractCSVDataSource { private boolean headersConsumed = false; private SimpleDateFormat dtf = new SimpleDateFormat("yyyy-MM-dd HH:mm"); @Override public void importRow(String[] data, int rowNum) { if(data.length == 0) return; Map<String, String> extraParams = new HashMap<>(); String[] rowData = data[0].split(";"); if(rowData.length < 7) //avoid index out of bounds return; try { //subtract the timezone, or you could put it into the date formatter (or add the timezone, //it's not always easy to know if they're saying those times are in UTC-5 or those times are UTC) long time = dtf.parse(rowData[3]).getTime() - 5*60*60*1000; this.parsedPoints.add(new NumericImportPoint("PV Solar kWh", Double.valueOf(rowData[5]), time, extraParams)); this.parsedPoints.add(new NumericImportPoint("PV Solar W/m^2", Double.valueOf(rowData[6]), time, extraParams)); } catch(Exception e) { System.out.println("Exception: " + e.getMessage()); } } }

Ah amazing, I'd done exactly that but never switched templates to get it to reload.
Wonderful! Thanks Phil.

The BACnet module's source is closed, so you cannot build that yourself. You downloaded the demo of the 3.0 core, so you can grab the BACnet module from 3.0/web/modules/BACnet, you can just move that into your git/ma-core-public/Core/web/modules and it will be loaded when you launch the core. That's where you got the Meta data source.

You will from build the pom.xml. Right click on it, run as a maven build. For the settings you need to link to the settings.xml file (which is in the other Maven builds you have defined for Virtual and Serial), the target is 'install' and the profile is 'install-module' (from the settings.xml file). This will create m2m2-YourModuleName-x.x.x.zip in git/ma-core-public/Core/web/modules which will be loaded when you launch Mango. Your module's 'loading' is done by checking which definitions classes (those in the com.serotonin.m2m2.module package) are extended in your module, and using them accordingly.

I have just done this again, new Eclipse workspace on the previously fresh computer. I started by deleting C:\Users\Phillip\.m2 to attempt to get it back to perfectly clean. Then I opened a new Eclipse workspace and cloned the projects from Github. I right clicked on the Core\pom.xml and did a Run As... --> Maven Install. I had to set / add my JDK again in Eclipse, through Window --> Preferences --> Java --> Installed JREs, (as well as the nested "Execution Environment" panel for JavaSE-1.8 and 1.7). Then I got some errors about Jars when running the maven install after setting the JDK. So, I did a Run As... --> Maven Clean on Core\pom.xml. Then I closed Eclipse, then deleted C:\Users\Phillip\.m2\repository. Then opened Eclipse into that workspace again, right clicked on Core\pom.xml, Run As... --> Maven Install ... success! Debug configurations.... Java Application --> New, selected project CoreBundle, did a search for Main classes, com.serotonin.m2m2.Main was right there in the list. Selected that, added the -Dma.home="C:\IA\Instance4\ma-core-public\Core" VM argument and started Mango.

Looks like a corrupt jar in Maven .... now to the next issue looks like I am missing a library

Tests in error:
DateUtilsTest.testPreviousMinutes:43 NoClassDefFound org/joda/time/DateTime
DateUtilsTest.testPreviousMonths:170 NoClassDefFound org/joda/time/DateTime
DateUtilsTest.quickTest:24 NoClassDefFound org/joda/time/DateTime
DateUtilsTest.testPreviousHours:74 NoClassDefFound org/joda/time/DateTime
DateUtilsTest.testPreviousWeeks:136 NoClassDefFound org/joda/time/DateTime
DateUtilsTest.testPreviousYears:201 NoClassDefFound org/joda/time/DateTime

Tests run: 6, Failures: 0, Errors: 6, Skipped: 0

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Mango Parent ....................................... SUCCESS [ 0.462 s]
[INFO] Mango Assembly Descriptors ......................... SUCCESS [ 0.555 s]
[INFO] Mango Core ......................................... FAILURE [ 1.329 s]
[INFO] Mango Modules ...................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE

@jefero
We don't have an example for integrating the Mango dashboards components into an app, however you should be able to leverage the Angular modules which are in the MA_HOME/web/modules/dashboards/web/js/mango-3.3 folder. I'd suggest looking at the adminTemplate/app.js file to see how to bootstrap the Angular application.

The login procedure is cookie based at the moment so its not ideal for integrating into an app. We will be implementing JSON Web Token authentication for the REST API in the next release.

Hi Dung,

You need to mvn install the core project. So,

cd /path/to/repos/ma-core-public
mvn install

Hi Joel,
Thank you so much for your help ^^

I've also posted a topic here with more detail on upgrading your dashboard.

Hi Mebius,

The error is as described, there is a mismatch in point type. Either this is in your code in the data source definition class you didn't define a unique data source type, or (more likely) you used another tab to browse either a data source or data point, which due to some state saved on the server in the user's session, then tried to perform an action which had relied on the state being another way. Eventually, it is our intention to remove a lot of this state tracking, but lots of pages use DWR so it is not a small effort.

To know if that is it, you would just have to edit the point again (click the pencil) and try to make your changes and save it again.

Hi Sasa,

For the core I believe that's all.

Hi Sasa,

You are most welcome!

The build.xml file in each other module's project can be used to build the module. Simply use these for your ant builds, and you can copy it into new modules and it should work fine. It relies on your core.home ant variable to point to the /path/to/ma-core-public/Core as it references that "module-build.xml" and it needs to know where to deploy the modules. This property was probably already set, as you need it to build the Core.

@phildunlap

Hi phildunlap,

I use the code from zip file instead of cloning code from git, module build works fine now with the same steps.

Thank you very much for your kind help.

Thanks for updating this with the solution Matteo.