2017-09-14T10:19:00Z

What is your primary use case for webMethods Integration Server?

Julia Miller - PeerSpot reviewer
  • 0
  • 246
PeerSpot user
29

29 Answers

AS
Real User
Top 20
2024-01-30T18:46:57Z
Jan 30, 2024

We use the solution for application-to-application integration and B2B integration.

Search for a product comparison
Derrick Brockel - PeerSpot reviewer
Real User
Top 5Leaderboard
2023-12-14T17:30:00Z
Dec 14, 2023

Most of our applications are business applications we support, customer lookups, and what methods provide those services that have calls to our apps that needed that infrastructure. We are a combination of of Rantor Docker web methods.

Ahmed_Gomaa - PeerSpot reviewer
Real User
Top 5Leaderboard
2023-08-10T10:49:11Z
Aug 10, 2023

The tool helps with the integration between multiple entities at the same time.

Mohamed Nagah - PeerSpot reviewer
Real User
Top 10
2023-05-08T12:58:35Z
May 8, 2023

This is an integration tool along with its having IoT applications and data integration applications.

PA
MSP
Top 10
2023-03-22T09:06:10Z
Mar 22, 2023

We primarily use it as an integration server. We have integration use cases, including B2B, et cetera.

AS
Real User
Top 5
2023-02-23T09:56:37Z
Feb 23, 2023

I am using webMethods Integration Server for integrating services mainly, enterprise services bus (ESB). It is a platform for the integration of different systems. The solution can be used in many industries and different IT systems, such as internal and external databases. We have many dedicated auditors for common projects.

Learn what your peers think about webMethods Integration Server. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.
RajShaker - PeerSpot reviewer
Real User
Top 10
2023-01-18T14:48:57Z
Jan 18, 2023

Today, we work with many financial organizations worldwide, and sometimes they have Legacy software, so we use webMethods Integration Server in those cases. We are not resellers, but we provide solutions to large financial institutions, and sometimes we have to work with a lot of legacy software. Sometimes we have webMethods Integration Server as part of the stack. Sometimes we do consulting, and sometimes we take ownership of parts of the projects that large financial institutions have. webMethods Integration Server is very similar to every integration product in the world, and in the past, we used to write point-to-point connectors with the concept of ESB. We used hub and spoke architectures, and webMethods Integration Server would be used in that context. Usually, the way large enterprises work is they acquire different licenses over time, so we check their internal IT asset management software in terms of their licenses. If they already have a webMethods Integration Server license, we use that as part of our solution. Otherwise, we would make recommendations to them on what to acquire in the open market. If the solution is cloud-based, we recommend that they use cloud-based ESB software to integrate different components of their solution. We choose different software pieces, put them together, and ensure that they add value on top of the integration headaches that come when you work with enterprise software.

RJ
Real User
Top 5Leaderboard
2022-10-21T14:03:22Z
Oct 21, 2022

We've used webMethods mainly as a full-fledged DSP. We had use cases where all the USP use cases, the deployment pattern, were mainly service-oriented architecture. We had patterns arranged from web services, this protocol, and also transformation use cases to convert from XML to COBAL, or XML to external data on to task format and all the different formats, including limited format. We have used webMethods for all these use cases and even connectivity-wise, for web services, JMS and MQ.

AS
Real User
Top 5
2022-10-03T15:18:14Z
Oct 3, 2022

I'm using the product every day, and I'm working on many different projects. Most use cases are for using webMethods Integration Server as a middleware software or a middleware platform that is connecting to at least two different endpoints. It can be from one side, for example, database, web service, SAP, or any kind of connection, including Salesforce, and the other side can be the same. We are just establishing connections between these systems and doing some transformations and modifications of data in the Integration Server so it can be sent from one side to another.

VA
Real User
2022-08-23T18:34:11Z
Aug 23, 2022

We don't use webMethods Integration Server directly, but we use another offering from one of our vendors. They have built a layer on top of the webMethods Integration Server and that's a solution we have been using. webMethods Integration Server is the underlying component, but our software vendor, has made some enhancements to the webMethods Integration Server and they offered it to us. That's what we are currently using along with some of the other solutions in the supply chain space. Their offering is more of an integration framework across all their systems and this is how we have been using the system. webMethods Integration Server is our primary integration tool across all the solutions that we have in our supply chain.

MU
Real User
Top 10
2022-08-11T06:58:19Z
Aug 11, 2022

We had multiple integrations in our internal applications. The webMethods Integration Server is integrated internally, plus we have integrated it with external entities depending upon SOAP, and REST. Additionally, there is some legacy system we have connectivity with.

Yeshwanth Rajendran - PeerSpot reviewer
Real User
Top 10
2022-06-23T12:35:57Z
Jun 23, 2022

We have some common services, like REST-based services. We have applications, general social services, and application services. We'll use the solution as a utility to share across the applications selected.

Martin Moralo - PeerSpot reviewer
Reseller
Top 10
2022-03-30T10:13:00Z
Mar 30, 2022

We had quite a heavy use case in terms of transactional traffic, and webMethods was quite fantastic in processing all of those workloads.

JB
Real User
2022-01-05T06:59:04Z
Jan 5, 2022

We are using it to orchestrate and configure our APIs. I believe we are using its latest version.

RS
Real User
2021-12-09T20:35:00Z
Dec 9, 2021

We have a lot of use cases for this product. Initially, when we bought this product from Software AG, it was only for a specific project. But, we did watch for other opportunities where it could be used for integration and that's what happened. Our business model has many verticals, so it's used across the enterprise. The main function is to provide application integration within the company. We have more than 60 applications and at the moment, it's talking to more than 30 applications and integrating them. In this context, it is used by our sales team and in a lot of automations. Our second use case is to provide Write as a Service. We write any custom service using webMethods and then expose it to others as a REST service. Another thing that we use this solution for is managed file transfers. We have this solution deployed in a hybrid environment. It is available in our private cloud, where it is installed in AWS, and we also have it in our data center.

RG
Real User
2021-10-26T16:20:05Z
Oct 26, 2021

By linking apps and services, the webMethods Integration Server allows you to automate processes.

DV
Real User
Top 20
2021-04-07T13:32:00Z
Apr 7, 2021

Our primary use case for webMethods Integration Server is for our internal application integration. We use it to expose REST and SOAP web services and to connect it with SAP. We also use it as a bridge to transform web service calls. We'll use an ESB if we want to transform the protocol or the message. It's also used to connect our internal custom-written Java applications with products like SAP, which don't have an open standards interface. We only use it on-premise. We are considering going to a hybrid setup but at the moment, we don't have it yet. Nevertheless, we still use the Integration Server to integrate our cloud applications. We only have cloud on-premise integrations and not cloud to cloud. That is also why we're not focusing on a hybrid setup.

BC
Real User
2021-03-25T13:22:00Z
Mar 25, 2021

We're a healthcare technology organization and that space has a great deal of integration work, so we use webMethods to help us manage and develop integration solutions for various healthcare-related needs. Those include HL7 messages, the new interop messages, the new CMS directives for data blocking, Affordable Care Act integrations, and integrations with other health systems. Our particular product is a SaaS, multi-tenant environment that's on-prem but moving to cloud. It is used by hundreds of healthcare providers to run their businesses.

SJ
Real User
2021-03-03T09:02:00Z
Mar 3, 2021

We use it for everything. Three years or four years ago our company was bought. In our original company we used it for EDI, although that has pretty much gone away since the purchase. We do use it for EDI, but we use it for more free EAI, enterprise application integration. It allows us to have plant software talk to SAP. It allows us to interface with external parties through their MFT (managed file transfer) product called Active Transfer. We use it to connect all kinds of systems. Also, in a company that's big, there are always acquisitions, and before the acquisition can be fully integrated there is always the challenge of getting data in and out of that acquisition. We use webMethods for that too, because we can either use internal network or external network. It's hosted in Azure, on VMs.

ZD
Real User
2020-12-21T06:00:00Z
Dec 21, 2020

By Software AG, we are also using Integration Server, Trading Networks, Active Transfer, Optimize for Infrastructure, My webMethods, and their EDI package. As long as there is product parity between products, it makes sense to continue using multiple products from the same vendor. Obviously, you want to make sure you have a diverse portfolio. Where those products start breaking those links, you want to make sure that you are using the best product for your company in this region. The fact that we were already using another solution from this vendor affected our decision to go with this particular product, mainly from a cost standpoint. As is any product in this region, the biggest cost is almost always the upfront cost of laying out the solution. Also, there are some costs in having that solution already available: between knowledge of the platform, having the licensing rights, and if you bring in a new solution, then you are now paying for two solutions. The native integrations between the vendors' products are very seamless. The products interact very well. At times, it's kind of hard to tell where one product ends and the next one starts. As new products come in, the integrations probably take one or two updates before they are fully integrated. However, once products are fully integrated, it is very seamless and easy to hop between one product to another. Using multiple products from the same vendor creates efficiencies: * In terms of knowledge. Obviously, there is a familiarity with the product and how you expect Software AG's products to act and respond. * In terms of operational understanding between end users who are looking for specific data. They know how these products work and how to pull up these reports. * In terms of having administrators overseeing these products. There is a cost savings for using many of the same products. There are lower training costs. Also, typically, there are a lot of integrations that you ended up needing to build out, whether they be custom or out-of-the-box. Even if they are out-of-the-box, a lot of times that takes a lot of work to get those to work. However, since we are using Software AG products, it's very much like installing a plugin into an Excel program. There was a reduction in the learning curve because we had already used the vendors' products. The products used work very similarly. In terms of verbiage, key aspects, or three-letter acronyms, you don't have to relearn any of those. There is an expectation of how these products will work. These products always work the same way when Software AG is rolling these types of products out. We use webMethods Integration Server for two main aspects: * For application-to-application integrations. * B2B: The transferring of on-premise data out to other business partners.

RF
Real User
2020-11-25T05:25:00Z
Nov 25, 2020

Our use case is our service-oriented architecture transformation which started in 2017. It has been a three-year journey. Before that, between 2007 and 2017, we had not conducted a re-architecting of the SOA. In 2017, we had a big initiative for digital transformation at the bank to make ourselves more flexible, more agile, and competitive with all the startups and the financial industry in general, not only in Indonesia but also in other regions. One of the critical capabilities included the integration area. That is why, in 2017, we re-architected the SOA to have layered architecture that is related closely to microservices. We are testing a new mobile banking channel to use a micro services architecture as well. The integration use cases for webMethods involve connecting all of the back-end core systems at the bank so that they use the SOA integration server layer. Everything must go through this layer to speak or communicate with the back-end systems, such as the core banking, HR systems, and the treasury system; all the core systems that sit behind the ESB layer of the Integration Server. All the front-end systems like mobile banking, sales management, the CRM, etc., must go through this ESB layer, the integration server, to communicate with the back-end system. That is the prime use case of Integration Server. Other than that, we successfully launched a new initiative for API about a year ago. We are commoditizing our financial services to not only be consumed by our channels, but by partners such as startups, FinTechs, InsureTechs, and other companies that would like to partner with us and use our financial services APIs. When it comes to commoditizing for external parties, the partners, the other banks, or financial institutions that are our subsidiaries, they can connect to it and consume our services through the API Gateway products that we are providing to them. That includes sandboxing to test their applications. If they would like to partner with us, they need to register themselves and make an agreement with the bank regarding what sort of packages and fees that will be applied for the cooperation. It's deployed on-prem. We are a banking institution. In Asia, regulators for the financial industry prohibit us from hosting financial transactions outside the Indonesian region. Are you using multiple products from this vendor? ------------------------------------------------- We are using multiple products to build the end state of our service-oriented architecture (SOA). This is all orchestrated as a big building house. Those SOAs have many capabilities inside of them on the integration side, such as webMethods Integration Server. There is also webMethods API Gateway and Software AG Apama. (Read my webMethods API Gateway review here.) Those modules inside of Software AG complement the building blocks of SOA. We also use it to complement other products in the markets outside Software AG, such as Kafka as well as all event processing and streaming. This is in combination with the capabilities (and beyond) of what Software AG stacks can do. I find the native integrations between Software AG products to be very useful from a plain vanilla standpoint. Though, when we implement native integrations, there needs to be slight customizations to fit them into our core legacy system, and that needs to be integrated with other systems. For plain vanilla capabilities, it is sufficient enough. The native integrations between Software AG products also have good performance in terms of transactions per second (TPS). These are acceptable in terms of the volume and speediness of a transaction that we can produce as well as being combined with the efficiency of using the hardware, memory, and CPUs. If you combine the commodity hardware and performance as well as the plain vanilla capabilities of internal products that Software AG has, then there is a good price per value. It gives you a one-stop service for your integrations area. You can really rely on one vendor, then you don't have to worry about sustainability or support. This is all guaranteed by Software AG as a single stop service from them. Whereas, when you need to combine other vendors, then you need to monitor each of their solutions, sustainability, product roadmaps, etc. Then, this becomes your technology liabilities, which is something that we consider. From the integration, we are selecting a good strategic partnership with one vendor in order to maximize our productivity. Thus, we don't have to worry how we can monitor each respective vendor if we do a best of breed combination of many vendors, just to do an integration. By selecting Software AG and using multiple products, this saved us about 72 percent, which has definitely given us more agility. Because we were already accustomed with webMethods Integration Server way before the webMethods API Gateway, they were almost the same. We just converted our knowledge from the prior WSDL into RESTful JSON standard messages. Therefore, the learning curve was very smooth because the environment that the developers use was still the same: My webMethods Console. It uses the IDEs coming from that, saving us a lot of time with the learning curve on new technologies.

AS
Real User
2020-10-27T06:41:00Z
Oct 27, 2020

It interfaces between applications, as well as between the cloud and our existing on-prem applications. We primarily utilize packaged applications; we don't really have a lot of custom applications. We do have a few custom interfaces, and some vendors may have created a custom interface on their own, but we present a standard integration, a standard enterprise service bus, to connect to.

AA
Real User
2020-07-19T08:15:42Z
Jul 19, 2020

We are looking to use webMethods as part of our business process management solution. We have a mainframe and it facilitates connectivity with our database.

it_user1008537 - PeerSpot reviewer
Real User
2020-07-12T11:48:45Z
Jul 12, 2020

This product is used for application integration. I have implemented this solution for many clients across the world.

SA
Real User
2020-07-02T10:05:56Z
Jul 2, 2020

We use webMethods for integrating our applications.

GM
Real User
2019-06-11T11:10:00Z
Jun 11, 2019

Our primary use case is for communication between different systems and automation of business processes.

SC
Real User
2019-02-09T20:37:00Z
Feb 9, 2019

* Traditional ESB solutions using multiple adapters * API development and management.

RA
Real User
2018-07-30T09:01:00Z
Jul 30, 2018

We're using it for managing secure file transfers for the company.

IH
Real User
2017-09-14T10:19:00Z
Sep 14, 2017

I've been developing with SAG webMethods in Telco industries for integrating provisioning (CRM) end-to-end Billing, BSS and OSS, Banks/Insurance/Finance integrating bancassurance, provisioning, Switching&Allocation and Government Instance (Oil and gas) integrating B2B oil company to government reporting.

webMethods Integration Server is widely considered to be the best integration server available in the marketplace today. The solution can help users integrate everything and anything. webMethods Integration Server allows organizations to display and integrate existing and new business activities. The solution offers components that help users create, test, and install new services. webMethods Integration Server can automate, organize, and construct various gathered services and traditional...
Download webMethods Integration Server ReportRead more