Avada Software Infrared360 Reviews

An offsite team performs a daily infrastructure health check using Infrared360 and sends reports to the technical/management teams. This fulfills an important security requirement within our organization.

Administration, Monitoring, and Delegation are the most valuable features of the solution.

• Administration: It provides a centralized audit trail of all the infrastructure changes.
• Monitoring: It gives the ability to integrate with my company's global notification system, and the ability to proactively automate corrective actions.
• Delegation: It allows non-technical users to inspect their individual components within the total infrastructure without disturbing other components and without bothering the technical teams.

The ability for development teams to have access to their MQ queues has freed us up as administrators to do things other than chase down an application’s message for research purposes.

- Monitoring that ties into our incident management system
- Visibility of the MQ environment to non-MQ personnel

With the use of the packaged MQ explorer eclipse thick client, there was a significant amount of time spent configuring each local installation and making sure environmental settings were individually validated to provision each client's access. The use of the IR360 administrative console has removed that variable, because of the use of a common interface managed via a browser. The IR360 central security configuration management is what drives the distributed access control via a group/role matrix we've set up according to our business. As we get more granular within our estate, we are able to support the scale out to create groups/roles to support new areas as required.

Some of the most valuable features we use include group and role management functions. These allow us to provision access to various development and support groups across the middleware estate. This provides a more transparent view into our messaging infrastructure flows. We have easily created use case testing harnesses for specific flows that incorporate various message types. This has been successfully used by different groups.

The monitoring that's available through their system alerts us early on to problems, so we're able to react quickly to the problems that come.

The product has a small footprint on our system. We don't use a lot of clients. They're very knowledgeable of MQ, which we use. It's what we use for monitoring our MQ system, so the features that they provide are just really, really good.

One way it's helped the business is how you're able to empower MQ users, without your administrators, to be able to do different types of processes in the environment. It has user group privileges that allow you to set up security roles in the system. You can allocate permissions and actions that other users can do to maintain different MQ tasks so that you don't have to. The administrator doesn't have to do all the work. They can delegate some of the work to people to do what that they're capable of doing, without risking access to parts of the system you don't need other people in.

The administration piece makes it very easy to do MQ administration. It gives us a lot more flexibility and capabilities.

The monitoring helps keep our organization's IBM MQ environment (including its applications) available for the business. In fact, we are able to send triggered alerts through our organization's central monitoring solution and generate the incident tickets easily with Infrared360.

Infrared360 also has an easy to use MQ navigation that let's our users quickly filter objects.

Documentation.

For several tenants, we need to manage a total of nearly 200 queue managers, and each queue manager has approximately 100 queues, aliases, etc. We run the queue managers on Windows Server in four operating centers.

• We now have the possibility of getting a central perspective on all tenants.

• We have defined access roles for developers. Therefore, they can 'read in' their queues on the development and testing stages. With special roles, they may also write. This improves our development and testing cycle.

• For operative systems, we have restricted the access. Still, selected people can react if something is happening in the various BOQs.