How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.
We implement this solution for our customers.
The solution is primarily a middleware. It's security-enabled and we are using the same credentials for development. We plan on making a backend to handle growing requests.
We primarily use the solution as a basic integration platform for all the complicated technology solutions we have.
Our primary use for this solution is to integrate different applications into the aviation area. We have an on-premises deployment.
The primary use case of this solution is as a corporate integration bus, between different financial applications. We use IBM Integration Bus (IIB) with IBM MQ for asynchronous interaction. Additionally, web services for synchronized integration such as REST APIs, SOAP and HTTP Interfaces with XML interaction. For instance, it uses for the integration of the Banking front end with the banking core application. IBM Integration Bus installed on-premise.
The IBM Integration Bus platform is Advanced Enterprise service bus , Typically used in SOA Environments . with newer version it can work it container based platforms and can be used to implement Micro services. We have implemented IIB/WMB Based Solution in multiple organizations helping them to adopt Service oriented architecture , and eliminating point to point integrations.
My primary use case of this solution is for establishing an enterprise service between the orchestrated transactions of two different channels. This is the main purpose of this product.
Our primary use case is a content-based tool for system messaging. IIB comes with IBM MQ as its messaging backbone. With respect to our requirements, IIB fits well, and it does its job.
We have used IIB as a complete ESB solution with IBM MQ for various financial institutions. IIB supports various connectors, message formats, and transport protocols. Its transformation language, ESQL, is easy to learn and use. Rich support of the mapping node (GUI mapping), JavaCompute Node, XSL, etc. make it useful and developer friendly. IIB 10's primary features: * REST API design and development support out-of-the-box. OpenAPI compliant. * Lightweight run time, hence it is ideal for Docker/microservices implementation. * Several ways to admin using web interface, REST API admin capabilities, and console administration. * Long list of already built-in connectors for legacy systems (CICS, MQ, etc) and modern system connectors (Salesforce, LoopBack, etc.). * Long list of parsers (XMLNSC, DFDL, JSON, etc.). * Easy to understand documentation with a huge list of examples and tutorials.