MQWhat is a tool for documenting which MQ components are installed and active on a particular server. Since MQ component information is contained in various files and/or output by MQ programs, MQWhat is designed to collect and summarize the MQ information and present the information to the user's screen in a concise manner.
When a user inputs a hostname or an IP address, MQ Port Scan will scan a range of ports looking for a queue manager's MCA, using the standard (system default) channel names, in order to make a successful connection. It is very easy to use. It has the ability to search across a range of IP addresses and scan the port range for each IP address. Any time MQ Port Scan successfully connects to a queue manager, the information is written to a CSV file. The output will include the queue manager name, MQ version, channel name, hostname or an IP address, and port number.
The MQ File Mover application is a software package designed to move files using WebSphere MQ (aka MQSeries). MQFM processes “Action” commands, which are controlled through an MQFM Workflow XML file. The user combines a series of Action commands to create the MQFM Workflow XML file.
The MQ Channel Monitor application is a software package designed to gather and to display the status of MQ channels of the queue manager. It displays 16 columns of channel status information. The display is automatically refreshed every 60 seconds (default value). The user can alter this refresh rate. By default, all of the channels of the queue manager that currently have a status will be displayed. The user can define filters so that only particular channels will have their status displayed. MQCM can connect to a queue manager in 3 possible ways: locally in binding mode; remotely using a Client Channel Definition Table (CCDT); and remotely using an MQ XML file. MQCM supports both forms of MQ security: SSL for connecting to remote queue managers, and 3rd party security exit for connecting to remote queue managers.
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.
Duke is a fast and flexible record linkage engine. It does not use the traditional blocking (sort by key) approach, but instead relies on Lucene. This makes it high-performance (able to process 1,000,000 records in ~10 minutes). Duke can be run from the command line, but also has an API allowing incremental linking applications to be built easily. It supports reading data from CSV, JDBC, SPARQL, and NTriples, and also supports a number of string comparators and string normalizers.
android-metadata is a utility library for Android designed to simplify reading metadata values from AndroidManifest.xml. It can quickly access metadata values from anywhere with a few lines of code, read individual metadata values into type-specific variables, and read one or more metadata values into annotated Java classes.
MirrorBrain is a framework to run a content delivery network using mirror servers. It solves a challenge that many popular open source projects face: a flood of download requests, often magnitudes more than a single site could practically handle. A central (and probably the most obvious) part is a "download redirector" that automatically redirects requests from Web browsers or download programs to a mirror server near them. Choosing a suitable mirror for a user's request is the key, and MirrorBrain uses geolocation and global routing data to make a sensible choice and achieve load-balancing for the mirrors at the same time. The algorithm is both sophisticated and easy to control and tune. In addition, MirrorBrain monitors mirrors, scans them for files, generates mirror lists, and more.