Showing posts with label OSB 12C. Show all posts
Showing posts with label OSB 12C. Show all posts

Saturday, September 24, 2016

OSB 12C - XQuery- Error executing the transformation: {http://www.w3.org/2005/xqt-errors}FODC0002: Error retrieving resource "file://.xml"


After migrating from 11g to 12C , XQuery function  fn:doc started failing in one of the OSB project when trying to refer a static XML. After some research found out that it's happening only with XQuery version 1.0 not with 2004.

fn:doc("file://<filename>.xml")

Error Message:

Error executing the transformation: {http://www.w3.org/2005/xqt-errors}FODC0002: Error retrieving resource "file://<filename>.xml"

Solution:


Xquery implementation has been changed in 12C. So, to resolve this issue, give full path for the file

e.g.

fn:doc("file:///soa11g/soa1213/user_projects/domains/osb_domain/filename.xml") 


OSB 12C - REST exposed pipeline - XML-24500: (Error) Can not build schema

When trying use WADL file from other OSB project and using in the pipeline which is exposed as REST, i got following errors

XML-24500: (Error) Can not build schema

It's happening only when yuou are using WADL file from other OSB project. There is no problem if you are using local WADL file.

In the schema files the xml header had encoding as:

<?xml version="1.0" encoding="utf-16"?>

This header prevented the WADL from loading the resource schema.

Solution:


To make it work, just remove the encoding from the header and it will resolve this issue.

from:
<?xml version="1.0" encoding="utf-16"?>

to:
<?xml version="1.0"?>

OSB 12C - WSDL import from MDS does not import cascading XSDs


When i was creating proxy services from WSDL by importing it from MDS which just have one XSD, it was working perfectly fine but when WSDL  has cascading XDSs  then its faling to create proxy service.

After some investigation, i found out that it was known issue and can be fixed by a oracle patch.

Solution:

  1. Download  Patch 19637023 from oracle support
  2. Follow the instruction in README file.
  3. Take back up of your system.
  4. Apply the patch.
  5. Try to create proxy service by importing WSDL with cascading XSDs from the MDS.
 After applying this patch, this issue was resolved.


Friday, September 23, 2016

OSB 12C - Unable to deploy service using File Transport


When i was trying to deploying a OSB project  with business service having File Transport from JDeveloper to OSB cluster, deployment failed due this error

Service Bus Deployment Error
No transport provider registered with ID: file


After going through Oracle documentation, i found out that File Transport was only  targeted to  my OSB cluster. It should targeted to both the Admin and OSB cluster.

 Solution:


Follow these steps:

 - Login into WLS Admin console and edit a session

- Go to Deployments

- Select File Transport application "Service Bus File Transport Provider"

- Open "targets"

- Select change target option and add target to both "Admin & OSB Cluster" for OSB Cluster domain. For single server domain (just admin server), target will be just "AdminServer"

- Save and active changes.

Tuesday, September 20, 2016

OSB 12C - Not able to login to SB console - Error 401--Unauthorized


When I was trying to login into OSB console http://localhost:7001/servicebus/, I  got Error 401--Unauthorized error on the browser. It was happening on OSB 12.1.3.0.0 version.

ADFC-0619: Authorization check failed: User 'weblogic' does not have 'VIEW' permission on 'jsf.resourcesPageDef'.[[
oracle.adf.controller.security.AuthorizationException: ADFC-0619: Authorization check failed: User 'weblogic' does not have 'VIEW' permission on 'jsf.resourcesPageDef'.


Reason:

After some investigation and following oracle documentation , i found out that i was using JDK 1.8 which was not certified with Oracle SOA Suite 12C 12.1.3.

Solution:

Download  and install  JDK 1.7 from  oracle site and reconfigure the weblogic start and managed scripts within and <wls_domainHome/bin> to update the JAVA_HOME parameter to your new JDK 1.7 install.

Restart the admin and managed servers. Now you wouldn't see that issue again.


OSB 12C : The conversion of MFL to XSD fails in an OSB 12c project



When using the Native Format Builder wizard in JDeveloper for an OSB project, the conversion from MFL to XSD fails with the error 'Root element must be provided.'.





Solution

Please use a SOA project for the conversion from MFL to XSD instead of an OSB project.

The feature is for SOA and is not for OSB in current JDeveloper. The feature for OSB has been requested as an enhancement.

Wednesday, September 14, 2016

OSB 12C :WSM-06404 error in a WS-AT web service call on OSB 12c

When executing a WS-AT web service operation the following error is thrown:

<WSM-06404> <The resource pattern "ResourcePattern [absolutePortableExpression=/WLS/osbdomain/|#MODULE|WS-Client({http://schemas.xmlsoap.org/ws/2004/10/wsat}WSAT10Service#ParticipantPortTypePort,wls)]" does not uniquely identify the subject.>

It was caused due to transaction is being left open even after the message was consumed.

Solution:

Use @TransactionManagement(value=TransactionManagementType.CONTAINER) instead of @TransactionManagement(value=TransactionManagementType.BEAN) in the web service.