Please share with the community what you think needs improvement with WebLogic Suite.
What are its weaknesses? What would you like to see changed in a future version?
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.