Skip to content
July 17, 2014 / Daniel Dias

SOA 12c End-to-end (e2e) Tutorial: Error deploying ValidatePayment

SOA 12c End-to-end (e2e) Tutorial:

https://java.net/projects/oraclesoasuite12c/pages/SOASuite12cEnd-to-endTutorial

During this tutorial you may have problems deploying the application ValidatePayment (Page 74 of the tutorial). This error occurs when your Oracle Service Bus and Oracle Business Process Manager are on the same domain.

ERROR:

WSDL Errors Can Occur When Oracle Service Bus and Oracle Business Process Manager Are on the Same Domain

Bug: 18856204
Added: 10-June-2014
Platform: All

If Oracle Service Bus is installed on the same domain as Oracle Business Process Manager (BPM), the following error can occur when creating a WSDL file:

The WSDL is not semantically valid: Failed to read wsdl file from url due to — java.net.MalformedURLException: Unknown protocol: servicebus.

WORKAROUND:

 1. Log in to the WLS Administration Console

2. On the navigation tree on the left, expand services and click OSGI Frameworks

Step02

3. Click on the bac-svnserver-osgi-framework link

Step03

4. Click lock and edit

Step04

5. In the init properties text field at the bottom add felix.service.urlhandlers=false

Step05

6. Click Save and activate the changes

7. Restart Weblogic Server 


 Updated: 2014/08/14

Carol Thom from Oracle informed us that this solution might cause issues with BPM.

Other solution to this problem is to remove the OSGi Framework from the AdminServer.

To do this replace the step 5. with the following instructions.

5. On the Targets tab, clear the AdminServer check box.

Step05-1

Thanks to Carol Thom for sharing this information with us, and Da Dinh who gave her the information.

Advertisements

6 Comments

Leave a Comment
  1. https://www.java.net/blogs/bleonard / Jul 23 2014 5:02 pm

    Wow, how’d you figure this out? Good stuff. Thanks!

  2. Senthil Kumar / Jul 24 2014 3:13 am

    Bravo! I did not expect a blog post addressing this issue in SOA 12c so soon!!

  3. Nikolay Smirnov / Jul 25 2014 2:58 pm

    Thanks a lot!!! Indeed, how’d you figure this out?

  4. Martin Chmelar / Jul 31 2014 2:31 pm

    Thank you so much, it works!!

  5. Prabodh Mitra / Aug 12 2014 6:49 pm

    thanks it worked!

  6. Carol Thom / Aug 13 2014 8:10 pm

    The above workaround fixes the WSDL issue, but might cause issues with BPM. Here’s another workaround to try if you are using both:
    1. In the WebLogic Server Administration Console, select Servers and then select OSBI Frameworks.
    2. Select bac-svnserver-osgi-framework.
    3. On the Targets tab, clear the AdminServer check box.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: