Problem when consuming web service on WIndows authentication applcation

Hi,
I am having a tough time in consuming web services on a
Windows authentication IIS server.
In one of my application I have created web services and
consuming those web services from my another application.
If I turned off the Windows authentication everything works
fine, but If I turned on the Windows authentication web services
stop working.
Has anyone encountered such error while working with web
services on Windows authentication server.
Attach Code
Could not perform web service invocation "funGetCustomer".
Here is the fault returned when invoking the web service
operation:
AxisFault
faultCode: {
http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (401)Unauthorized
faultActor:
faultNode:
faultDetail:
{}:return code: 401
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "
http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>You are not authorized
to view this page</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html;
charset=Windows-1252">
<STYLE type="text/css">
BODY { font: 8pt/12pt verdana }
H1 { font: 13pt/15pt verdana }
H2 { font: 8pt/12pt verdana }
A:link { color: red }
A:visited { color: maroon }
</STYLE>
</HEAD><BODY><TABLE width=500 border=0
cellspacing=10><TR><TD>
<h1>You are not authorized to view this page</h1>
You do not have permission to view this directory or page
using the credentials that you supplied because your Web browser is
sending a WWW-Authenticate header fi...

You could try switching the HTTP transport provided in the
Apache Axis embedded in ColdFusion to "CommonsHTTPSender".
See this blog post:
http://tjordahl.blogspot.com/2007/03/apache-axis-and-commons-httpclient.html

Similar Messages

Problem consuming web service with basic authentication

Hello,
I've set up a web service with basic authentication. Although I have to log in before being able to open the overview page of the web service in the Web Service Navigator, the response I get after sending a request is:
Authority check failed
I get this response in the Web Service Navigator as well as when consuming the web service via standalone proxy classes.
The following is strange, too: It is not possible to change authentication in the generated logical port. It is set to "none". I changed it via the XML file where I added the properties "AuthenticationMethod" (value "BasicAuth") and "AuthenticationMechanism" (value "HTTP"). But I got the above response anyway.
Thanks for your help!
Regards

I used basic authentication for my web service.
I was able to obtain a hardcopy of the logfiles in the meantime. The invocation of the web service is stored there with the following error messages:
<i>SOAP Runtime: Exception message: Schwerer Prozessierungsfehler macht eine SOAP-Fault-Behandlung erforderlich
SOAP Runtime: SOAP Fault exception occurred in program CL_SOAP_RUNTIME_SERVER========CP in include CL_SOAP_RU NTIME_SERVER... [the picture is cut here]</i>
In addition to that I found a thread in SDN that dealt with exactly the same problem:
Web Service Homepage: Authority check failed
But I have the same problem like Kimberly Carmack (the last post on the second page). We do not have that role in our system.

Problem at Consume WEB Service in ABAP

hello!!
I tell them my problem, is to create a web service from the SE80, which could be used properly.
Then there was a change of server, which migrated to the developments and the web service is recreation, but this can not be consumed.
now I need help, is where do I indicate that the basis so that they can return to consume web services, what services or settings should be activated.
any suggestion or help are welcome.
The ECC system is a 5 AS ABAP only.
from now, I appreciate any help or guidance I can get.

What is the problem? Are all the services active in SICF for web services and how is the web service being consumed is it through a wsdl file ?

How to reference complex data type when consuming web services in WAS 620?

In WAS 620, I tried to consume a web service in ABAP. I was successful when the web service returned one or more simple data type. But when the web service is changed to return a complex data type (eg. a structure with 3 elements), the call to the web service did not return anything.
Do any of you know how to reference the individual element in the structure of an output parameter in a web service? I use the add_parameter method of the CSoapDocument class to identify the output parameters.
Here is part of the WSDL file:
<?xml version="1.0" encoding="UTF-8" ?>
- <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:s0="urn:sap-com:document:sap:rfc:functions" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="urn:sap-com:document:sap:rfc:functions">
- <types>
- <xsd:schema targetNamespace="urn:sap-com:document:sap:rfc:functions">
- <xsd:element name="Z_SRM_SOAP_TEST_COMPLEX">
- <xsd:complexType>
- <xsd:all>
- <xsd:element name="INTEXT">
- <xsd:simpleType>
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
- <xsd:element name="Z_SRM_SOAP_TEST_COMPLEX.Response">
- <xsd:complexType>
- <xsd:all>
<xsd:element name="OUTTEXT" type="s0:ZSRM_TEST_STRUCT" />
</xsd:all>
</xsd:complexType>
</xsd:element>
- <xsd:complexType name="ZSRM_TEST_STRUCT">
- <xsd:sequence>
- <xsd:element name="ELEMENT1" minOccurs="0">
- <xsd:simpleType>
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
- <xsd:element name="ELEMENT2" minOccurs="0">
- <xsd:simpleType>
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
- <xsd:element name="ELEMENT3" minOccurs="0">
- <xsd:simpleType>
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>

Hi,
[email protected] is my id and one more thing u by looking at the wsdl file u can know what al the parameters we have to give to the webservice so try it out also.
Regards,
Sirisha.

Basic http authentication not working when consuming Web Service in BPEL.

Hi,
I am consuming an AXIS Web Service from BPEL 10.1.3. The Web Service uses basic http
authentication so we need a way to get username and password into the http
header. In the Oracle BPEL Process Manager Administrator's Guide 10g
(10.1.3.1.0) section 1.3.4.1 HTTP Basic Authentication (10.1.2.0.2) is stated
that this can be done using the properties httpUsername and httpPassword. I
have set the 2 for the partner link in bpel.xml but username and password does
not get in to the http header. Has anybody got an idea?
Regards Pete

I'm having the same sorts of problems with 10.1.3.1.0. I've got a deployed BPEL suitcase that's trying to hit a BASIC AUTH-secured web service running on a WebLogic 8.1 server. I've set up my partner link according to the documentation, and the BPEL console Descriptor tab even shows the parameters correctly:
partnerLinkBindings
client
     wsdlLocation      awardService.wsdl
spsAwardSubmitPartnerLink
     basicHeaders      credentials
     basicUsername      ko1
     basicPassword      xxxxx
     wsdlLocation      IAwardDraftServiceRef1.wsdl
However, when I funnel the resultant call to the endpoint specified in IAwardDraftServiceRef1.wsdl, none of the fields I would expect show up in the HTTP header:
POST /pd2WebServices/service/IAwardDraftService HTTP/1.1
Host: vm-orcl-app-srv:4444
Connection: Keep-Alive, TE
TE: trailers, deflate, gzip, compress
User-Agent: Oracle HTTPClient Version 10h
SOAPAction: ""
Accept-Encoding: gzip, x-gzip, compress, x-compress
Content-type: text/xml; charset=UTF-8
Content-length: 3800
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><env:Body><IAwardDraftSubmitNew xmlns="http://www.caci.com/pd2/pub">
<IAwardDraft>
<accessController/>
<agreementEndDate/>
Is there some other configuration piece I'm missing?? I've tried the other variation using httpBasicHeaders, with the same results. I even noted that the "Oracle® BPEL Process Manager Administrator's Guide" says that "Starting with Oracle BPEL Process Manager release 10.1.3, all partner link properties are automatically propagated into the HTTP header." I've tried putting "extra" parms in the partner link bindings, but they don't show up either.
What am I missing??
Thanks,
Mike

Have problem when generate Web Service from bapi function

Dear all,
Please kindly help me about generating Web Service from BAPI function, It does not success only this attached function.
I have done so many function without any problems.
I found 1 case that I use specific variable to be an import/ export then, it can't create as well.
As for this one, I try so many changes but I can't success it as well.
This is my function on R/3 4.6C, Dot net connector 2.0, Dot net Frame Work 1.1.
FUNCTION Z_BAPI_ATTACHMENT_CREATE.
""Local interface: Type: Remote-enabled module
*" IMPORTING
*"     VALUE(P_BOTYPE) LIKE BORIDENT-OBJTYPE
*"     VALUE(P_BO_ID) LIKE BORIDENT-OBJKEY
*"     VALUE(P_MSGTYP) LIKE SOFM-DOCTP
*"     VALUE(P_DOCTY) LIKE BORIDENT-OBJTYPE
*"     VALUE(P_RELTYP) LIKE BRELTYP-RELTYPE
*"     VALUE(P_FNAME) LIKE RLGRAP-FILENAME
*"     VALUE(P_OBJDES) TYPE SO_OBJ_DES
*" EXPORTING
*"     VALUE(RETURNMESSAGE) TYPE CHAR50
INCLUDE : <cntn01>.
P_BOTYPE TYPE BORIDENT-OBJTYPE DEFAULT 'BUS2105'
P_BO_ID   TYPE BORIDENT-OBJKEY
P_MSGTYPE TYPE SOFM-DOCTP DEFAULT 'URL'
P_DOCTY   TYPE BORIDENT-OBJTYPE DEFAULT 'MESSAGE'
P_RELTYP TYPE BRELTYP-RELTYPE DEFAULT 'ATTA'
P_FNAME   TYPE RLGRAP-FILENAME
P_OBJDES TYPE SO_OBJ_DES
TYPES: BEGIN OF ty_message_key,
foltp TYPE so_fol_tp,
folyr TYPE so_fol_yr,
folno TYPE so_fol_no,
doctp TYPE so_doc_tp,
docyr TYPE so_doc_yr,
docno TYPE so_doc_no,
fortp TYPE so_for_tp,
foryr TYPE so_for_yr,
forno TYPE so_for_no,
END OF ty_message_key.
DATA : lv_message_key TYPE ty_message_key.
DATA : lo_message TYPE swc_object.
DATA : lt_doc_content TYPE STANDARD TABLE OF soli-line
WITH HEADER LINE.
First derive the Attachment's ( MESSAGE )document type.
p_docty = 'MESSAGE'.
CASE p_reltyp.
In case of URls
WHEN 'URL'.
    p_msgtyp = 'URL'.
In case of Notes / Private Notes
WHEN 'NOTE' OR 'PNOT'.
    p_msgtyp = 'RAW'.
WHEN 'ATTA'.
Take given parameter e.g. 'DOC', 'PDF' etc.
P_MSGTYP = 'EXT'.
WHEN OTHERS.
....exit
    EXIT.
ENDCASE.
Create an initial instance of BO 'MESSAGE' - to call the
instance-independent method 'Create'.
swc_create_object lo_message 'MESSAGE' lv_message_key.
define container to pass the parameter values to the method call
in next step.
swc_container lt_message_container.
Populate container with parameters for method
swc_set_element lt_message_container 'DOCUMENTTITLE' p_objdes.
swc_set_element lt_message_container 'DOCUMENTLANGU' 'E'.
swc_set_element lt_message_container 'NO_DIALOG' 'X'.
swc_set_element lt_message_container 'DOCUMENTNAME' p_docty.
swc_set_element lt_message_container 'DOCUMENTTYPE' p_msgtyp.
In case of URLs..it should be concatenated with &KEY& in the begining.
CASE p_msgtyp.
WHEN 'URL'.
lt_doc_content = '&KEY&http://www.rmtiwari.com' .
    CONCATENATE '&KEY&' p_fname INTO lt_doc_content.
    APPEND lt_doc_content.
In case of Notes or Private Notes, get the data from files on appl
server or from wherever(? - remember background).
WHEN 'RAW'.
    lt_doc_content = p_fname.
    APPEND lt_doc_content.
In case of PC File attachments
WHEN OTHERS.
    OPEN DATASET p_fname FOR INPUT IN BINARY MODE.
    IF sy-subrc EQ 0.
      DO.
        READ DATASET p_fname INTO lt_doc_content.           "2 of 27
        IF sy-subrc EQ 0.
          APPEND lt_doc_content.
        ELSE.
          EXIT.
        ENDIF.
      ENDDO.
      CLOSE DATASET p_fname.
    ENDIF.
ENDCASE.
'DocumentContent' is a multi-line element ( itab ).
swc_set_table lt_message_container 'DocumentContent' lt_doc_content.
Size is required in case of File attachments
DATA : lv_doc_size TYPE i.
DATA : l_file_lines TYPE i.
DESCRIBE TABLE lt_doc_content LINES l_file_lines.
READ TABLE lt_doc_content INDEX l_file_lines.
lv_doc_size = ( 255 * ( l_file_lines - 1 ) ) +
STRLEN( lt_doc_content ).
swc_set_element lt_message_container 'DOCUMENTSIZE' lv_doc_size .
Refresh to get the reference of create 'MESSAGE' object for attachment
swc_refresh_object lo_message.
swc_call_method lo_message 'CREATE' lt_message_container.
Get Key of new object
swc_get_object_key lo_message lv_message_key.
Now we have attachment as a business object instance. We can now
attach it to our main business object instance.
Create main BO object_a
data: LO_IS_OBJECT_A type SIBFLPORB. "type SIBFLPORB is unknown, so I
DATA: lo_is_object_a TYPE borident.
lo_is_object_a-objkey = p_bo_id.
lo_is_object_a-objtype = p_botype.
LO_IS_OBJECT_A-CATID = 'BO'.
Create attachment BO object_b
data: LO_IS_OBJECT_B type SIBFLPORB. "type SIBFLPORB is unknown
DATA: lo_is_object_b TYPE borident.
lo_is_object_b-objkey = lv_message_key.
lo_is_object_b-objtype = p_docty.
LO_IS_OBJECT_B-CATID = 'BO'.
*TRY.
*CALL METHOD CL_BINARY_RELATION=&gtCREATE_LINK
EXPORTING
IS_OBJECT_A = LO_IS_OBJECT_A
IS_OBJECT_B = LO_IS_OBJECT_B
IP_RELTYPE = P_RELTYP.
CALL FUNCTION 'BINARY_RELATION_CREATE'
EXPORTING
    obj_rolea    = lo_is_object_a
    obj_roleb    = lo_is_object_b
    relationtype = p_reltyp
EXCEPTIONS
    OTHERS       = 1.
Check if everything OK...who cares!!
COMMIT WORK.
if sy-subrc = 0.
RETURNMESSAGE = 'S-Success'.
else.
RETURNMESSAGE = 'E-Error'.
endif.
ENDFUNCTION.
Thanks in advance,
Benjawan
Edited by: Nitipat Chadchavalpanichaya on Oct 20, 2008 9:02 AM

There is no any error message show up. It just the class
Z_BAPI_ATTACHMENT_CREATE doesn't create autometically as normal. I showed you as below.
That means I can't call class z_bapi_attachment_create.
' <autogenerated>
'     This code was generated by a SAP. NET Connector Proxy Generator Version 2.0
'     Created at 21/10/2551
'     Created from Windows
'     Changes to this file may cause incorrect behavior and will be lost if
'     the code is regenerated.
' </autogenerated>
Imports System
Imports System.Text
Imports System.Collections
Imports System.ComponentModel
Imports System.Runtime.InteropServices
Imports System.Xml.Serialization
Imports System.Web.Services
Imports System.Web.Services.Description
Imports System.Web.Services.Protocols
Imports SAP.Connector
'@ <summary>
'@ Client SAP proxy class
'@ </summary>
<WebServiceBinding(Name:="dummy.Binding", Namespace:="urn:sap-com:document:sap:rfc:functions")> _
Public Class PRAttachment
    Inherits SAPClient
    '@ <summary>
    '@ Initializes a new PRAttachment.
    '@ </summary>
    Public Sub New()
    End Sub
    '@ <summary>
    '@ Initializes a new PRAttachment with a new connection based on the specified connection string.
    '@ </summary>
    '@ <param name="connectionString">A connection string (e.g. RFC or URL) specifying the system where the proxy should connect to.</param>
    Public Sub New(ByVal ConnectionString As String)
      MyBase.New(ConnectionString)
    End Sub
    '@ <summary>
    '@ Initializes a new PRAttachment and adds it to the given container.
    '@ This allows automated connection mananged by VS component designer:
    '@ If container is disposed, it will also dispose this SAPClient instance,
    '@ which will dispose a contained connection if needed.
    '@ </summary>
    '@ <param name="Cont">The container where the new SAPClient instance is to be added.</param>
    Public Sub New(ByVal Cont As Container)
      MyBase.New(Cont)
    End Sub
End Class

Problem with consuming web services in Flex

So i'm trying to set up a basic flex application to consume a
web service (POJO exposed with axis2). Here's the WSDL:
<wsdl:definitions xmlns:wsdl="
http://schemas.xmlsoap.org/wsdl/"
xmlns:axis2="
http://ws.apache.org/axis2"
xmlns:mime="
http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:http="
http://schemas.xmlsoap.org/wsdl/http/"
xmlns:ns0="
http://webservices.emailcenter.pas/xsd"
xmlns:soap12="
http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:ns1="
http://org.apache.axis2/xsd"
xmlns:xs="
http://www.w3.org/2001/XMLSchema"
xmlns:soap="
http://schemas.xmlsoap.org/wsdl/soap/"
targetNamespace="
http://ws.apache.org/axis2">
<wsdl:types>
<xs:schema xmlns:ns="
http://webservices.emailcenter.pas/xsd"
targetNamespace="
http://webservices.emailcenter.pas/xsd"
elementFormDefault="unqualified"
attributeFormDefault="unqualified">
<xs:element name="getTime">
<xs:complexType />
</xs:element>
<xs:element name="getTimeResponse">
<xs:complexType>
<xs:sequence>
<xs:element type="xs:string" name="return" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</wsdl:types>
<wsdl:message name="getTimeMessage">
<wsdl:part element="ns0:getTime" name="part1" />
</wsdl:message>
<wsdl:message name="getTimeResponse">
<wsdl:part element="ns0:getTimeResponse" name="part1"
/>
</wsdl:message>
<wsdl:portType name="SimpleServicePortType">
<wsdl:operation name="getTime">
<wsdl:input message="axis2:getTimeMessage" />
<wsdl:output message="axis2:getTimeResponse" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding type="axis2:SimpleServicePortType"
name="SimpleServiceSOAP11Binding">
<soap:binding style="document" transport="
http://schemas.xmlsoap.org/soap/http"
/>
<wsdl:operation name="getTime">
<soap:operation style="document" soapAction="urn:getTime"
/>
<wsdl:input>
<soap:body namespace="
http://ws.apache.org/axis2"
use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body namespace="
http://ws.apache.org/axis2"
use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding type="axis2:SimpleServicePortType"
name="SimpleServiceSOAP12Binding">
<soap12:binding style="document" transport="
http://schemas.xmlsoap.org/soap/http"
/>
<wsdl:operation name="getTime">
<soap12:operation style="document"
soapAction="urn:getTime" />
<wsdl:input>
<soap12:body namespace="
http://ws.apache.org/axis2"
use="literal" />
</wsdl:input>
<wsdl:output>
<soap12:body namespace="
http://ws.apache.org/axis2"
use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding type="axis2:SimpleServicePortType"
name="SimpleServiceHttpBinding">
<http:binding verb="POST" />
<wsdl:operation name="getTime">
<http:operation location="getTime" />
<wsdl:input>
<mime:content type="text/xml" />
</wsdl:input>
<wsdl:output>
<mime:content type="text/xml" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SimpleService">
<wsdl:port binding="axis2:SimpleServiceSOAP11Binding"
name="SimpleServiceSOAP11port0">
<soap:address location="
http://10.1.1.149:8080/axis2/services/SimpleService"
/>
</wsdl:port>
<wsdl:port binding="axis2:SimpleServiceSOAP12Binding"
name="SimpleServiceSOAP12port0">
<soap12:address location="
http://10.1.1.149:8080/axis2/services/SimpleService"
/>
</wsdl:port>
<wsdl:port binding="axis2:SimpleServiceHttpBinding"
name="SimpleServiceHttpport0">
<http:address location="
http://10.1.1.149:8080/axis2/rest/SimpleService"
/>
</wsdl:port>
</wsdl:service>
the code for my application is very simple and
straightforward:
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute" creationComplete="ss.getTime()">
<mx:WebService id="ss" wsdl="
http://10.1.1.149:8080/EmailCenter/services/SimpleService?wsdl">
<mx:operation name="getTime"/>
</mx:WebService>
<mx:DataGrid
dataProvider="{ss.getTime.lastResult}"></mx:DataGrid>
</mx:Application>
when I try to consume this in my flex application I keep
getting the following error:
[RPC Fault faultString="Required parameter 'getTime' not
found in input arguments." faultCode="Client.Input"
faultDetail="null"]
at
mx.rpc.soap::Operation/mx.rpc.soap:Operation::createFaultEvent()
at mx.rpc.soap::Operation/
http://www.adobe.com/2006/flex/mx/internal::invokePendingCall()
at mx.rpc.soap::Operation/
http://www.adobe.com/2006/flex/mx/internal::invokeAllPending()
at mx.rpc.soap::WebService/::unEnqueueCalls()
at mx.rpc.soap::WebService/
http://www.adobe.com/2006/flex/mx/internal::wsdlHandler()
at
flash.events::EventDispatcher/flash.events:EventDispatcher::dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at mx.rpc.soap::WSDLParser/dispatchEvent()
at mx.rpc.soap::WSDLParser/::parseCompleted()
at mx.rpc.soap::WSDLParser/
http://www.adobe.com/2006/flex/mx/internal::httpResultHandler()
at
flash.events::EventDispatcher/flash.events:EventDispatcher::dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at mx.rpc::AbstractInvoker/
http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent()
at mx.rpc::AbstractInvoker/
http://www.adobe.com/2006/flex/mx/internal::resultHandler()
at mx.rpc::Responder/result()
at mx.rpc::AsyncRequest/acknowledge()
at ::DirectHTTPMessageResponder/completeHandler()
at
flash.events::EventDispatcher/flash.events:EventDispatcher::dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at flash.net::URLLoader/flash.net:URLLoader::onComplete()
Any advice anyone could give would be wonderful. I'm pretty
new at this flex stuff but I feel like the problem may be with my
WSDL?

perhaps you missed this step:
--> Modify the code and add Credentials before calling the web method:
Public
SubMain()
Dim
ws As NewService1
ws.Credentials =
New System.Net.NetworkCredential("user name",
"password",
"domain name")
MsgBox("Square
of 2 = "& ws.Square(2))
Dts.TaskResult = Dts.Results.Success
End
Sub
Arthur
MyBlog
Twitter

Wrong data when consuming web service via ABAP

Dear all,
we tried to consume a web service via ABAP and used one of the various existing how-to papers from the internet in order to develop everything.
The development was not that difficult, but when we now execute our ABAP, we noticed that
- the first 100 returned rows from the webservice are completely correct
- then we receive 10-15 completely incorrect rows (empty fields, redundant lines, etc.)
- the rest of the data (60 records) is correct again
As we nearly all objects have been generated automatically via SE80, I do not really know where this problem might come from. We double checked the original data and there everything is correct.
Any ideas?
Thanks for your feedback,
Andreas

Marcelo Almeida wrote:
> You can use Logial port for it in LPCONFIG ( Transaction). See this examplo Below:
>
> TRY.
>
> CREATE OBJECT my_proxy
> EXPORTING
> logical_port_name = 'LP01'.
> CATCH cx_ai_system_fault.
> ENDTRY.
>
> TRY.
> input-airline_id = p_carrid.
> input-connection_id = p_connid.
> input-flight_date = p_fldate.
>
> CALL METHOD my_proxy->flight_get_detail
> EXPORTING
> input = input
> IMPORTING
> output = output.
> CATCH cx_ai_system_fault.
> CATCH cx_ai_application_fault.
> ENTRY.
>
> Its necessary create a connection in SM59 (type H) and setting in the call parameters logical port (LPCONFIG).
Hi,
thanks for your answer. It´s working!
Cheers,
Andy

Get error (There is an error in XML document (3, 4)) when consuming web service HelpDesk_QueryList_Service with New-WebServiceProxy

Dear all,
I'm using the powershell cmdlt New-WebServiceProxy to query ITSM incidents. I'm able to get the WSDL definition ..
$uri='http://pitsm/arsys/WSDL/public/pitsmapp/HPD_IncidentInterface_WS'
$myitsm=New-WebServiceProxy -Uri $uri -Namespace ITSM -Verbose true
$auth= New-Object ITSM.AuthenticationInfo
$cred=get-credential
$auth.username=$cred.username
$auth.password= [System.Runtime.InteropServices.marshal]::PtrToStringAuto([System.Runtime.InteropServices.marshal]::SecureStringToBSTR($cred.password))
$auth.authentication="Domain Authentication"
$myitsm.AuthenticationInfoValue=$auth
$myitsm.RequestEncoding = [System.Text.Encoding]::UTF8
$tid="INC000002237910"
$criteria="'Incident Number' = ""$tid"""
When i'm consuming now the web service i get back an error messages:
$answer=$myitsm.HelpDesk_QueryList_Service($criteria,0,100)
Exception calling "HelpDesk_QueryList_Service" with "3" argument(s): "There is an error in XML document (3, 4)."
At line:1 char:1
+ $answer=$myitsm.HelpDesk_QueryList_Service($criteria,0,100)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : InvalidOperationException
Has anybody an idea what could be wrong?
Any idea how to debug the commandlet New-WebServiceProxy?
Best Regards
Chris

Hello Christian,
i know this reply is really late ;) I am actually the author of the blog post mentioned by @AnnaWY, the post she mentioned is in regards of a situation 'where everything' is how it should be. Basically, (i think) sometime administrator, or the
person who implements ITSM webservices makes an error, hence this script will not run. You will end up with that issue mentioned, in order to fix it, either you should contact the person who is responsible for that service, OR rewrite the wsdl for it yourself.
It might be a bit problematic, but, it is for sure doable, as in my latest blog post about this issue.
I am writing it here, because i also saw this page, while googling for explanation, i guess there are more people who are looking for this so here is the link to the explanation:
http://wp.me/pAXaY-ht
I hope that helps !
Regards,
Greg

Problem in consuming web service from esworkplace

Hello
I am useing CE7.2 evaluation version
I want to consume a web service from SAP workplace
I've built a process composer project then I tried to import a WSDL and chose the "service registry" option
However I keep getting the message "internal error in the services registry"
BTW u2013 I defined the "esworkplace" as the services registry in the Preferences.
Any ideas what can be the problem? Thanks.
Thanks

Hi Experts,
Please help me with this issue. I am really stuck up here.
Thanks,
Radhika

"end-of-body reached" Error when consuming web service from 10GR1

Hi all,
Im consuming a number of web services, all of which work fine apart from one which returns the error:
29266. 00000 - "end-of-body reached"
*Cause: The end of the HTTP response body was reached.
*Action: If the end of the HTTP response is reached prematurely, check if
the HTTP response terminates prematurely. Otherwise, end the
HTTP response.
I don't understand why this is happening and would really appreciate some help. I have checked the invoke procedure and there is a ' utl_http.end_response(http_resp);' call which online searching suggests can be a cause of the problem (if not used). The procedure which calls the service is:
function Events_Insert(id varchar2, pwd varchar2) return clob as
req opf_portal.pkg_call_web_services.request;
resp opf_portal.pkg_call_web_services.response;
aEventRecord varchar2(4000);
begin
req := opf_portal.pkg_call_web_services.new_request('Events_Insert', 'xmlns="<removed>');
aEventRecord:='<Options>
<EventOptionRecord>
<Comments>None</Comments>
<Quantity>1</Quantity>
<OptionID>53</OptionID>
</EventOptionRecord>
<EventOptionRecord>
<Comments>None</Comments>
<Quantity>1</Quantity>
<OptionID>53</OptionID>
</EventOptionRecord>
</Options>
<Badges>
<EventBadgeRecord>
<Company>Oracle</Company>
<JobTitle>Consultant</JobTitle>
<Name>GregCox</Name>
<EventBadgeRecord>
</Badges>
<SpecialRequirements>
<EventSpecialRequirementRecord>
<Notes>bob</Notes>
<Pvkey>110606</Pvkey>
<RequirementCode>VEG</RequirementCode>
</EventSpecialRequirementRecord>
</SpecialRequirements>
<Pvkey>110606</Pvkey>
<DelegateType>DELEGATE</DelegateType>
<EventID>524938</EventID>';
opf_portal.pkg_call_web_services.add_parameter(req, 'userid', 'xsd:string', id);
opf_portal.pkg_call_web_services.add_parameter(req, 'password', 'xsd:string', pwd);
opf_portal.pkg_call_web_services.add_parameter(req, 'aEventRecord', 'xsd:complexType', aEventRecord);
resp := opf_portal.pkg_call_web_services.invoke(req, '<removed>', '<removed>');
return resp.doc.getstringval();
end;

Incase anybody else encounters this problem, it was my XML that was invalid:
<EventBadgeRecord>
<Company>Oracle</Company>
<JobTitle>Consultant</JobTitle>
<Name>GregCox</Name>
<EventBadgeRecord>
was missing '/' in closing tag

Invalid characters when consuming web service

Morning all,
I am using Apache Axis 1.3 (yes, slightly old version) to consume a Microsoft SharePoint web service. The problem I am finding is that the returned XML contains an invalid XML character which is causing Axis to throw an exception. I have no control over the SharePoint web service so I am wondering if it is possible to somehow obtain the XML returned from SharePoint so that I can pre-process it, removing all the bad characters, before then letting Axis process as normal. Or perhaps there is a more elegant solution?
This snippet of code shows how I am currently calling the web service :
String endpoint = listSite.endsWith("/") ? listSite + "_vti_bin/Lists.asmx" : listSite + "/_vti_bin/Lists.asmx";
org.apache.axis.client.Service service = new org.apache.axis.client.Service();
org.apache.axis.client.Call call = (org.apache.axis.client.Call) service.createCall();
call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY, "http://schemas.microsoft.com/sharepoint/soap/GetListItems");
call.setSOAPVersion(org.apache.axis.soap.SOAPConstants.SOAP11_CONSTANTS);
call.setOperationName(new javax.xml.namespace.QName("http://schemas.microsoft.com/sharepoint/soap/", "GetListItems"));
call.setTargetEndpointAddress(new java.net.URL(endpoint));
call.addParameter(new javax.xml.namespace.QName("http://schemas.microsoft.com/sharepoint/soap/", "listName"),
     new javax.xml.namespace.QName("http://www.w3.org/2001/XMLSchema", "string"),
     java.lang.String.class,
     javax.xml.rpc.ParameterMode.IN);
call.addParameter(new javax.xml.namespace.QName("http://schemas.microsoft.com/sharepoint/soap/", "rowLimit"),
     new javax.xml.namespace.QName("http://www.w3.org/2001/XMLSchema", "string"),
     javax.xml.rpc.ParameterMode.IN);
call.setUsername(domain + "\\" + user);
call.setPassword(password);
call.setReturnType(org.apache.axis.Constants.XSD_SCHEMA);
Schema schema = (Schema) call.invoke(new Object[]{ listGUID, "100" });The error occurs after the call to the invoke method :
org.xml.sax.SAXParseException: Character reference "&#11" is an invalid XML characterMany Thanks,
Ben.

You're not going to like this but... get the producer (SharePoint) fixed.
Because if you get invalid XML then yes you'd have to pre-process it, which basically will entail you throwing out Axis and doing it all yourself. Which seems brutal.
Bottom line is that a webservice producing invalid XML is not in fact a webservice.

Problems when deploying web service onto Weblogic 12c

Hello everybody:
Created a web service with MyEclipse 8.5; when deploying onto Weblogic I'm facing this next problem:
Nov 3, 2012 7:44:40 AM com.sun.xml.ws.transport.http.servlet.WSServletDelegate destroy
INFO: WSSERVLET15: JAX-WS servlet destroyed
Nov 3, 2012 7:44:40 AM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextDestroyed
INFO: WSSERVLET13: JAX-WS context listener destroyed
<Nov 3, 2012 7:44:40 AM CST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1351950260963' for task '0'. Error is: 'weblogic.application.ModuleException: [HTTP:101216]Servlet: "com.sun.xml.ws.tx.webservice.member.at.CompletionCoordinatorPortTypeImpl" failed to preload on startup in Web application: "WSConsultaTrabajadorCurp".
javax.xml.ws.WebServiceException: [failed to localize] WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL()
at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1052)
at com.sun.xml.ws.wsdl.parser.DelegatingParserExtension.finished(DelegatingParserExtension.java:183)
at com.sun.xml.ws.wsdl.parser.WSDLParserExtensionFacade.finished(WSDLParserExtensionFacade.java:328)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:242)
at com.sun.xml.ws.server.EndpointFactory.getWSDLPort(EndpointFactory.java:550)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:496)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:539)
at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:183)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:135)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:54)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: com.sun.xml.ws.policy.PolicyException: [failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getPolicyMap(PolicyMapBuilder.java:85)
at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1048)
... 54 more
weblogic.application.ModuleException: [HTTP:101216]Servlet: "com.sun.xml.ws.tx.webservice.member.at.CompletionCoordinatorPortTypeImpl" failed to preload on startup in Web application: "WSConsultaTrabajadorCurp".
javax.xml.ws.WebServiceException: [failed to localize] WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL()
at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1052)
at com.sun.xml.ws.wsdl.parser.DelegatingParserExtension.finished(DelegatingParserExtension.java:183)
at com.sun.xml.ws.wsdl.parser.WSDLParserExtensionFacade.finished(WSDLParserExtensionFacade.java:328)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:242)
at com.sun.xml.ws.server.EndpointFactory.getWSDLPort(EndpointFactory.java:550)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:496)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:539)
at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:183)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:135)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:54)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: com.sun.xml.ws.policy.PolicyException: [failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getPolicyMap(PolicyMapBuilder.java:85)
at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1048)
... 54 more
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
Truncated. see log file for complete stacktrace
Caused By: com.sun.xml.ws.policy.PolicyException: [failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
Truncated. see log file for complete stacktrace
>
<Nov 3, 2012 7:44:40 AM CST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application '_appsdir_WSConsultaTrabajadorCurp_dir'.>
<Nov 3, 2012 7:44:40 AM CST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application '_appsdir_WSConsultaTrabajadorCurp_dir'.>
<Nov 3, 2012 7:44:40 AM CST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: [HTTP:101216]Servlet: "com.sun.xml.ws.tx.webservice.member.at.CompletionCoordinatorPortTypeImpl" failed to preload on startup in Web application: "WSConsultaTrabajadorCurp".
javax.xml.ws.WebServiceException: [failed to localize] WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL()
at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1052)
at com.sun.xml.ws.wsdl.parser.DelegatingParserExtension.finished(DelegatingParserExtension.java:183)
at com.sun.xml.ws.wsdl.parser.WSDLParserExtensionFacade.finished(WSDLParserExtensionFacade.java:328)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:242)
at com.sun.xml.ws.server.EndpointFactory.getWSDLPort(EndpointFactory.java:550)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:496)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:539)
at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:183)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:135)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:54)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: com.sun.xml.ws.policy.PolicyException: [failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getPolicyMap(PolicyMapBuilder.java:85)
at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1048)
... 54 more
:com.sun.xml.ws.policy.PolicyException:[failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
Truncated. see log file for complete stacktrace
It seems it is looking for the file; it is in the specified path so I cannot figure out what's wrong. No reference about the problem found over internet. Same web service deploys without problem on Tomcat, but by requirement, needed to deploy onto Weblogic 10g or above. Any help?
Thanks in advance.

how did you configured this ws-policy file?
are you using any @Policy annotations?
Regards,
Sunil P

Problem when generating web service client using eclipse JavaEE

Hi,
I have created a subservience in SAP .. and the WSDL endpoint is :http://10.130.105.8:8000/sap/bc/srt/wsdl/flv_10002A111AD1/srvc_url/sap/bc/srt/rfc/sap/ztm_ws_get_emp_holidays/520/offici…
But there is problem when I set the service definition. Can you help me, in how to generate the Java classes for SAP web service ?

Hi,
Hello again .
Have you tried your service using soapui ?
You can use your WSDL as input .
In order to eliminate eclipse problem try this service:(I just did)
http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL
Regards.
package main;
import java.io.FileInputStream;
import java.rmi.RemoteException;
import java.util.Properties;
import org.oorsprong.www.websamples_countryinfo.CountryInfoServiceSoapType;
import org.oorsprong.www.websamples_countryinfo.CountryInfoServiceSoapTypeProxy;
import org.oorsprong.www.websamples_countryinfo.TCountryCodeAndName;
public class Main {
public static void main(String[] args) {
try {
   final Properties properties = new Properties();
   properties.load(new FileInputStream("properties.ini"));
   System.getProperties().putAll(properties);
} catch (final Exception exception) {
   exception.printStackTrace();
new Main();
public Main() {
try {
   final CountryInfoServiceSoapType infoServiceSoapType = new CountryInfoServiceSoapTypeProxy();
   final TCountryCodeAndName[] tCountryCodeAndNames = infoServiceSoapType.listOfCountryNamesByName();
   for (final TCountryCodeAndName tCountryCodeAndName : tCountryCodeAndNames) {
    System.out.println(tCountryCodeAndName.getSName());
} catch (final RemoteException exception) {
   exception.printStackTrace();

Problem with consuming web service from abap

Hello,
I want to consume this web service VatatWebService Web Service From SAP.
The transaction code soamanager doesn't exist in our system, i'm the only man who use SAP in our company(we don't have BC peoples....).
I find some advice to use "wsadmin" and "lpconfig", but i do not know the step: wish data i have to fill in in tcode "wsadmin" or "lpconfig".
I'm very new in this case...
Is there any doc showing the step to consume a web service?
Thank u very match.
Ouail

Hi,
Have you tried to search using that magical tool called Google? If I search for "SAP LPConfig" I get lots of promising looking answers:
You could also try searching help.sap.com
I appreciate you are new but one of the best skills you can learn in the world of SAP is how to search out and find information, so you aren't dependant upon SCN and/or others to help you when you get stuck.
Cheers,
G.

Problem when consuming web service on WIndows authentication applcation

Similar Messages

Maybe you are looking for