Oracle Service Bus (OSB) for the Busy IT Profesional

Audience

Oracle Service Bus is one of these software products that haven’t changed much in their core since many years. These days I tend to see more and more OSB projects and one reason certainly is that license wise OSB is included with Oracle SOA Suite.

Compared to SOA Suite, OSB is conceptually different though. Even with a good understanding of SOA Suite (which I will cover in one of the following posts), there will be a slightly steep, but rather short learning curve for OSB.

The following recipes tries to motivate and explain the usage of OSB without the usual marketing hype. Make sure to read the previous posting about getting started with SOA in general and Oracle Fusion Middleware.

Technology

OSB is virtualizing service calls from clients to the service implementation. By using so called proxy and business services (both are components within OSB) incoming and outgoing requests can be arbitrarily connected and protocols can be converted. Proxy services contain the processing logic (validation, enrichment, transformation etc.).

Oracle Service Bus OSB Architecture

Download

If you are trying to get started with OSB, here is the link to download Oracle Service Bus Overview and Getting Started (PDF).

Enjoy!

PS. Actually this recipe is taken out of my book Oracle WebLogic Server 12c – Distinctive Recipes.

DOAG 2012 Konferenz: WebLogic and Cloud Talk

WebLogic Talk

I will hack a WebLogic password live at DOAG 2012 conference ;)
… and explain 9 more things you should know about WLS12c. Mostly stuff out of my WebLogic Advanced Recipe book.

There will also be some chocolate and a book to win!

My WebLogic 12c talk on Tuesday.

Cloud Talk

Don’t miss my cloud talk! I will demonstrate live a couple of things you won’t be able to with the Oracle cloud ;)  Public Cloud talk on Wednesday. More chocolate and of course another book to win!

WebLogic 12c JMX DevCast

I was doing a DevCast on behalf of the Oracle WebLogic team.

Learn about the WebLogic 12c JMX ecosystem: JMX clients, WebLogic scripting tool, JConsole, Jolikia JMX shell with syntax highlighting and tab completion, developing MBeans for your own applications with Spring and Java EE 6.

The slides can be accessed from here as PDF. They are just supporting the presentation, so I recommend to grab a coffee and watch it instead.

It’s a free DevCast, sign up by clicking on the image below.

Enjoy ;) You’ll find many more recipes in my WebLogic 12c book.

Simple Custom JMX MBeans with WebLogic 12c and Spring

Using the Spring framework bundled with WebLogic 12 the programming of JMX MBeans becomes as easy as writing a simple POJO within a web application. After coding the MBean as a POJO all that is left to do is creating the Spring configuration file and editing the web.xml deployment decriptor:

- Firstly you have to add the Spring <listener> to the web.xml deployment descriptor with the web.xml to get Spring started.

- Secondly create the applicationContext.xml for Spring in the WEB-INF subdirectory. Declare the Spring bean and let Spring export it to the platform MBean server.

- Thirdly deploy the web application and test it with JConsole, WLST or j4psh.

For your convinience I already built an example. You can download the deployable SimpleJMX.war file or the complete NetBeans project.

You can see the application in action, including the involved files and the deployment in the following screencast:

How to access custom MBeans from WLST is shown in the second part:

The third part is showing how to retrieve MBean attributes from a JSP:

EJB 3.1: Stateless Session Bean Deployed as .war, Dependency Injection, Asynchronous Methods

Development of an EJB 3.1 stateless session bean has become incredibly simple. You add an annotation, there is no XML required at all, no need to implement an interface anymore, and you can easily implement asynchronous methods that decouple your client calls from the method execution. Then, at the end you deploy the EJB as a simple .war file – no need to warp it in an .ear file.

 

The following screencasts explain you how to do it. You can also download the whole NetBeans project  or just a deployable .war file exactly the sources created in the screencasts.

 

Simple Stateless Session Bean with asynchronous method, developed with NetBeans 7.1 and deployed as .war file:

Asynchronous Methods with Stateless Session Bean:

Inject Stateless Session Bean into Servlet:

 

Here is a tough question at the end:

Imagine you have to add a WebLogic specific settings for your stateless session bean. There is no annotation for that. These settings have to be put in the deployment descriptor which typically used to be the weblogic-ejb-jar.xml file within an .ear file. But what if you have already build a .war file which is perfectly possible now (and neither an .ear nor an ejb.jar file).

Where do you put these settings then? Post your answer here.

Web Service Development with NetBeans and Testing with WebLogic Admin Console

Developing of SOAP based web services for WebLogic 12c (or any other application server) with NetBeans is a breeze. You can do it without using any templates or IDE wizards, no XML is required, no modification of deployment descriptors.

The following screencast shows how to develop the most simple web service pobbislbe, how to test it entirely with WebLogic admin console, and how modifying the web service will work without redeployment.

WebLogic 12c Configuration Management: Change Your Defaults to Track What Happens

Good morning. I just finished the chapter about configuration management for my new WebLogic book. Here is a very short summary of it.

There is a number of default configuration settings that I recommend to change to better keep track of configuration changes. The screencast showing you hands-on how to do this is still rendering and will be available once you are reading this (you can subscribe to all of them here).

After creating a WebLogic domain, consider the following:

 

1.) User personalized administration users.

2.) Audit WebLogic configuration changes (including usernames) so you will know who changed what.

3.) Enable the configuration archiving so you will be able to revert to a previous set of configuration files.

 

None of these settings are enabled per default. All of this you should think about for your environment.

Here is the three-part screencast how to enable it (switch to HD quality and full screen).