TIBCO Integration (including BusinessWorks and Flogo)
Likelihood to Recommend
1. For simple tasks / moderately difficult tasks (where there are not too many condition checks) 2. We have less time for development, and the Agenda is simple. 3. Avoid Azure Logic Apps when you are unsure about hitting the limits (check latest limitations of Azure Logic Apps in MS docs)
Well suited for duplicating operational processes and transforming data. It's less suited for querying and updating medium to large datasets. It is possible our connection wasn't configured correctly, and the speed could be improved. However, it still takes a long time to update mass changes.
Scribe can dependably map or sync data between systems. When you have different systems being used by many departments, this is the tool to keep the data in-sync!
API's are widely used by many applications and companies. Tibco Cloud Integration allows companies to integrate data from an older ERP system with a newer system using an API.
Tibco provides the flexibility for business users, developers and anyone in-between to understand where data is moving within their organization.
One example of flexibility of the solution is easily manipulating data on the fly.
Microsoft Azure should be unclouded with its pricing. We don't always know how much an inclusion will affect the monthly price. So we have to speculate where we are with the price and if we can afford to include another asset.
Missing functionality: We like to run all the files available in the FTP when clicking the run button. Right now, we have to click the run button several times (or have multiple solutions) in order to run files from our FTP site one at a time.
Generating column fields every time a file changes from the source in the FTP is very tedious. Working in integrations makes me have to go back and forth a lot of the time, and doing this is incredibly annoying.
The security is horrendous. We installed an on-premise agent on the customer side, but we don't want them even touching the ETL tool at all. The only knowledge we are fine with knowing and being able to see is that they installed the agent, not the solutions themselves.
Our company's connector would have to point to the dataset name rather than dataset ID. It was very frustrating because we change the dataset name a lot, and then we'd have to repoint it.
It's very difficult to monitor the different integrations that go on because there isn't a consolidated dashboard.
The project which required the Scribe tool has been cancelled due to business direction change. Unless another project requiring Scribe comes up, it will likely not be renewed. Companies are always looking for cost savings though and Scribe is less expensive than competitors, so you never know.
I found them easy to use and adapt to different scenarios, from Azure management to link processes between REST APIs. Together with Function Apps, they're probably the most useful resource type for Azure. Today, I use them in production, and that's a key component: stable, secure, easy to manage, and maintain.
The maps are fairly straightforward to create and use. The logical expressions and other units in the mapmaking process are straightforward, functional and understandable. It makes life much easier when you know you can figure out a way to make an integration work because of the toolset and commands that are available.
We have not had any issues with TIBCO not being available when needed. I have only had to contact support less than 5 times in about 5 year time frame due to syncing issues or a problem with the agent. Support is very quick to respond as well as very helpful.
TIBCO Cloud Integration (including BusinessWorks and Scribe)'s performance of the user interface are not to be complained about. The user interface is swift and is a pleasant user experience. The replication jobs take some time to finish but that is because the number of records to be updated/created on a daily basis is quite big. I did split up the jobs between highrunners (entities with a lot of changes) I update on a daily basis and quite stable entities that I update weekly. That solved my issue of a way to long replication.
Azure Logic Apps are backed by Azure and Microsoft. There is a wealth of information on the internet about both of these platforms. In addition to this Microsoft has a huge bush to using this platform and have offered many solutions and support options to the user. The only drawback is that it is a fairly new platform so the 3rd party information tends to be lacking.
For creating new process, you have lots of palettes to do every develop you need. For created process it is easy to understand even if you have ever seen before it. You can analyze your process in all their detail. User Experience is positive for beginner and expertise people. Just debug mode is still raw, but better in TIBCO BusinessWorks 6.x than TIBCO BusinessWorks 5.x .
Before using TIBCO Businessworks, I participated an official training with a specialized instructor. In this training, I learned what I needed to know to build some applications or web services and how to manage its. It was been very important to me. I understood many technical stuff to familiarize with this powerful platform. I can advice TIBCO Educational Services.
If we don't design the process correctly, it can do lot of damage (like deleting files or data etc.,) and might assume product issue rather than a design flaw. So it is always recommended to do thorough unit testing , QA and a design review even for a small process to avoid major problems.
When we proposed products for central integration, we were also introduced to software like Pabbly - which was in its early stages of company growth. The main reason why we picked Azure Logic apps over the other software is that it is manufactured by the renowned company Microsoft and we had nothing to worry about our data security. Also, Logic apps offered a great deal when it came to pricing and it was also so much easier to negotiate the plans and prices with the customer care representatives at Azure Logic Apps!
Provide technical support: Respond to customer inquiries and issues related to TIBCO software products via phone, email, or support tickets. Troubleshoot and resolve technical problems to ensure customer satisfaction. Testing and validation: Assist customers in testing and validating TIBCO integrations, configurations, and deployments. Problem diagnosis and resolution: Analyze and diagnose complex technical issues reported by customers. Collaborate with customers and internal teams to identify root causes and provide effective solutions.Continuous improvement: Identify opportunities for process improvements, automation, and efficiency gains within the support function. Collaborate with cross-functional teams to implement enhancements and drive customer satisfaction.
Rating is based on the features provided which are very good and useful. Scalability is very good and data workloads can be managed with less replication, lower costs, and greater agility making the overall use of the tool very smooth. So far experience is great, it is easy to understand and implement.
Moving to Serverless Computing obviously makes the organization get rid of dependent Infra.
ROI can be seen immediately as the required infra can be decommissioned after a successful quarter run.
Being deployed as a single entity or single app on Azure Logic Apps, Organizations need to be more careful with controls applied to meet compliance and security posture.
Integrations with different applications Workday,Single Sign-On,CertTracker,Okta,Partner contact sync and Questionmark is succesful.
LOD: Learn on demand is a third party vendor application where all Virtual classes are delivered by the vendor application. Learning management system sends the class and registration events to learn on demand via real time web service call through TIBCO
