TagEventor is a project to enable radically simple computer usage by creating physical-object-based user interfaces. It does this using commercially available (and relatively cheap), standardized RFID technology in the form of small, simple USB connected contacted card/tag readers and small, cheap tags. The project was started based on products available from the "touchatag" company, which has clients for Windows and Mac, and run their own Web service to enable many interesting Web-based applications. However, no simple, lightweight Linux client was available, and the Web focus meant that some client-focused functionality was not possible. The software is currently a daemon that monitors the presence of one or more RFID tags on a connected reader and generates "system events" when tags are placed on it or removed from it.
XMLBeans is a technology for accessing XML by binding it to Java types. XMLBeans provides several ways to get at the XML. You can do this through XML schema that has been compiled to generate Java types that represent schema types. In this way, you can access instances of the schema through JavaBeans-style accessors after the fashion of "getFoo" and "setFoo". The XMLBeans API also allows you to reflect into the XML schema itself through an XML Schema Object model. There is a cursor model through which you can traverse the full XML infoset. There is support for XML DOM.
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.
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 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.
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.