Apply a background image with the desired dimensions.

I'm running Mango 1.9.0 and recently converted my derby db to mysql version 5.5.8. I ran into a couple of issues which I was able figure out and fix. Note: these issues may have already been addressed in the newer versions of Mango.

1. There is a new version of the mysql java connector jar available from the mysql website. Download mysql-connector-java-5.1.14.tar.gz, unzip it, and place mysql-connector-java-5.1.14-bin.jar in WEB-INF/lib directory.

2. Several sql scripts and db upgrade source files used a deprecated mysql keyword in 'create table' statements. Search for 'type=InnoDB' and replace with 'engine=InnoDB'.

I've run into the same issue with meta points referred to by other meta points. The importer requires an object to exist at the time it is referred to by another object, but, unfortunately, the exporter does not guarantee to order them appropriately. Until someone fixes the exporter, you will have to edit the exported json and move referent objects above the obects that refer to them. Hopefully, that's not too many for you.

It might be faster to export the point hierarchy, edit the json by hand, and then reimport.

I would first check that I was using the correct data types. It's easy to get the byte-swapping wrong.

You will first need to define a Modbus data source and add your two points to it. Then take a look at the Meta Data Source. You can use the two modbus data points as input to a meta data point that combines them using javascript.

Scalable y-axis would be a useful feature. Also:

• Multiple y-axes so you can show two different but perhaps related quanties in the same chart

• The ability to plot something other than time on the x-axis

After looking at the code I now understand the difference between script point (simply passed on to the browser for execution) and metapoint javascript (executed in the server). My situation is that I have integer error codes coming from the device which need to be turned into localized error messages. There's also a bit of logic involved because of relationships between error codes, so the best option for me is to collect these error code datapoints in a metapoint and process them in java code (via javascript and importClass) and return a localized string message. I've completed the code, and it works quite nicely!

A nice addition to Mango for users who don't mind writing java code would be java-enabled metapoints. Configuration would include the java class and method to call, perhaps via an xml bean configuration. In this way, the metapoins could bypass the creation of the javascript execution engine and go right to java.

I think I figured out how to do this. I read up on the metapoint dox and noticed that Mango's implementation of javascript is Rhino. Rhino provides the functions importClass() ana importPackage() which allow you access to java code from within your javascript. So, I can call out to java code to to perform the localization of messages.

I'm writing custom jsp pages, and I need a some help understanding how to use scriptPoint tags. I've read the graphical view dox that discusses server side scripts, but am still confused. :oops:

<view:scriptPoint xid="DP_123456" raw="true">
// my script goes here
</view:scriptPoint>

• Is the script executed on the server or is it sent back to the browser for execution?

• What variables are available within the script? It looks like the script will be called with 'value' and 'time' arguments; is that all that are available?

• Can I call java code through a dwr from this script?

What I'm trying to do is take a metapoint string value and use it as a key in a <fmt:message> tag. Alternatively, I would like to take a modbus integer error code value and send it to a java method to produce the localized message.

Thanks for any help anyone can provide.