TIBCO Integration (including BusinessWorks and Flogo)

It's suited for low volume data movement on sources and targets which don't have many fields and are located on databases without many objects. The amount of metadata generated when retrieving database schemas causes extreme slowness when you have many fields and/or numerous DB objects. We tried to create schemas with access to as little as possible to limit this. It also should be something closely monitored if using it for scheduled tasks. It often fails for varying reasons, and needs to be restarted or have individual records reprocessed. It's not incredibly stable.
Because of the diverse connector types available, Scribe is useful for accessing a variety of source/target types.

Back-end data transformation/enhancement and processing are the best scenarios where Tibco BusinessWorks is suited. Service development is too much of an over-kill scenario.

Tibco BusinessWorks is well suited for middleware integration and for building our own connectors. Sometimes we need to study whether it is preferable to build our own connectors or to buy them directly from Tibco. We appreciate in our current version (v5.12) the simplicity of the administration using Tibco Administrator. But on the other hand, we regret the complexity of Hawk Monitoring Management.

In my experience, I can't really face a scenario where the TIBCO product is inappropriate. Everything was working well even during stress tests and heavy loads (as number or frequency). The solution is perfect for our customers with a really small effort from a technical side.

It is suitable for medium to large enterprise needs. Allows compatibility with most major applications as well as adapters. It is good for quick deployments.

We have used Scribe in the past (on-prem) and it was very helpful for a lot of scenarios, so I cannot imagine very many that it would not be beneficial. We are looking into Scribe to power our future SMS projects.

Well suited for point to point schedule integrations, somewhat limited on real-time integrations (without a lot of customization at the source).

It is useful when there are requirement to integrate two different package products. Business logic/rule should not be used in Tibco BusinessWorks.

CRM integration between GP has been working really well for us.

1.Creation of any web service - Tibco BusinessWorks is suitable for creating any soap/restful API

Less Appropriate scenarios:
- Calling a target service which has no properly defined soap action and has generic schema APIs- this requires a lot of XSLT transformation and calling the target API using send HTTP request palette.This is quite complex and requires quite some skill in Tibco and may not be achieved by a junior developer

It very user-friendly to integrate with other systems.

It's great to give business users an easy way to mass insert records while keeping the data clean.

You can make fast progress when building maps due to good usability. But, Scribe Online is not made for really big migrations and lacks performance speed in this scenario.

For large-scale integrations between ERP and CRM systems, Scribe works like a charm. Because of its licensing cost, it may not suite for SMB companies.

Scribe Online is ideal for quick data migrations of any complexity, provided staging and transformation can be handled by another tool. The platform also shines at fast integrations that can be scheduled to run multiple times a day. Large volumes of data per run can bring its speed down. Overall, this is still one of the most versatile, fast-start iPaaS solutions available.

Better suited: Having very few customers. Having OK customer support. Having a complex database schema in the source.
Not suited: Having many customers (being able to monitor them all effectively). Wanting a lot of customization. Wanting a lot of security. Wanting to minimize the amount of time it takes to go back and forth on integration solutions.

It's well suited if you have several applications that need integration. The build and management are just so easy and fast. It has a small learning curve and setup is a breeze. I wouldn't recommend if you'll not be using more than 3 connectors.

TIBCO Cloud Integration is being used to integrate systems. It's a total Saas product.

I think it is well suited for most integration needs. We had pretty simple migration requirements, haven't used for integration, so not sure how it stacks up to say Boomi or Informatica regarding complex integration requirements.

I think Scribe is perfect for data migrations and data integrations. As a Microsoft Dynamics partner, our goal for 2019 has been to migrate ten clients from their partner-hosted CRM systems to Microsoft's Cloud D365. Scribe has been the perfect tool for quickly and accurately creating mappings between the two systems. We also have a client who will be migrating from their old system to D365 as well as integrating to another system. I feel confident that Scribe will allow us to migrate in a timely fashion as well as push data back and forth accurately between their other system and D365. I would say Scribe would be less appropriate for a one-time small scale data migration. I don't know if the benefit of saving time with Scribe would outweigh the cost of implementing, learning, and using it. I personally feel that having a partner teach me how to use Scribe made the learning go much faster. When I originally wanted to learn Scribe, I did not have the resources to learn.

I haven't done integration back in but speaking from replication, it's perfect for our needs and removes the need to develop our own ETL tool.

Data mart replication - best suited for this.

Just the overall purpose and business aspect on how we utilize the service. It's a huge help to not have to manually enter bills and each line expense. And being that it's fast and user-friendly just makes it that much better.