Suppressing the Selection Failure exception in Assign activity – Oracle SOA

In BPEL Assign activity if the xpath returns empty result then SelectionFailure RuntimeFault will be thrown by the engine. But some cases we may need to suppress the selectionFailure error while assigning the optional elements. In my case I have a assign activity that will mapthe elements  input and input1 from inputVariable to result and result1 of outputVariable. The input2 is optional and somecases input2 element  will not be available in the request payload. <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sup="http://xmlns.oracle.com/Application1/SuppressSelectionFailure/SuppressSelectionFailure">    <soapenv:Header/>    <soapenv:Body>       <sup:process>          <sup:input>?</sup:input>       </sup:process>    </soapenv:Body> </soapenv:Envelope> While invoking the service I am getting the selectionFailure exception as shown below. <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">    <env:Header/>    <env:Body>       <env:Fault>          <faultcode>env:Server</faultcode>          <faultstring>faultName: {{http://schemas.xmlsoap.org/ws/2003/03/business-process/}selectionFailure} messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}</faultstring>          <faultactor/>          <detail>             <exception/>          </detail>       </env:Fault>    </env:Body> </env:Envelope> I want to suppress the selectionFailure exception because input2 is a optional element . The ignoreMissingFromData attribute will help us to suppress the selectionFailure if the target is missing in the copy operation. <copy bpelx:ignoreMissingFromData="yes|no"/> Now even though the input1 element is missing in the request the assign activity will not throw the selectionFailure exception instead the empty tag will get assigned to the outputVariable. The bpelx:insertMissingToData attribute will help us to suppress the selectionFailure if the target is missing in the copy operation. <copy bpelx:insertMissingToData="yes|no"/> If the xpath in the copy operations returns empty node for the target then we will be getting exception "The assign activity of the to node query is returning zero node" Configure the attribute bpelx:insertMissingToData will help us to suppress this error.  <copy bpelx:insertMissingToData="yes">         <from variable="inputVariable" part="payload"               query="/client:process/client:input1"/>         <to variable="outputVariable" part="payload"             query="/client:processResponse/client:result1"/>       </copy> The runtime will crate the to-spec element if it is missing and assign the source value(used Remove operation to remove the result1 element from outputVariable for testing). The attributes insertMissingToData and ignoreMissingFromData can be added by righ clicking the copy rules.

Invocation of https/SSL service is not working from OSB

We were trying to install the wildcard certificate to enable the communication from OSB to end system, but the following exception was displayed in the log file and also the communication to the end system is failing even though the certificate installation was successful; <Jan 23, 2015 10:45:05 PM PST> <Notice> <Security> <localhost> <AdminServer> <[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <bac54c313ca42523:46f5522b:14b61066510:-7ffd-000000000008b798> <1423456801909> <BEA-090898> <Ignoring the trusted CA certificate "CN=*.sample.com,O=Sample,L=Sample,ST=Sample,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>  After analysis, we found that JSSE flag should be enabled along with Custom Host Name Verification (weblogic.security.utils.SSLWLSWildcardHostnameVerifier) to support wildcard certificate.  After enabling the JSSE flag, none of the https communication from OSB is working but https communication from BPEL is working fine even with the wildcard certificate(BPEL and OSB is running in the same server). The following exception is thrown while invoking the https service from OSB. <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <soapenv:Fault> <faultcode>soapenv:Server</faultcode> <faultstring> BEA-380000: General runtime error: java.lang.NullPointerException </faultstring> <detail> <con:fault xmlns:con="http://www.bea.com/wli/sb/context"> <con:errorCode>BEA-380000</con:errorCode> <con:reason> General runtime error: java.lang.NullPointerException </con:reason> <con:location> <con:node>RouteToSFDC_SearchService_BS</con:node> <con:path>request-pipeline</con:path> </con:location> </con:fault> </detail> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope> This is the internal OSB server issue; the cause of the issue is that the AsyncResponseHandler does not properly register JSSEFilter for JSSE SSL. The Weblogic patch 11866509 based on the Weblogic server version (this issues is identified in Weblogic server version 10.3.4 and 10.3.5) should be installed to resolve the issue.

How to enable SSL debug tracing in Weblogic Server?

Add the following start up options to the start up file startWebLogic.cmd/startWebLogic.sh or startManagedWebLogic.cmd/startManagedWebLogic.sh based on which file is used to start the server. JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.debug.DebugSecuritySSL=tue -Dweblogic.debug.DebugSSL=true -Dweblogic.StdoutDebugEnabled=true -Dweblogic.log.StdoutSeverityLevel=Debug -Dweblogic.log.LogSeverity=Debug"