Universal File Mover (UFM) manages the transfer of files. The user combines a series of Action commands to create the UFM Workflow XML file. These Action commands define which actions are to be taken, the order of the actions, and how errors are to be handled. UFM processes the Action commands as per the UFM Workflow XML file. UFM currently contains 41 Action commands. These action commands fall into five categories: WebSphere MQ Actions, Network Actions, File Actions, Control Actions, and Other Actions. UFM can transfer files in one of five ways, using WebSphere MQ, FTP, SFTP, SCP, or HTTP.
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.
WapSNMP is an SNMP client library for Go. It allows you to query SNMP servers for any variable, given its OID (no MIB resolution). It has been written to be in the Go style, which means it should be very resistant to all error conditions. It's entirely non-blocking/asynchronous, very fast, and will timeout, not block. It's also surprisingly small and easy to understand. It supports SNMPv2c or lower (not 3, due to its complexity), and supports all methods provided as part of that standard. This library works with OIDs and does not support OID-to-name translation.
OWASP Zed Attack Proxy (ZAP) is an easy-to-use integrated penetration testing tool for finding vulnerabilities in Web applications. It is designed to be used by people with a wide range of security experience and as such is ideal for developers and functional testers who are new to penetration testing as well as being a useful addition to an experienced pen tester's toolbox. ZAP provides automated scanners as well as a set of tools that allow you to find security vulnerabilities manually.
Bear is a lightweight remote automation tool for Groovy/Java/JVM. It allows you to deploy projects, setup your cluster, and install software to your remote machines. It differs from other existing tools in that it uses a programmatic approach - your deployment is a regular Java class. It also uses static types, chained method calls, FP, and fluent programming techniques.