IBM DevOps Code ClearCase vs. IBM Netcool Network Management vs. NetVizura NetFlow Analyzer

IBM Rational ClearCase might be better suited for a smaller / simpler code base. Larger code bases really slow it down... but then again there are better alternatives out there for source control

Incentivized

This tool was integrated with Control-M, so whenever we receive any job failure, long-running job, job not started yet, etc, we receive an alert against it. This tool is also integrated with Maximo where we receive the incidents as well for it. Alert's color was as per the criticality of the job and that makes it very easy for an associate to act on it to resolve. We have the SLAs for the jobs as per the urgency of the jobs.

Incentivized

The capacity planning was a big help in our company as we grew the number of connected locations. Grow or die is pretty much the business model of today but that growth is only as good as the network it travels on. Being able to recommend appropriate network requirements is a big deal in our line of business.

Incentivized

• Rational ClearCase is excellent for handling versioning and branching. No other tool I've used has the depth that ClearCase has when it comes to handling complex branching scenarios and identifying where certain versions of particular files are within a particular configuration.
• Rational ClearCase handles parallel development of many dependent applications really well.
• The use of ClearCase Views to switch between projects and configurations is extremely convenient as opposed to the local workstation model of the competitors.

Incentivized

• This is one of the best monitoring tools.
• Very simple to user.
• Color code makes it very simple as per severity.
• We receive the heartbeat alert every hour that shows the system is running up and fine.
• We have black, red, yellow, and orange color alerts that show the critical, urgent, major, and minor incidents.

Incentivized

• Ease of use

• Extremely buggy.
• Sometimes the repository gets locked for no reason.
• Slow.

Incentivized

• Sometimes color differences of the incidents as per the criticality .
• We don't receive the heartbeat alerts sometimes.
• If the tool is down and we don't receive the alerts on the console we wait for the heartbeat alert and it makes some extra delay in resolving things.

Incentivized

• At this point, I don't have any suggestion for improvements.

Incentivized

If development is centrallized to one location and your company releases hundreds of customized versions of your software per year, then ClearCase is the best tool for managing the complexity of multiple versions of customized software. If your company has globally distributed development, then I'd recommend Team Foundation Server over ClearCase. If your organization uses Agile Methodologies, then I'd recommend TFS with GIT.

Incentivized

This is one of the essential tools for monitoring. This tool was integrated with Maximo and Control-M in my organization. So whenever any job failed in Control-M, we receive an alert against it in the IBM Netcool/OMNIbus. We receive the alerts in different colors as per the criticality. Black for critical ones(Sev1), red for urgent (Sev2), yellow for major(Sev3), and orange for minor(Sev4). So it makes an easy to operate and act on the alerts as per the severity. This tool is very user-friendly and easy to use. No additional training is required for the tool to operate, just a simple KT is enough.

Incentivized

Easier to use

• Managed code versioning for many years.
• Only one person can edit code at a time - slows processing down.
• IBM is an expensive product to support.

Incentivized

• Color feature of the alerts as per the criticality is the amazing feature.
• Heartbeat alert is also an unique feature.
• No additional training is required to use this tool. just a simple KT is enough.

Incentivized

• As I mentioned in a previous statement, the capacity planning was the big thing. In our line of business, speed is everything. Customers hate to be slowed down so having the appropriate network connections is a must.
• Anomaly Detection with the threshold based alerting has made our network team more proactive in stopping things before they can really affect the company.
• Productivity with the use of monitoring conversations and amount of used bandwidth has helped weed out the works versus the campers.

Incentivized