We just raised a $30M Series A: Read our story

IBM WebSphere Application Server OverviewUNIXBusinessApplication

IBM WebSphere Application Server is #2 ranked solution in top Application Server tools and #6 ranked solution in top Application Infrastructure tools. IT Central Station users give IBM WebSphere Application Server an average rating of 8 out of 10. IBM WebSphere Application Server is most commonly compared to Tomcat:IBM WebSphere Application Server vs Tomcat. The top industry researching this solution are professionals from a computer software company, accounting for 28% of all views.
What is IBM WebSphere Application Server?
IBM WebSphere Application Server provides a range of flexible, secure, Java EE 7 runtime environments available on premises or across any public, private or hybrid cloud.

IBM WebSphere Application Server is also known as WebSphere Application Server.

IBM WebSphere Application Server Buyer's Guide

Download the IBM WebSphere Application Server Buyer's Guide including reviews and more. Updated: November 2021

IBM WebSphere Application Server Customers
TalkTalk, Property management group, E.SUN Bank, Ohio National Financial Services, Aviarc, Cincom Systems, FJA-US, D+H, Staples, Michigan Municipal League
IBM WebSphere Application Server Video

Pricing Advice

What users are saying about IBM WebSphere Application Server pricing:
  • "We used to pay about $100,000-$120,000 US or somewhere around there. That was a bit cost-prohibitive for us to continue."
  • "It is very expensive."
  • "We pay around $200,000 annually."
  • "The price of this product is higher than that of competitors."
  • "The price of IBM WebSphere Application Server could be less expensive and there is an annual license required for this solution."

IBM WebSphere Application Server Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
SR
Head, Operations at a tech services company with 51-200 employees
Real User
Top 10
Bad documentation, does not scale well, and has a lot of complexities

Pros and Cons

  • "It does integrate well with the Tivoli Federated Identity Management system."
  • "Based on the field and based on the build that was provided, we've noticed a lot of constraints in terms of the performance now."

What is our primary use case?

This solution is part of an enterprise web presence. It integrates well with the Tivoli Federated Identity Management system, which works as a single sign-on mechanism for other e-services that we have shared with other clients. They utilize some of our authentication engines and they provided access for their users back into their system, however, the presentation and the web presence for it comes on the WebSphere portal solution.

What is most valuable?

We've had so many challenges with the solution in the last two years that it's a bit difficult to find highlights.

It does integrate well with the Tivoli Federated Identity Management system.

What needs improvement?

I'm not certain if the WebSphere solution was deployed by IBM. There are a lot of complexities in how the solution was actually built and deployed, which means troubleshooting on management for us is pretty difficult. 

One of the biggest issues that we've had is there are certain features that we required that were hardcoded into the solution itself. When you manage them for making any architectural or solution changes, it becomes very difficult and near impossible to do. With respect to that, we tried to change the SSL certificate that would be in use, and because of how we tried to change the SSL certificate, we tried to change the DNS mover that it was pointing to.

There were hardcoded elements in the solution that didn't make it very easy for us. At the end of the day, we just kind-of renewed whatever services that we had already ongoing with it, which was a duplicate payment with what we had from other sources. We couldn't take advantage of the shared resources that we had before. We now have to maintain it as an isolated instance.

Based on the field and based on the build that was provided, we've noticed a lot of constraints in terms of the performance now.

Due to GDPR and other issues, not everybody is able to utilize cloud services. That's something that people need to be aware of. The company needs to be clear on the business use case and how they need to maintain compliance with its policies and regulations. Some of the feature sets that we found a little lacking in this particular solution. By now they've probably changed the ability to embed and utilize the rich media content and web presence. 

Our site is basically little image JPEGs, and that's it. We have low embedded video. We have low dynamic speech response for mobile viewing, we have low integration or extension for mobile apps. We have low integration as well as for dynamic content of bits from other sites. For some of our clients who wish to display information on our website, we actually have to lift the content, reform our tips, and recreate it into the content management engine.

For how long have I used the solution?

We first did a deployment back in 2008. It was an enterprise deployment where we wanted to get modules for forms and themes and gateways, especially an SMS Gateway. We needed to have different services. The IBM WebSphere solution was the only one at the time that was able to provide a full suite solution. 

We upgraded in 2014 and since then, we've kind of continued to utilize the service. In 2017 it became a bit cost-prohibitive for us to maintain all the different levels of support on it. We've just kind of been getting by with some third party support services and reactive support services.

What do I think about the stability of the solution?

Since we've been monitoring it directly ourselves, we've found that there has been an increase in the number of failures. The failures result in deadlock processes that generate very little to no troubleshooting logs. A lot of time we find ourselves just really staffing services to get these solutions to market in our online space. Reviewing logs to get the root cause and drilling down into something more definitive so that we could enable resolutions that are more permanent, that has been absent, basically.

What do I think about the scalability of the solution?

When we exited the contracts, IBM did an audit of the solution and there were licensing entitlements that we had no information about. The products themselves could only run on specific servers of specific configurations, which we worked at up until the audit was done. 

The scalability in terms of company full storage looks fine. What we've realized is that the DB2 disappears, as there is an amendment and build. Therefore the IBM DB2 database has been less than optimal as we've grown over the last two to three years. And we've started to see this as a little more of a challenge, in terms of the configuration for the build as well. It doesn't support the groups. The license entitlement rarely gives us a bare minimum for the capacity to process what we have now. So the scalability of the solution is very limited.

The scalability for the solution was supposed to be for about 800,000 users. We just coming up on 100,000 and we're already seeing performance issues.

We have roughly 100,000 users and the majority of them would be using the single sign-on service to access our client services. We have probably about 20 to 30 persons who deal with user administration and content of this onsite maintenance and management in terms of web posts, et cetera.

The rest of them are really just users - either web browser users or users of the single sign-on.

How are customer service and technical support?

The documentation around the product is not very clear, even post-implementation. IBM just basically cut us off and whatever we had was what we had. They weren't going to offer us anything. If we found gaps in the configurations or the documents, and we asked for the other stored information, nothing was forthcoming. IBM was actually very dependent on a third-party provider. There were a few instances where IBM directly handled either an implementation or configuration aspects. A lot of it was actually passed on to a third-party provider, who was the person that we used to know. A very small fraction of the price was what we were paying to IBM, in fact.

Which solution did I use previously and why did I switch?

A Microsoft solution that was used between 2006 and 2008. I believe it was based on a SharePoint platform. It really utilized the IIS together with standard HTML features, et cetera. It looked good, however, it didn't have the expandability for the other service modules that we wanted to use at the time to expand to true competitors bid. The IBM solution would have been the most comprehensive in terms of meeting the technical requirements. 

How was the initial setup?

The first deployment took about 18 months. That was in 2008. The upgrade took roughly six months, however, there were certain features and there was specific stuff we wanted that was never implemented. For example, the authentication system. While it uses our randomly generated 16 digit username, we wanted to do an alias for that system and we couldn't. I don't know what was the reason, however, it just couldn't be done. We've had issues as well with the file sizes being very bloated of using Blogger instead of any other optimized file storage mechanism. When the IBM deployment was contracted it used to run very smoothly. What we recognize now is that we're not set up properly and we're finding a lot of intricate complexities that we don't believe were necessary.

What's my experience with pricing, setup cost, and licensing?

We used to pay about $100,000-$120,000 US or somewhere around there. That was a bit cost-prohibitive for us to continue.

You need to pay for both software licenses and software support, which was the IBM backline. There were two levels of support for software and software bots. We had hardware support, which was separate, and we had to proactively monitor service maintenance support as well.

What other advice do I have?

The solution that we have now, one of the challenges we have is with the WebSphere portal. The WebSphere application and WebSphere content management software are no longer IBM products. IBM would have sold it off to ETL back in 2018 or 2019. Maintaining that as a full end to end IBM solution has become very difficult. They basically have a hands-off approach now. Anybody who's using this needs to be aware of what is available to them by way of manufacturer support and then other support. The licensing entitlements for the product need to be very carefully understood. There are limitations to the hardware configuration that goes together with the implementation.

The other thing is that we've recognized that there are few resources that have the experience and capability of monitoring this system. If you are going to deploy it, you should ensure that you either have strong and continued backline support with your vendors or third party managers or that your in-house team is well skilled in order to monitor and maintain everything and administer the system. If you can get to a point where the build, implementation, and commissioning could be done in house, that will give you a lot more visibility to all the different elements of the solution and how they integrate and interoperate so that it makes the management on troubleshooting a lot easier. 

I'm biased due to my previous experiences. My experiences are really more influenced by the build and not necessarily the product as a standalone product. 

I would rate the solution at a three out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PRINCEWILL OPARA
Head Banking Application Customization and Reporting at a financial services firm with 10,001+ employees
Real User
Top 5Leaderboard
Very stable, supports many languages, and helpful for faster time to market

Pros and Cons

  • "As compared to other applications, it has tremendous support. We have built internal capability so that we use it extensively internally. It is also easier to use with the outside data. You can write in ESQL, Java, or any other technology that you want to use for development. So, it is a lot more flexible in the language that it supports."
  • "The business logic side of it is sort of missing in the sense that if I want to track and measure velocity, it is not really available. You have to buy another application and embark on a separate implementation. Instead of having different licensing, IBM DataPower should be integrated with WebSphere. It will allow us to build the business layer and rules a lot more efficiently, rather than developing rules within the application. It would be good if we can set up the business layer through parametrization rather than development. IBM DataPower has the business rule and the controls, and if it can be integrated, it would be fantastic. It will help the application in working better in terms of security features and business logic. If you're going to use it for open banking, you will be able to monitor velocity on the total pricing."

What is our primary use case?

There are two use case categories. We use it for integration with other parties or external parties across the world, and we also use it for internal applications. It has an enterprise service bus, and all applications talk to each other through IIB. We also using WebSphere for the exchange of messages between core banking applications and other applications and servers.

How has it helped my organization?

It has helped tremendously. Before we embarked on the enterprise service bus, we had to develop applications for integration with in-house and third-party applications. We had to develop an application and get a dedicated server. We also had to get the server within the firewall. There was no concrete policy around that, and it just was disorganized and disoriented. Now, we have a lot more structure. The time to market is a lot faster, and there is a structure around it.

What is most valuable?

As compared to other applications, it has tremendous support. We have built internal capability so that we use it extensively internally. It is also easier to use with the outside data. You can write in ESQL, Java, or any other technology that you want to use for development. So, it is a lot more flexible in the language that it supports.

What needs improvement?

It is very tough to get developers. It is not open, so there is a shortage of its knowledge in the industry. We have to get freshers and train them. We can't just go out there in the market and get developers who are proficient in IIB. I have attended several boot camps on AI and other products of IBM. Similar to what IBM is doing with big data and AI, IBM should open up IIB so that there is a lot more knowledge. They should open up the WebSphere application so that there is a lot more knowledge.

The business logic side of it is sort of missing in the sense that if I want to track and measure velocity, it is not really available. You have to buy another application and embark on a separate implementation. Instead of having different licensing, IBM DataPower should be integrated with WebSphere. It will allow us to build the business layer and rules a lot more efficiently, rather than developing rules within the application. It would be good if we can set up the business layer through parametrization rather than development. IBM DataPower has the business rule and the controls, and if it can be integrated, it would be fantastic. It will help the application in working better in terms of security features and business logic. If you're going to use it for open banking, you will be able to monitor velocity on the total pricing.

Its price is a bit expensive. They should improve its price to compete with other applications that are out there, which we are also exploring.

For how long have I used the solution?

We've been using this solution for more than five years.

What do I think about the stability of the solution?

It is very stable and very rugged.

What do I think about the scalability of the solution?

You can't reduce what you buy from there. You have to buy the whole product. It is highly scalable and extendable in terms of extending the feature developed to be used in other areas.

We have two sets of users. We have the developers and the support people in different teams. There are approximately 12 developers in the Developer team. There is also a Support team with six or seven people. The support people are in the CTO organization, whereas, developers are in the forward-looking arm of our IT, which is the CIO organization. That's the way we are structured.

How are customer service and technical support?

They have partners who helped us with the initial installation, and we got technical support from them. The other one is the second level of support from IBM, which goes in line with their normal licensing framework. So, there is strong support from IBM.

How was the initial setup?

It is complex. It is not something that you can do on your own without recourse to IBM. You need access and all the support and help from IBM for this. We need consultants who are proficient and IBM partners to do the setup. When you get the license from IBM, they have the recommended partners in a country to set it up. 

What's my experience with pricing, setup cost, and licensing?

It is very expensive.

What other advice do I have?

I would advise others to have a very strong partner who understands IBM WebSphere very well. They should be mindful of the architecture that they're going to put in place for the IBM solution. You should ensure that load balancing and the architecture of the implementation are right. Otherwise, there could be issues. Having a stronger partner for handling implementation makes life a lot easier and more meaningful.

I would rate IBM WebSphere Application Server an eight out of 10.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Flag as inappropriate
Learn what your peers think about IBM WebSphere Application Server. Get advice and tips from experienced pros sharing their opinions. Updated: November 2021.
552,305 professionals have used our research since 2012.
GE
Principal Architect with 1-10 employees
Real User
Top 10
Valuable connection management and scalability but is quite expensive

Pros and Cons

  • "The solution is robust. The connection management and the scalability, which IBM provides to the Stack, are also valuable."
  • "They should make the solution more lightweight and not bundle everything into a single product."

What is our primary use case?

We have some services which are doubled up using Java. To deploy this research we are using the WebSphere Application Server. A lot of channel applications are consuming these services in particular.

What is most valuable?

The solution is robust. The connection management and the scalability, which IBM provides to the Stack, are also valuable.

What needs improvement?

Nowadays the industry is moving towards a more open-source operating framework.

The cost factor is huge. It's very pricey compared to other open-source stacks. In the future, we'll deal with the IBM Stack so we might move to a compact server and other open-source alternatives which are comparatively less in terms of cost.

They should make the solution more lightweight and not bundle everything into a single product.

The solution would benefit from having a different licensing model.

For how long have I used the solution?

I've been using the solution for 12 to 14 years.

What do I think about the scalability of the solution?

The solution's scalability is good, but there is a cost factor, which is a disappointing element. If you want to go for another node then you have to go pull up that code license model, and that produces another licensing cost.

How are customer service and technical support?

We've reached out to technical support. I find them good, but not excellent. They aren't very quick to respond.

Which solution did I use previously and why did I switch?

We were using WebLogic BL as our stack. Now we use an IBM Stack. It was about eight years ago when we switched, so we've been using IBM for a while now.

How was the initial setup?

Depending on which platform you are on, the initial setup isn't too complex.

Currently, it is all straightforward, but it should be where the next generation of container-based, docker-based is and it's not there yet. Everyone wants that type of compatibility.

Deployment takes about two to three hours.

What about the implementation team?

We have our in-house team who are trained in the deployment of IBM WebSphere Application Servers, so we didn't need outside assistance. 

What's my experience with pricing, setup cost, and licensing?

The solution is very expensive compared to an open-source stack.

What other advice do I have?

The solution is deployed in the UX operating system.

Although the solution is good, open-source options keep getting better and better, so I'd recommend others to look into that. This solution is expensive. So is Oracle. I find open-source more innovative and they often have a good community around them that offers helpful support.

I'd rate the solution seven out of ten. I'd rate it higher, but there are basic features that have minimum capabilities that can be very dissatisfying. Apart from that, they provide good support, offer a good clustering model that's reliable, and it's properly tested with certified code.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
MV
Service Relationship Manager at a manufacturing company with 10,001+ employees
Real User
Top 10
Has a lot of native connectors with legacy sistems and so for complex systems, it simplify a lot integration tasks.

Pros and Cons

  • "We needed this type of integration and WebShepere is the best tool for it."
  • "I think that this is a good product but I think that the cloud environment could be improved. I think that the future is in the utilization of the product in a product as a service way which is something that is lacking at this moment."

What is our primary use case?

We have used it for the implementation of a web interface on very old mainframe system.

How has it helped my organization?

We've avoided the remake of mainframe application logics.

What is most valuable?

WebSphere connects with old legacy systems, like CICS and TX Series that typically run on the mainframe environment and that must be integrated with open systems.

What needs improvement?

Cloud service offering should be improved because the future is in the utilization of the PaaS provided by principal cloud providers; I mean that it would be very useful to have the possibility to use WebSphere as a service like many other tools has already done.

For how long have I used the solution?

I have been working with this system for ten years. 

What do I think about the stability of the solution?

I think the stability of the product is very good. 

What do I think about the scalability of the solution?

The main problem is the licensing cost of the product. The product can scale but the budget cannot. We pay for core utilization and so we have to consider and manage peaks in resources utilization. 

How are customer service and technical support?

IBM is our mail provider for DC facilities, system integration and AMS.

Which solution did I use previously and why did I switch?

No

How was the initial setup?

The initial setup was very complex due to the complexity of the already existing business logics.

What about the implementation team?

We implemented the solution with IBM services.

What was our ROI?

The system is very old so it is not so easy to calculate. 

What's my experience with pricing, setup cost, and licensing?

The product is very expensive because PVU has to be calculated on maximun virtual cores and there is no difference between production and non-production environments.

Which other solutions did I evaluate?

No

What other advice do I have?

If you need a small system that needs to be exposed on the web for simple transations, or if you are considering a cloud environment you should consider a different solution. 

I would rate it an eight out of ten because for complex system development, it is the best solution at this moment. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
NC
System and Solutions Architect at a tech services company with 501-1,000 employees
Real User
Top 10
Easy to install and the GUI is intuitive and easy-to-use

Pros and Cons

  • "This solution is easy to use with a GUI that is intuitive and very helpful."
  • "Some things are very difficult to do, so the interface and usage could be more intuitive for those."

What is our primary use case?

This solution is normally used on the front-end of applications that we have in DB2 for IBM i. Our customers are in a variety of industries including insurance, financial, and retail. They use the WebSphere Application Server as part of their portal that talks with the database.

We have installed this application under several different operating systems including Red Hat Linux, IBM i  and IBM AIX.

What is most valuable?

This solution is easy to use with a GUI that is intuitive and very helpful.

You have the ability to do a lot of things with the commands.

What needs improvement?

Some things are very difficult to do, so the interface and usage could be more intuitive for those.

The main complaint that my customers have about this product is the price.

For how long have I used the solution?

I have been working with WebSphere Application Server for between five and ten years.

What do I think about the stability of the solution?

My customers have told me that this solution is very stable and it is working well.

How are customer service and technical support?

I have dealt with IBM's technical support on a variety of issues and normally it is pretty good. The response time is good and depending on the area, some support is more diligent and more effective than others. In general, I would say that they are above average, but the support could be improved in certain areas.

How was the initial setup?

The initial setup is quite easy. You don't necessarily need to be a technical person. The configuration can be a little more demanding, but the initial installation is not difficult.

What's my experience with pricing, setup cost, and licensing?

The price of this product is higher than that of competitors.

What other advice do I have?

IBM WebSphere Application Server works well and fulfills all of the requirements that are demanded of it, so it is a product that I recommend.

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PC
Sen. Fab Manager at a manufacturing company with 10,001+ employees
Real User
Top 20
Good data consistency and decent scalability but needs to be more customizable

Pros and Cons

  • "The scalability of the product is quite good."
  • "The availability of the solution needs improvement."

What is most valuable?

The solution's data consistency is great. It's very reliable. This is important for a transitional scenario. It is critical for us, so data consistency is the most important feature that we count on.

The user interface is reliable.

The scalability of the product is quite good.

What needs improvement?

The availability of the solution needs improvement.

The product should be more enhanced and responsive. We need to have the capabilities to customize it a bit more.

Their pricing is always too high.

The user interface isn't too impressive.

The stability of the solution could be much better.

The solution's technical support could be improved. They can be too technical and too detailed.

For how long have I used the solution?

We've been using the solution for ten years.

What do I think about the stability of the solution?

The stability of the solution is okay. I'd rate it overall seven out of ten. It's mostly reliable, however, I believe it could use some major improvements.

What do I think about the scalability of the solution?

The scalability of the solution is pretty good. I'd rate it seven out of ten. It's possible to scale a bit if you need to.

How are customer service and technical support?

I've dealt with technical support in the past. It's not the best. It could be improved.

How was the initial setup?

The initials setup is not straightforward. It's quite complicated. An organization needs some pretty good experience. They need a high skill level.

For us, deployment took half a year.

What other advice do I have?

We're just users. We don't have a business relationship with IBM.

I'd rate the solution seven out of ten. I'd rate it higher if they offered more customization capabilities and was more responsive.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
SherifHassan
Application Integration Engineer at EFG-Hermes
Real User
Top 5Leaderboard
Has a variety of configuration database certificates and good stability

Pros and Cons

  • "It has good stability of the application server in the long term compared to other solutions."
  • "It should be able to serve more concurrent requests like Oracle. Oracle has more powerful stability, availability, and real-time serving."

What is our primary use case?

We use it as a gateway for our payment application. It receives requests and processes it. 

What is most valuable?

The most valuable feature is the configuration of the application server. It has a variety of configuration database certificates and connection pools. It has good stability of the application server in the long term compared to other solutions. 

What needs improvement?

It should be able to serve more concurrent requests like Oracle. Oracle has more powerful stability, availability, and real-time serving. 

WebSphere is not light enough to implement high available applications like gateways. But WebSphere has more configuration abilities and customizability.  

For how long have I used the solution?

I have been using it for three months. 

What do I think about the stability of the solution?

Stability is frustrating. It goes down after a specific number of user connections. It does not have high availability. 

How are customer service and technical support?

I have contacted their technical support. They offer good help to help resolve the issue. They were efficient and helpful. They have good documentation. 

How was the initial setup?

I deployed it from scratch. It was not complex. It's easy to implement compared to other application servers. 

The implementation took eight hours. 

We require three engineers who do maintenance. We have an unlimited amount of users.

What's my experience with pricing, setup cost, and licensing?

There aren't any additional costs besides for the standard licensing. 

What other advice do I have?

I would rate it an eight out of ten. 

It has a sensitive implementation. If you do a wrong step, it will destroy the whole thing and you will need to start from scratch. 

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Viktor Dolyna
DevOps Engineer at Integrity
Real User
Top 5Leaderboard
Stable, good performance, and responsive technical support

What is our primary use case?

We use IBM WebSphere Application Server in the financial industry for applications.

What is most valuable?

The solution has good performance.

What needs improvement?

The solution could improve the integration.

For how long have I used the solution?

I have been using BM WebSphere Application Server for a few years.

What do I think about the stability of the solution?

The solution is stable.

What do I think about the scalability of the solution?

I have found the solution to be scalable. We have approximately 1,000 users using this solution in my organization.

How are customer service and technical support?

The technical support from IBM is very good and responsive.

How was the initial setup?

The installation is not straightforward…

What is our primary use case?

We use IBM WebSphere Application Server in the financial industry for applications.

What is most valuable?

The solution has good performance.

What needs improvement?

The solution could improve the integration.

For how long have I used the solution?

I have been using BM WebSphere Application Server for a few years.

What do I think about the stability of the solution?

The solution is stable.

What do I think about the scalability of the solution?

I have found the solution to be scalable.

We have approximately 1,000 users using this solution in my organization.

How are customer service and technical support?

The technical support from IBM is very good and responsive.

How was the initial setup?

The installation is not straightforward and it can take three days.

What about the implementation team?

We use approximately four technicians for the implementation and maintenance of the solution.

What's my experience with pricing, setup cost, and licensing?

The price of IBM WebSphere Application Server could be less expensive and there is an annual license required for this solution.

What other advice do I have?

I recommend this solution to others.

I rate BM WebSphere Application Server an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Integrator
Flag as inappropriate