Oracle Service Bus 11g Development Cookbook:

In this chapter, we present different recipes for making the daily work with the Oracle Service Bus (OSB) more efficient. The Eclipse OEPE has some good-to-know features, which supports the creation and changing/refactoring of the message flow of a proxy service as well as the refactoring of the project structure.

We will also show how to set up an OSB project so that the JCA adapters known from the Oracle SOA Suite can be efficiently used within the OSB.

Also in this chapter, we will cover how to debug a proxy service using the graphical debugger built into the Eclipse OEPE development environment and we will see how to reuse functionality through private proxy services.

Since Oracle Service Bus 11g, the JCA adapter's framework is available at runtime, but the definition of the adapters through the wizards is only available in JDeveloper and not in Eclipse OEPE. To be able to use the adapters, JDeveloper with the SOA Suite extension installed needs to be available.

This recipe will show the basis for how to use the JCA adapters together with an OSB project. The idea is to avoid having to copy metadata from one place to the other by nesting the JDeveloper project inside the OSB project. This approach will be used by all other recipes working with the JCA adapters, such as the File, DB and AQ adapter recipes.

So far we have used the drag-and-drop feature for adding nodes and actions to the message flow of a proxy service. However, there is also a more developer-friendly approach, where we don't have to know where in the palette a given item is and especially which items are allowed in a given context.

This recipe will just present a simple approach for doing refactoring of nodes and actions within a single message flow. It uses the drag-and-drop functionality of the Eclipse OEPE to move around the items on the graphical representation of the message flow.

This recipe will just present a simple approach for doing refactoring of nodes and actions. It uses the copy/paste functionality of the Eclipse OEPE to copy a node/action from one place to another.

This recipe will show how to refactor the structure of an OSB project inside Eclipse OEPE. Simply use the drag-and-drop functionality to move an artifact from one place to another and Eclipse OEPE will make sure that all internal links are updated accordingly.

We will use a simple OSB project with one proxy service calling another proxy service:

Both proxy services implement the same WSDL interface. We will show how the proxy services can be refactored so that the private proxy service is located in its own folder. In the second step, we will also move the WSDL file into another folder.

This recipe will show how to copy artifacts from one OSB project into another OSB project. This is useful for duplicating artifacts in order to reuse them.

We will use the same project as in the previous recipe, with one proxy service calling another proxy service.

We have already seen in the Testing the proxy service through the OSB console recipe that the OSB provides an Invocation Trace when executing an OSB service through the test console. The Invocation Trace is one possible solution for debugging if something is not working as expected. But its use is limited to the test console.

This recipe will show a more developer-friendly way for debugging. We will show how to use the visual debugger available with the Eclipse OEPE.