6 projects tagged "HP-UX"

Pop	149.20
Vit	4.03

STAF (Software Testing Automation Framework) is a framework designed to improve the level of reuse and automation in test cases and test environments. Its goal is to provide a complete end-to-end automation solution for testers.

Pop	37.47
Vit	1.05

MQ Authenticate User Security Exit (MQAUSX) is a solution that allows a company to fully authenticate a user who is accessing a WebSphere MQ resource. It verifies the user's user ID and password (and possibly domain name) against the server's native OS system (or domain controller) or a remote LDAP server. The security exit will operate with WebSphere MQ v5.3, v6.0, or v7.0 (and MQSeries v5.2) in Windows, iSeries (OS/400), Unix, and Linux environments. It works with Server Connection, Client Connection, Sender, Receiver, Server, Requestor, Cluster-Sender, and Cluster-Receiver channels of WebSphere MQ queue manager. The MQ Authenticate User Security Exit solution is comprised of 2 components: client-side security exit and server-side security exit.

Pop	24.17
Vit	1.82

MQ Channel Encryption (MQCE) is a solution that provides AES encryption for message data flowing between WebSphere MQ (WMQ) resources. It operates with Sender, Receiver, Server, Requestor, Cluster-Sender, Cluster-Receiver, Server Connection, and Client Connection channels of the WMQ queue managers. It is a simple drop-in solution and can be configured as a queue manager channel message exit or as a channel sender/receive exit pair.

Pop	17.92
Vit	1.05

MQ Standard Security Exit is a solution that allows a company to control and restrict who is accessing a WebSphere MQ resource. The security exit will operate with WebSphere MQ v5.3, v6.0, and v7.0 (and MQSeries v5.2) in Windows, iSeries (OS/400), Unix, and Linux environments. It works with Server Connection, Receiver, Requestor, and Cluster-Receiver channels of WebSphere MQ queue manager. The MQ Standard Security Exit solution is comprised of a server-side security exit.

Pop	23.83
Vit	1.46

MQ Auditor is a solution that allows a company to audit and track all MQ API calls performed by MQ applications that are connected to a queue manager. The API Exit operates with WebSphere MQ v5.3, v6.0, or v7.0 in Windows, Unix, IBM i, and Linux environments. Under WMQ v5.3 and higher, MQA audits the following MQ API calls: MQCONN, MQCONNX, MQOPEN, MQGET, MQPUT, MQPUT1, MQINQ, MQSET, MQCLOSE, MQDISC, MQBACK, MQBEGIN, and MQCMIT. Under WMQ v6.0.2.7 and higher, MQA audits the above calls as well as the following calls: XASTART, XAEND, XAOPEN, XACLOSE, XACOMMIT, XACOMPLETE XAFORGET, XAPREPARE, XARECOVER, XAROLLBACK, AX_REG, and AX_UNREG. Under WMQ v7.0 and higher, MQA also audits the following additional MQ API calls: MQCALLBACK, MQCB, MQCTL, MQSTAT, MQSUB, and MQSUBRQ.

Pop	39.19
Vit	2.49

MQ Message Encryption (MQME) is a solution that provides encryption for WebSphere MQ message data while it resides in a queue and in the MQ logs. It uses AES and offers the ability to control who accesses protected queues. This control is obtained through the use of UserID grouping, and group files are similar to the Unix /etc/group file. It also has the ability to generate and validate messages using a SHA-2 digital signature.