NetXMS Support Forum

What kind of error?

Hi

Yes, it's supported. You need to install new packages, then run "nxdbmgr upgrade". Don't forget to backup first.

Error is quite unexpected, but to be honest - we never tried such jump with packages. Which distro and version you are running?

You can upgrade this way:
mkdir ~/nx-backup
cp -R /etc/netxmsd.conf /etc/nxagentd.conf /var/lib/netxms ~/nx-backup
systemctl stop netxms-server
nxdbmgr check
apt-get --purge netxms\*
apt-get install netxms-server netxms-dbdrv-pgsql # select correct DB driver, additional packages if needed
systemctl stop netxms-server
cp ~/nx-backup/nxagentd.conf ~/nx-backup/netxmsd.conf /etc/
nxdbmgr upgrade
nxdbmgr check
systemctl enable --now netxms-server

Also I found an issue with plugin packaging, so bundled jar might not work.
Replace $NETXMS_HOME/lib/netxms/java/opcua.jar with this version: https://cloud.radensolutions.com/s/WazFQAC3KrnJpTM.

Check agent's log on debug level 1 or higher, there should be lines like
2022.09.19 15:47:54.074 *D* [                  ] Initializing Java subagent
2022.09.19 15:47:54.074 *D* [                  ] JAVA: Default JVM: /Users/alk/.asdf/installs/java/zulu-17.32.13/zulu-17.jdk/Contents/Home/lib//server/libjvm.dylib
2022.09.19 15:47:54.074 *D* [                  ] JAVA: using JVM /Users/alk/.asdf/installs/java/zulu-17.32.13/zulu-17.jdk/Contents/Home/lib//server/libjvm.dylib
2022.09.19 15:47:54.095 *D* [                  ] Java SubAgent created

If JVM is not found, you can set it with parameter "JVM=..." in "JAVA" section.

You can execute any action which is provided by the ageng (e.g. System.Restart). Also you need to select target object (where action will be executed).

List of actions can be queried from the agent, either with "nxget -l AGENT_IP Agent.ActionList" or in the GUI - right click on the node, then select Tools -> Info->Agent->Supported actions

Hi.

"pass" should be "password" in your config. Also debug tag "nc.*" should be "nc".

Correct confiration:

host=10.0.0.1
secondaryHost=10.0.0.2
login=user1
password=password1
mode=TEXT
mode can be either "TEXT" or "PDU". Secondary host is optional.

Sample session attached (added new notification channel and tried to send message to non-existing device):

I've build nddload which should be compatible with 4.1.420 packages. Please download it here: https://cloud.radensolutions.com/s/Y8AS9HWgXNb6BfY.

It's missing from packages, I'll add it to next release.

thanks

Jasper Reports is a 3rd-party product. All custom extensions (parameter types for GUI, etc.) are described the repository i've shared earlier.

Report designer is unrelated to the NetXMS and you should see TIBCO's guides.
Check section "Resources" at https://www.jaspersoft.com/products/jaspersoft-studio, specifically this video: https://www.youtube.com/watch?v=yRLvJgz9Dxk.

Alternatively, we can offer you custom development or training on both NetXMS and reporting. Plese contact [email protected] for offer.

Quote from: blairmc96 on August 12, 2022, 06:23:49 PM
Can I please get some help with this?

Simplest way is to copy any sample report, change name in file .project, then import into jaspersoft studio. Another way - copy, import, then rename project in the studio.
Once done, edit pom.xml and change "buildUuid" to any other UUID (it's used to distinguish between deployed reports).

Then open main.jrxml and start designing.

DB connection is provided by the reporting server or jaspersoft studio during development phase.
Fields are either defined manually, or you can click "read" in query editor.

You need to copy just .jar (or .zip) files to definitions folder. These files will be unpacked by the reporting server and deployed automatically.

Check this repo: https://github.com/netxms/sample-report

in Script Library there is a script call Hook::CreateInterface. You can put any code there, which will be executed when new interface is about to be created. If you return "true" (or hook is empty) - interface will be created, if false - it will be ignored.

This will not affect existing interfaces, and you'll have to delete them either by hand (filter them by name, for example, and bulk delete) or using script

for (n : GetAllNodes()) {
    println(n->name . "(" . n->id . ")");
    for (i : n->interfaces) {
        println("\t" . i->name);
        if (...) { i->delete(); }
    }
}


Check NXSL documentation for more information: https://www.netxms.org/documentation/nxsl-latest/

Script-based DCI will be the best soluion here, I think.

Script should be something like (pseudo code):


value = null;
if (CURRENT_NAME@$node != null) { // custom attribute CURRENT_NAME on current node
  value = $node->readAgentParameter("..." . CURRENT_NAME@$node);
}
if (value == null) {
  for (item : $node->readAgentList("...")) {
    if (item match "...") {
      // correct element found
      $node->setCustomAttribute(CURRENT_NAME, item);
    }
  }

  if (CURRENT_NAME@$node != null) { // custom attribute CURRENT_NAME on current node
    value = $node->readAgentParameter("..." . CURRENT_NAME@$node);
  }
}

return value;