jniThreadCPUUsage is a Java library to get the amount of user and system CPU time used per thread. This is done via JNI, which calls getrusage() on the system. getrusage() is only available on Linux 2.6.26 or later and Solaris. One useful application of this is measuring the amount of CPU time used for a servlet request. getrusage() CPU time reporting is better than using the real time clock because it measures actual CPU time used and disregards times when the thread is idle or waiting (such as when it is waiting for network I/O).
TIXI is a fast and simple XML interface library for applications written in C, C++, Fortran, Java, and Python. Although simplified and somewhat restricted compared to a fully-fledged XML processing library, it can create documents, create and delete nodes, and add and remove element attributes. Routines for reading and writing text nodes and nodes holding integer and floating point numbers are included, along with routines that process aggregates of these simple types for the processing of geometric data, multidimensional arrays, or arrays of vectors.
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.
The Exquisite `df' (xdf) is a souped-up version of df(1) rewritten from scratch and focused on flexibility of field selection and output format. It offers HTML and CSV outputs, besides the traditional text-based console output. It is fit for system administrators who are tired of post-processing df(1) output through shell or Perl scripts in order to avoid broken lines or to get a simple total/summary line.
WSO2 Web Services Framework for C is a standards compliant, enterprise grade, C library for providing and consuming Web services. WSO2 WSF/C is a complete solution for building and deploying Web services, and implements a very wide range of WS-* specifications, including MTOM, WS-Addressing, WS-Policy, WS-Security, WS-SecurityPolicy, WS-Reliable Messaging, and WS-eventing. All the Web services specification implementations are tested for interoperability with Microsoft .NET, WSO2 WSAS, and other J2EE implementations.
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.
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.
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.