Overall Satisfaction with Oracle WebLogic Application Server
We use Oracle Weblogic Application Server to host JAVA/J2EE applications, both web and enterprise at US Cellular. It is used by various teams within the information services department. We use Weblogic to host web applications related to Interactive Voice Response (IVR), sending SMS notifications to US Cellular customers, and managing the campaign material of our marketing department.
- WebLogic Server can be best utilized for mid-large sized applications - applications with medium to large volumes of customers.
- Use of work managers - to create specific work management logic for different applications.
- Ability to use single data source vs. multi data source gives us failover possibility.
- Thread management can improve... If we can review the thread performance more clearly on the WebLogic admin console, that would be helpful.
- Store and Forward functionality in JMS - for managing messages SAF (Store and Forward) mechanism isn't working as efficiently as it could. Improvement would help.
- Ability to control node manager from the WebLogic admin console would be helpful.
- Provides a stable environment and JVM crashes are very low.
- JMS message processing is good, so it is best utilized for the SMS & email notifications sent to our customers.
- License costs seem slightly on the higher end for the business functionality we are using. It would be good if the licensing costs are lower.
- JBoss and Apache Tomcat
JBoss and Apache Tomcat application servers are open source and cost less, however I do not find them as sophisticated enough to handle the various critical functionality used at US Cellular corporation. WebLogic stands way ahead in the way it provides opportunities for performance tuning, be it datasource/connection pool tweaking or threads/work manager tuning, etc.