Oracle WebLogic Server vs. TIBCO ActiveMatrix Service Grid

I see Oracle WebLogic Application Server being appropriate when an application needs several different data sources and messaging providers configured and accessible, with a configured level of control of resources (connection pools) and timeouts. It is also advisable to create distributed resources that you can configure as always active to provide more processing power, or as failover for situations of availability in case of disaster recovery, for example. An application where the number of required resources configured is very small and almost non-changeable, and no scalability is required, some other options exist in the market with less cost.

Incentivized

It fits perfectly for SOA and EAI architecture with large numbers of services that required to be wired to each other, the binding virtualization is quite good to simply this part. For the simple scenario of orchestration and /or ESB architecture could be a better use traditional stack.

Incentivized

• I love that the weblogic dashboard allows you to manage applications and see the status of each application.
• Oracle WebLogic Application Server simplifies usage periods in the development and production of business applications.
• Oracle WebLogic Server allows me to define various aspects of data source entry, including creating a specific multiple connection to facilitate data entry.
• Performance and administration are highlighted in weblogic.

Incentivized

• reduce the number of http port required by services
• simplified the binding connection amongst services
• high scalability and fast deployment of applications

Incentivized

• The Admin UI should be further simplified, the UI design was not too user-friendly— too many options and clicks required, difficult for the new beginners to figure out what they are looking for.
• The admin server becomes the single failure point, although Oracle suggested some workarounds by setting VIP and VHost, it was not quite easy and straight forward.
• Domain replication is hard, requiring a lot of knowledge and scripts efforts.
• Admin will hang if the node manager communication encounters some issues for one or some nodes in the domain/cluster.
• Not able to kill/terminate the stuck thread, the only way is to restart the managed server (JVM)
• License cost is too high, for small businesses.

Incentivized

• health check of services and application features has been released with a lot of bugs that have never been fixed
• it is not so simple to apply the security policy to service/reference binding

Incentivized

Oracle WebLogic Server has so many features that sometimes it's hard to find the right place to setup things, I think the dated user interface does not help with that either. This has a direct impact when deciding to use it as your application server, you'd need to have the right people and invest the time needed to master it. If you're application justifies it then it will definitely be a great choice in the long run.

Incentivized

Oracle WebLogic Application Server is great at security, performance and features.

Incentivized

The Oracle support is not great sometimes. They take a long time and need a lot of data over and over to resolve issues.

Incentivized

I wasn't involved in selecting the server we were using but in our team we've made some efforts to improve the local deployment process by trying some other Applicational servers too. Apache Tomcat was a more lightweight solution for sure, and it coped well with our applications needs, configuration and performance wise. Despite that, since we didn't got clearance to change that into our local servers, we kept using Weblogic to guarantee compliance between the testing environments and production.

Incentivized

TIBCO service grid has been chosen as a natural selection of the TIBCO product evolution. The high flexibility and the binding virtualization fits very well with client needs for its EAI applications due to the huge number of services and applications, the management of application dependencies during deployment, the advantage of perfect integration with EMS for logging

Incentivized

• It made it easy to handle over a 100 of deployments across multiple nodes every quarter.
• It was easy to scale up our application to 36 nodes as the volume of transactions increased over the years.
• Helped us achieve 99.999 availability for our users.

Incentivized

• The integration of old BW with BWSE and its interface quite similar to design time has reduced the cost of training for developers
• The TIBCO support for this product is no the best and clients complains too much about this. This required to find a workaround or force the client to move to new/or different product. Huge impact on ROI

Incentivized