Calling a webservice with SOAP Receiver

Hi Guys,
   Im calling web service from XI using SOAP. I could call the webservice using XML Spy, It is working fine.In XML spy I could se the response (variable out , type double).
   When i call the same web service from XI It doesnt give any error in the beginning and later it would convert the same to "Acknowledment contains system errors" in Ack staus(SXMB_MONI). I configured my scenario as Asyn.However there is a response from webservice. Is it mandatory to create a sync scenario in this case? If so I couldnt configure as Im sending an Idoc as a SOAP request.But Response of Webservice is of double type( some integer it returns) So I couldnt map both as it was giving some problems in message mapping.
   I would like to know how XI sends a soap request ? I mean in SXMB_MONI some where it must be there. I wanted to copy the same from XI n paste in XML spy so that i can test whether it would go throgh.
    In plance of that webservice, We created an asp page and configured IIS. I wrote the ASP in such a way that It would read the SOAP request and dump into my default website area. I Could see the SOAP request coming up from XI.When i paste this in XML spy its working fine but not from XI Im wondering what went wrong?
   Appriciate your help.
Thanks a lot
Kiran

Hi Raghavesh,
   My id is [email protected]
Hi Vijay,
    As Bhavesh said,
         I can handle the response by makign async message interface , I did it but in SOAP adaptor I dont see any option of setting QOS?
        Ya WS is responding So by doing like asyn i can go ahead with that right? Now its throwing error in ask status as :
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Not enough message parts were received for the operation.: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Not enough message parts were received for the operation.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace

Similar Messages

Error while calling webservice with SOAP Receiver

Hi Experts,
When we run the report on the ECC 6.0 server we call the web service which is configured as a receiver SOAP Adapter, we are getting the following error:
XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Not enough message parts were received for the operation
Can somebody throw a light on this error and how to overcome it.
Thanking You
With Best Regards
Suk4023

>Can somebody throw a light on this error and how to overcome it.
Import WSDL and Use soapui or xmlspy and try to send the request and see the response. Make sure your WSDL URL is valid one too. After testing update more informaton on this.

How to call a webservice with SOAP Binding Style RPC

Hi Guys,
I'm pretty new to the LiveCycle ES product and I'm trying to call a web service that is of SOAP binding style 'RPC'. After some research I found out that Adobe LC ES only support WSDL files of doc/literal type.
My question is, is there a workaround for calling RPC style web services? can RPC style web services be converted into doc/literal type?
Any information regarding this would be greatly appreciated.
Kazz.

Hello,
I had the same problem and I've regenerated my WSDL ( Apache Axis ) with docu/litteral parameters.
I think it's the only way...
thomas

Problem with SOAP receiver adapter? Please help!

Hi experts
   I have the following scenario:
   SAP R/3 -ABAP Proxy>XI--->SOAP --webservice
   As you can see, I am sending data from R/3 system to XI via ABAP proxy. XI then sends data or calls a webservice via SOAP adapter.
When I test this scenario I am getting a error in the sxmb_moni that is,
"com.sap.aii.af.ra.ms.api.DeliveryException: TEXT/HTML; HTTP 504 Gateway Time-out"
I have checked the webservice url and it is working fine.
Can somebody tell me why am I getting this error message? How do I resolve this?
Thanks
Gopal

Hi,
Can you please check the settings in Soap Adapter with Module Adapter setting with ModuleTranformBean parameters? There may be some problem. use HTTP Adapter and the message type 'HttpPostIn' to send as HTTP Post.
Also
There is the note 450226 gives an overview over error codes
Probably below solution may help you.........
As an administrator on your portal go to:
System Configuration > Service Configuration >applications
Under: com.sap.portal.ivs.httpservice > Services > Proxy
If any proxy settings are configured you may end up with the problem, so you need to set the "nonProxyHosts" to include the trex host.
regards
Aashish Sinha
PS : reward points if helpful

Call a Webservice with SAML securty in PI 7.0

Hi experts,
I need to call a Webservice with SAML security from PI 7.0, Is It possible? or only It is possible with PI 7.1?
Thanks in advance,
Jose Manuel

Hi Jose,
Let me answer your questuion first :
No, using PI 7.0 I dont think its posible..
Below is a brief overview on SAML.
SAML: It stands for Security Assertion Markup Language, it is an XML standard which is used to exchange security information between a service provider and an identity provider.
Why we need it ???
We have a concept called Principal Propagation in PI 7.1, Principal Propagation allows to securely pass the identity of a user from a sender application to a receiver application. There are various adapters and protocols which support the Principal Propagation and one protocol amongst them is the Webservice Reliable Messaging Protocol or WS-RM. Principal Propagation solution for WS-RM protocol is based on SAML and uses the SAML assertions.
There are some video recordings available for configuration and you can view the same as below,
Configure a Trust Relationship between Sender and Integration Server: Exchange sender's digital certificate between sender and Integration Server.
Configure Trusted Issuer: Map user in the Integration Server, and specify issuer. Default issuer is the sender's system ID, default attester is the sender's certificate.
Configure Sender Agreement and Sender Communication Channel: In Integration Directory, select SAML Sender Vouches Assertion as authentication method.
Regards,
Divya

Is it possible to call a webservice with just the url to its WSDL

hi all
can anyone tell me if it is possible to call a webservice with just the url to its WSDL file. must we create the proxy class for webservice client? thanks

if you are in the context of a J2EE 1.4 container, you do not need to generate any stub, you can use either a dynamic proxy mechanism or dynamic invocation.
check JWSDP tutorial.

Send and symbols with soap receiver adapter

I have a integration scenario (IDOC to WebService).
The web service has an action with receives 2 parameters
<MaterialNumber>
and
<MaterialList>
I have imported the wsdl file into Repository and I have define my interface.
But this webservice has a peculiarity:
The content of the second tag is also in xml format (but this is not defined in wsdl). For example
<MaterialList>
    <Item>
      <MaterialID>1</MaterialID>
      <MaterialDescription>Example</MaterialDescription>
      <CreationDate>10102007</CreationDate>
    </Item>
</MaterialList>
A have tried to invoque the webservice with SAP SOAP Client. If i used < and > symbols for Item, MaterialID, MaterialDescription and CreationDate tags I get an xml error. So I have to use &lt; and &gt; instead and its works fine.
So in my message mapping I have done that. I have test it in integration repository and uses &lt; and &gt; in the generated xml. It does exactly what I want. I have a message in this form:
&lt;MaterialList&lt;
    &lt;Item&lt;
      &lt;MaterialID&lt;1&lt;/MaterialID&lt;
      &lt;MaterialDescription&lt;Example&lt;/MaterialDescription&lt;
      &lt;CreationDate&lt;10102007&lt;/CreationDate&lt;
    &lt;/Item&lt;
&lt;/MaterialList&lt;
But once I execute my integration scenario, I do a communication channel monitoring and for my surprise i get the next message
& amp; &lt;MaterialList& amp;&gt;
    & amp; &lt;Item& amp; &gt;
      & amp; &lt;MaterialID& &gt;1& amp; &lt;/MaterialID& amp; & amp;gt;
      & amp; &lt;MaterialDescription& &gt;Example& &lt;/MaterialDescription& &gt;
      & amp; &lt;CreationDate& &gt;10102007& amp; &lt;/CreationDate & amp; &gt;
    & amp; &lt;/Item& &gt;
& amp; &lt;/MaterialList& &gt;
It seems that the soap adapter has changed &< to & amp;lt;
Is there any way to avoid this?
Thanks to all.

Use CDATA tag and you won't have those problems.
Check this blog: /people/michal.krawczyk2/blog/2005/11/01/xi-xml-node-into-a-string-with-graphical-mapping
Regards,
Henrique.

Problem with SOAP receiver

Hello,
Our PI system is 7.4 . We have a lot of interface with related to proxy to soap.When they are used very intensively, errors occur in soap receiver .
Types are error:
503 server not avalibale,
401 unauthorized ,
invalid content type for SOAP:TEXT/HTML such as...
When system is restarted, mostly it is worked but after while again errors occur and a lot of message is waiting in queue.
what can we do for it?
Thanks in advance,
Nurhan

Hi Claudia,
It is dual stack installation. While calling soap receiver adapter, error occur. In sxmb_moni display error as follows:
After restart, we have new error:
It is abap proxy to soap scenario. It's synchronous communication.
Thanks,
Nurhan

Issue with SOAP receiver

Hi,
I'm using PI 7.0, SP13 and I'm sending a message to a MS webservice, using BURP as a proxy in between to avoid NTLM authorisation issues.
The problem is that it's perfecly possible to send a message using soapUI, but sending the exact same message ends up in an error:
"SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request"
I already configured the MessageTransformBean by setting the ContentType to text/xml; charset=utf-8. Here are the settings of my communication channel:
Target URL: http://<correct URL on local network>
User authentication: false
Certificate authentication: false
Proxy: BURP proxy and BURP port
Proxy user authentication: false
Secutiry profile: false
Do not use SOAP envelope: false
Keep headers: false
Keep attachments: false
Use encoded headers: false
Use query string: false
SOAP action: <correct SOAP action>
I also played with the parameters "Do not use SOAP envelope", "Keep headers" and "Keep attachments", without any success. The only difference that I can think of is that soapUI runs on Windows, and the PI system runs on Linux.
Ideas, anyone?

@Baskar Gopal: I didn't generate a WSDL: I'm using the SOAP receiver to post a message to an existing webservice.
@sdnuser: the endpoint URL is 100% correct. I also added the MessageTransformBean like I stated before.
@Chirumamilla Sukarna: HTTP adapter doesn't work because I need the SOAP envelope.
The payload is in both cases (soapUI and PI) the same. Here's the part that's different:
soapUI (working part):
POST /DynamicsNAV/WS/Rendon%20Voorburg/Codeunit/Webservice HTTP/1.0
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: "urn:microsoft-dynamics-schemas/codeunit/Webservice:ContractorOrderInSync"
User-Agent: Jakarta Commons-HttpClient/3.1
Host: 192.168.1.8:7049
Proxy-Connection: Keep-Alive
Content-Length: 4292
Connection: Keep-Alive
SAP PI (not working part):
POST /DynamicsNAV/WS/Rendon%20Voorburg/Codeunit/Webservice HTTP/1.0
Accept: /
Host: 192.168.1.8:7049
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
Authorization: Basic aGFhZ3dvbmVuQGJpbTpRYnFyRU84IQ==
content-id: <soap-C89FD74E68782E13E1000000C0A8E010 @ sap.com>
Content-Type: text/xml;charset=UTF-8
Content-Length: 4292
SOAPACTION: "urn:microsoft-dynamics-schemas/codeunit/Webservice:ContractorOrderInSync"
Connection: Keep-Alive
I know the content type looks correct here, but the SOAP adapter gives an error about this nevertheless.

Problem with soap receiver adapter

Hi All
I have Idoc sender and soap receiver in my scenario.
I am calling web service deployed on WAS.
The web service is getting called but the acknowledgement message in xi contains following system error acknowledgement because of which xi changes the status of message to WAIT and starts retrying.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.MessagingException: java.net.SocketTimeoutException: Read timed out: com.sap.aii.af.ra.ms.api.RecoverableException: java.net.SocketTimeoutException: Read timed out</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please anybody can help to resolve this problem. This scenario has worked without any error previously.
Thanks in advance
Beena

Hi Bhavesh,
It is an Async call where method does not return anything.
I added entries in IDX_NOALE but still it is setting the message status to WAIT and does retry.
Following is the Audit Log in Runtime workbench :
Audit Log for Message: 22b3052d-c519-034e-85db-e65d541d6414
Time Stamp Status Description
2006-12-13 10:25:23 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
2006-12-13 10:25:23 Error Exception caught by adapter framework: Read timed out
2006-12-13 10:25:24 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
2006-12-13 10:25:24 Success The asynchronous message was successfully scheduled to be delivered at Wed Dec 13 10:30:24 GMT+05:30 2006.
2006-12-13 10:25:24 Success The message status set to WAIT.
2006-12-13 10:30:25 Success Retrying to deliver message to the application. Retry: 1
2006-12-13 10:30:25 Success The message was successfully retrieved from the receive queue.
2006-12-13 10:30:25 Success The message status set to DLNG.
2006-12-13 10:30:25 Success Delivering to channel: INSPWCCT_PVtoSAP_Ack
2006-12-13 10:30:25 Success SOAP: request message entering the adapter
2006-12-13 10:35:28 Success SOAP: call failed
2006-12-13 10:35:28 Success SOAP: sending a delivery error ack ...
2006-12-13 10:35:28 Success SOAP: sent a delivery error ack
2006-12-13 10:35:28 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
2006-12-13 10:35:28 Error Exception caught by adapter framework: Read timed out
2006-12-13 10:35:28 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
2006-12-13 10:35:28 Success The asynchronous message was successfully scheduled to be delivered at Wed Dec 13 10:40:28 GMT+05:30 2006.
2006-12-13 10:35:28 Success The message status set to WAIT.
I have tried this scenario earlier. I am sending the same Idoc from R3 which was processed successfully earlier.
Thanks
Beena.

How To call java WebService with flex.

Hi Friends
can any body guide me how to use webservices that call java at server side.i have experience of http service dont know how to call the webservices.please give me a basic demo on both side(java and flex).i am using eclipse ide for java and flex.
Thanks in advance
Vineet osho

The ADF Mobile Container Utilities API may be used from JavaScript or Java.
Application Container APIs - 11g Release 2 (11.1.2.4.0)

Calling Web Service with SOAP header from BPEL

Hi,
I am calling a web service (with header information) from BPEL. In the Invoke activity, i created a header variable to pass the header information.
But, when i test the BPEL service, invoke activity fails because the header information is not being passed.
Below is the error message (copied from clipboard).
+<messages><input><Invoke_1_getsubinfo_InputVariable><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="parameters"><getsubinfoElement xmlns="http://ws/its/tabs/webservices/SingleRowWS/SingleRowWS.wsdl">+
+<pSubnoin>+
+<insubno>12345678</insubno>+
+</pSubnoin>+
+</getsubinfoElement>+
+</part></Invoke_1_getsubinfo_InputVariable></input><fault><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>exception on JaxRpc invoke:+
start fault message:+
Internal Server Error (Caught exception while handling request: javax.xml.rpc.JAXRPCException: Not authenticated user)+
*:end fault message*</summary>
+</part></bindingFault></fault></messages>+
As said, no header information is visible in the Invoke activity.
Please provide help for the above issue.
-MJ

Hello Patrick,
Thanks for the response. I am using normal assign activity to assign values to the header variable as shown below. HeadMT is the header variable which is passed in the invoke activity.
+<assign name="Assign_Header">+
+<copy>+
+<from expression="'tkl12'"/>+
+<to query="/ns1:LOGIN_INFO/ns1:USER_NAME" variable="*HeadMT*"+
part="payload"/>
+</copy>+
+<copy>+
+<from expression="'tkl123'"/>+
+<to query="/ns1:LOGIN_INFO/ns1:PASSWORD" variable="*HeadMT*"+
part="payload"/>
+</copy>+
+<copy>+
+<from expression="'TKL'"/>+
+<to query="/ns1:LOGIN_INFO/ns1:CHANNEL_ID" variable="*HeadMT*"+
part="payload"/>
+</copy>+
+</assign>+
The expected input by the web service is as below with the header information highlighted.
+<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://ws/webservices/RowWS/RowWS.wsdl">+
+*<soap:Header>*+
+*<ns1:LOGIN_INFO>*+
+*<ns1:USERNAME>tkl12</ns1:USERNAME>*+
+*<ns1:PASSWORD>tkl123</ns1:PASSWORD>*+
+*<ns1:CHANNEL_ID>TKL</ns1:CHANNEL_ID>*+
+*</ns1:LOGIN_INFO>*+
+*</soap:Header>*+
+<soap:Body>+
+<ns1:substatusElement>+
+<ns1:pInparam>+
+<ns1:insubno>7674988</ns1:insubno>+
+</ns1:pInparam>+
+</ns1:substatusElement>+
+</soap:Body>+
+</soap:Envelope>+

Issue with SOAP receiver AXIS adapter

Hi All,
We have a scenario SOAP -- > PI -- > SOAP (axis) using SOAP 1.2 version synchnrous scenario. Using Webservice navigator am trying to trigger a message to PI .
Message has reached to PI box and failing in the receiver SOAP(axis) channel as :
Delivering to channel: Receive_SOAP_BulkFeedback 18.08.2014 10:33:24 Information MP: processing local module localejbs/AF_Adapters/axis/AFAdapterBean 18.08.2014 10:33:24 Error
MP: processing local module localejbs/AF_Adapters/axis/AFAdapterBean
MP: processing local module localejbs/AF_Adapters/axis/AFAdapterBean 18.08.2014 10:33:24 Error MP: exception caught with cause javax.ejb.EJBException: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.axis.app, BC-XI-CON-SOP) Exception raised from invocation of public com.sap.aii.af.lib.mp.module.ModuleData com.sap.aii.adapter.axis.modules.AFAdapterBean.process(com.sap.aii.af.lib.mp.module.ModuleContext,com.sap.aii.af.lib.mp.module.ModuleData) throws com.sap.aii.af.lib.mp.module.ModuleException method on bean instance com.sap.aii.adapter.axis.modules.AFAdapterBean@6bbad627 for bean sap.com/com.sap.aii.axis.app*xml|com.sap.aii.adapter.axis.ejb.jar*xml|AFAdapterBean in application sap.com/com.sap.aii.axis.app.; nested exception is: java.lang.NullPointerException: while trying to invoke the method com.sap.aii.af.lib.mp.module.SModule.process(com.sap.aii.af.lib.mp.module.ModuleContext, com.sap.aii.af.lib.mp.module.ModuleData) of an object loaded from field com.sap.aii.adapter.axis.modules.AFAdapterBean.core of an object
Please help and suggest.

Hi Raja,
The end system is closing the communication. Try to reset your PI ICM instance. Also check if your PI system is affected by this note 1675953 - SSL Client Authentication failed with PI SOAP Axis Adapter
Regards.

Help with SOAP Receiver

Hello PI friends,
I'm connecting PI to an external SOAP web service developed in .NET. I created a scenario which should be very close to what I need but I was getting an error when testing in RWB:
SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request
So then I captured my payload and tried to get this working in SOAPUI, but came to the same 400 response.
I have a prototype program written in .NET which can execute the call correctly :-).
I watched this in Fiddler and compared the headers / payload to what I had, making an interesting discovery.
The overall message structure is something like this:
<soap:Envelope>
<soap:Body>
<WebServiceMethod>
<usuario/>
<password/>
<MyPayload>
.....more "XML", I use quotes here for a reason, please read on...
</MyPayload>
</WebServiceMethod>
</Body>
</Envelope>
What I noticed in Fiddler with the working .NET prototype is everything inside MyPayload is escaped XML, like: <?xml version="1.0" encoding="utf-8"?><
My message in PI is sending true XML inside that element structure. So when I change from my payload in SOAPUI using that escaped notation it works great.
But now either I need to accomplish this strange notation in PI, or perhaps I am doing something wrong with the way I've configured my datatype and mapping in the first place and it should always get escaped this way by using only passing the "MyPayload" section into the SOAP adapter?
However, when I tried this I am missing the key parts of the SOAP Body... e.g. WebServiceMethod, usuario, password, MyPayload
(BTW - This web service is in Spanish so username is really "usuario". I don't know if there is a way for this to be passed using the Adapter authentication options or if it must be coded into the message body)
Currently I named my datatype to match like "WebServiceMethod" and then defined all nodes underneath this. When I capture the SOAP output it looks OK to me structure wise... its just this internal web service XML payload which is giving me trouble.
Anyone run into this before? I hope it is something simple, I'm not a web service developer and am more accustomed to using the RFC / IDOC / JMS / JDBC adapters. Thanks for your ideas.
-Aaron

Hi Aaron,
about "usario" being part of payload: The receiver seems to want it that way.As long as transport protocol is HTTPS you should not be worried about this.
About your escaped XML: I'm assuming this is a follow up of your last post? Anyways, having an additional <?xml version...> statement within an xml document is not allowed and would render the whole document ill-formed (is that proper English?) Seems like the .net program implicitly sends all payload data (maybe only the actual data within the tags) through a serializer , which is quite normal / best practice.
You could do so on PI also of course. As the .net program works, receiver should be able (or even may assume) that any data within <MyPayload> is serialized. Have a look at my post in your former thread about some possible util classes for that. Re: How to insert <?xml version="1.0" encoding="utf-8"?> before an element (Beware, I'm not a Java expert and haven't done this yet, so YMMV)
HTH
Cheers
Jens

Invalid request when calling REST-webservice with UTL_HTTP.

Hello,
When i try to send some data to a REST-webservice i get as response "INVALID REQUEST"
I Think it is about the request-body that seems to be no UTF-8.
I tried to set the characterset with utl_http.set_body_charset(t_http_req, 'UTF-8').
But when i read the characterset with utl_http.get_body_charset(t_charset);, is still get "ISO-8859-1"
I am using: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Product
Some help would realy be appreciated because i am out of options trying to get the code working..
======MY CODE==========
create or replace procedure ipm40_send_bekendmaking(p_bdmg_id in number)
as
r_bekendmaking ipm40_bekendmakingen%rowtype;
r_gemeente ipm40_gemeenten%rowtype;
l_url httpuritype;
t_http_req utl_http.req;
t_http_resp utl_http.resp;
t_request_body varchar2(32767);
t_respond varchar2(32767);
-- t_teller integer := 1;
-- t_output varchar2(2000);
t_start number := 1;
t_body_lengte number;
t_chunkdata varchar2(4000);
t_tijd_1 varchar2(256);
t_tijd_2 varchar2(256);
t_timeout integer;
t_length number;
t_charset varchar2(256);
begin
select *
into r_bekendmaking
from ipm40_bekendmakingen
where id = p_bdmg_id;
select *
into r_gemeente
from ipm40_gemeenten
where gmte_code = r_bekendmaking.gmte_code;
l_url := httpuritype.createuri('http://zwolle.stadsbeheer.com:82/apex/ipm40bekendmaking?p_bdmg_id='||r_bekendmaking.id);
t_request_body := l_url.getClob();
/* request that exceptions are raised for error Status Codes */
--Utl_Http.Set_Response_Error_Check ( enable => true );
/* allow testing for exceptions like Utl_Http.Http_Server_Error */
--Utl_Http.Set_Detailed_Excp_Support ( enable => true );
utl_http.set_transfer_timeout(300);
t_http_req:= utl_http.begin_request( r_gemeente.url_webservice_bekendmakingen
, 'POST'
, 'HTTP/1.1');
utl_http.set_body_charset(t_http_req, 'UTF-8');
utl_http.get_body_charset(t_charset);
utl_http.set_authentication(t_http_req,r_gemeente.user_webservice_bekendmakingen,r_gemeente.pw_webservice_bekendmakingen);
t_length := length(t_request_body);
utl_http.set_header(t_http_req, 'Content-Type', 'application/xml charset=UTF-8');
utl_http.set_header(t_http_req, 'Content-Length', t_length);
utl_http.set_header(t_http_req, 'Transfer-Encoding', 'chunked' ); --
t_body_lengte := dbms_lob.getlength(t_request_body);
loop
t_chunkdata := dbms_lob.substr(t_request_body, 2000, t_start);
utl_http.write_text ( t_http_req, t_chunkdata );
t_start := t_start + 2000;
if t_start > t_body_lengte
then
exit;
end if;
end loop;
t_http_resp:= utl_http.get_response(t_http_req);
utl_http.read_text(t_http_resp, t_respond);
utl_http.end_response(t_http_resp);
if instr(t_respond,'Successfully document processed') != 0
then
update ipm40_bekendmakingen
set ind_status = 'S'
, datum_verzonden = sysdate
, response = t_respond
where id = r_bekendmaking.id;
else
update ipm40_bekendmakingen
set ind_status = 'F'
, datum_verzonden = null
, response = t_respond
where id = r_bekendmaking.id ;
end if;
commit;
exception
when others
then
t_tijd_2 := to_char(sysdate,'HH24:MI:SS');
t_respond := substr(sqlerrm,1,2000);
update ipm40_bekendmakingen
set ind_status = 'F'
, datum_verzonden = null
, response = t_respond
where id = r_bekendmaking.id ;
commit;
end;
===THE RESPOND=============
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The requested URL could not be retrieved</TITLE>
<STYLE type="text/css"></STYLE>
</HEAD><BODY>
<H1>ERROR</H1>
<H2>The requested URL could not be retrieved</H2>
<HR noshade size="1px">
<P>
While trying to process the request:
<PRE>
POST /pushxml/pushxml-bm HTTP/1.0
Authorization: Basic Ymtfc21hcnRob2xkaW5nOllyZXMzdlFR
Content-Type: application/xml charset=UTF-8
Content-Length: 2096
Transfer-Encoding: chunked
Connection: close
</PRE>
<P>
The following error was encountered:
<UL>
<LI>
<STRONG>
Invalid Request
</STRONG>
</UL>
<P>
Some aspect of the HTTP Request is invalid. Possible problems:
<UL>
<LI>Missing or unknown request method
<LI>Missing URL
<LI>Missing HTTP Identifier (HTTP/1.0)
<LI>Request is too large
<LI>Content-Length missing for POST or PUT requests
<LI>Illegal character in hostname; underscores are not allowed
</UL>
<P>Your cache administrator is [email protected].
<BR clear="all">
<HR noshade size="1px">
<ADDRESS>
Generated Fri, 12 Aug 2011 17:33:24 GMT by asd2cc001.asp4all.nl (squid)
</ADDRESS>
</BODY></HTML>

Always check the access_log and error_log files of the Apache web server in such a case. This will identify whether the error comes from Apache itself, mod_plsql, the Apex run-time engine, or the Oracle database.
I see that you're creating a HTTP/1.1 in PL/SQL - however, the web server response indicates a HTTP/1.0 call was received. Unusual. And could be part of the problem.

Calling a webservice with SOAP Receiver

Similar Messages

Maybe you are looking for