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.
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.
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.
SNOW is a utility for concealing messages in ASCII text by appending whitespace to the end of lines. Because spaces and tabs are generally not visible in text viewers, messages concealed with whitespace are effectively hidden from casual observers. If SNOW's built-in encryption is used, the message cannot be read even if it is detected. SNOW exploits the Steganographic Nature Of Whitespace, similar to finding a polar bear in a snowstorm; hence the name.
The Apache Traffic Server (TS or ATS) is a modular, high-performance reverse proxy server, generally comparable to Squid. It was created by Inktomi, and distributed as a commercial product called the Inktomi Traffic Server, before Inktomi was acquired by Yahoo!. Traffic Server has been actively used inside of Yahoo for over 4 years, serving billions of requests every day. As of fall 2009, Traffic Server is an Open Source project, and in April 2010 the Apache Traffic Server was promoted to a top-level project of the ASF.
By adding a user-friendly interface, predefined best practices, and fine-grained compliance reporting to your own IT configuration rules, Rudder enables enterprises to rapidly benefit from increased productivity and insight throughout their IT operations. It can measure the drift of IT infrastructures. It enables you to automate installation and configuration of services, continuously verify and repair them, and centralize information and knowledge about your infrastructure and generate compliance reports, helping you analyze and control the deviation between a service’s current state and its nominal behavior.