IBM App Connect vs. Planview Hub

IBM App Connect Enterprise is well-suited for high-volume enterprise systems that demand robust scalability and high reliability. It excels at hybrid connectivity by easily integrating various on-premises systems using its extensive catalog of connectors. It is also ideal for workflows that require a balance between efficient low-code and the incorporation of complex, custom Java logic. On the other hand, the platform is less appropriate in scenarios requiring high development autonomy, as installation and configuration at the server level is excessively complex, creating a strong dependency on other infrastructure teams. It is also not ideal if detailed traceability and monitoring of workflows must be seamlessly managed within the tool itself, as this is difficult to manage directly in ACE. IBM App Connect Enterprise está bien adaptado para sistemas empresariales de alto volumen que exigen una escalabilidad robusta y alta confiabilidad. Sobresale en la conectividad híbrida al integrar fácilmente diversos sistemas locales (on-premises) utilizando su amplio catálogo de conectores. Además, es ideal para flujos que requieren un equilibrio entre el low-code eficiente y la incorporación de lógica Java compleja y personalizada. Por otro lado, la plataforma es menos apropiada en escenarios donde se requiere una alta autonomía de desarrollo, debido a que la instalación y configuración a nivel de servidor es excesivamente compleja , lo cual crea una fuerte dependencia de otros equipos de infraestructura. Tampoco es ideal si la trazabilidad detallada y el monitoreo de los flujos deben gestionarse sin problemas dentro de la propia herramienta, ya que esto resulta difícil de manejar directamente en ACE. Parts of this review were originally written in Spanish and have been translated into English using a third-party translation tool. While we strive for accuracy, some nuances or meanings may not be perfectly captured.

Incentivized

Planview TaskTop Hub is very well suited to implement the integrations to synchronise data such as requirement, task, bugs. We have very good experience with the integration between Jama and Jira as well as between two Jama instances. In the context test management, related to Test steps in a test case, it's quite complicated. Test Case synchronization between two Jama instances works with Steps. But we aren't able to implement the synchronisation of Test Cases including Steps to such Plugin of Jira like Xephyr.

Incentivized

• Just the ability to display and consume data through a single dashboard makes this a great application for our business purposes.
• With the ability to consume their exposed API, data validation and manipulation becomes a breeze.

Incentivized

• Allows for one- vs bi-directional field flow which is useful per segment
• Allows for the relationship mapping of Parent/Child cards
• Allows for customization of mapped fields

• modernization made easy, when a modernized project is created by importing a java code.
• more pre-built connectors
• watsonx code assistance for ESQL capability.

• I'd like to see more robust reporting capabilities available from the UI.

Incentivized

It is the best on-premise application to cloud integration in the market. I guess IBM is planning to integrate IBM App Connect with the IBM API Connect solution.

Incentivized

Planview TaskTop Hub supports our use cases. I think its continuous development goes in the right direction.

Incentivized

You can do some really powerful things with this system. The overall design is an attempt to make configurable some of the routine tasks/common functionality, but allow for development/customization of the core of the application.

Incentivized

A great integration tool, which comes with a wide range of supported end tools. Planview TaskTop Hub works with an integration concept that maximizes the scalability and flexibility of integrations across more than just two tools. For example, from our experience, we started with the integration between Jama Connect and Jira. We were able to extend our integration concept to a new tool, Pro Cloud Server, by ourselves. The element was synced within 10 minutes.

Incentivized

We're hosting Planview TaskTop Hub by ourselves. The availability was good until now. A part of that, we have a strict plan for the quality control on any update of both Hub and End tools to avoid as much as possibily any disruptions.

Incentivized

Planview TaskTop Hub does generate traffic for some end tools. It is still in an acceptable range. For certain kind of retry to resolve issue in synchronizing relationships, an additional manual attention was required.

Incentivized

Usually, the IBM Ops team provides a resolution or a response for 80% of defects raised in my project. There is one which has been open on their end for more than 3 months. With literally no response even after multiple follow-ups.

Incentivized

I was considering giving a rating between 9 and 10. Overall, the support has been very good so far. However, I have noticed that the members of the support team have varying levels of know-how about Planview TaskTop Hub. When a ticket about a complex technical issue reaches a member such as Christoph T., Sr. Customer Engineer, the analysis is done thoroughly, and a sustainable solution is provided. With other members of the support team, the experience might be different.

Incentivized

We've received a good, in-deep training from Christoph T. during the implementation phase.

Incentivized

The integration documentation was sufficient.

Incentivized

We had a very good collaboration with the enabling team from Tasktop in 2018. The enablement program was adequately structured, starting with building an integration concept based on use cases of the synchronized data. The training provided a good foundation for us to operate and maintain the tool. The tool administration and architecture were straightforward.

Incentivized

IBM App Connect started as MQSeries Integrator (MQSI) more than 20 years ago. In the IT environment, this is like an eternity. And this allowed a lot of customer experience and needs to be embedded in the product. Without it becoming a legacy application. The changes done in the latest version are preparing it for a Cloud/containers world without losing the previously learned knowledge.

Jira Align does not synch items outside of JIRA and Azure Dev Ops; TT Hub is specifically utilized to address connections to various other SDLC application.

Incentivized

We don't need to deploy Planview TaskTop Hub in other units but we could extend the integration to cover the new data, new data type and new projects.

Incentivized

• We never implemented Cast Iron in production. When compared to five competing products in the iPaaS space it didn't make it past the first few test scenarios we threw at it.

Incentivized

• We track monthly updates and each month there are typically over 30,000 updates being made which we know is saving time.