Business Head - Enterprise Solutions at ImageGrafix Software FZCO
Reseller
Top 20
2024-09-30T10:04:00Z
Sep 30, 2024
WebLogic requires a person with coding knowledge for easy configuration and quick integrations. Some of the other Oracle applications, like Oracle Integration Cloud or SOA, are easier to use since they don't require much coding.
Java Full Stack Developer at a financial services firm with 5,001-10,000 employees
Real User
Top 20
2024-04-03T22:28:41Z
Apr 3, 2024
The documentation is too broad. The content search is not easy. We see a lot of sources of information, but we must dig in to get what we need. We need to do trial and error. It might be because there is a lot of information in the documentation.
Systems Analyst at a government with 201-500 employees
Real User
Top 5
2023-07-25T08:05:01Z
Jul 25, 2023
A supplier installed the solution. They were managing the solution, and then the contract ended. Then, we faced issues because we did not get the necessary training to use the solution. I had to train myself to use the product. The product is not easy to use if we do not have proper training.
Deliver Head - Database and Infrastructure Cloud Services at Tech Mahindra Limited
Real User
Top 20
2022-09-22T14:29:45Z
Sep 22, 2022
I noticed a few areas for improvement in WebLogic Suite. If you use the pure play higher-availability features, then yes, it can be switched over to the other system from the high-availability point of view, but that comes with a certain price. If you prefer simpler high-availability, that requires manual intervention. I'd also recommend a tuning feature in WebLogic Suite because it's not self-tuning, and this means you need thorough expertise to do the tuning and leverage the best benefit out of it. If Oracle makes WebLogic Suite automated or self-driven, then it becomes a wonderful product, similar to what Oracle did for the Autonomous Database which is self-driven or has an autonomous operating system. If automation is added in the next release of the solution, combined with more affordable pricing, though as a technical person, I know how much goes into having automation as a feature, and it could be difficult to lower the price, but if Oracle can do it, then that would make WebLogic Suite better.
I think the only area where Weblogic could be improved would be if they were to develop a solution for smaller applications. WebLogic is really a solution for enterprise companies, meaning that it requires a lot of RAM. Sometimes you're working on a smaller application but WebLogic still needs a huge amount of RAM for it to work. Jboss or Apache, on the other hand, would start with the minimum amount of RAM, for example, 300 megabytes and with WebLogic, you need 3GB or 4GB. Because it's very heavy, the extraction time is longer compared to other solutions. Jboss would start in seven seconds, whereas WebLogic would start in 40 or 50 seconds. If there was a light version of WebLogic that would be useful. I would also like to be able to turn off features. For example, if I don't want to use the GMS, I can't turn it off.
Technical Specialist at a financial services firm with 10,001+ employees
Real User
2020-03-05T08:39:52Z
Mar 5, 2020
Customization is a bit of an issue for us. Support could be better. The expertise when we have some Oracle WebLogic issues and challenges is not there. The issues are not being addressed in time. This really needs to be improved going forward.
Operations Manager EMEA at a computer software company with 201-500 employees
Real User
Top 20
2020-01-30T07:55:00Z
Jan 30, 2020
Sometimes there are issues when we work on a VM because people use it to put all of their reports on it at the same time. Then I have to restart and rebuild the machine. That is more of an issue with the users though.
Data Networking at a manufacturing company with 1,001-5,000 employees
Real User
2020-01-27T06:39:00Z
Jan 27, 2020
The restart capability needs to be improved because it takes us 15 minutes to restart any application. This is a heavy application, like everything that comes from Oracle. Debugging with this solution is tough and a bit complex. The interface is not very user-friendly.
Senior Cloud Infrastructure Consultant at a tech vendor with 51-200 employees
MSP
2019-11-20T05:39:00Z
Nov 20, 2019
All the areas of this program needs to improve. The integration with other providers and the user management could be better, and the upgrades are pretty complicated. So I would like to see that being improved in the next version.
Enterprise Architect at a tech services company with 201-500 employees
Real User
2019-11-14T06:33:00Z
Nov 14, 2019
The solution needs to share more information in terms of training. There needs to be more documentation involved to help those who are completely new to the product.
Oracle Fusion Middleware specialist at a tech services company with 10,001+ employees
Real User
2019-09-05T05:37:00Z
Sep 5, 2019
It is difficult to say which features can be improved at the moment, as we are not working with the most current version and I am not aware of the features offered in the new version. Once we catch up and move on to version 12C, we need to see what can be migrated to the cloud. It might not be suitable to migrate the systems to the cloud, or maybe only portions of it. For example, it makes sense for our web services to go on the cloud, but not the actual application, the CRM system. If we are considering the version that we are currently working with, then I would say that it's all fairly straightforward when it comes to using it. However, there are some small things, such as being able to restart clusters, where you can choose to restart each server one by one instead of all at the same time. The ripple start is what we refer to as shutting down and restarting one server at a time in a cluster. In other words, when you kick off a ripple start, and it would go through, it will shut down the one instance, and start it up, then it would move to the next one. It wouldn't shut them all down, and I wouldn't have to manually, stop one, start it up, wait for it to come up and then move down to the next one. This solution would benefit from the inclusion of a ripple start function for clusters. Also, the cloud integration, which I've heard is very strong with Oracle, it's the shift and lift methodology. IBM WebSphere used to do things like that, where you could do a ripple start as opposed to shutting everything down and it would manage each one individually. That would be useful. if it's a live environment we have to ripple start. That's the big one, otherwise, we are pretty happy with everything. The debugging function is nice on the Weblogic, but one thing WebSphere has, is, that you can apply the debugging permanently, or just until the server is restarted. That might also be a feature that would be nice on WebLogic, but not critical because we turned it off afterward.
Senior Enterprise Architect at a healthcare company with 11-50 employees
Real User
2018-07-16T10:04:00Z
Jul 16, 2018
We need to have more adapters and connectors, especially healthcare system adapters. This solution doesn't have connectors to other external applications. We connect with other vendors' and other companies' systems, therefore we have been asking Oracle for specific interfaces because we have been unable to integrate with these systems using any adapters.
Oracle WebLogic Suite is an integrated solution for building onpremise cloud application infrastructures that span web server, application server and data grid technology tiers. It includes Oracle WebLogic Server, an application server for developing and deploying applications across conventional and cloud environments, Oracle Coherence Enterprise Edition, Oracle Web Tier, Oracle TopLink, Oracle Java Mission Control and Flight Recorder, and other component technologies.
WebLogic requires a person with coding knowledge for easy configuration and quick integrations. Some of the other Oracle applications, like Oracle Integration Cloud or SOA, are easier to use since they don't require much coding.
The documentation is too broad. The content search is not easy. We see a lot of sources of information, but we must dig in to get what we need. We need to do trial and error. It might be because there is a lot of information in the documentation.
A supplier installed the solution. They were managing the solution, and then the contract ended. Then, we faced issues because we did not get the necessary training to use the solution. I had to train myself to use the product. The product is not easy to use if we do not have proper training.
I noticed a few areas for improvement in WebLogic Suite. If you use the pure play higher-availability features, then yes, it can be switched over to the other system from the high-availability point of view, but that comes with a certain price. If you prefer simpler high-availability, that requires manual intervention. I'd also recommend a tuning feature in WebLogic Suite because it's not self-tuning, and this means you need thorough expertise to do the tuning and leverage the best benefit out of it. If Oracle makes WebLogic Suite automated or self-driven, then it becomes a wonderful product, similar to what Oracle did for the Autonomous Database which is self-driven or has an autonomous operating system. If automation is added in the next release of the solution, combined with more affordable pricing, though as a technical person, I know how much goes into having automation as a feature, and it could be difficult to lower the price, but if Oracle can do it, then that would make WebLogic Suite better.
I think the only area where Weblogic could be improved would be if they were to develop a solution for smaller applications. WebLogic is really a solution for enterprise companies, meaning that it requires a lot of RAM. Sometimes you're working on a smaller application but WebLogic still needs a huge amount of RAM for it to work. Jboss or Apache, on the other hand, would start with the minimum amount of RAM, for example, 300 megabytes and with WebLogic, you need 3GB or 4GB. Because it's very heavy, the extraction time is longer compared to other solutions. Jboss would start in seven seconds, whereas WebLogic would start in 40 or 50 seconds. If there was a light version of WebLogic that would be useful. I would also like to be able to turn off features. For example, if I don't want to use the GMS, I can't turn it off.
For improvement, I think the area of clusters are sometimes problematic and we do have issues around that.
Customization is a bit of an issue for us. Support could be better. The expertise when we have some Oracle WebLogic issues and challenges is not there. The issues are not being addressed in time. This really needs to be improved going forward.
Sometimes there are issues when we work on a VM because people use it to put all of their reports on it at the same time. Then I have to restart and rebuild the machine. That is more of an issue with the users though.
Deployment and integration should be simplified. I would like to see the licensing policy simplified.
The restart capability needs to be improved because it takes us 15 minutes to restart any application. This is a heavy application, like everything that comes from Oracle. Debugging with this solution is tough and a bit complex. The interface is not very user-friendly.
All the areas of this program needs to improve. The integration with other providers and the user management could be better, and the upgrades are pretty complicated. So I would like to see that being improved in the next version.
The solution needs to share more information in terms of training. There needs to be more documentation involved to help those who are completely new to the product.
I had issues when I installed the SSL. With WebLogic, it's a very lengthy process.
It is difficult to say which features can be improved at the moment, as we are not working with the most current version and I am not aware of the features offered in the new version. Once we catch up and move on to version 12C, we need to see what can be migrated to the cloud. It might not be suitable to migrate the systems to the cloud, or maybe only portions of it. For example, it makes sense for our web services to go on the cloud, but not the actual application, the CRM system. If we are considering the version that we are currently working with, then I would say that it's all fairly straightforward when it comes to using it. However, there are some small things, such as being able to restart clusters, where you can choose to restart each server one by one instead of all at the same time. The ripple start is what we refer to as shutting down and restarting one server at a time in a cluster. In other words, when you kick off a ripple start, and it would go through, it will shut down the one instance, and start it up, then it would move to the next one. It wouldn't shut them all down, and I wouldn't have to manually, stop one, start it up, wait for it to come up and then move down to the next one. This solution would benefit from the inclusion of a ripple start function for clusters. Also, the cloud integration, which I've heard is very strong with Oracle, it's the shift and lift methodology. IBM WebSphere used to do things like that, where you could do a ripple start as opposed to shutting everything down and it would manage each one individually. That would be useful. if it's a live environment we have to ripple start. That's the big one, otherwise, we are pretty happy with everything. The debugging function is nice on the Weblogic, but one thing WebSphere has, is, that you can apply the debugging permanently, or just until the server is restarted. That might also be a feature that would be nice on WebLogic, but not critical because we turned it off afterward.
We need to have more adapters and connectors, especially healthcare system adapters. This solution doesn't have connectors to other external applications. We connect with other vendors' and other companies' systems, therefore we have been asking Oracle for specific interfaces because we have been unable to integrate with these systems using any adapters.