The Message Router (MRTR) application will move a message from a central WebSphere MQ queue to a specific application WebSphere MQ queue. The destination queue that the message will be placed into will be based on a keyword in the message. Context information is maintained. MRTR will look in the message for a Start Keyword and an End Keyword. The value between these two keywords is the Keyword Value (inifile Token). MRTR will search its ini file for that particular Keyword Value. The field value associated with the looked-up keyword value is the destination queue name. MRTR performs each MQGET and the subsequent MQPUT under a Unit of Work (UOW) so that message integrity is kept.
The Message Multiplexer (MMX) application will get a message from a WebSphere MQ queue and output it to one or more queues. Context information is maintained across the message put(s). MMX can move messages from a single source queue to (up to) 99 target queues. Messages put to each target queue are an exact replicate of the original message from the source queue (including the message's MQMD). MMX performs each MQGET and the subsequent "n" MQPUT(s) under a Unit of Work (UOW), so that message integrity is kept.
MultiTail lets you view one or multiple files like the original tail program. The difference is that it creates multiple windows on your console (with ncurses). Merging of 2 or more log files is possible. It can also use colors while displaying the log files (through regular expressions) for faster recognition of what is important. It can also filter lines (again with regular expressions). It has interactive menus for editing given regular expressions and deleting and adding windows. One can also have windows with the output of shell scripts and other software. When viewing the output of external software, MultiTail can mimic the functionality of tools like 'watch'.
Pandora FMS is a software-monitoring tool created for all kinds of companies. It is specially designed for large environments, and works by first managing servers, applications, and communications, and then notifying clients of problems and failures before they occur. Pandora FMS also includes a configurable report system that evaluates and notifies the client on the level of fulfillment and compliance of their systems. It supports all kinds of technologies unifying the management tools of your system, such as performance monitoring, network monitoring, and availability management. Pandora FMS makes your company management more agile and improves your process performance.
XMLFoundation provides a foundation for XML support in an application. However, it is more than just another XML parser. It applies a unique approach to handling XML that allows your application code to focus on the application rather than traversing DOM or subscribing to SAX events. The most unique feature of the XMLFoundation is the object oriented encapsulation that provides XML support in the application layer. XMLFoundation allows you to easily integrate XML with your GUI or with your server objects, and it natively supports COM, DCOM, and CORBA objects.
nxlog is a modular, multi-threaded, high-performance log management solution with multi-platform support. In concept, it is similar to syslog-ng or rsyslog, but is not limited to Unix/syslog only. It can collect logs from files in various formats, receive logs from the network remotely over UDP, TCP, or TLS/SSL on all supported platforms. It supports platform-specific sources such as the Windows Eventlog, Linux kernel logs, Android device logs, local syslog, etc. Writing and reading logs to/from databases is also supported for many database servers. The collected logs can be stored into files, databases, or forwarded to a remote log server using various protocols. The old BSD Syslog and the newer IETF syslog standard (RFC 3164 and RFC 5424-5426) are fully supported by nxlog in addition to XML, JSON, CSV, GELF, and other custom formats. A key concept in nxlog is to be able to handle and preserve structured logs so there is no need to convert everything to syslog and then parse these logs again at the other side. It has powerful message filtering, log rewrite, and conversion capabilities. Using a lightweight, modular, and multi-threaded architecture which can scale, nxlog can process hundreds of thousands of events per second.
Socat is a relay for bidirectional data transfer between two independent data channels. Each of these data channels may be a file, pipe, device (terminal or modem, etc.), socket (Unix, IP4, IP6 - raw, UDP, TCP), SSL, a client for SOCKS4, or proxy CONNECT. It supports broadcasts and multicasts, abstract Unix sockets, Linux tun/tap, GNU readline, and PTYs. It provides forking, logging, and dumping and different modes for interprocess communication. Many options are available for tuning socat and its channels. Socat can be used, for example, as a TCP relay (one-shot or daemon), as a daemon-based socksifier, as a shell interface to Unix sockets, as an IP6 relay, or for redirecting TCP-oriented programs to a serial line.