As Solace does not support deleting and disconnecting client via SEMP over a message bus, as mentioned here, may I know how do I do that programmatically? I need to manage clients, especially client connection from my application. Can I run trigger CLI scripts from my program to achieve that?
Thank you.
Disconnecting a client is an administrative action that can only be executed by management users over the management interface. Client applications are not allowed to execute this action.
To disconnect a client, you can send a SEMP command through the management interface using a management user. (Not via SEMP over Message Bus.)
Related
When I try to publish to different topics using same client id it disconnects the previous connection.
It says the mosquitto_pub publishes a single message at a time so was wondering if this is a limitation.
MQTT Client Ids MUST be unique across all clients connected to the broker. The spec says the broker must disconnect any existing client when a new client with the same client id tries to connect.
The mosquitto_pub command will only publish a single message to a single topic (unless reading from a file or stdin, in which case it publishes a message per line, but again to a single topic).
If you want a single client to publish to multiple topics then you should look at one of the many MQTT client libraries and built a client that meets your needs.
I have an Automation Server where both the Control Room and the clients are installed. The Automation Server is accessed from another Main Server and so the Control Room. I have created some clients in the Control Room from the Main Server. I have logged in to 3 different sessions of the Automation Server and also logged in to the Clients which were created in the Control Room on the Main Server.Now, when i am trying to run a bot from the Main Server, the bot is running on the Automation Server but only in the first client logged in even if i have not selected it. Can anyone help or suggest anything about this issue?
I am expecting to run a bot from the Control Room of the Main Server into the Automation Server into the selected clients.
I am using ejabberd-16.04 on my mac and XMPPFramework from robbiehanson.
It works fine for chatting, no problem.
But now I want to add voice calling into my application.
I am using Jingle Protocol for call establishment and it works fine for direct communication (i.e. both caller and callee are in same network).
The problem I am facing is for cross-network and I want to implement Jingle ICE for this, NATed clients.
1 Can any one tell me how can I enable and use STUN/TURN module on ejabberd server and same thing at client side.
1.1 Iam also facing problems with urn:xmpp:extdisco:2 for external service discovery.
2 Is there any library for XMPP which implements Jingle-ICE for iOS?
The community version of ejabberd includes STUN and TURN.
https://docs.ejabberd.im/admin/guide/configuration/#stun-and-turn
You'll need to configure SRV records for both STUN and TURN in order for client discovery of STUN/TURN to work correctly.
http://wiki.xmpp.org/web/SRV_Records#STUN_SRV_records
The only significant limitation is that TURN Authentication does not work with SCRAM password storage.
My project, using mosquitto is mqtt server.
I want to get the information clientid once it connects or disconnects to server. Then it will automatically send to sub default. Please help me with this issue.
Assuming you want some other client to know when a certain client connects to the broker,
When your client connects , maybe in onConnected(depends on the client library) handle you can have a specific message published with connectin info. Which the listening client can be subscribed to.
Whereas for disconnection, try the last will message. To quote mosquitto.org
Last Will and Testament
The last will and testament or just “will” is a very nice feature of MQTT. When your client connects to the MQTT broker/server, it can give the broker this will, which consists of a topic and a message. If the client is disconnected from the broker unexpectedly, that is to say without sending a disconnect message, then the broker publishes the will message on the will topic.
My application Connecting to QuickBooks 2013 with QBFC 12.
QuickBooks is running on a Server
Multiple users login to the same server and run QuickBooks from the server at the same time.
Application is also running on the Server.
Application connects to QuickBooks if only ONE user is logged in to the Server and has QB running.
If any other user logs in to the server and opens QuickBooks then the application does not connect.
Message Type: ERROR
Message: The application trying to connect to QuickBooks is not supported while multiple instances of QuickBooks are running.
at Interop.QBFC11.QBSessionManagerClass.BeginSession(String qbFile, ENOpenMode openMode)
at QBFSSyncManager.OpenQBSession()
Message: The application trying to connect to QuickBooks is not supported while multiple instances of QuickBooks are running.
at Interop.QBFC11.QBSessionManagerClass.BeginSession(String qbFile, ENOpenMode openMode)
at Turbo.THUB.QBProcess.QBFSSyncManager.OpenQBSession()
Solution that I found (if it applies to your problem):
If you are running your application from within Visual Studio (any version), make sure VS is NOT running as an Administrator.
This took me hours of hair pulling, name calling, forum screaming and a broken mouse to figure out.
My application works with multiple users, each with separate computers and separate instances of QB, all working in the same QB file via network file share.
I recommend move your application to a separate computer with its own QB instance and open the QB file remotely (not by remote desktop).
A common approach is to move Quickbooks to its own machine , and then write your application such that it receives requests from the other machines. The request can be processed and some sort of message returned. The message can be either a result set or a message letting the caller know if it worked, or if there was a problem.
Without knowing more about what you are trying to do, its hard to give specific advice.