I am always working. I am working with WebLogic and WebSphere. Some things are running on WebLogic and others on WebSphere. I use both.
It is deployed on-premise, and I am able to do everything they are doing on the cloud.
I am always working. I am working with WebLogic and WebSphere. Some things are running on WebLogic and others on WebSphere. I use both.
It is deployed on-premise, and I am able to do everything they are doing on the cloud.
I would not compare WebSphere and WebLogic because both servers are really good.
However, once you have set up both of them, they work perfectly.
There are always bugs, such as the recent bug with log4j, but they're both good web servers. I can make use of either one, it makes no difference. It's just a different setting, but I'd say the quality is the same.
I am satisfied with this solution, as well as WebLogic. Both are good.
The performance is good.
I don't think about what needs improvement, I work with what I have.
There is always room for improvement. But it's getting better every time, with every new release, and every new patch, it's getting better. They are continuously improving.
When compared with WebLogic, Weblogic is lighter and consumes less memory.
IBM WebSphere Application Server is a stable solution.
I usually solve my problems on my own. I Google it. I do the research, find out what other people are having problems with, otherwise look to Oracle for solutions to some of them. I was always able to Google it and find the solution.
I have never had to contact Oracle or IBM for support.
I have worked with WebLogic, Apache Server, and SAP NetWeaver in the past. I've had a lot of experience.
I set up everything. you just need the hardware, and I do everything else.
When you purchase Maximo, you get WebSphere for free. Why would you pay more for WebLogic?
I would recommend using whichever is cheaper. Both are interchangeable, and I don't see a difference in their performance.
I would rate IBM WebSphere Application Server a nine out of ten.
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.
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.
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.
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.
We've been using this solution for more than five years.
It is very stable and very rugged.
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.
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.
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.
It is very expensive.
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.
The most valuable features are its user-friendliness and reliability in terms of application hosting.
The licensing could be improved, and I would like it to give the longevity of the lifespan of the visions. In the next release, I would like to be able to download and extract the files so that I can just use my application server.
I have been using this solution for fifteen years.
This is a scalable product.
Technical support is available instantly.
The initial setup was straightforward.
I would rate this solution as eight out of ten.
We use IBM WebSphere Application Server in the financial industry for applications.
The solution has good performance.
The solution could improve the integration.
I have been using BM WebSphere Application Server for a few years.
The solution is stable.
I have found the solution to be scalable.
We have approximately 1,000 users using this solution in my organization.
The technical support from IBM is very good and responsive.
The installation is not straightforward and it can take three days.
We use approximately four technicians for the implementation and maintenance of the solution.
The price of IBM WebSphere Application Server could be less expensive and there is an annual license required for this solution.
I recommend this solution to others.
I rate BM WebSphere Application Server an eight out of ten.
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.
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.
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.
I have been working with WebSphere Application Server for between five and ten years.
My customers have told me that this solution is very stable and it is working well.
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.
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.
The price of this product is higher than that of competitors.
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.
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.
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.
We've been using the solution for ten years.
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.
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.
I've dealt with technical support in the past. It's not the best. It could be improved.
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.
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.
We have used it for the implementation of a web interface on very old mainframe system.
We've avoided the remake of mainframe application logics.
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.
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.
I have been working with this system for ten years.
I think the stability of the product is very good.
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.
IBM is our mail provider for DC facilities, system integration and AMS.
No
The initial setup was very complex due to the complexity of the already existing business logics.
We implemented the solution with IBM services.
The system is very old so it is not so easy to calculate.
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.
No
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.
We use it as a gateway for our payment application. It receives requests and processes it.
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.
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.
I have been using it for three months.
Stability is frustrating. It goes down after a specific number of user connections. It does not have high availability.
I have contacted their technical support. They offer good help to help resolve the issue. They were efficient and helpful. They have good documentation.
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.
There aren't any additional costs besides for the standard licensing.
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.