Fault Handling in Web Services

Hi,
Can anyone please point me to any document which explains about the fault handling in Web Services using Bottom-up Approach?
Thanks

Can you give some further information?
Do you want to throw a fault an your webservice and you are asking how this fault is seen by the service requestor? If you throw a exception it is mapped to
<?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>
Have you tried
http://www.oracle.com/technology/products/ias/bpel/pdf/orabpel-Training-Segment06.pdf?
This is top down but perhaps you can learn from it.

Similar Messages

Fault elt in web-services.xml NOT WORKING

We are trying to capture an invalid message coming into our service before our
service actually processes it. Per WLS7 documentation, it provides the ability
to add a <fault> elt under the <params> elt in web-services.xml to perform that.
Here's how the operations portion of our web-services.xml looks like:
<operations>
<operation method="echo(java.lang.String)" component="jcComp0" name="echo"
handler-chain="diagnosticChain">
<params>
<param location="body" class-name="java.lang.String" style="in" name="echoString"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:string">
</param>
<return-param location="body" class-name="java.lang.String" name="Result"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:string">
</return-param>
<fault name="InvalidMessageException" class-name="com.gmacfs.routeone.diagnostic.InvalidMessageException"/>
</params>
</operation>
</operations>
However, when we tried doing that, we got a BIG set of exception while trying
to build our client. It looks as follows:
client:
[clientgen] Generating client jar for diagnostic.ear ...
[clientgen] Could not read Web Service deployment descriptor
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.java:112)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --- Nested Exception ---
[clientgen] Could not read Web Service deployment descriptor
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EARClientGen.java:332)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.java:110)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --- Nested Exception ---
[clientgen] weblogic.webservice.dd.DDProcessingException: Could not find required
attribute "type" for element <fault> (Line 28, Column 8)
[clientgen] at weblogic.webservice.dd.ParsingHelper.getRequiredAttribute(ParsingHelper.java:287)
[clientgen] at weblogic.webservice.dd.DDLoader.processFaultElement(DDLoader.java:1195)
[clientgen] at weblogic.webservice.dd.DDLoader.processFaultElements(DDLoader.java:1166)
[clientgen] at weblogic.webservice.dd.DDLoader.processParamsElement(DDLoader.java:1004)
[clientgen] at weblogic.webservice.dd.DDLoader.processOperationElement(DDLoader.java:977)
[clientgen] at weblogic.webservice.dd.DDLoader.processOperationElements(DDLoader.java:853)
[clientgen] at weblogic.webservice.dd.DDLoader.processOperationsElement(DDLoader.java:841)
[clientgen] at weblogic.webservice.dd.DDLoader.processWebServiceElement(DDLoader.java:378)
[clientgen] at weblogic.webservice.dd.DDLoader.processWebServiceElements(DDLoader.java:283)
[clientgen] at weblogic.webservice.dd.DDLoader.processWebServicesElement(DDLoader.java:271)
[clientgen] at weblogic.webservice.dd.DDLoader.load(DDLoader.java:249)
[clientgen] at weblogic.webservice.util.WebServiceWarFile.getWSDD(WebServiceWarFile.java:79)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EARClientGen.java:330)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.java:110)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --------------- nested within: ------------------
[clientgen] weblogic.webservice.util.WebServiceJarException: Could not load deployment
descriptor - with nested exception:
[clientgen] [weblogic.webservice.dd.DDProcessingException: Could not find required
attribute "type" for element <fault> (Line 28, Column 8)]
[clientgen] at weblogic.webservice.util.WebServiceWarFile.getWSDD(WebServiceWarFile.java:81)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EARClientGen.java:330)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.java:110)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
BUILD FAILED
Anybody has any ideas?
Thanks much,
sami

Manoj,
Thanks a lot, THAT DID IT... two very helpful hints from you in a row.
By the way, one thing worth mentioning is that the Weblogic documentation that
we explored did not have enough information about that issue.
Thanks again.
sami
"manoj cheenath" <[email protected]> wrote:
Buried deep in the stack trace, is this little
detail:
Could not find required
attribute "type" for element <fault> (Line 28, Column 8)
So the correct DD should look something like:
<fault type="typeNS:string"
xmlns:typeNS="http://www.w3.org/2001/XMLSchema"
class-name="tutorial.sample9.HelloWorldException"
name="HelloWorldException">
</fault>
Also, check out this example:
http://manojc.com/?sample9
There is a know problem: WLS can not handle
exceptions that contain complex data types.
This will be fixed in SP1.
Regards,
-manoj
http://manojc.com
"sami titi" <[email protected]> wrote in message
news:[email protected]...
We are trying to capture an invalid message coming into our servicebefore
our
service actually processes it. Per WLS7 documentation, it providesthe
ability
to add a <fault> elt under the <params> elt in web-services.xml toperform
that.
Here's how the operations portion of our web-services.xml looks like:
<operations>
<operation method="echo(java.lang.String)" component="jcComp0"name="echo"
handler-chain="diagnosticChain">
<params>
<param location="body" class-name="java.lang.String" style="in"name="echoString"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:string">
</param>
<return-param location="body" class-name="java.lang.String"name="Result"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:string">
</return-param>
<fault name="InvalidMessageException"class-name="com.gmacfs.routeone.diagnostic.InvalidMessageException"/>
</params>
</operation>
</operations>
However, when we tried doing that, we got a BIG set of exception whiletrying
to build our client. It looks as follows:
client:
[clientgen] Generating client jar for diagnostic.ear ...
[clientgen] Could not read Web Service deployment descriptor
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.ja
va:112)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenT
ask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --- Nested Exception ---
[clientgen] Could not read Web Service deployment descriptor
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EAR
ClientGen.java:332)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.ja
va:110)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenT
ask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --- Nested Exception ---
[clientgen] weblogic.webservice.dd.DDProcessingException: Could notfind
required
attribute "type" for element <fault> (Line 28, Column 8)
[clientgen] atweblogic.webservice.dd.ParsingHelper.getRequiredAttribute(ParsingHelper.java
:287)
[clientgen] atweblogic.webservice.dd.DDLoader.processFaultElement(DDLoader.java:1195)
[clientgen] atweblogic.webservice.dd.DDLoader.processFaultElements(DDLoader.java:1166)
[clientgen] atweblogic.webservice.dd.DDLoader.processParamsElement(DDLoader.java:1004)
[clientgen] atweblogic.webservice.dd.DDLoader.processOperationElement(DDLoader.java:977)
[clientgen] atweblogic.webservice.dd.DDLoader.processOperationElements(DDLoader.java:853)
[clientgen] atweblogic.webservice.dd.DDLoader.processOperationsElement(DDLoader.java:841)
[clientgen] atweblogic.webservice.dd.DDLoader.processWebServiceElement(DDLoader.java:378)
[clientgen] atweblogic.webservice.dd.DDLoader.processWebServiceElements(DDLoader.java:283)
[clientgen] atweblogic.webservice.dd.DDLoader.processWebServicesElement(DDLoader.java:271)
[clientgen] at weblogic.webservice.dd.DDLoader.load(DDLoader.java:249)
[clientgen] atweblogic.webservice.util.WebServiceWarFile.getWSDD(WebServiceWarFile.java:79
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EAR
ClientGen.java:330)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.ja
va:110)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenT
ask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --------------- nested within: ------------------
[clientgen] weblogic.webservice.util.WebServiceJarException: Couldnot
load deployment
descriptor - with nested exception:
[clientgen] [weblogic.webservice.dd.DDProcessingException: Could not
find>required>> attribute "type" for element <fault> (Line 28, Column 8)
[clientgen] atweblogic.webservice.util.WebServiceWarFile.getWSDD(WebServiceWarFile.java:81
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EAR
ClientGen.java:330)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.ja
va:110)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenT
ask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
BUILD FAILED
Anybody has any ideas?
Thanks much,
sami

Generating wsdl:fault with Oracle Web Services

What conditions are required to have Oracle Web Services throw a defined wsdl:fault over a soap:fault? Is there documentation on how to map these correctly from your java code? I can't seem to find anything in the documenation that discusses this and when using the WebServiceAssembler to generate WSDLs including an exception in a method signature does nothing to generate a wsdl section in the generated portType.
Any pointers are appreciated.

Hi,
If a method throws Exceptions that are not instances / subclasses of java.rmi.RemoteException, then it's not a SOAP Fault, but a wsdl:fault. This is the manner in which JAX-RPC handles the Exceptions.
Regards,
Sandeep

Request handling in web service

Hi guys,
is there a way to "handle" the request within a web service (like HTTPrequest obj in servlets)? i.e. for retrieving the context and so on .. ?
thanks to anybody who will answer me
J.

Hi guys,
is there a way to "handle" the request within a web
service (like HTTPrequest obj in servlets)? i.e. for
retrieving the context and so on .. ?
thanks to anybody who will answer me
J.See if this works for you. Have your service impl class also
implement javax.xml.rpc.server.ServiceLifecycle. Then you'll
have to add an init() and destroy() method (see the javadocs).
If you declare a ServletEndpointContext field, then in
init you can do
public void init(Object context) {
myServletEndpointContext = (ServletEndpointContext) context;
and in subsequent methods do
myHttpSession = servletEndpointContext.getHttpSession()
(don't do this part in init, do it during business method calls)
Cheers,
Bobby

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.

Generating Faults in a Web Service

I'm having trouble getting my web service to generate a fault message in the WSDL. Even though the jws class throws exception com.bea.jws.SoapFaultException, there is no sign of a fault message in the WSDL that I generated using Workshop. In the sample code below I tried generating the SoapFaultException in a couple of different ways. How do I get Workshop to generate the fault message in the WSDL for me?
public class pathwayWS implements com.bea.jws.WebService
* @common:control
private empPathway.pathwayJCS.pathway pathway;
static final long serialVersionUID = 1L;
* @common:operation
public EmpAddResponse0 empAdd (message.inEmpAdd addMessage) throws com.bea.jws.SoapFaultException
EmpAddResponse0 m_employee;
EmpAddResponse1 m_error;
Object response = pathway.addEmployee(empPathway.empConstants.pathwayName,
empPathway.empConstants.serverClassName,
addMessage.employeeInfo.employee_number,
addMessage.employeeInfo.empName.first,
addMessage.employeeInfo.empName.last,
addMessage.employeeInfo.empName.middle,
addMessage.employeeInfo.regnum,
addMessage.employeeInfo.branchnum);
if ( response instanceof EmpAddResponse0) {
m_employee = (EmpAddResponse0) response;
} else if ( response instanceof EmpAddResponse1) {
m_error = (EmpAddResponse1) response;
XmlString fault = XmlString.Factory.newInstance();
fault.set(m_error.reply_code);
throw new com.bea.jws.SoapFaultException(fault);
} else {
m_error = new EmpAddResponse1();
m_error.reply_code = "-1";
m_error.error_text = "Unexpected response received from pathway control";
XmlString empErrorDoc = XmlString.Factory.newInstance();
empErrorDoc.set(m_error.reply_code);
com.bea.jws.SoapFaultException fault = new com.bea.jws.SoapFaultException(new XmlObject[]{empErrorDoc});
throw fault;
return m_employee;
}

The sample code in the PDK uses:
        iusermaint = userFactory.newUser(username);
        //Save the data permanently.
        iusermaint.commit();
        //Save the new user's unique name and ID to the strings.
        uniqueName = iusermaint.getUniqueName();
        uniqueID = iusermaint.getUniqueID();
        //Create user account using the unique name and ID read
        //from the system before and the password read from the bean.
        IUserAccount iUserAccount = accountFactory.newUserAccount(uniqueName, uniqueID);
        iUserAccount.setPassword(password);
        //Save the data permanently.
        iUserAccount.commit();
The difference to your code is that they appear to get the uniquieID from the just created user, whereas you have hardcoded it...
Cheers

Handling Java Web Service Exception in ABAP

Hi
I have created a web service in Java using NWDS.
Which has a businessMethod which throws a Exception based on certain business logic.
I have consumed this Web Service Method using .NET Client.
i am able to catch the Exception and get the Exceltion Message.
But when i try to consume the same web service Method in ABAP,
i am not getting the Exception Message .
The Method call works fine.
What am i missing here ?
regards
Rajendra

Hi,
Upon further investigation and comparison of the custom exception object (generated during consumer proxy creation for a CUSTOM web service) with a standard exception object(generated during consumer proxy creation for a STANDARD web service) I found that the sub-elements of the exception structure errorPart are not available in the custom exception object (and one of these sub-elements is the message text).
Call Stack,ExceptionName and MessageText Elements are missing in the errorPart node of Exception
Node. as seen in the ABAP Exception structure generated.
Queries:
1. Are there any standards which need to be followed when coding exceptions in the Java web service for consumption in ABAP such that all sub-elements of the exception object are also created in ABAP during the proxy creation?
2. Can we get the Java code for a standard web service available in SAP Netweaver? Asking the same as the exception object created for the standard web service RoomABAPWS contains the sub-elements. Getting the Java code of the same will be very helpful in resolving the issue.
Regards
Rajendra

Getting Fault String in Web Service response

Hi,
I developed a Web Service and deployed it on Glassfish Server. When I am trying to call web service some times I am getting following error
<faultstring>String index out of range: 0</faultstring>What is the meaning of this ? How to solve this ?
Regards,
Ajay Sharma

Either cal it with values that do not cause a String index to be out of range or change the webservice to deal with the case that causes this differently. Either way the starting point is finding out where in the webservice the String index is out of range.

Excpetion handling in web services

Hi!
What happens when returning a custom exception in a web service, can I run instanceof on
SOAPFaultException)ex.getCause();
how do I know what kind of Exception it is?
Thanks,
I.

instanceof, different catch blocks

Exception handling in Web Services

Hi all,
I am exposing ejb2-based webservices and am unable to find a way to throw checked Exceptions.
Could anyone provide resources about how to leverage SOAP/WSDL features of exception handling (i.e. wsdl:fault tag)?
Thanks, regards
Vincenzo

Hi, thanks for replying
actually on saphelp I found that supported Exceptions are:
java.lang.Exception -> no fault generated
java.rmi.RemoteException -> deploy refused with explicit error (RemoteException not allowed in ejb business method signature)
java.lang.Throwable -> doesn't seem very appropriate to use such a root class
Any suggestion?
Thanks, regards
Vincenzo

Fault Handling a netbeans generated web service fault

Hi, we have been unsuccessful in creating a simple example where a bpel process could handle an exception thrown be a web service deployed in a EJBModule created in netbeans 5.5.
The fault handling of fault thrown be other bpel process seems to work fine, but in the case of a web service fault the process dies.
We come to realise that the soap message of a fault is different for a bpel thrown fault and a web service one. Dont know if it has something to do with the problem...
Note that there is no example of fault handling of a netbeans created webservice in a bpel process (at least we didn't find one).
Has someone been able to do this kind of fault handling?
Maybe someone could post a link to an example?
Any help is appreciated

What BPEL expects is a WS fault. The fault has to be defined on the WSDL operation that the BPEL invokes. If the EJB sent a soap fault, and that is the contract between the EJB and the BC, then i would say it is the resposibility of the SOAP BC to translate it into a WSDL operation defined fault and pass it on to the BPEL engine.
If the BC just hints that a fault has happened but doesn't give enough information that is necessary for the fault handling, the process will surely terminate.
If in the process you define a catchAll around the EJB invoke, you would be able to handle the fault from the BC.
I know of this one example, but not sure if they handle faults
http://blogs.sun.com/gopalan/page/gopalan?entry=ts_3175_building_a_service
The following link may be of some use.
https://blueprints.dev.java.net/bpcatalog/ee5/soa/

Implementation of session handling for using web services

Hi,
I would like to use session handling in web services using ABAP stack in order to start the session with an user login function followed by other RFC calls till a user logout. So far, I found only the following help note in the SAP online help:
Interface Profile
In the interface profile, choose the required processing type: Stateful or Stateless.
A stateful service retains its status within the framework of a HTTP session throughout several calls form the same service consumer. The standard value for services is Stateless.If you require stateful communication, you can choose this instead.
[http://help.sap.com/saphelp_nwpi71/helpdata/de/45/25291b5a2657c0e10000000a1553f7/content.htm |http://help.sap.com/saphelp_nwpi71/helpdata/en/45/25291b5a2657c0e10000000a1553f7/content.htm]
Please, could someone explain me the further required steps of SAPs session handling idea cause just settting the status to stateful is still not the solution itself...
Regards,
Jens

Now, I found the possible scenarios, suggest by SAP Help, regarding security for Web Services ([http://help.sap.com/saphelp_nw73/helpdata/en/48/8ebbba66be06b2e10000000a42189b/content.htm|http://help.sap.com/saphelp_nw73/helpdata/en/48/8ebbba66be06b2e10000000a42189b/content.htm]):
- SAML & WS SecureConversation -> SSO
- WS Security UsernameToken & WS SecureConversation
- User ID and Password in HTTP Header & HTTPS
- SAP Authentication Assertion Ticket & HTTPS -> SSO
- X.509 SSL Client Certificate through HTTPS
- WS Security: X.509 Certificate Authentication at Message Level
Are scenarios with SSO the solution for creating sessions!?

Fault handling using BPEL

Good, I'm working on a research project and I have been assigned the task of processing errors in SOAP BPEL.
I've been searching on Internet and the most commonly methodology used is soap-fault with throwing and catching exceptions in BPEL process.
I wonder if I can do it in a more proactive and comprehensive way, catching those exceptions through a web service, and if possible, how can the BPEL process send the information encapsulated in the soap-fault to the web service?
If there is another way of treating errors or someone can suggest me another way, I would be very grateful.

I am not clear on your objective, but in so far as BPEL SE Component of Open-ESB Project, running on JBI is concerned you can read more about Fault handling and other features of BPELSE here at http://wiki.open-esb.java.net/Wiki.jsp?page=BPELSE. Also, you can find some working examples on this page http://wiki.open-esb.java.net/Wiki.jsp?page=HowToDo
- Malkit

Error in E-rec web Service and BSP

Hi Folks
We are facing an issue with Requisition Management in E-rec. A workflow is triggered for requisition management and goes to approver. The workitem does not appear in the UWL of the user however when we monitor the log, it shows the workitem is with approver and without any error.
Our problem is it does not show the workitem in the approver's UWL and when we test the approval serivce and handler service in SICF, it gives us the following message
1.Service Name : wshandler (REQUEST HANDLER FOR WEB SERVICES)
Error in Web service execution
The launch handler was called with an incomplete parameter list
2.Service name : hrrcf_approval (Recruiter: Approval of Status Change)
Error message : Calling the BSP page was terminated due to an error.
SAP Note
The following error text was processed in the system:
BSP Exception: Das Objekt default.htm in der URL /sap/bc/bsp/sap/hrrcf_approval/default.htm?sap-client=100&sap-sessioncmd=open ist nicht gültig.
Please guide us, how to fix.
Regards
Netweaver team

Hi, Were you able to resolve this issue?
IF not then please go to transaction wf_handcust and maintain the entries under Launch Handler, Callback Handler and callback Dialog. I had the same issue and your's was the only related message I could search in SDN so thought of sharing the solution.
Regards,
VInay

Getting error System.Web.Services.Protocols.SoapException: Server did not r

I am trying to acces my web service using this code
Call call = new Call ();
SOAPMappingRegistry soap = new SOAPMappingRegistry();
call.setTargetObjectURI ("http://tempuri.org/");
call.setMethodName ("EarnNValue");
Vector params = new Vector ();
params.addElement (new Parameter("customer_id", String.class, "gauravbehl",Constants.NS_URI_SOAP_ENC));
params.addElement (new Parameter("channel_id", String.class, "C0002",Constants.NS_URI_SOAP_ENC));
call.setParams (params);
Response resp = call.invoke(new URL("http://203.199.76.2/api/earnnvalue.asmx"), "http://tempuri.org//EarnNValue") ;
if (resp.generatedFault ())
Fault fault = resp.getFault ();
System.out.println (" Fault Code = " + fault.getFaultCode ());
System.out.println (" Fault String = " + fault.getFaultString ());
else
Parameter result = resp.getReturnValue ();
System.out.println (result.getValue ());
out.println (result.getValue ());
and i am getting the the following error
Fault Code = soap:Client
Fault String = System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: http://tempuri.org//EarnNValue.
at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest()
at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
Please help.
Thanx
GB

<%@ page language="java" import="java.util.*, java.io.*, javax.mail.*, java.net.*, org.apache.soap.util.xml.*, org.apache.soap.encoding.soapenc.BeanSerializer, org.apache.soap.encoding.*,org.apache.soap.*, org.apache.soap.rpc.*"%>
<%
try
out.println ("Starting");
System.out.println("heree");
Call call = new Call ();
System.out.println("here");
SOAPMappingRegistry soap = new SOAPMappingRegistry();
call.setTargetObjectURI ("http://tempuri.org/");
call.setMethodName ("EarnNValue");
call.setEncodingStyleURI("http://schemas.xmlsoap.org/soap/encoding/");
Vector params = new Vector ();
params.addElement (new Parameter("customer_id", String.class, "gauravbehl",Constants.NS_URI_SOAP_ENC));
params.addElement (new Parameter("channel_id", String.class, "C0002",Constants.NS_URI_SOAP_ENC));
params.addElement (new Parameter("category_id", String.class, "club",Constants.NS_URI_SOAP_ENC));
params.addElement (new Parameter("transaction_date", String.class, "16/07/04 14:41:20",Constants.NS_URI_SOAP_ENC));
params.addElement (new Parameter("parameter_id", String.class, "login",Constants.NS_URI_SOAP_ENC));
params.addElement (new Parameter("parameter_value", String.class, "1",Constants.NS_URI_SOAP_ENC));
call.setParams (params);
Response resp = call.invoke(new URL("http://203.199.76.2/api/earnnvalue.asmx"), "http://tempuri.org//EarnNValue") ;
if (resp.generatedFault ())
Fault fault = resp.getFault ();
System.out.println ("Something is wrong");
System.out.println (" Fault Code = " + fault.getFaultCode ());
System.out.println (" Fault String = " + fault.getFaultString ());
else
Parameter result = resp.getReturnValue ();
System.out.println (result.getValue ());
out.println (result.getValue ());
catch (Exception e)
System.out.println ("********Exception*******");
System.out.println (e);
out.println ("Ending");
%>

Fault Handling in Web Services

Similar Messages

Maybe you are looking for