Oracle SOA 12C - com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.1 Client was not authenticated

When i was trying to send an email from Oracle SOA 12C, i was getting following error


com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.1 Client was not authenticated

 After some research and oracle documentation's help, I found out that my SOA server was not approved in the SMTP server whitelist.

Solution:

 

Added the SOA servers to the SMTP server whitelist and send email started working.

Oracle SOA 12C - Not able to search instances with Instance ID

After migrating from 11g to 12C, when i was trying search process instances using instance id then i found out that  this option is no longer availble in EM console.

As per Oracle this option will be available in future release.

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.

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.

Oracle JDeveloper 12C- Error in Integrated Weblogic 12C in SOA Suite - Not find or load main class

When i was trying to run SOA project first time in Jdeveloper Integrated Weblogic server , i got following error

Could Not find or load main class
Stopping Derby Server
Derby Server Stopped

Reason: 

 It was happening due to there was space in my user name

i.e.

 C:\Users\FirstName LastName\AppData\Roaming\JDeveloper\system12.2.1.0.42.151011.0031\DefaultDomain

 Solution:

 I have replaced my <firstName lastName> with <firstName~1> in all the *.cmd files under the  /DefaultDomain/bin folder. You can find Weblogic default domain at following path

 C:\Users\<username>\AppData\Roaming\JDeveloper\system12.2.1.0.42.151011.0031\DefaultDomain

 After that i was able to run the integrated weblogic server.