We use Oracle WebLogic Server to host our Fintech-related applications for our consumers.
What I find most valuable in Oracle WebLogic Server is its flexibility in administering and managing applications, along with the built-in dashboards that offer high visibility into vulnerabilities.
Managing and monitoring the WebLogic server environment has been challenging because most monitoring tools don't support it. However, I have managed by using plugins for observability and logging tools.
Apart from application performance and monitoring, I would like to see improvements in how Oracle WebLogic Server handles logging. In my experience, there have been issues with performance degradation and thread interruptions, often requiring server restarts to resolve. This has been a significant concern across various companies and platforms, particularly in the financial technology sector in Egypt.
Additionally, Oracle WebLogic Server could benefit from incorporating containerization features to align with modern architectural practices seen in Fintech software and other Oracle products.
I have been working with Oracle WebLogic Server for about a year and a half.
Oracle WebLogic Server is not very scalable. We have over 100 key users accessing WebLogic Server daily in our environment, typically using one server with micro server setups.
I have an Oracle support account and have reached out with questions, but I haven't always received satisfactory answers. It could be due to the way I asked the question or the limitations of the support tools. I haven't always found the support to help resolve my issues. Overall, I would rate the support as a seven out of ten.
Oracle WebLogic Server has several advantages when compared to other products. Firstly, it offers a user-friendly platform for deployment and management. Secondly, it provides on-premises monitoring through its console portal, eliminating the need for external tools. Additionally, it allows for a high level of customization through the WebLogic console UI. Lastly, the WebLogic scripting tool provides administrators with a powerful CLI for performing security-related tasks and batch operations. Despite some limitations, these features make WebLogic a robust choice for enterprise applications.
Setting up Oracle WebLogic Server initially wasn't straightforward, but I received guidance from my team. It involved multiple steps, such as installing Java, which lacked clear instructions. With experience, I can now set it up in about 15 minutes. Maintenance can be difficult, especially in cases of open constraints or timeouts.
We haven't noticed any significant improvements in application deployment or management with Oracle WebLogic Server. Since our application traffic isn't massive and doesn't require heavy encryption, we haven't encountered any opportunities for business enhancement. However, we still rely on WebLogic for accessing performance data and records.
The clustering feature of Oracle WebLogic Server is the most beneficial for application performance, as it enables handling high traffic without compromising service continuity. In my experience, applications running on WebLogic without clustering struggled with performance issues, particularly in handling high-traffic loads.
I haven't worked extensively with the security features in WebLogic Server, but I have heard it offers powerful security layers with options for network protection, encryption, and server blocking.
I strongly recommend Oracle WebLogic Server as an enterprise solution for applications. Its user-friendly platform, on-premises monitoring capabilities, high level of customization, and powerful scripting tool make it a robust choice for businesses.
Overall, I would rate Oracle WebLogic Server as an eight out of ten.
