Oracle Blog

Tuesday Apr 08, 2014

Thanks to all the partners for the excellent contribution and
on-going business! You are the key for the joint Fusion Middleware
success. Due to all the excellent work and contributions, Every Year it
becomes harder to choose the winners.

The
awarded partners have proven cutting edge projects with the latest
Oracle technology and most important their contribution to the community
like blogs, newsletters, conferences, papers, twitter, linkedin and
their participation in the partner advisory councils.

The Oracle internal award also acknowledges the special contribution to the community. Ritu Chhibber
publishes since years every month the newsletter you read. Ritu, as you
could not come to Malta to receive it in person, when you read these
lines THANKS for your great work!

Monday Mar 17, 2014

Oracle WebLogic was originally developed by BEA Systems, a company which was acquired by Oracle in 2008.

Since
WebLogic had a much larger user base, Oracle quickly made their
intentions to deprecate their own Oracle Application Server (OAS,
sometimes referred to as OC4J, the J2EE container component) in favour
of WebLogic as their primary offering.

C2B2 have worked with
WebLogic since it was owned by BEA and have partnered with both BEA and
Oracle. As partners, C2B2 have worked on a wide variety of customer
engagements across Oracle’s full middleware portfolio.

Migration from OAS to WebLogic

Oracle
Application Server has been deprecated for a number of years now, since
Oracle have pushed forward with their plans to offer only WebLogic as
their application server of choice. Even so, many businesses are still
using OAS or OC4J to run their Java EE applications and are increasingly
finding that they need to migrate to WebLogic to avoid being left with
legacy infrastructure that they can no longer support effectively.

Fortunately,
Oracle has anticipated the need for the process of migration to be as
seamless as possible so, for their part, they have put a lot of effort
into helping customers migrate their infrastructure. Unfortunately,
however much work Oracle might do to help with this migration, there
will always be problems or unforeseen circumstances due to the
dependencies that applications might have on OC4J which change when
moving to WebLogic.

Non-standard technology

A
great advantage of buying from a company like Oracle is the ecosystem
that you get along with the product. WebLogic, for example, has many
other components built by Oracle to improve on the standard Java EE way
of doing things. Problems can occur purely down to the vast amount of
products and services that Oracle offer. Should you use WebLogic’s JMS
implementation, Oracle’s Advanced Queuing (AQ) or Oracle
Store-And-Forward for your messaging scenario? How do they differ? Is
one better than another, or just better suited to certain applications?
It’s clear to see that, although you can be sure that Oracle has a
product or component to suit your scenario, it’s a significant task to
review even the portfolio of components that come with WebLogic, let
alone WebLogic compatible software from Oracle.

Performance Tuning

With
considerations like migration and such a range of technologies to use,
how can you be sure you’re getting the best performance out of your
infrastructure? Consider the scenario – you have a suite of
applications, migrated from OC4J which used to use AQ for messaging but
now bridge endpoints with Oracle SAF. Are the defaults for the
connection pools associated with your data sources optimal for
persistent messaging?

It’s very common for users who are not
familiar with performance concepts to get completely lost when trying to
tune every aspect of their application and server. Should you buy more
hardware? Do you need to? Performance issues can get very expensive,
whether in terms of buying additional hardware, man-hours to maintain
responsiveness or just in terms of your reputation to customers so it
should never be an afterthought. Read the complete article here.

Wednesday Jan 08, 2014

With the release of W ebLogic 12.1.2
websocket support has come to WebLogic. In this blog post we'll show
you how to write a simple websockets echo example just to get you
started. Unfortunately the api released with WebLogic is not the JEE7 JSR356 api, which I suspect will come when WebLogic gets JEE7 compliance. On the plus side it's a pretty simple api. In this blog I'm using NetBeans 7.4 and I've started off by creating a basic web project and I've called it Echo. . Read the complete article here.

With the release of W ebLogic 12.1.2
websocket support has come to WebLogic. In this blog post we'll show
you how to write a simple websockets echo example just to get you
started. Unfortunately the api released with WebLogic is not the JEE7 JSR356 api, which I suspect will come when WebLogic gets JEE7 compliance. On the plus side it's a pretty simple api. In this blog I'm using NetBeans 7.4 and I've started off by creating a basic web project and I've called it Echo. . Read the complete article here.