Posts tagged administration
In recent months, I have had a lot of dealings with middleware administrators, responsible for the management of WebLogic Server and other Fusion Middleware components such as SOA Suite, Oracle Service Bus, WebCenter and UCM. My role is frequently one that allows me to step back a little and observe. These observations made it very clear that not only is middleware administration a challenging task – one that is underestimated in many organizations – it is also one that is frequently made much harder than necessary by actions that developers take or do not take. Developers create the artifacts that administrators will deploy and manage on the middleware infrastructure. These developers can make life easier for the administrators if they adhere to certain best practices in creating and handing over these artifacts. However, out of ignorance, disinterest or lack of time it is unfortunately common for administrators to experience severe frustrations over the work of developers.
I am trying to compile a list of various points of frustration for middleware administrators caused by developer ignorance or carelessness. Below is the list if have compiled so far – with some help from More >
One of the perhaps somewhat counterintuitive challenges with at least the initial stages of adopting Fusion Middleware is the fact that there is too little work in terms of administration.
On the one hand, Fusion Middleware administration entails quite a bit, starting with WebLogic Server
and typically extending to one or more FMW components:
all of which the administrator – or rather the administration team – needs to deal to with. Typically even around the clock to ensure the availability required by the business.
On the other hand, the actual workload for FMW administration for a small number of applications, services and processes does not justify a dedicated resource. This proves a serious problem for many organizations: 24/7 availability requires 3 FTE while the effort is on average less 0.5 FTE.
Organizations can adopt several strategies to address this challenge, as is illustrated in the next picture.
Where as in WebLogic 11g JPA was not support by default, in WebLogic 12c it is the default persistency provider.JPA 2.0 is part of JAVA EE 6.
I was trying some new JAVA EE 6 features in WebLogic 12c, so here is a is a way to create a Web Application with JPA under WebLogic 12c
Some of the JAVA EE 6 specifications weâ€™re already supported in WebLogic 11g. JPA 2.0 was one of them. Though version 1.0 was the default. 2.0 also worked.Unless an explicit <provider>…</provider> wass specified in the persistence.xml file of a deployed application, WebLogic 11g used OpenJPA/Kodo by default.
The default JPA provider setting is exposed via a new MBean: JPAMBean on the DomainMBean, and persists the configuration into the config.xml file.
Furthermore, you needed to install the patch QWG8 – Enable JPA 2.0 support on WebLogic Server.
To make it work on 11g, you had to use Oracle TopLink as the persistency provider like the image shows youÂ in the WebLogic Admin Console
Now for 12c this is not needed anymore, TopLink will be the default JPA Provider
Sometimes, you would like to have an extract from a SOA Suite 11g Â production environment to test it in a test or acceptance environment.
There are several ways to do this, but in this post I’d like to discuss about how to get a clone of your SOA Suite 11g, from one WebLogic Server host to another.
To extract a clone, you will have to determine which components should be cloned:
- The SOA repository schema’s, like MDS, SOA-INFRA and so on.
- The WebLogic and FMW software
- The SOA Suite Domain Configuration including all SCA components and other deployments.