Missing namespace on XAI Inbound Service Fault Element

Hi,
when a XAI Inbound service errors out, it uses the Fault element defined in the WSDL, which normally should be:
+<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">+
+<soapenv:Body>+
+<soapenv:Fault>+
+<faultcode>soapenv:Client</faultcode>+
+<faultstring>Client Error</faultstring>+
+<detail>+
*+<ouaf:Fault xmlns:ouaf="urn:oracle:ouaf">+*
-- omiting details
+</ouaf:Fault>+
+</detail>+
+</soapenv:Fault>+
+</soapenv:Body>+
+</soapenv:Envelope>+
However, in one environment i am getting this response, without the namespace:
+<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">+
+<soapenv:Body>+
+<soapenv:Fault><faultcode>soapenv:Client</faultcode>+
+<faultstring>Client Error</faultstring>+
+<detail>+
*+<ouafFault>+*
-- Omiting Details
+</ouafFault>+
+</detail>+
+</soapenv:Fault>+
+</soapenv:Body>+
+</soapenv:Envelope>+
This happens both for Custom and Base XAI Inbound services.
Already validated the patching level between environments.
The logs do not show any obvious difference.
I will appreciate any idea or suggestion.
Thanks
Regards
Ernesto.

All the environments had the same patching level and our problem was in one environment only.
We cloned the rowking environment ontop of the non-working one and it's solved, although we don't know which was the reason. My guess is some of the patches was not properly applied.
Thanks
Regards
Chipi.

Similar Messages

How to get only mandatory elements of BO schema using XAI Inbound service

Hi Folks,
I create a XAI Inbound service for a BO and I just want to generate the WSDL xml request schema with only mandatory fields of that BO.
How to acheive this? Is it possible and is there any solution already for this?

Hi Folks,
I create a XAI Inbound service for a BO and I just want to generate the WSDL xml request schema with only mandatory fields of that BO.
How to acheive this? Is it possible and is there any solution already for this?

Using a Response XSL on XAI Inbound Service creates an invalid XML

I created a Response XSL and plugged it into my XAI Inbound Service, however the Response XML it creates is invalid:
<?xml version="1.0" ?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="urn:schemas-xmlsoap-org:envelope">
<SOAP-ENV:Body >
*<?xml version="1.0" encoding="UTF-8"?>*
<CmAccountSearch>
<Request AccountNumber="" StreetNumber="740" StreetLine1="Polaris Ave" City="Foster City" State="CA"/>
<Response ReturnCode="I">
<CustomerDetailsList AccountNumber="9231764166" CustomerName="Rovno,Aleksandr" AmountDue="0" IsCashOnly="false" StreetLine1="740 Polaris Ave"/>
<CustomerDetailsList AccountNumber="0304039866" CustomerName="Ray,Jamse" AmountDue="0" IsCashOnly="false" StreetLine1="740 Polaris Ave"/>
</Response>
</CmAccountSearch>
</SOAP-ENV:Body >
</SOAP-ENV:Envelope>
Note that a second <?xml...> tag is created after the SOAP tags.
Here is my XSL:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
     <xsl:output method="xml" indent="yes" encoding="UTF-8"/>
     <xsl:template match="/">
          <CmAccountSearch>
               <xsl:apply-templates/>
          </CmAccountSearch>
     </xsl:template>
     <xsl:template match="input">
          <xsl:element name="Request">
               <xsl:attribute name="AccountNumber">
                    <xsl:value-of select="accountId"/>
               </xsl:attribute>
               <xsl:attribute name="StreetNumber">
                    <xsl:value-of select="streetNumber"/>
               </xsl:attribute>
               <xsl:attribute name="StreetLine1">
                    <xsl:value-of select="streetName"/>
               </xsl:attribute>
               <xsl:attribute name="City">
                    <xsl:value-of select="city"/>
               </xsl:attribute>
               <xsl:attribute name="State">
                    <xsl:value-of select="state"/>
               </xsl:attribute>
          </xsl:element>
     </xsl:template>
     <xsl:template match="output">
          <xsl:element name="Response">
               <xsl:attribute name="ReturnCode">
                    <xsl:value-of select="returnCode"/>
               </xsl:attribute>
               <xsl:for-each select ="//customerDetails">
                    <xsl:element name="CustomerDetailsList">
                         <xsl:attribute name="AccountNumber">
                              <xsl:value-of select="accountId"/>
                         </xsl:attribute>
                         <xsl:attribute name="CustomerName">
                              <xsl:value-of select="customerName"/>
                         </xsl:attribute>
                         <xsl:attribute name="AmountDue">
                              <xsl:value-of select="currentAmountDue"/>
                         </xsl:attribute>
                         <xsl:attribute name="IsCashOnly">
                              <xsl:value-of select="cashOnlySw"/>
                         </xsl:attribute>
                         <xsl:attribute name="StreetLine1">
                              <xsl:value-of select="premiseAddressLine1"/>
                         </xsl:attribute>
                    </xsl:element>
               </xsl:for-each>
          </xsl:element>
     </xsl:template>
</xsl:stylesheet>
Here is the Response XML before applying the Response XSL to the XAI Inbound Service:
<?xml version="1.0" ?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="urn:schemas-xmlsoap-org:envelope">
<SOAP-ENV:Body >
<CmAccountSearch>
<input>
<accountId/>
<streetNumber>740</streetNumber>
<streetName>Polaris Ave</streetName>
<city>Foster City</city>
<state>CA</state>
</input>
<output>
<customerDetails>
<accountId>9231764166</accountId>
<customerName>Rovno,Aleksandr</customerName>
<currentAmountDue>0</currentAmountDue>
<cashOnlySw>false</cashOnlySw>
<premiseAddressLine1>740 Polaris Ave</premiseAddressLine1>
</customerDetails>
<customerDetails>
<accountId>0304039866</accountId>
<customerName>Ray,Jamse</customerName>
<currentAmountDue>0</currentAmountDue>
<cashOnlySw>false</cashOnlySw>
<premiseAddressLine1>740 Polaris Ave</premiseAddressLine1>
</customerDetails>
<returnCode>I</returnCode>
</output>
</CmAccountSearch>
</SOAP-ENV:Body >
</SOAP-ENV:Envelope>
I would like to know if anyone is familiar with this issue and how I can go about to fix it.
Any response will be greatly appreciated.
Thanks in advance.

Just set RETRIEVE_SW to 'false', APPT_RETRIEVE_FLG will be automatically set to 'C' internally.
Setting ACTION_SHOW_APP_SW to true has no meaning for pageAction 'read'.

How XAI inbound service creates an activity ?

Hi,
Can any one help me with how an XAI inbound service creates an activity on invoking from middle ware and the same automatically creates an outbound communication?
any help will be appreciated.

You cannot extend the MO with a BO, as the MO is Read Only.
See the MO Option +'BO Maintenance (Y/N)'+ for 'BATCH JOB'.
Alternatively, you can define a Business Service instead. Use Service *'CILZRBPP'*, below is an example (element values have been defaulted for demonstration purposes):
<schema pageAction="add">
    <batchJobId mapField="BATCH_JOB_ID"/>
    <batchCode mapField="BATCH_CD" default="TD-BTERR"/>
    <userId mapField="USER_ID"/>
    <programName mapField="PROGRAM_NAME" default="CIPQBERB"/>
</schema>XAI Submission:
<RXS-BatchSubmission>
</RXS-BatchSubmission>Result/Response:
<RXS-BatchSubmission>
<batchJobId>23110150739990</batchJobId>
<batchCode>TD-BTERR</batchCode>
<userId>SYSUSER</userId>
<programName>CIPQBERB</programName>
</RXS-BatchSubmission>if your Batch Daemon is running, batch will be executed without any delay.

Create a flat-file upload for a BO XAI Inbound Service?

Hello all,
If we don't have a schema defined for a BO XAI Inbound Service, how can we create the XSL and the flat-file upload schema file for it.
Any advice?
Regards,
Kerr

I don't have problem to create the XSLT mapping.
But because it is to create a flat-file upload for a Business Object XAI Inbound Service, it doesn't have a schema on the server as to the thread Create Schema for Business Object to use for XAI Inbound Service?
And I can't create that flat-file upload without a schema on the server.
Or I can use the BO XAI Inbound Service WSDL instead to create the mapping for the flat-file upload.
Regards,
Kerr

Problem in uploading XML via XAI Inbound Service and XAI Receiver..

Problem in MDM 2.0.1
I'm trying to upload some interval data in batches via XAI.
I have created one XAI Inbound service *(D1-SUNXAI)* where i am using BO *(D1-IMDSeeder)*
Then I have created one XAI RECEIVER where XAI class is XMLFILERCVR, XAI user id is XAIURL+
My scan directory is C:\ouaf\DEV9\upload where i'm keeping the *.xml files.
But these files are not uploading to database.
Please provide a solution for this..
Edited by: Suraj Keerthi on Apr 26, 2011 6:24 PM

You need to create TWO inbound services to accomplish it. One is to create the XML message and the other one is to process the transaction (add meter read).
Thanks,
Sankara.

Cancel Payment using XAI Inbound Service (CC&B)

Hi All,
Do you have any idea how to cancel payment using XAI in CC&B?
Now Im using xai Inbound service (SSvcPaymentEventMaintenance) to do cancellation process, but it just affects for the payment status only, meaning payment and payment tender status become cancel but the payment amount for the related bill is still not deducted. The bill is still in status "Fully Matched". Seems the financial transaction for payment cancellation is not created. Any idea about this ?
Thank you,
Taufix

You must use a Business Service to perform such actions, although there is no such default available even in the Demo data, follow below steps (assuming you are on CC&B 2.2.x or higher):
- Create/Configure a Business Service using Service Program 'CILPTNDP - Cancel Payment Tender'.
- Create/Configure a SS with following steps (SS Schema would contain the Payment Event Id):
1. Invoke/read Payment Event and retrieve the PAY_TENDER_ID
2. Invoke Business Service created above for each PAY_TENDER_ID by providing the Cancel Reason Code.
- Expose above created SS as an XAI Inbound Service.

OUAF / MDM 2.0.1 / XAI Inbound Service - SyncRequestInbound

I am trying to "import" an Device from my system to MDM using D1-SyncRequestInbound, but some errors have occurred. Can someone post an example ?
This is my xml:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:d1="http://oracle.com/D1-SyncRequestInbound.xsd">
<soapenv:Header/>
<soapenv:Body>
<d1:D1-SyncRequestInbound dateTimeTagFormat="xsd" transactionType="?">
<d1:externalReferenceId>1</d1:externalReferenceId>
<d1:initialLoad>F1IL</d1:initialLoad>
<d1:bo>D1-InitialSyncRequestDevice</d1:bo>
<d1:targetMo>D1-DEVICE</d1:targetMo>
<d1:targetBo>D1-DEVICE</d1:targetBo>
<d1:externalSystem>CM-EXT1</d1:externalSystem>
<d1:externalPkValue1>1</d1:externalPkValue1>
<d1:syncRequestDetails>
<d1:original>
<d1:initialSnapshot>
<d1:deviceType>CM-METER-TYPE1</d1:deviceType>
<d1:manufacturer>CM-MANUF1</d1:manufacturer>
<d1:model>CM-MODEL1</d1:model>
</d1:initialSnapshot>
</d1:original>
</d1:syncRequestDetails>
</d1:D1-SyncRequestInbound>
</soapenv:Body>
</soapenv:Envelope>

Below should work provided you have created/configured:
- External System : CM-EXT1
- Device Type: CM-METER-TYPE1
- Manufacturer/Model : CM-MANUF1 / CM-MODEL1
You SHOULD NOT define <bo> element, it'll be derived based on <initialLoad> tag, i.e. F1IC - Ongoing Sync/Incremental Sync and F1IL - Initial Load.
<finalSnapshot> is what you need and you should be at least SP5 or above, if below you'd have to apply appropriate patch.
<D1-SyncRequestInbound>
<externalReferenceId>32100057871898</externalReferenceId>
<initialLoad>F1IC</initialLoad>
<targetMo>D1-DEVICE</targetMo>
<externalSystem>CM-EXT1</externalSystem>
<externalPkValue1>1</externalPkValue1>
<externalPkValue2 />
<externalPkValue3 />
<externalPkValue4 />
<externalPkValue5 />
<syncRequestDetails>
    <original>
      <initialSnapshot>
        <customElements />
        <formattedElements>
          <formattedElements />
        </formattedElements>
      </initialSnapshot>
      <finalSnapshot>
        <deviceType>CM-METER-TYPE1</deviceType>
        <boStatus>ACTIVE</boStatus>
        <manufacturer>CM-MANUF1</manufacturer>
     <model>CM-MODEL1</model>
        <customElements />
        <formattedElements />
      </finalSnapshot>
    </original>
</syncRequestDetails>
</D1-SyncRequestInbound>

Creating XAI inbound schema for add transaction

Hi friends,
I am tring to creating xai inbound service for add transaction using business objects, when i tested that inbound service through dynamic xai i am getting error like this ,would some body suggest me to solve this.
Transformation Error
com.splwg.shared.common.LoggedException;
Logged Exception was rethrown;
com.splwg.base.web.xaiui.webxaischemaRepository.getSchemaFileNameFor
ServiceAndVersion(WebXaiSchemaRepository.java:84)
XAI Submission tab error for CMADDMETERREAD
thanks and regards
sivaram

Registered Inbound Service should work either from 'XAI Dynamic Submission' or 'XAI Submission'.
Alternatively, you could also input/provide values on the 'XAI Dynamic Submission' screen, click 'Show XML', copy the SOAP Envelope, and paste on 'XAI Submission' screen for testing purposes.
This approach would be similar to soapUI.
Ensure that parameters/values on 'XAI Options' are configured correctly as per your installation.

WSDL, custom datatypes, fault element name issues

Hello all,
I am having a LOT of problems with BEAs webservices. I am posting
this here in the hope that someone can help me and tell me what I am
doing incorrectly. I am running
WebLogic Server 7.0 SP1 Mon Sep 9 22:46:58 PDT 2002 206753
WebLogic XMLX Module 7.0 SP1 Mon Sep 9 22:54:41 PDT 2002 206753
Background:
My goal is to make my company's product web services aware. I take an
EJB, try to run it through the standard ant tasks and generate a web
services accessible EJB. Sounds pretty easy, but complex types seem
to make this quite difficult.
I have been able to create a web service accessible EJB (only since
7.0.1), but I am quite unhappy with the quality of what I am able to
produce.
I have a datatype which acts as a key, but it does not follow the
javabeans idiom - i.e. it does not have a default constructor or
accessor methods and I am not in the position to change it. I have
created a codec for this class which works and an xml schema (both by
hand). Its name is AgentKey. I have also had to use the autotyper to
create codecs and typemapping entries for java.util.Properties,
I can connect using the WebLogic classes and I am now trying to
interact using MS Excel and Apache's Axis as my test clients.
Issues:
My first question deals with generating a client. There seem to be
two ways to generate a client. Firstly via the <client> subtask of
<servicegen><service>, the second way via <clientgen> task. Since I
am using a custom data type (AgentKey) I have to manually insert the
AgentKey schema into the web-services.xml file generated by
servicegen. When I try to generate a client via the
servicegen/service/client task there is no opportunity for me to
insert this datatype schema information and I therefore get the
following messages (lots of them, but I'm only including one):
[servicegen] WARNINIG: Unable to find a javaType for the xmlType:['java:net.agentis.apml.runtime']:AgentKey.
Make sure that you have registered this xml type in the type mapping
[servicegen] Using SOAPElement instead
BTW: I am also receiving the same problem with java.util.Properties.
BTW: WARNING is misspelt
If I attempt to generate a client class via the <clientgen> task, I
need to supply either a wsdl or ear file as a parameter. I cannot
supply a wsdl file because I haven't deployed the EAR yet (and I don't
want to until the EAR has the client classes in it), and I can't
supply the EAR because I want the ear to include the client classes.
It is a bit of a catch 22 situation. Is there a solution I can't see?
NOTE: it would be very, very nice if you added a schemaMapping
attribute to the <servicegen/service> task so the web-services.xml
file didn't have to be manually hacked. Something similar to the
typemapping attribute already in the servicegen/service task would do
it.
My next problem deals with the validity of the WSDL. I am seeing that
the WSDL created has exceptions defined multiple times. I saw a
message from Manjo saying that it looked like a bug. I agree and
would like to get a copy of the patch. On a more significant note,
when is either SP2 or 7.1 due for release?
Another problem with the WSDL (once you have cleansed the multiple
exception messages) is that the fault elements of the
binding/operation elements require names and they don't have any. For
example, this is straight from the deployed EJB WSDL file:
<binding name="ExampleAgentPortSoapBinding" type="tns:ExampleAgentPort">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="serviceWithPrimitiveDatatypes">
<soap:operation soapAction="" style="rpc"/>
<input>
<soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output>
<soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
<fault>
<soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</fault>
</operation>
<operation ...
The schema definition at http://schemas.xmlsoap.org/wsdl/ says the
fault element require a name attribute:
<complexType name =" tBindingOperationFault">
<complexContent>
<extension base="wsdl:tExtensibleDocumented">
<attribute name="name" type="NCName" use="required"/>
</extension>
</complexContent>
</complexType>
The name of the fault should be the same name as the fault in the
portType definition. In my example the name is "AgentisException" as
evidenced by this snippet:
<portType name="ExampleAgentPort">
<operation name="serviceWithPrimitiveDatatypes">
<input message="tns:serviceWithPrimitiveDatatypes"/>
<output message="tns:serviceWithPrimitiveDatatypesResponse"/>
<fault name="AgentisException" message="tns:AgentisException"/>
</operation>
Once these changes have been made then the WSDL will validate. Are
there plans to fix these bugs?
On a different note, when I try to interact with a method that uses a
custom data type, such as AgentKey, via the "WebLogic Webservice
standard testing home page" the custom data type without a default
constructor cannot be rendered correctly. For instance, the AgentKey
value is:

<agentKey/>
Since I can't deploy a valid WSDL, I can't get either Axis or Excel to
connect to my web services.
When I attempt to invoke Axis' (beta 1.1) wsdl2java I recieve the
following message.
java.io.IOException: ERROR: Fault is missing a name= attribute in operation
"serviceWithPrimitiveDatatypes", in binding {http://sillyurl.com/reallysilly}ExampleAgentPortSoapBinding.
This seems understandable considering the issues I mentioned earlier.
Unfortunately Excel doesn't really give me anything to go with. If I
type in the WSDL URI then it will give me a list of methods I can
invoke, but if I try to add the service I get the very unhelpful "The
Web Service References Tool could not generate the requested code.
Any changes that were made to your project have been rolled back."
Any help with those two issues would be greatly appreciated also.
One final issue is that I cannot seem to fix is taskdef'ing
<servicegen> properly from Ant. I can do the actual taskdef but then
it cannot find classes from within the weblogic.jar. If I run the
setExamplesEnv.cmd first the I don't need to do the taskdef and
everything works fine. Has anyone else had this issue? (we can't run
that command on our clients desktops before we build our build scripts
- anyway, I've put it down to one of those weird Ant classpath
issues.)
In summary:
Problems I can see and would like some help on are:
- multiple exception messages
- fault operations with no name
- the ability to generate client code with complex data types before
the EAR is deployed.
Could the product team add
- a clean way to add in schema datatypes without having to manually
hack the web-services.xml file.
I know this has been quite a long email, but it has been months in the
making. Anyone's time would be greatly appreciated.
Mark Mansour
Agentis Software
[email protected]

Hi Mark,
From your base post:
My next problem deals with the validity of the WSDL. I am seeing that
the WSDL created has exceptions defined multiple times. I saw a
message from Manjo saying that it looked like a bug. I agree and
would like to get a copy of the patch. On a more significant note,
when is either SP2 or 7.1 due for release?I would recommend starting here with support since getting valid WSDL seems to be the root of most of
your issues.
Concerning the upcoming release, I believe it is scheduled for late this quarter; contact Michael
([email protected]) for more information.
Also, at the bottom of this post:
I would just like to see an automated way to do this (I've had to write my own
utility to do this for me :(Does the autotype ant task help in this situation? Have you taken a look at this?
http://e-docs.bea.com/wls/docs70/webserv/anttasks.html#1080062
Thanks,
Bruce
Mark Mansour wrote:
Hiya Bruce,
I will try and get some time to follow this up with the support people too.
In response:
Problems I can see and would like some help on are:
- multiple exception messages
In your client code, you can set the following property to avoid the exceptionmessages so that the typemapping
registry can be setup.
//dont parse wsdl till we set the typemapping
System.setProperty( "weblogic.webservice.servicenamechecking","false" );
This is not a client issue. The WSDL is generating incorrect WSDL. Here is a
little snippet :
<message name="AgentisException" >
<part name="AgentisException" xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
<message name="setTraceLevel" >
<part name="agentKey" xmlns:partns="java:net.agentis.apml.runtime" type="partns:AgentKey"
/>
<part name="intVal" xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:int"
/>
</message>
<message name="AgentisException" >
<part name="AgentisException" xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
As you can see the AgentisException is defined twice (in my real WSDL it is redefined
every time a method has the AgentisException in its interface (which in my case
is 5 times))
- fault operations with no nameI believe the fault issues that you have raised have been addressed in the upcomingrelease that will be
available for beta testing shortly. Contact [email protected] if you
want to participate in the beta.
great. Is there any ETA on the final release date?
- the ability to generate client code with complex data types before
the EAR is deployed.
There is an example to show how to do this: http://dev2dev.bea.com/direct/webservice/dyncmplx.zip
Unfortunately this doesn't solve my problem. I still don't have an EAR or WSDL
file from which I can generate a client to be included in the final EAR file that
gets deployed to the server. My original post explains this a bit better.
Could the product team add
- a clean way to add in schema datatypes without having to manually
hack the web-services.xml file.
Take a look at http://dev2dev.bea.com/direct/webservice/wswa.html#qz50 and others
in this area.
This was more in reference to the building of the web services in the first place
rather than registering custom datatypes at runtime. The manual procedure is
documented at http://edocs.bea.com/wls/docs70/webserv/customdata.html#1058102,
I would just like to see an automated way to do this (I've had to write my own
utility to do this for me :(
Hope this helps,
Bruce
Thanks Bruce.
Mark

Inbound Service Interface without Input Request Message

Is it possible to create an Inbound Service Interface without Input Request Message? We are trying to create a web service to get all records from a database table hence no input parameter is needed. We have tried in both XI 7.0 and PI 7.1 but couldn't do it. Is this scenario not supported by ESR or am I missing something? Any hint will be appreciated.
Regards,
Jiannan

In the scenario I described in my initial post the table structure is only needed in the response message to receive the data.
For a web service generated from a RFC function module using the service creation wizard (SE80) a table parameter is automatically included in the request message. I can understand this as the wizard can not figure out if the table parameter is needed in the request message or not.
I have tried to use the service creation wizard to generate a web service from the function module RFCPING that has no input or output parameters. As shown in below WSDL segment the WSDL does allow not having any input or output parameters.
- <wsdl:types>
- <xsd:schema attributeFormDefault="qualified" targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style">
- <xsd:element name="Rfcping">
- <xsd:complexType>
<xsd:sequence />
</xsd:complexType>
</xsd:element>
- <xsd:element name="RfcpingResponse">
- <xsd:complexType>
<xsd:sequence />
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
- <wsdl:message name="Rfcping">
<wsdl:part name="parameters" element="tns:Rfcping" />
</wsdl:message>
- <wsdl:message name="RfcpingResponse">
<wsdl:part name="parameter" element="tns:RfcpingResponse" />
</wsdl:message>
Thanks,
Jiannan

How to use an ABAP exception as a web service fault

Hi experts,
I have created a web service out of an ABAP function module, using the SAP standard wizard for web services. The ABAP function has some exceptions defined. Now the question is: How can I "translate" these ABAP function exceptions to web service faults?
In the WSDL file I can see that the web service defines the faults, but they are not part of the web service operation (in the WSDL file). So when I load the definition into JDeveloper, the faults are not recognized.
Any ideas what I am missing here?
Thanks in advance!
Kind regards, Matthias

Exceptions from SAP function module are not translated as web service fault message, this is a standard behaviour due among other to the fact that exceptions are not "in line" with the definition a web service fault message.
Usually when you want to use a standard SAP function module and expose it as web service, you need to "wrap-it" into a new Z function module.
In that new function module you must capture the exceptions and convert them into a web service fault message structure (usually containing error type, text and number)
Karim

Fault element name issues

Back in January I noticed a post concerning generated WSDL files and fault
element not containing a required attribute "name".
I seem to be having the same problem in WLS8.1
Can this be possible since it was fixed in version 7SP2?
After I generate the web service, when I try to generate a JAXRPC client
(via the JavaSoft web services toolkit), it complains that the WSDL file is
invalid because there are <FAULT> elements without name attributes.
Also, I'm having a problem using the clientgen Ant task, its having an error
generating types. This worked 2 days ago when I was running 8.1beta, but
since I upgraded to 8.1 it no longer works.
M
"Bruce Stephens" <[email protected]> wrote in message
news:[email protected]...
Hi Mark,
From your base post:
My next problem deals with the validity of the WSDL. I am seeing that
the WSDL created has exceptions defined multiple times. I saw a
message from Manjo saying that it looked like a bug. I agree and
would like to get a copy of the patch. On a more significant note,
when is either SP2 or 7.1 due for release?I would recommend starting here with support since getting valid WSDLseems to be the root of most of
your issues.
Concerning the upcoming release, I believe it is scheduled for late thisquarter; contact Michael
([email protected]) for more information.
Also, at the bottom of this post:
I would just like to see an automated way to do this (I've had to write
my own
utility to do this for me :(Does the autotype ant task help in this situation? Have you taken a lookat this?
http://e-docs.bea.com/wls/docs70/webserv/anttasks.html#1080062
Thanks,
Bruce
Mark Mansour wrote:
Hiya Bruce,
I will try and get some time to follow this up with the support people
too.
>>
In response:
Problems I can see and would like some help on are:
- multiple exception messages
In your client code, you can set the following property to avoid the
exception
messages so that the typemapping
registry can be setup.
//dont parse wsdl till we set the typemapping
System.setProperty(
"weblogic.webservice.servicenamechecking","false" );
>>>
>>
This is not a client issue. The WSDL is generating incorrect WSDL.Here is a
little snippet :
<message name="AgentisException" >
<part name="AgentisException"xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
<message name="setTraceLevel" >
<part name="agentKey"xmlns:partns="java:net.agentis.apml.runtime" type="partns:AgentKey"
/>
<part name="intVal"xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:int"
/>
</message>
<message name="AgentisException" >
<part name="AgentisException"xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
As you can see the AgentisException is defined twice (in my real WSDL itis redefined
every time a method has the AgentisException in its interface (which inmy case
is 5 times))
- fault operations with no nameI believe the fault issues that you have raised have been addressed in
the upcoming
release that will be
available for beta testing shortly. Contact [email protected]
if you
want to participate in the beta.
great. Is there any ETA on the final release date?
- the ability to generate client code with complex data types before
the EAR is deployed.There is an example to show how to do this:
http://dev2dev.bea.com/direct/webservice/dyncmplx.zip
>>
Unfortunately this doesn't solve my problem. I still don't have an EARor WSDL
file from which I can generate a client to be included in the final EARfile that
gets deployed to the server. My original post explains this a bitbetter.
>>
Could the product team add
- a clean way to add in schema datatypes without having to manually
hack the web-services.xml file.
Take a look at http://dev2dev.bea.com/direct/webservice/wswa.html#qz50
and others
in this area.
This was more in reference to the building of the web services in thefirst place
rather than registering custom datatypes at runtime. The manualprocedure is
documented athttp://edocs.bea.com/wls/docs70/webserv/customdata.html#1058102,
I would just like to see an automated way to do this (I've had to writemy own
utility to do this for me :(
Hope this helps,
Bruce
Thanks Bruce.
Mark

Please try 8.1 sp1, it is strictly wsdl spec complaint. It generates
<fault> with name.. Clientgen requires fault name to correctly parse wsdl.
thanks,
-Neal
"Mark Fine" <[email protected]> wrote in message
news:[email protected]...
Back in January I noticed a post concerning generated WSDL files and fault
element not containing a required attribute "name".
I seem to be having the same problem in WLS8.1
Can this be possible since it was fixed in version 7SP2?
After I generate the web service, when I try to generate a JAXRPC client
(via the JavaSoft web services toolkit), it complains that the WSDL fileis
invalid because there are <FAULT> elements without name attributes.
Also, I'm having a problem using the clientgen Ant task, its having anerror
generating types. This worked 2 days ago when I was running 8.1beta, but
since I upgraded to 8.1 it no longer works.
M
"Bruce Stephens" <[email protected]> wrote in message
news:[email protected]...
Hi Mark,
From your base post:
My next problem deals with the validity of the WSDL. I am seeing that
the WSDL created has exceptions defined multiple times. I saw a
message from Manjo saying that it looked like a bug. I agree and
would like to get a copy of the patch. On a more significant note,
when is either SP2 or 7.1 due for release?I would recommend starting here with support since getting valid WSDLseems to be the root of most of
your issues.
Concerning the upcoming release, I believe it is scheduled for late thisquarter; contact Michael
([email protected]) for more information.
Also, at the bottom of this post:
I would just like to see an automated way to do this (I've had to write
my own
utility to do this for me :(Does the autotype ant task help in this situation? Have you taken a
look
at this?
http://e-docs.bea.com/wls/docs70/webserv/anttasks.html#1080062
Thanks,
Bruce
Mark Mansour wrote:
Hiya Bruce,
I will try and get some time to follow this up with the support people
too.
In response:
Problems I can see and would like some help on are:
- multiple exception messages
In your client code, you can set the following property to avoid the
exception
messages so that the typemapping
registry can be setup.
//dont parse wsdl till we set the typemapping
System.setProperty(
"weblogic.webservice.servicenamechecking","false" );
>
This is not a client issue. The WSDL is generating incorrect WSDL.Here is a
little snippet :
<message name="AgentisException" >
<part name="AgentisException"
xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
<message name="setTraceLevel" >
<part name="agentKey"xmlns:partns="java:net.agentis.apml.runtime" type="partns:AgentKey"
/>
<part name="intVal"
xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:int"
/>
</message>
<message name="AgentisException" >
<part name="AgentisException"
xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
As you can see the AgentisException is defined twice (in my real WSDL
it
is redefined
every time a method has the AgentisException in its interface (which
in
my case
is 5 times))
- fault operations with no nameI believe the fault issues that you have raised have been addressed
in
the upcoming
release that will be
available for beta testing shortly. Contact [email protected]
if you
want to participate in the beta.
great. Is there any ETA on the final release date?
- the ability to generate client code with complex data types
before
the EAR is deployed.There is an example to show how to do this:
http://dev2dev.bea.com/direct/webservice/dyncmplx.zip
Unfortunately this doesn't solve my problem. I still don't have an
EAR
or WSDL
file from which I can generate a client to be included in the final
EAR
file that
gets deployed to the server. My original post explains this a bitbetter.
Could the product team add
- a clean way to add in schema datatypes without having to manually
hack the web-services.xml file.Take a look at
http://dev2dev.bea.com/direct/webservice/wswa.html#qz50
and others
in this area.
This was more in reference to the building of the web services in thefirst place
rather than registering custom datatypes at runtime. The manualprocedure is
documented at
http://edocs.bea.com/wls/docs70/webserv/customdata.html#1058102,
I would just like to see an automated way to do this (I've had to
write
my own
utility to do this for me :(
Hope this helps,
Bruce
Thanks Bruce.
Mark

Where is the Web Service fault in the WSDL definition?

Hi all,
I have created a Web Service out of function module, using the SAP standard wizard. The creation went fine, I can receive the WSDL file via the SOAMANAGER application. But: In this WSDL file it seems that the Web Service faults (i.e. the exceptions of the underlying function module) are not part of the "wsdl:operation" definition (even if they and their format are defined in that file).
Is that a bug or do I miss something here?
How are the faults integrated in the response definition of the service?
Thanks in advance for your help!
Kind regards, Matthias

solved, see SAP note 1270688

Accepting a SOAP message that contains fault elements

Hi,
I am trying to create a webservice that will accept a valid soap messages that
contains faults. Actual functionality required is to accept a valid soap message
with or without faults. For this, I created separate methods in my java class
(one for normal flow and one that will handle fault elements) that implements
my web service. I need to manipulate the soap message for both cases. Hence, I
created separate handlers to do this task. I created two handler chains in my
web-services.xml one for handling soap messages that contains faults and one for
handling soap messages that doesn't contain faults. The web services was successfully
deployed and works fine for soap messages that doesn't contain fault. But, if
I send a soap message with faults the client (that calls my webservice) is not
even hitting my web service. It gets a HTTP
500. Can anybody help me on this ?
Thanks,
Ganesh Balachandran

Hi Ganesh,
Which version of weblogic server you are using? Can you turn on verbose in
client side? You can give a "-Dweblogic.webservice.verbose=true" to client
side JVM. We need to see what your soap message with fault looks like.
Thanks,
-Neal
"Ganesh" <[email protected]> wrote in message
news:[email protected]..
>
Hi,
I am trying to create a webservice that will accept a valid soap messagesthat
contains faults. Actual functionality required is to accept a valid soapmessage
with or without faults. For this, I created separate methods in my javaclass
(one for normal flow and one that will handle fault elements) thatimplements
my web service. I need to manipulate the soap message for both cases.Hence, I
created separate handlers to do this task. I created two handler chains inmy
web-services.xml one for handling soap messages that contains faults andone for
handling soap messages that doesn't contain faults. The web services wassuccessfully
deployed and works fine for soap messages that doesn't contain fault. But,if
I send a soap message with faults the client (that calls my webservice) isnot
even hitting my web service. It gets a HTTP
500. Can anybody help me on this ?
Thanks,
Ganesh Balachandran

Missing namespace on XAI Inbound Service Fault Element

Similar Messages

Maybe you are looking for