How to return a Soap Fault from a business process

I'm trying to re-implement an existing web service in WLI that can return soap
faults to clients when business errors occur while processing a request. Is this
possible to do with WLI, and if so can someone please point me in the right direction?
thanks...

If your JWS can throw a SOAPFaultException, that should return a SOAP fault to
the client.
"Michael Hanes" <[email protected]> wrote:
>
I'm trying to re-implement an existing web service in WLI that can return
soap
faults to clients when business errors occur while processing a request.
Is this
possible to do with WLI, and if so can someone please point me in the
right direction?
thanks...

Similar Messages

How to propogate SOAP fault from JPD to JWS

Hello,
I am new to weblogic and i am facing a problem with propogation of SOAP Fault from JPD to Process Control to JWS.
I need to throw a custom SOAP Fault from JPD to the client of the JWS which wraps this JPD.
Currently when i set and throw the soap fault from JPD it goes to the Process Control but the Process Control in turn throws a ProcessControlException to the JWS. Does any one know how can i retrieve the original SOAP Fault in the JWS?
Thanks

Hello man.....
You cannot get the the original SoapFault by usually try/catch operation, but there is a trick to do that....
When you use your service control do that:
try{
yourServiceControl.yourMethodThatThrowsException();
}catch(ServiceControlException e){
//With this "e" variable you can retrieve the exception
//looking for the the methods in it
//e.getXXXX
//you will find what you need
I hope it helps you
Sincerely
messenger:[email protected]
e-mail:[email protected]

How to return SOAP Fault from MII?

Hello, there!
I'd like an MII 12 transaction to return a SOAP Fault response when it fails for some reason.
The closest thing I found to this is to terminate the transaction (using the "Terminate Transaction" action) with error.
But this will cause MII to return an HTML page containing the error message, which is not satisfactory at all. It even causes the client to fail, since it is expecting a SOAP response.
Does anyone have any clue about this?
Thanks in advance!

The client will get a 500 error, with the error data available in the HTML content. Using the 500 error as the notification that something went wrong is probably the easiest way at present.
You could also create a "simulated" SOAP call using the Runner servlet and HTTP post, along with input and output XML documents that use a SOAP envelope/structure. You could then add a SOAP fault to the returned XML from within your transaction logic. It's not easy, but it can be done. The transaction itself is easy, but creating the WSDL is a bit more work, since you need to override the SOAP URL in the WSDL to point to Runner instead of SOAPRunner, and to include the InputParameter parameter in the URL to tell MII to map the "posted" XML (SOAP Input message) to a specific transaction input parameter.

Apex_web_service.make_request throws ORA-29273: HTTP request failed. How to get the soap fault XML?

I am trying to call a web service using apex_web_service.make_request function.
It works fine when all the parameters are correct. However, when something is wrong in the request XML, it throws an exception instead of returning the soap:fault message:
ORA-29273: HTTP request failed
ORA-06512: at "SYS.UTL_HTTP", line 1369
ORA-29269: HTTP server error 500 - Internal Server Error
ORA-06512: at "APEX_040200.WWV_FLOW_WEBSERVICES_API", line 130
ORA-06512: at line 37
I need to get back the soap:fault and parse it to display a proper error message to the users (e.g. what was wrong with the input), yet the call throws an exception instead of returning it.
I am trying the exact same request from soapUI and it returns me the soap:fault below:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
   <soap:Body>
      <soap:Fault>
         <soap:Code>
            <soap:Value>soap:Receiver</soap:Value>
         </soap:Code>
         <soap:Reason>
            <soap:Text xml:lang="en">Fault occurred while processing.</soap:Text>
         </soap:Reason>
         <soap:Detail>
            <ns1:RegisterFault xmlns:ns1="http://www.exchangenetwork.net/wsdl/register/1">
               <description xmlns:ns2="http://www.exchangenetwork.net/wsdl/register/1">The security token has expired.</description>
               <errorCode xsi:type="ns2:RegisterErrorCode" xmlns:ns2="http://www.exchangenetwork.net/wsdl/register/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">E_TokenExpired</errorCode>
            </ns1:RegisterFault>
         </soap:Detail>
      </soap:Fault>
   </soap:Body>
</soap:Envelope>
How do I get this back from APEX?
Thanks!

Hi,
   I've just run into this.
   If the webservice returns a fault, such as:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>INVALID_REQUESTER_INFO</faultstring></soap:Fault></soap:Body></soap:Envelope>
   then the user gets presented with an unfriendly error message and there's no chance to output a more friendly one.
   The response above is seen when testing the webservice, when run from the Form/Report page, we get something like:
soap:ServerINVALID_REQUESTER_INFO
Contact your application administrator.
OK
   When OK button is clicked everything is rolled back and we don't even get the fault XML.
   It would be good if Apex could be optionally set to not give the unfriendly messages, so that we could code such a message ourselves.
   Unless anybody has a workaround for this, I guess that I'll have to see if I can code this in PLSQL.
Regards,
Chris

How to get the SOAP Fault XML?

Can anyone describe how we can get the full XML that is send
when the server returns a SOAP fault?
Thanks
Andrew

I think the problem is that faults return a 500, and that
makes flex quit looking. If you can make the server return say a
200, then you can get the actual exception. Search the archives on
flexcoders, this was discussed extensively there.
Tracy

Java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Client received SOAP Fault from server : Failure in SDOSerializer.deserialize

Hi All,
I am getting this exception while invoking one of our service from EM. Any pointers will be very helpful.
java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Client received SOAP Fault from server : Failure in SDOSerializer.deserialize. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:813) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:385) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:303) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.el.parser.AstValue.invoke(AstValue.java:187) at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:297) at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53) at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1491) at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:111) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:384) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:114) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:101) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:111) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:384) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:114) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:95) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:972) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:439) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:219) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:102) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:211) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:131) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:447) at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:447) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:181) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:183) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.core.model.targetauth.EMLangPrefFilter.doFilter(EMLangPrefFilter.java:158) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:542) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460) at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.security.wls.filter.SSOSessionSynchronizationFilter.doFilter(SSOSessionSynchronizationFilter.java:419) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3739) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3705) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2282) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2181) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1491) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Client received SOAP Fault from server : Failure in SDOSerializer.deserialize. at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:362) at oracle.sysman.emSDK.webservices.wsdlparser.OperationInfoImpl.invokeWithDispatch(OperationInfoImpl.java:1004) at

Hi,
its JDeveloper and ADF on this forum. For EM related questions, you should try the EM forum
Frank

Dynamic Invocation: Error The SOAP PA receives a SOAP Fault from SOAP serve

Hi All,
I am trying to run the sample code "Dynamic Invocation of Oracle9i Web Services using Oracle UDDI registry"
I was able to run the web services, publish them, and inquiry them using local UDDI registry.
However, while invoking any method provided by the web services using the inovk method I get the following error
oracle.j2ee.ws.client.WebServiceProxyException: Invocation failed 5,100: The SOAP PA receives a SOAP Fault from SOAP server
Can anybody help me please?
Regards,
S.Al Shamsi

It looks like the problem is occuring on the server side. I guess you have included the stacktrace from the client, can you get hold of the server side stacktrace?

How to return a ref cursor from this dbms_sql?

Hi,
Can anyone show me how to return a ref cursor from this dbms_sql based procedure? I see 11g has a dbms_sql.to_refcursor(cursor_handle). How can this be done is 10g?
Thx.
CREATE OR REPLACE PROCEDURE Sample_Get_t
p_sample_id sample.sample_id%TYPE,
p_contract_id sample.contr_id%TYPE
IS
cursor_handle INT;
sql_stmnt varchar2(500);
rows_processed NUMBER;
BEGIN
sql_stmnt :=
'SELECT
sample_id,
contr_id,
rcpt_id
FROM
sample s
WHERE
s.contr_id = :1
and s.sample_id = :2
ORDER BY
sample_id';
cursor_handle := dbms_sql.open_cursor;
dbms_sql.parse(cursor_handle, sql_stmnt, dbms_sql.native);
dbms_sql.bind_variable(cursor_handle, ':1', p_contract_id);
dbms_sql.bind_variable(cursor_handle, ':2', p_sample_id);
rows_processed := dbms_sql.execute(cursor_handle);
dbms_sql.close_cursor(cursor_handle);
END Sample_Get_t;

In 10 this cannot be done with dbms_sql (to my knowledge). There are a couple of other options.
1) open the ref cursor for the dynamic statement using bind variables (or SYS_CONTEXT variables, which i prefer since they are much easier to deal with when you are dynamically adding predicates).
declare
   wRefCursor SYS_REFCURSOR;
begin
   open wRefCursor for 'select * from all_objects where owner = :Logged_in_user' using user;
end;
/or using the context (the context will bind for you)
declare
   wRefCursor SYS_REFCURSOR;
begin
   open wRefCursor for 'select * from all_objects where owner = SYS_CONTEXT(''CONTEXT_NAME'', ''VARIABLE_NAME'') ';
end;
/Be aware that contexts ALWAYS return varchar values, so if you are comparing to a number you should wrap it in TO_NUMBER, a date, TO_DATE and so on....
2) change the DBMS_SQL to do an insert into a global temporary table and return the ref cursor which select's * from GTT;
3) upgrade to Oracle 11 :)

Trying to throw fault from one BPEL process to another

We are trying to throw a fault from one BPEL process to another and apparently are experiencing a common problem. That is, the invoking process times out and never receives the fault.
Likely a beginner's mistake is at fault (pun intended).
Below are samples of a simple "Hello World" process that tries to throw the fault.
snippet of pbel file....
<process name="HelloJavaWorldSynchronous"
targetNamespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:ns1="http://helloworldjavaproject/"
xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:client="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">
<faultHandlers>
<catchAll>
<sequence name="Sequence_1">
<assign name="Assign_3">
<copy>
<from expression="12345"/>
<to variable="FaultVar" part="code"/>
</copy>
<copy>
<from expression="'Hello fault summary'"/>
<to variable="FaultVar" part="summary"/>
</copy>
<copy>
<from expression="'Hello test detail'"/>
<to variable="FaultVar" part="detail"/>
</copy>
</assign>
<throw name="Throw_2" faultName="client:myFault"
faultVariable="FaultVar"/>
</sequence>
HelloJavaWorldSynchronous.wsdl file
<definitions
name="HelloJavaWorldSynchronous"
targetNamespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:ns1="http://schemas.oracle.com/bpel/extension"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:client="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
>
<import namespace="http://schemas.oracle.com/bpel/extension" location="RuntimeFault.wsdl";/>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous" schemaLocation="HelloJavaWorldSynchronous.xsd";/>
</schema>
</types>
<message name="HelloJavaWorldSynchronousRequestMessage">
<part name="payload" element="client:HelloJavaWorldSynchronousProcessRequest"/>
</message>
<message name="HelloJavaWorldSynchronousResponseMessage">
<part name="payload" element="client:HelloJavaWorldSynchronousProcessResponse"/>
</message>
<portType name="HelloJavaWorldSynchronous">
<operation name="process">
<input message="client:HelloJavaWorldSynchronousRequestMessage"/>
<output message="client:HelloJavaWorldSynchronousResponseMessage"/>
<fault name="myFault" message="ns1:RuntimeFaultMessage"/>
</operation>
</portType>
<plnk:partnerLinkType name="HelloJavaWorldSynchronous">
<plnk:role name="HelloJavaWorldSynchronousProvider">
<plnk:portType name="client:HelloJavaWorldSynchronous"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
The standard RuntimeFault.wsdl file (RuntimeFaultMessage message is defined in here, so I don't need a message in HelloJavaWorldSynchronous.wsdl. Do I?)
<?xml version="1.0"; encoding="UTF-8"?>
<definitions name="RuntimeFault"
targetNamespace="http://schemas.oracle.com/bpel/extension"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<message name="RuntimeFaultMessage">
<part name="code" type="xsd:string"/>
<part name="summary" type="xsd:string"/>
<part name="detail" type="xsd:string"/>
</message>
</definitions>
But when we invoke the process, after the standard 45 seconds timeout, we still get...
<Faulthttp://schemas.xmlsoap.org/soap/envelope/>
<faultcode>env:Server</faultcode>
<faultstring>com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is f290d62d2ad31aa6:-49eb76f4:124eb51622a:-7c91. Please check the process instance for detail.</faultstring>
</Fault>
The console audit below might hold a clue. I noticed the mesage BPELFault" has not been caught by a catch block at the end.
<catchAll>
<sequence>
Assign_3
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
</FaultVar>
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
</FaultVar>
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello test detail
</detail>
</part>
</FaultVar>
Throw_2 (faulted)
[2009/11/13 11:18:32] "{http://xmlns.oracle.com/HelloJavaWorldSynchronous}myFault" has been thrown. More...
-<myFault xmlns="http://xmlns.oracle.com/HelloJavaWorldSynchronous">
-<part name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello test detail
</detail>
</part>
</myFault>
</sequence>
</catchAll>
[2009/11/13 11:18:32] "BPELFault" has not been caught by a catch block.
[2009/11/13 11:18:32] BPEL process instance "570162" cancelled

Thanks very much for this answer. It was right on.
You wanted to know "how (I) get on". Funny you should ask. Believe it or not, I had figured out the problem on my own just about the time you were posting your reply (of course, this is a bit too convenient. No one will ever believe me).
But the answer leads to another question. What is the Throw activity for, if not to throw an error to the calling process? Is it only used to throw within scope of the process its self?
I am probably biased by the Java world I am coming from, but Throw feels like it should terminate the process (without side effects like a big red mark in the console) bubble up the fault to the calling process who can catch it (if so desired). Using the reply we must explicitly Terminate (which includes that unsightly red mark).
Is there any way to get this behavior from the Throw, or should we just reprogram the "wetware" and learn a new paradigm?
Is there any way to end a process without marking it with a red flag that suggests something went wrong?

How to execute SQOOP.cmd file from SSIS execute process task?

How to execute SQOOP.cmd file from SSIS execute process task?
What is argument need to be prefixed in the arguments property
Executable: C:\Hadoop\sqoop-1.4.2\bin\sqoop.cmd
Arguments: /C "sqoop import -connect "jdbc:sqlserver://mysystem:1433;database=test;username=myuser;password=mypwd;" -table emp -target-dir /user/emptable -m 1"
Thanks
Durga

Hi Durga,
SQOOP.cmd must be no different than any other .cmd/.bat I assume, your question is more about setting the parameters up I guessed.
So unless the arguments change dynamically you can call SQOOP.cmd from yet another .cmd that has its parameters passed to it and the former you simply set to run without the arguments in Execute Process Task.
Otherwise, in general to set a bat/cmd file to run in SSIS one needs to do this:
PS: It is a good idea to populate the working directory with the path to the .cmd
Arthur My Blog

WLI: Can't call synchronous web services from async business process?

I have three web services, X, Y, and Z, that I want to call from a business process B. X is asynchronous, Y and Z are synchronous. Therefore, B must be asynchronous. B is called from another business process, A, that must be synchronous. So, I have A call B synchronously using the SyncAsync pattern described in "Best Practices for Oracle WebLogic Integration Application Life Cycle". This worked fine in earlier development when I was only calling X from B. However, when I try to add synchronous calls to Y or Z and run A, I get the following error message from B:
com.bea.control.classic.ServiceControlException: Attempting to perform the client
callback 'doY' while servicing a blocking request from the same client. This can
result in a deadlock condition. An @jws:message-buffer tag should be placed on
the synchronous operation or on this callback.This is obviously an old error message, since it recommends an annotation in the old style. Anyway, what can I do? Shouldn't it be possible to invoke web services synchronously from process B? If so, then how? I don't know what synchronous operation it's talking about -- is it A's call to B? As for the callback, I don't see a separate callback. Annotating the SBControl's method with weblogic.jws.MessageBuffer did no good, and I can't use com.bea.control.annotations.MessageBuffer because the method doesn't return void. Can I make this work without rewriting B, and if so, how? It'd be nice if I could call X, and then call Y and Z while waiting for X's callback.
Alternatively, I could rewrite my processes so that A calls a new process C synchronously, which in turn calls B (which calls X), Y, and Z. That should work, right? Thanks for any help y'all can give me.

Greetings everyone,
We have found a solution to this problem, and it is very much like one offered by Trinidad, except there was some confusion in my understanding.
http://sql-patch/B1WS/webreferences/LoginService.wsdl
Indeed, the url http://localhost/Service.asmx appears in the WSDL files, as well as the web.config.
I changed it to http://sql-patch/B1WS/webreferences/LoginService.wsdl in the WSDL files only. This did not work.
We then found it in the web.config file also, and changed it to http://sql-patch/B1WS/webreferences/LoginService.wsdl also.
The reason I was using this URL is because the files exist there. Looking at IIS, there is no Service.asmx anywhere in the B1WS path, and this confused me.
This got us one step further, but now a new error was showing itself -- 405 Method Not Allowed.
It turns out that the URL we needed to change it to is this:
http://sql-patch/B1WS/Service.asmx
That is, we replace localhost with the name of the machine, and NOTHING else.
This seems to have solved it for us, and is hopefully useful for you.
Thanks all,
Mike

Timeout error calling a Business Process from another Business Process

Hi to all,
How can I call a Business Process (BP2) from another Business Process (BP1) and wait for the response before other things are performed? I'm trying to call from BP1 in a synchronous step the process BP2; the first step of BP2 is an Open S/A Bridge and, after a transformation, a Close S/A Bridge, but no response returns to BP1 till a timeout error.
Thank you very much,
Antonio

I did some changes and the error now I am getting is,
===========================================================
Error : null oracle.jsp.JspServlet.internalService(JspServlet.java:186)oracle.jsp.JspServlet.service(JspServlet.java:156)javax.servlet.http.HttpServlet.service(HttpServlet.java:588)org.apache.jserv.JServConnection.processRequest(JServConnection.java:456)org.apache.jserv.JServConnection.run(JServConnection.java:294)java.lang.Thread.run(Thread.java:534)
Error : oa_html._Text__Button__Lat._jspService(_Text__Button__Lat.java:712)oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:119)oracle.jsp.app.JspApplication.dispatchRequest(JspApplication.java:417)oracle.jsp.JspServlet.doDispatch(JspServlet.java:267)oracle.jsp.JspServlet.internalService(JspServlet.java:186)
============================================================
Does the middle tier need to be bounced?
Thanks

How to catch SOAP fault from PeopleSoft web service

I am trying to catch the SOAP fault thrown from pplsoft. Currently we get only runtime error if we call pplsoft web service thru ESB. Fault is not being propagated back to route ESB.
thanks for your help

Have you managed to solve this issue? BPEL does allow you to do this.

Catching and rethrowing a SOAP Fault from an OSB 11g Proxy service

Hello,
We have a chain of proxy services (that last one of which calls a business service) in our 11.1.1.6 OSB project. At one of the lower levels, we successfully throw a fault like this:
<soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Fault xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
    <soap:faultcode>SOAP-ENV:Client</soap:faultcode>
    <soap:faultstring>Non-Existent User</soap:faultstring>
    <soap:faultActor>Client who consumed this Web Service operation</soap:faultActor>
    <soap:detail>
      <sc:UserNonExistentFault xmlns:sc="http://xmlns.sc.com/Services/V1">
        <sc:CustomerNumber>12345</sc:CustomerNumber>
      </sc:UserNonExistentFault>
    </soap:detail>
</soap:Fault>
</soapenv:Body>
In the proxy service which calls this proxy service, I tried to catch this fault in an Error Handler so that I could confirm that it's available for me to re-throw back up the chain. Curiously, the proxy service which calls that proxy service cannot see that fault. But rather it sees what appears to be an OSB-overridden fault:
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-380000</con:errorCode>
<con:reason>com.bea.wli.sb.pipeline.PipelineException</con:reason>
<con:details>
    <err:ErrorResponseDetail xmlns:err="http://www.bea.com/wli/sb/errors">
      <err:response-metadata xsi:type="sb:SBResponseMetaDataXML" xmlns:sb="http://www.bea.com/wli/sb/transports/sb" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <tran:headers xsi:type="sb:SBResponseHeadersXML" xmlns:tran="http://www.bea.com/wli/sb/transports"/>
        <tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">1</tran:response-code>
        <tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">utf-8</tran:encoding>
      </err:response-metadata>
    </err:ErrorResponseDetail>
</con:details>
<con:location>
    <con:node>PipelinePairNode</con:node>
    <con:pipeline>PipelinePairNode_request</con:pipeline>
    <con:stage>GetCustomerByNumber</con:stage>
    <con:path>request-pipeline</con:path>
</con:location>
</con:fault>
I have tried printing out the values of $body, $fault, $outbound and $inbound from the calling proxy service's Error Handler just to see if our <sc:UserNonExistentFault> is nested anywhere therein. Unfortunately, it is nowhere to be found.
How can we force OSB to NOT override our faults with OSB-framework faults and, instead, just throw our custom fault all the way up the chain and back to the consumer?
Thank you,
Michael

I think I figured this out.
In proxyService-2, build the <soap:Fault> and assign it to the body, then Reply with Failure (as you mentioned above).
When proxyService-1 receives this, it will still be in the $body variable. But the $fault variable is now populated with a BEA-38000 error. It seems that as long as the $fault variable has data in it, then the OSB system will throw that instead of my fault (ignoring the <soap:Fault> I put into the body).
So what I did was to Delete the $fault variable in the error handler of proxyService-1, then Reply with Failure (again).
It would seem as if the inner workings of OSB has some logic like:
if $fault is not null, throw the BEA-####### fault. Otherwise, return the contents of the $body.
By removing the fault, I effectively got to that "else/otherwise" condition.
Of course, the Reply with Failure is still needed to ensure that an HTTP 500 error is passed with the fault (per the SOAP specification).
Cheers!
Michael

In BPEL, how to create a SOAP fault?

I am using JDeveloper 11.1.1.6. I need to send SOAP fault by setting faultstring, faultcode and faultactor. How can I define asoap fault and send?

Thank you very much for your response. Is there any other module/component I can able to access SOAP fault and set my own faultcode, faultstring and fault actor? Presently, when a custom fault is sent from BPEL, it is setting fault code as name of the fault (with namespace: ex: ns0:ProcessFault). Instead of that I want to set a specific fault code (like 100) and appropriate fault actor and fault string. Or is it possible using java code in BPEL SOAP fault can be created and set appropriate values?
If not is it available in OSB? (I have not looked OSB yet). Thanks for you response.

How to return a Soap Fault from a business process

Similar Messages

Maybe you are looking for