Service Bus 12c QuickTip: Fix HTTP 403 on calling SOAP/REST Proxy Services by Sven Bernhardt

A few days ago, I faced a strange behaviour when I tried to test SOAP and REST services deployed to a fresh SOA Suite 12c (12.2.1.1) installation. Using SOAP UI for testing the services always gave me an response in a HTML format, which says ” Error 403 Forbidden”, like it is displayed in the screenshot below:

Going through all log files of the corresponding Managed Server, where Servicebus was installed to, I didn’t find any hint that even the request was delivered to the servers. The requests simply had no footprint in the access.log or the server’s diagnostics.log – which seemed to be very strange to me. Assuming that the behaviour might have been something to do with the security policies applied to the services, I disabled all security policies as a next step – without any success.

After testing the services successfully in another environment, it was quite clear to me that something was wrong with the domain setup and after some investigations, I found the root cause for the “Error 403 Forbidden” message: Using the deployments view in Weblogic Console, I noticed that “API Manager Starter Application” was targeted to the Servicebus Cluster. Like described in MOS Note 2087277.1, I un-targeted this application from the Cluster, restarted the corresponding Managed Servers and afterwards, I was able to test the services without receiving the mentioned exception. Like the MOS note described this behaviour might happen, if the wrong Template (Oracle API Manager Template) is chosen for Servicebus, when setting up a domain. Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Facebook Wiki

Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress

Building OSB 12c releases on resource level using Maven by Mike Heeren

A while ago I published a Whitebook (in Dutch) about building OSB 12c releases on resource level using Maven. In the Whitebook, you could read which functionality we were missing in the regular Oracle Service Bus plugin for Maven and how we were able to create this functionality using a custom Maven plugin.

I have added the code of this custom Maven plugin to the following public repository: https://bitbucket.org/whitehorsesbv/servicebusplugin

Used settings

The custom Maven plugin has been developed and tested on multiple environments, so we can confirm that the Maven plugin is working if you are using the following version(s):

Installing the custom Maven plugin

First start to install the custom Maven plugin to your local Maven repository. To do this, you can download both the JAR and the POM file from the download page of the repository. After you have downloaded both files, you can execute the following commands to install it to you local Maven repository: Please read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Facebook Wiki

Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress

Complex Composites Simplified by Dan Reynebeau

How many times have you developed a new composite, or migrated an older composite, that simply turned into an overly complex process?  Modifying and debugging the new process can become more difficult and take longer to implement.

A good java implementation breaks the problem into manageable classes that can be easily understood and managed over the life of the implementation.  Since this works well with java, why not apply the basic principle to a composite.  In comes SOA 12C and the implementation of subprocesses, which can be utilized for breaking down a composite into manageable components.

Breaking down a complex composite provides several benefits:

• Easy modification – smaller processes that focus on particular functionality are much easier to visualize and understand
• Reducing duplication – smaller processes provide the ability to be re-used within the composite
• Localized error handling – smaller processes allow specific error handling requirements to be handled and thrown to calling process

Now I will show a simplistic example of a composite that performs database syncing.  The composite will attempt to sync table 1 and if any number of records are sync’d, then we want to sync table 2.  I will not go into the details of how to create a subprocess since there are many tutorials already available.

My general approach is to simplify the main process so the flow is easier to follow.  This concept can be extended to the subprocess layer in a similar fashion as the BPEL layer, if the subprocess layer becomes too complex. Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Facebook Wiki

Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress