Oracle WebLogic was originally developed by BEA Systems, a company which was acquired by Oracle in 2008.
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
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.
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.
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.
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
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.
WebLogic Partner Community
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.
Blog Twitter LinkedIn Mix Forum Wiki