I'm lookin at the camel SNMP component: http://camel.apache.org/snmp.html and it looks like it's a consumer only component.
Am I misunderstanding? Is there a way to generate SNMP traps from within a route?
not yet, but it has been requested: https://issues.apache.org/jira/browse/CAMEL-5271
As boday stated. However, you could of course do SNMP stuff within a bean or processor using regular Java. Maybe with a third party lib such as http://www.snmp4j.org/
Related
I'm trying to implement a native SFTP protocol with simple terminal interface like SSH in Apache Guacamole.
I've done the official tutorial from: https://guacamole.apache.org/doc/gug/custom-protocols.html
But the "bouncing ball protocol" it's too simple and i can't understand how to, in this case, implement an interactive terminal. Also i didn't found any project related to the creation of non-native protocols in Guacamole.
Any info is useful, thanks for reading.
In the RabbitMQ tutorials there's a demonstration of how to do remote process calls in all but C-languages (C, C++). I'm using rabbitmq-c and I'm close to replicating what the Python tutorial is doing, after all correlation_id and reply_to are available fields in the amq_basic_properties.
That been said, I can see the following two methods in the amqp.h header:
amq_simple_rpc
amq_simple_rpc_decoded
It's my understanding that these are used internally for the library's communication with the broker (e.g. that how a call to create a queue goes through) but I was wondering whether I can use those directly to support my own remote process calls, i.e. have a function that "lives" in one client and make it callable by another client.
If these methods can't be used like this, is there a standard alternative or a description of how to do routed RPCs with librabbitmq-c? Is my approach of replicating the pika tutorial "sane"?
You're right in your suspicion that amq_simple_rpc etc are for low-level client-broker communication. They are indeed unsuitable for (broker-mediated) client-to-client communication.
My opinion is that your approach following the pika tutorial is sensible. I'm afraid I do not know of any standard RPC helper library for librabbitmq-c.
I am using Camel in a multi-homed environment. Therefore I need to specify which local address should be used as the source address when building outbound SFTP connections. I did not find any configuration to do so, the only way I currently see is to write a proxy which simple opens the TCP connection using the correct local address and provide that to Camel.
Are there any obvious ways besides that which I probably simply missed?
Thanks for your help,
Heri
I don't think there is an out-of-the-box solution in Camel.
Camel uses Jsch component to make SFTP connections.
This question/answer implies that it is also not possible out-of-the-box when you use Jsch directly.
Perhaps you can adapt the solution from the question/answer link above.
Actually I'm using D-Feet (D-Feet can be used to inspect D-Bus interfaces of running programs and invoke methods on those interfaces) to connect to a BLE peripheral that advertises proximity profile.
When I try the Connect() method on the remote object /org/bluez/hci0/dev_88_6B_0F_00_C4_3A every thing is fine and the connection succeed but when I try to connect only the proximity profile using ConnectProfile("0x1802") method an error occurs saying that the host is down:
g-io-error-quark: GDBus.Error:org.bluez.Error.Failed: Host is down
(36)
Can anyone help me solving this problem (I'm blocked for 2 weeks and there still to much to deal with in the project :/)
ConnectProfile("0x1802")
ConnectProfile (and the Bluez API in general) does not deal with handles, only UUIDs. Your input argument does not look like a UUID: I suggest you find the remote service UUID that matches the handle (I'm assuming your current input argument is a handle).
I believe you can find the UUID with d-feet (after Connect() the service objects should be there) or with bluez command line tools.
Can somebody please provide an example for sending (and if possible also receiving) messages using basic ZMQ socket from some external python script. I understand that we can use Agent objects and their vip.pubsub.publish and vip.pubsub.subscribe methods to do this, but I feel like having a whole agents objects, and letting them run in background adds unnecessary complexity to scripts that just need a simple way to access the VIP message bus.
Thank you.
While this is possible, it would require re-implementing the vip protocol. The best way to do this is to use the internal web service that is available through the platform itself.
Your agent will register with the master web service either a python callback or a static directory and a regular expression for routing.