I receive the requirements, and I build my services on typical BusinessWorks.

We have TIBCO BusinessWorks installed, and we also had an old iProcess installation. I am a consultant for TIBCO BusinessWorks.

The typical use case for TIBCO BusinessWorks functions as middleware. When you have multiple systems connected, you want to avoid point-to-point connectivity. In place of point-to-point connectivity, you have middleware which exposes all your API services to the external world. You are developing all the orchestration rules.

If more than one API needs to be aggregated together, the response needs to be sent in a consolidated manner, then all these logics are being built.

I use TIBCO BusinessWorks for my daily operation work.

We use the solution in the steel manufacturing industry.

TIBCO BusinessWorks is used as middleware for us.

In my company, we use TIBCO BusinessWorks for middleware integration.

I mostly use it for communication between SAP and EMEA systems. I'm using TIBCO BusinessWorks and VMS.

Since it is an integration platform, we use it for integration purposes in our company.

We currently have 500 or more than 1,000 applications of TIBCO BusinessWorks. Our primary use case for the solution is the apps leader operations batch. We have users all across the globe. We have business in Japan, Amsterdam, the US, and Korea, among other countries. Whenever we need to perform region-specific activities when a region is not there – like region-related calculations, for example, we use TIBCO BusinessWorks. Even if a region is around, there will be some midday activities that we need data from different systems. All the backend-related logic and business rules are there in TIBCO BusinessWorks.

TIBCO BusinessWorks is used for web services. I have a few processes with collecting data from a database and putting it somewhere. 

This solution is deployed on-premise. 

We use the solution for business integration.

I work mostly in telecommunications and use BusinessWork for job processes. It's primarily used for orchestration and transformation from one language to another, whether you're using HTML, XML, etc. 

Our primary use case for the solution is using the system interface exposing APIs using a tip code as a target button.

Our primary use case of BusinessWorks is integration, to ensure that our various systems are communicating and integrated. Instead of doing point-to-point integration, we implemented this solution to ensure that system A can talk to system B via BusinessWorks. 

We started with on-premise, but have migrated to the cloud version, so we're using the latest update of BusinessWorks. We have a hybrid deployment—some services still run on-premise, but the latest services are running on our private cloud. We have a Kubernetes cluster set up within our VMs. 

This solution is for enterprise application integration. Basically, it does the integration between the applications. If you want to integrate multiple systems, it lets you expose an API. For a business application that is running on, for example, AS/400 or COBOL system, if you want to expose some information pertaining to the system, TIBCO would also play a role there. It will get the information from the latest system and just transform it into a simple format and give it as a response to the operating system. We are currently using versions 5.14 and 6.5. 

We are using the solution to control different markets, banking, security, and transportation. The solution can be deployed both on-premises and cloud.

We use it to maintain the domains and applications of product-based applications.

This product is useful for all aspects of corporate integration. Our front-end channel does not have B2B connections to the legacy systems; it's all done by TIBCO which presents services that do the communication between the different applications of our architecture enabling direct links to the different applications.

We are a system integrator and this is one of the products that we implement for our clients.

We are using this in the banking industry and we have some APIs that are based on BusinessWorks.

We using TIBCO BusinessWorks 5 and the container edition to work with integrations.  

We use this product to trigger campaign management related marketing for our customers. 

BusinessWorks is the regional and official software of the company.

We primarily use the solution for various systems.

Our primary use for the solution is contrariwise integration.

TIBCO BusinessWorks is mainly used to build services based on SOA principles.

It can be used to build synchronous services using SOAP or REST, event-based architecture based on XML over JMS.

REST services based on Swagger Specifications are supported.

We use the solution to develop applications. 

TIBCO BusinessWorks is helpful, especially in the pharmaceutical industry. I'm working with a big pharmaceutical company right now, and we're using it to manage orders, invoices, and patient licenses.