How to achieve High availability in QuickFIX/J 2.1 with ConnectionType=initiator? - high-availability

We are using QuickFIX/J 2.1 with ConnectionType=initiator.
We have configured our PersistMessages to Y and are saving all the messages to Oracle Database.
Now we are trying to make our FIX engine highly available.
In the official documentation they have mentioned the acceptor failover support but no clue on initiator
Can some one please guide us on how to achieve HA for ConnectionType=initiator.

Related

Elastic APM - How to detect monitored nodes/servers failure in real time?

My company is considering using Elastic APM for performance monitoring, and we're trying to figure out if the tool could be used to detect nodes/servers failure in the case of outage for instance. I've read/seen many articles/tutorials on APM, but there's no mention of failure/outage detection.
Can this be achieved using Elastic APM? or does Elastic APM have to be paired with another tool to handle servers/nodes failure.
I found the following document in the official docs for configuration related to certain thresholds that could be used:
https://www.elastic.co/guide/en/machine-learning/7.17/ootb-ml-jobs-apm.html
but haven't not found any mention of how to detect services are down.
I've also found the following link describing integration of APM and Prometheus:
https://www.elastic.co/what-is/prometheus-monitoring
The main goal for the company, is to detect major failures, and emit SMS/Email incident alerts using PagerDuty to assigned developers on rotation.
Thanks!

Use case for Apache NiFi?

I was wondering if the following IoT problem/use case would be an intended fit for using Apache NiFi:
I use NB-IoT/LTE-M as connectivity means for sending messages to an IoT cloud platform (e.g. AWS IoT Core, Azure IoT Hub or others). I need a protocol converter/gateway for the messages entering as UDP or TCP and leaving as MQTT. Of course I can develop an UDP/TCP listener/server that listens for the entering messages and publishing them to the desired IoT cloud platform (MQTT) broker. But I was thinking of eventual using Apache NiFi, as it has processors for UDP, TCP and MQTT. However, I was wondering if Apache NiFi is meant for these kind of (IoT) scenarios?
Thanks.
Guy
We are using Apache NiFi to ingest and route IoT data at scale. I had to write a custom processor because of a proprietary IoT protocol, however assembling the rest of the flow has been just drag and drop. Before you invest into developing your own UDP/TCP listener/server at least try NiFi and see if you can solve your problem. With NiFi you can design your directed graphs of data routing pretty fast and have a short learn feedback loop.
Further think about:
What will limit the ability to grow the system?
Which resource constraints are important to pay attention to? E.g. metric volume, velocity, variety, volatility
How big can it get? Do you need resiliency?
With clustered NiFi you can spread your workload to multiple instances and satisfy the growth and resiliency requirement. You can also merge data and throttle its volume to protect downstream systems. The capabilities of NiFi are very versatile.
To answer your question: yes, Apache NiFi is actively used for IoT scenarios. There is even a NiFi IoT tutorial on cloudera: https://www.cloudera.com/tutorials/nifi-in-trucking-iot.html

How to configure High Availability in SonarQube

I have installed SonarQube 6.3 version. Kindly guide me to enable High Availability for the sonar Server.
Elaboration on Jeroen's comment:
Consulting the "plans-and-pricing" page reveals that you can make use of the Data Center version, which comes with significant licensing costs (compared to other plans, I don't doubt the value).
The installation page defines:
the supported database versions (MySQL is currently not supported for example)
the topology (2 application nodes, 3 search nodes)
the need for a loadbalancer
and of course the actual process

NiFi - Distributed Tracing capability

We have integrated NiFi within our product suits. We would like to track a user request by "Trace Id", which spans across different components. Do let me know whether NiFi have some capability to support something similar to ZipKin.
Thanks
Senthil.
You can use Apache NiFi's built-in provenance capabilities to trace how a given flow went through the system.
https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#data_provenance

Enable Trace/Debug logs for JMS client of Websphere MQ

How do I enable Trace or DEBUG level logging in the JMS client of Websphere IBM MQ.
I have no control over server and it doesn't even run in our infrastructure.
Thanks,
Anuj
If you want instructions for tracing the MQ classes for JMS, try using your favourite search engine. You'll probably come across this Technote:
http://www-01.ibm.com/support/docview.wss?uid=swg21174924#Java
that has details for different product versions and environments.
Alternatively, why not look in thte "Toubleshooting and support" section of the production documentation in the IBM Knowledge Center:
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.tro.doc/q031860_.htm
You can enable the trace log easily using the command line argument below.
-Dcom.ibm.msg.client.commonservices.trace.status=ON
Refer to the below link for more information on using this argument:
https://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.tro.doc/q131840_.htm#q131840_
For other options of enabling the trace:
https://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.tro.doc/q031860_.htm
Also, just bear in mind that the trace logs grow too large over time and affect performance. Try to use them in lower environments (not production) first and investigate your issues. You may also refer to the below link for more options on controlling the generated trace output.
https://www-01.ibm.com/support/docview.wss?uid=swg27018159&aid=1

Resources