Is there possibity to migrate data(topic, queues and all other config) from Old Solace VMR to latest Solace pubsub+ version?
Upgrading your VMR to the latest Solace PubSub+ software message broker will preserve all data including messages that are spooled.
If upgrading is not an option, you can capture all message-vpn level data (including topics and queues) with the "show current-config message-vpn *" command. You can use the “>” and “>>” characters to redirect the output to a file and run this file as a script on the new Solace PubSub+ software message broker.
The output is generally backwards compatible but keep in mind that it may not be possible to take the configuration from a newer version of the Solace message broker and apply it on an older version as there may have been new features and commands added.
Related
Why nodeJS supports the following protocol and why not paho client
Mqtt nodejs vs org.eclipse.paho.client.mqttv3
Why Nodejs supports the following protocols
mqtt.connect([url], options)
The URL can be on the following protocols: 'mqtt', 'mqtts', 'tcp', 'tls', 'ws', 'wss'.
And Paho supports Only tcp && ssl
MqttClient.connect(options)
* #throws IllegalArgumentException if the URI does not start with
* "tcp://", "ssl://" or "local://".
The Java Paho client should now accept ws:// and wss:/ as it has MQTT over Websocket support. Earlier versions didn't so it made sense to throw an error if you try to specify these transports. The update to the doc probably just got missed (issue opened to fix).
tcp:// and ssl:// are legacy from the original IBM Java MQTT client from which the Paho client pulls a lot of inspiration if not actual code.
mqtt:// and mqtts:// were not formally on the IANA list but a formal request has been made as part of the MQTT v5 spec so once the next version of the client is formally released support v5 the client will support them. ref: https://github.com/eclipse/paho.mqtt.java/issues/464
How to monitor mosquitto server through HTTP? I am looking something like https://my.mosquitto.server.com/health or https://my.mosquitto.server.com/info.
Mosquitto Server: v3
OS: CentOS 7
Mosquitto Web: Enabled
Thanks
You are always going to need a MQTT client to get access to the information in the $SYS topic space.
When MQTT over Websockets is enabled you can have mosquitto serve a page that will connect to the broker with the Paho Javascript client with MQTT over Websockets. The page can subscribe to what ever topics you want.
e.g. You can use the http_dir option to specify a directory that moquitto will server static files from. Here you could deploy a slightly modified (The modification would be to change the topic from # to %SYS/#) version of my D3 MQTT topic tree viewer (code on github).
From the mosquitto.conf man page:
http_dir directory
When a listener is using the websockets protocol, it is possible to
serve http data as well. Set http_dir to a directory which contains
the files you wish to serve. If this option is not specified, then no
normal http connections will be possible.
Not reloaded on reload signal.
Can Solace integrate with IBM Websphere Application Server 8.5.5.0? We are thinking to eliminate the existing IBM MQ7.0 from our IBM WAS 8.5.5.0 integration components.
I have found one article/document on the Solace portal for IBM WAS 7/8.0, but not for 8.5.5.0? But we need to know the capability of Solace and whether it will integrate with IBM WAS 8.5.5.0 or not?
Solace can absolutely integrate with IBM Websphere Application Server 8.5.5.0. The current Websphere Integration Guide that is available on the Solace dev portal is applicable to Websphere Application Servers 7.x and 8.x. It is available here: http://dev.solace.com/integration-guides/websphere-application-server/
The Solace JMS Resource Adapter is designed to be generic. It is generally able to integrate with any Jave EE Application Server.
If you have a support contract with Solace and you encounter any specific issues integrating Solace with any version of the IBM Websphere Application Server, you can contact support by emailing support#solace.com with a description of your issue.
May I know whether there is any limitations to Solace VMR trial version? I exported CLI commands to setup a VPN from a Solace appliance. I can run the CLI script to create a VPN on appliance but when I tried to run the same script in VMR, it seems to have issues. Similarly, VMR does not seem to allow me to setup SSL. Any advice?
Thank you.
The following Solace appliance features are not currently supported by the Solace VMR:
High-Availability (HA) router redundancy
TLS/SSL client certificates
TLS/SSL bridging
TLS/SSL client connections with Solace Java and JMS messaging API versions less than 7.1.1.169
Compressed traffic
Eliding
HA Config-Sync
Upgrades and downgrades using the ‘boot’ command
Legacy mode SEMP over msg-bus commands
Legacy mode ACL rule enforcement
SNMP
Cut-through guaranteed messaging
This list of feature limitations and other known issues are available in the Solace VMR Release Notes.
The Solace VMR has a lower capacity than the Solace hardware solution, therefore some of the limits on system resources differ. If you have a license for the Solace appliance, you will have access to the SolOS_system_limits_and_alerts_VMR.xlsx spreadsheet in your customer portal which documents all limits of the VMR.
Some examples include:
Client connections - 1000 on VMR, 9000/200,000 on the appliance (depending on the model)
Queues and topic endpoints - 1000 on VMR, 16000 on appliance
Topic subscriptions - 500000 unique and 1000000 non-unique on VMR, 5000000 unique and 10000000 non-unique on appliance
These feature and resource limitations are accurate for the 7.1.1.342 SolOS version of the VMR and appliance. These values may be different for other versions.
Note that these limits apply for both the Evaluation and the Enterprise version of the Solace VMR. The limitation of the Evaluation version, as compared to the Enterprise version, is that it contains only a 30-day trial license and is not supported for production environments.
If your CLI script is returning errors, it could be that it is trying to enable a feature that isn't supported or it has exceeded a limit on the VMR.
I have just started looking into flume for writing messages to hdfs using the hdfs sink. I am wondering if flume source can act as a jms consumer for my message broker.
Does flume provide integration with message broker.
Or do i need to write a custom jms client that will push messages to a flume source.
Flume 1.3 does not provide JMS source out of the box. However, it seems that such component will be shipped with the next version, Flume 1.4: https://issues.apache.org/jira/browse/FLUME-924.
Meanwhile you can get the source code of this new component here and build it. AFAIK, Flume 1.4 does not break its interfaces, so probably the component will work with 1.3 as well.