NetXMS Support Forum

Hi!

Unfortunately it does not exist. I start creating one long time ago, but it is in initial state. Demand is very low, and there are always tasks with higher priority. Existing document attached - but it covers very small part of the API. But feel free to ask me any questions - I'll do my best to answer them fast and accurate. Also, for new development and integration I would suggest using Java API when possible - it is simplier and has JavaDoc for most classes and methods.

Best regards,
Victor

Hi!

I can package RedHat/CentOS (I have development CentOS machine and can build agent on it right now) agent binaries as simple .tar.gz expandable into /opt/netxms (or any other location). Most likely they will run on SUSE as well.

Best regards,
Victor

It is in https://www.netxms.org/download/archive/

Best regards,
Victor

Do you have any response from the port when you connect with putty?

If you connect to com with terminal, what did you get?

Best regards,
Victor

Also, I found that some Powerware models shows management interface on serial console by default. They need to be switched into "pass-through" mode before using BCM/XCP protocol. That also may be the reason why UPS subagent cannot communication with the device.

Best regards,
Victor

Hi!

Syntax is correct. Can you please tell exact UPS model? Most probably it uses different protocol or protocol version. Also, please check that you can open COM1 with terminal application - just to make sure that no other apps holds it open.

Best regards,
Victor

Hi!

I could implement it easily, I just never thought about that. Will do this for 1.1.5 agent.

Best regards,
Victor

Hi!

File looks correct. Did you get something in log file? Also, do you have event with ID 100 in application log?

Best regards,
Victor

Hi!

They both works, but should be considered experimental and has some limitations so far:

There are reporting engine, but no actual reports yet. We will provide actual reports later on. Reporting uses Jasper Reports, so you have to install Java runtime on the server if you wish to generate reports. And you can create your own reports using Jasper. When standard reports will be available, you will be able to use them as example.

Business services is a basis for SLA monitoring functionality. Currently, you can define business services and see availability percentage. Service in in unknown state because you have to define actual services and checks to calculate service status. It is quite long story, I'll try to put it into manual.

Best regards,
Victor

Hi!

In fact, for many versions server expects that agent running on server allows connections from both 127.0.0.1 and machine IP. But I already has reports that 1.1.4 has strange issues with loopback interface. I'll check it out.

Best regards,
Victor

Yes, there was changes in communication protocol, so you need server 1.1.4. And I recommend to wait for 1.1.5 due to all recently discovered upgrade problems.

Best regards,
Victor

Hi!

Sorry for delay. I have published apk file for Android client on web site.

Best regards,
Victor

Quote from: lindeamon on September 14, 2011, 04:41:43 PM
what version of the sql.ddr patches do i have to save for now ? the latest one ?

Yes.

Best regards,
Victor

I put .deb files for version 1.0.12 for x64 architecture on the web site. They was built on Debian 6.

Best regards,
Victor