Implementing HTTP client in CAPS
hi all,
i am invoking a webservice from JCD using HTTP Client eWay when i am running the project i am getting the follwing error but the same webservice when i'm calling from XML spy or from normal java(HTTPClient) program its working fine and i'm getting result also. can any body any clues.
[#|2006-04-22T19:34:23.251+0530|WARNING|IS5.1|javax.enterprise.system.stream.err|_ThreadID=18; ThreadName=http18001-Processor4;|ERROR: 'Content is not allowed in prolog.'|#]
[#|2006-04-22T19:34:23.392+0530|SEVERE|IS5.1|javax.xml.messaging.saaj.soap|_ThreadID=18; ThreadName=http18001-Processor4;|SAAJ0511: Unable to create envelope from given source|#]
[#|2006-04-22T19:34:23.407+0530|SEVERE|IS5.1|com.sun.xml.rpc.server|_ThreadID=18; ThreadName=http18001-Processor4;stacktrace-id=121;|Unable to create envelope from given source:
com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to create envelope from given source:
at com.sun.xml.messaging.saaj.soap.EnvelopeFactory.createEnvelope(EnvelopeFactory.java:95)
at com.sun.xml.messaging.saaj.soap.ver1_1.SOAPPart1_1Impl.createEnvelopeFromSource(SOAPPart1_1Impl.java:51)
at com.sun.xml.messaging.saaj.soap.SOAPPartImpl.getEnvelope(SOAPPartImpl.java:106)
at com.sun.xml.rpc.client.HandlerChainImpl.checkMustUnderstand(HandlerChainImpl.java:235)
at com.sun.xml.rpc.server.StreamingHandler.callRequestHandlers(StreamingHandler.java:927)
at com.sun.xml.rpc.server.StreamingHandler.preHandlingHook(StreamingHandler.java:851)
at com.sun.xml.rpc.server.StreamingHandler.handle(StreamingHandler.java:110)
at com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doPost(JAXRPCServletDelegate.java:448)
at com.sun.xml.rpc.server.http.JAXRPCServlet.doPost(JAXRPCServlet.java:102)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:768)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:289)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:318)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:205)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:283)
at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:102)
at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:192)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:261)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:215)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:200)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:180)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:582)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:254)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:161)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:979)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:211)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:692)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:647)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:589)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:691)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.xml.transform.TransformerException: org.xml.sax.SAXParseException: Content is not allowed in prolog.
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:650)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:279)
at com.sun.xml.messaging.saaj.util.transform.EfficientStreamingTransformer.transform(EfficientStreamingTransformer.java:371)
at com.sun.xml.messaging.saaj.soap.EnvelopeFactory.createEnvelope(EnvelopeFactory.java:83)
... 56 more
Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1269)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transformIdentity(TransformerImpl.java:584)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:638)
... 59 more
Thanks In Advance
rss
IMO, the problem is here: 'Content is not allowed in prolog'. in most cases, it means that you have some white spaces more than allowed in your http header. try to remove them
Similar Messages
-
Getting runtime error while running HTTPS client
hi
i have return https client in java,which does not give error while compiling but its giving runtime error as shown below.
java.security.NoSuchAlgorithmException: Algorithm RSA not available
at javax.net.ssl.SunJSSE_b.a(DashoA6275)
at javax.net.ssl.KeyManagerFactory.getInstance(DashoA6275)
at SSLSocketClientWithClientAuth.main(SSLSocketClientWithClientAuth.java
:65)
java.lang.NullPointerException
at SSLSocketClientWithClientAuth.main(SSLSocketClientWithClientAuth.java
:78)
and this is the code
import java.net.*;
import java.io.*;
import javax.net.ssl.*;
//import javax.security.cert.X509Certificate;
import java.security.KeyStore;
import java.security.*;
* This example shows how to set up a key manager to do client
* authentication if required by server.
* This program assumes that the client is not inside a firewall.
* The application can be modified to connect to a server outside
* the firewall by following SSLSocketClientWithTunneling.java.
public class SSLSocketClientWithClientAuth {
public static void main(String[] args) throws Exception {
//String host = null;
//int port = -1;
String host="10.11.25.251";
int port = 443;
SSLSocket socket;
String path = null;
for (int i = 0; i < args.length; i++)
System.out.println(args);
/*if (args.length < 3) {
System.out.println(
"USAGE: java SSLSocketClientWithClientAuth " +
"host port requestedfilepath");
System.exit(-1);
/*try {
host = args[0];
port = Integer.parseInt(args[1]);
//path = args[2];
} catch (IllegalArgumentException e) {
System.out.println("USAGE: java SSLSocketClientWithClientAuth " +
"host port requestedfilepath");
System.exit(-1);
try {
* Set up a key manager for client authentication
* if asked by the server. Use the implementation's
* default TrustStore and secureRandom routines.
SSLSocketFactory factory = null;
try {
SSLContext ctx;
KeyManagerFactory kmf;
KeyStore ks;
char[] keystorepass = "123456".toCharArray();
char[] keypassword ="13051983".toCharArray();
ctx = SSLContext.getInstance("TLS");
//kmf = KeyManagerFactory.getInstance("RSA");
ks = KeyStore.getInstance("JKS");
ks.load(new FileInputStream("testkeys"), keystorepass);
kmf = KeyManagerFactory.getInstance("RSA");
kmf.init(ks, keypassword);
ctx.init(kmf.getKeyManagers(), null, null);
factory = ctx.getSocketFactory();
} catch (Exception e) {
//throw new IOException(e.getMessage());
e.printStackTrace();
socket = (SSLSocket)factory.createSocket(host, port);
socket.startHandshake();
* send http request
* See SSLSocketClient.java for more information about why
* there is a forced handshake here when using PrintWriters.
PrintWriter out = new PrintWriter(new BufferedWriter(new OutputStreamWriter(socket.getOutputStream())));
// out.println("GET " + path + " HTTP/1.1");
out.println();
out.flush();
* Make sure there were no surprises
if (out.checkError())
System.out.println(
"SSLSocketClient: java.io.PrintWriter error");
/* read response */
BufferedReader in = new BufferedReader(
new InputStreamReader(
socket.getInputStream()));
String inputLine;
while ((inputLine = in.readLine()) != null)
System.out.println(inputLine);
in.close();
out.close();
socket.close();
} catch (Exception e) {
e.printStackTrace();
please help me out .
regards,
sunilHi
Please do a fetch from the database and then change the information in DRM console for the CSS parameter. This error I received only due to the CSS details in DRM 11.1.2.
Thanks
Rupak
Mantra to Win | WinMantras.com | http://hyperion.winmantras.com -
Problems with HTTP Client Authentication in jdev 10.1.2.17.84.
Hi,
I've told HTTP Client Authentication doesn't work in jdev 10.1.2.17.84. I need users to be authenticated using a certificate so I'm trying several workarounds but none seems to be valid. Any help?
Thanks.
Luis Serrano.been there done that.. ive decompiled the oc4j code, debuged down to the core... its big waste of my time... :(
my advice to you is to leave it.. if you do not plan to use oracle ldap sso or xml provider you can do nothing... your hands are tied... they hardcoded everything and if you want more than classic "username & password" custom login module you will have to change oc4j...
there is no point to make a custom loginmodule which utilize a client certificate because oracle JAZN do not suport that type of login module!
just implement a login filter and manage authentication and authorization yourself... just like steve muench did in his java store demo - he didnt use JAZN... :)
anyway current approach do not allow you to leverage JAAS in ADF model layer so why bother to have that in the view/controller layer anyway...
and if i understood correctly oracle plans big changes in this area in the next jdeveloper release, and they alredy said that custom login modules would be depreciated in the next releases... -
How to implement HTTP Streaming for Flash Player 10.1 ?
Hi there,
I have been developing a streaming video player application in Flash Builder 4, and have been really excited about the HTTP Streaming functionality now available in Flash Player 10.1.
Unfortunately, there seems to be an extreme dearth of materials on how to actually implement HTTP Streaming both server side and client side. Does anyone have a straightforward tutorial/example of how to implement HTTP Streaming from start to finish, or do any of the Adobe Developers plan on releasing documentation for this?
I've looked through the BETA Actionscript 3.0 API Documentation and noticed the new NetStream.appendBytes() and NetStream.appendBytesAction(), which I suspect are involved in HTTP streaming. I also saw a sketchy introduction from Ryan Shin on the Open Source Media Framework (OSMF) website (https://admin.na3.acrobat.com/_a204547676/p96986524?launcher=false&fcsContent=tr ue&pbMode=normal), but it seems to be lacking in details regarding how to actual implement a "file packager" on the server or how to open an HTTP Stream on the client side.
Any help would be much appreciated.
Thanks!
Ho TuanIt is unlikely that you will get an answer here in the Flash Player (release version) forum. Better try in the appropriate Flash, Actionscript, or FP 10.1 beta forum http://forums.adobe.com/community/labs/flashplayer10/flashplayer10.
-
HTTP Client VIs help or examples?
I am trying to use the HTTP Client VIs to implement a version of the C# code found HERE. Unfortunately there are no NI examples of how the client VIs are to be used and my various attempts to string them together only seem to result in "Error 42" (LabVIEW: Generic Error) from the POST vi, rather than returning the headers and body text.
I have also tried using DOTNET calls and was at least able to get the login page returned but could not seem to trigger the login.
I switched to the HTTP Client VIs because they offered an alternate hope and I could at least see where to attach a cookie file with them (though a cookie file may not be the same as reserving space for a session cookie).
Solved!
Go to Solution.
Attachments:
HTTP_Client VI.jpg 61 KB
DotNet VI.jpg 120 KBHello Warren,
At this point, your best reference is probably the LabVIEW help documentation on the HTTP client VIs you are using, but here are a few examples that might offer some insight as well:
Easy HTTP Client VIs
https://decibel.ni.com/content/docs/DOC-22383
Reading Coordinates Information from Google Maps Web Services Using HTTP Client VIs
https://decibel.ni.com/content/docs/DOC-20762
Additionally, it looks like there was an issue addressed in LabVIEW 2011 related to the Post VI and Error 42 when downloading large files (see CAR 251094 in the 2011 release notes), which might apply in this situation.
I would recommend contacting our support directly to troubleshoot the error you are seeing, particularly as it is so generic. If the lack of examples is a hindrance, definitely create a product suggestion at http://digital.ni.com/applications/psc.nsf/default?OpenForm or by posting on the LabVIEW Idea Exchange (http://forums.ni.com/t5/LabVIEW-Idea-Exchange/idb-p/labviewideas .)
Tom L. -
We are trying to use HTTPS client certificate based authentication to access a Java Applet in Firefox v21.0. We have followed the instructions as per the below two urls to enable JSS 4 -
https://developer.mozilla.org/en-US/docs/JSS/Using_JSS<br />
http://docs.oracle.com/javase/6/docs/technotes/guides/deployment/deployment-guide/keystores.html<br />
http://download.java.net/jdk8/docs/technotes/guides/deployment/deployment-guide/keystores.html
We are using JRE version 1.7.0_25-b16 Java HotSpot(TM) Client VM in Firefox v21 but we are getting - <br />
security: Accessing keys and certificate in Mozilla user profile: null<br />
security: JSS is not configured
followed by SSK handshake failure when trying to load the client certificate.
<pre><nowiki>javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(Unknown Source)
at sun.plugin.PluginURLJarFileCallBack.connect(Unknown Source)
at sun.plugin.PluginURLJarFileCallBack.retrieve(Unknown Source)
at sun.net.www.protocol.jar.URLJarFile.retrieve(Unknown Source)
at sun.net.www.protocol.jar.URLJarFile.getJarFile(Unknown Source)
at sun.net.www.protocol.jar.JarFileFactory.get(Unknown Source)
at sun.net.www.protocol.jar.JarURLConnection.connect(Unknown Source)
at sun.plugin.net.protocol.jar.CachedJarURLConnection.connect(Unknown Source)
at sun.plugin.net.protocol.jar.CachedJarURLConnection.getJarFileInternal(Unknown Source)
at sun.plugin.net.protocol.jar.CachedJarURLConnection.getJarFile(Unknown Source)
at com.sun.deploy.security.DeployURLClassPath$JarLoader.getJarFile(Unknown Source)
at com.sun.deploy.security.DeployURLClassPath$JarLoader.access$1000(Unknown Source)
at com.sun.deploy.security.DeployURLClassPath$JarLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.deploy.security.DeployURLClassPath$JarLoader.ensureOpen(Unknown Source)
at com.sun.deploy.security.DeployURLClassPath$JarLoader.<init>(Unknown Source)
at com.sun.deploy.security.DeployURLClassPath$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.deploy.security.DeployURLClassPath.getLoader(Unknown Source)
at com.sun.deploy.security.DeployURLClassPath.getLoader(Unknown Source)
at com.sun.deploy.security.DeployURLClassPath.getResource(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader$2.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.plugin2.applet.Plugin2ClassLoader.findClassHelper(Unknown Source)
at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader.loadClass0(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader.loadClass0(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source)
at sun.plugin2.applet.Plugin2Manager.initAppletAdapter(Unknown Source)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)</nowiki></pre>
The client cert based authentication is working when using IE v8 and IE v9 with the same JRE version (JRE version 1.7.0_25-b16 Java HotSpot(TM) Client VM)
Any help to resolve this issue will be very much appreciated.Thank you for your response.
Yes we have added the client certificate file (.pfx) in the Firefox browser Certificate manager / Store. It's also showing the certificate in the View Certificate window. We could not resolve it yet. -
Error while creating the HTTP client with destination GB_DPSRetrieve
Hi All,
It is an interface R/3 -->XI --> HTTP ( proxy to HTTP ).
Please find the error log below and throw some light why the HTTP adapter is getting error -
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>DC98499F-7E42-74F1-A41F-0017A4107EE6</SAP:MessageId>
<SAP:RefToMessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:RefToMessageId>
<SAP:TimeSent>2007-11-21T15:51:30Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">GovernmentGateway</SAP:Party>
<SAP:Service>GGMailbox</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>SAP_DEV_ERP2005</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/HR">HR_GB_EFI_DPSretrieve</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT_DEST</SAP:Code>
<SAP:P1>GB_DPSRetrieve</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while creating the HTTP client with destination GB_DPSRetrieve</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="BS">SAP_DEV_ERP2005</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="IS">is.00.lbsth-tb1ci</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="IS" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20071121</SAP:Date>
<SAP:Time>155130</SAP:Time>
<SAP:Host>lbsth-tb1ci</SAP:Host>
<SAP:SystemId>XIS</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>ORACLE</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>023</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>PISUPER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>000</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
<SAP:QIdInternal />
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID" />
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>0</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>2918</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>0</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>PLAINHTTP</SAP:AdapterInbound>
<SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
<SAP:InterfaceAction>INIT</SAP:InterfaceAction>
<SAP:RandomNumber>15</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
<SAP:Receiver_Agreement_GUID>24422A5646443F8E9D975D57A3EE8162</SAP:Receiver_Agreement_GUID>
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.5</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.656</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">SystemError message generated. Guid: DC98499F7E4274F1A41F0017A4107EE6</Trace>
<Trace level="1" type="T">Error during execution of message : DC98499CA1EABEF1B4DD00110A63BF06</Trace>
<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): DC98499CA1EABEF1B4DD00110A63BF06</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
<SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />
</SOAP:Body>
</SOAP:Envelope>
Regards,
KishoreHi,
In the HTTP Receiver what is the Addressing Type used ? (URL Address or HTTP Destination).
If its URL Addressing Type, check if right Authentication Type is used with valid values and for HTTP Addressing Type check this HTTP Client Create Error, it could be helpful.
Also check if the Target system can be reached from the XI server to validate the configuration parameters.
Regards,
S.Santhosh Kumar -
How to setup HTTP client for HTTP to File scenario
Hey guys
i have a scenario wherein one of our clients is sending invoices(as XML message) over HTTP(client is outside our landscape) and i have to to send this invoice to a File system from where it will be picked up by an ABAP code(picking of the file has to be done by ABAper so i m not concerned with that)
the way i m starting off this project is that
i will create a sender and receiver data type,message type and Message interface,Message mapping is 1-1 so its kinda simple and then Interface mapping.
in configuration i wont be creating and sender communication channel and sender Agreement,i need receiver communication channel,receiver determination and interface determination.
does my design and configuration looks good to you guys?
also i waz goin through some threads and it says that i need to setup HTTP client for this scenario and then specify a URL in a specific format.
where will i setup the HTTP client and where will i specify the URL?
thanx
ahmadAhmad,
><i>does my design and configuration looks good to you guys?</i>
Is correct.
><i>where will i setup the HTTP client and where will i specify the URL?</i>
Take a look at this thread and check the HTTP Client code.
Copy the code and save it as a HTML file and you have the HTTP Cliet ready. GIve the details of your server, sender service, interface etc and trigger the call to XI.
In a real time scenario, you will need to use the URL used in the HTTP Client code from your WebApplication to trigger the call to XI.
/message/266750#266750 [original link is broken]
Regards
Bhavesh -
Is there a way to detect a bad http client handle before it locks up LabVIEW?
The attached VI demonstrates a simple way to hang LabVIEW such that the only way to recover full use of it is to kill the LabVIEW process. LabVIEW version is 11.0.1f2 and this problem will occur in both WinXP and Win7.
Is there a way to detect when an HTTP Client Handle refnum is stale and should not be used?
Is this a known bug?
Attachments:
Hang after Bad HTTP Client Handle.vi 15 KBHave you tried the bad reference comparator?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps -
Error while creating Sales Order From HTTP Client
Hi,
I have a scenario, wherein I need to create SO from HTTP client (an HTML page). I paste my xml source data in the payload area and send the message. I get back this response:
Result:
<?xml version="1.0" encoding="UTF-8"?>
<ns1:Deep_RFCResponse_MT xmlns:ns1="http://mindtree.com/xi/m1004968"><SALESDOCUMENT><SALESORDERNO></SALESORDERNO></SALESDOCUMENT><RETURN><item><TYPE>E</TYPE><ID>V1</ID><MESSAGE>Sales document type OR is not defined</MESSAGE></item></RETURN></ns1:Deep_RFCResponse_MT>
I am supposed to get a SO no. here, but I get this message.
Whereas if I give same data at back end (in SAP system) the SO no is created successfully!
Can anybody tell me where am I going wrong, if I am?
Thank you,
Cheers,
Deepak.Hi Prateek.
You were right.....
The problem was with the data that I was passing. I was passing OR as the document type, which internally was being converted to TA.
It was creating the SO successfully because I was using the transaction se37 and this is where OR was converted to TA.
But if we use va01 to create the SO, we get this error.
Thank you....
Points!! definitely
Cheers,
Deepak.
Edited by: Deepak MS on Mar 13, 2008 5:20 AM -
Calling Web Service from EJB using HTTP Client
Hi,
Scenario:
I need to Call a Web Service from an EJB Application.I used HttpClient for calling the Web Service in the EJB Application. When i call the execute method of the HttpCLient it throws an exception
The element type "META" must be terminated by the matching end-tag "</META>"
The input XML does not have a node called META.
When i call the Web Service using Http Client form an Java Application it is working fine.
Kindly Suggest me the changes/steps that needs to be done
Regards,
S.V.Satish KumarHi Manish,
SOAP adapter does pass the message to XI (this message contains SOAP envelope although XI expects to get message without it), and during the mapping step i get "Runtime Exception in Message-Mapping transformatio~".
I suppose it's because i created proxy manually. I did so because when i imported WSDL, and tried to generate proxy in CRM, i got an error message that said that proxy couldn't be generated because external definitions are only allowed in XI 3. But my XI version is 3.0! And when I generate the same proxy in my R/3 system that is installed on WAS 640, it works.
What can I do?
Cheers,
Anya. -
Sending Msg From HTTP client to XI through JMS Adapter using WebSphereMQ
Hello
I am trying to send some msg from Http client
I configured JMS adapter as receiver
Transport Protocol :WEBsphereMQ JMS provider
Message protocol :JMS1.x
I have given the Ip address of my machine where I installed WEB Sphere MQ
Server Port :1416
Transport Protocol :WebSphere MQ
JMS compliant: JMS-compliant
In SXMB_MONI
Http client sends message without any error.
But while tracing I got message
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
Can anybody tell me the solution..
ThnaksHi,
I have not directly faced this but i may suggest ,
1. What do you see in sxmb_moni, do you have a queue problem?
2. see this File-to-File Scenario Stopped Working the reply from Shravan and the last message.
<i>The XBTO que was the problem. I deleted all LUWs in it and now new transactions are working again</i>
3. You may also use this /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Regards,
Anirban. -
Error while creating the HTTP client with destination
Hi ,
I am getting this error while connecting to https location on receiver channel . The below error i am getting in SXMB_moni
Error while creating the HTTP client with destination
The receiver party is doing some security setting on there end and for that purpose we have provided the external IP address to them , after that we are getting the above error.
We have already installed the client certificate on our staging server , and have done the correct setting in SM59 and channel.Check few things..
1) I believe you use specify destination for the addressing type field in the comm channel. If so make sure you entered valid target URL address in the SM59 of type http destination.
2) Check the validitity of the certificate. You can import the certificate both in java and abap stack.
3) Make sure certificate is installed as expected.
4) Send the request and talk to the target system and check what error information they get in their log related to ssl. -
Scenario is HTTP to db. In HTTP client, when Sender is Business Component, Pi is getting data successfully but when Business system is used as sender Pi is not getting any message in sxi monitor. Please help
Hi Ankita,
Try to trace at ICM level, Go to smicm transaction
Set level to 3.
Later send your request. Finally trace the request in:
When you have seen the log, check if any exception is raised with your request or the request and share it here.
Regards. -
HTTP Receiver Adapter - HTTP client code 110 reason error when sending
Hi,
I am getting the following error when using the HTTP adapter as a receiver to perform an HTTP Post in a destination system :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client code 110 reason</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Does anyone know what causes this error and more importantly how to trace it ?
Cheers
Colin.hi Colin,
Check in SMICM if your HTTP service is running. Also in RFC destination one of the parameter (SSL client Certificate) might be wrong which could also cause this problem.
Also check this thread:-
XI Error when upgraded to SP14 (Error Code 110) CLIENT_RECEIVE_FAILED
Have a look into this SAP Note - 897583
Regards.
Praveen
Maybe you are looking for
-
Just downloaded IOS 6 and it disabled my favorite game, Bubblets Tllt. Restarted and no luck. Tried to download new app and it is gone. Tried to download from website off Safari and message it is no longer sold in the US. Please help. Apple owes me f
-
I need help on iPhoto to print more than one picture at a time
I would like to know how to print 4 pictures on an 81/2x11 sheet of paper?
-
Question about a start routine
Hello, I'm trying to write a start routine to make some changes to the data while it is brought into a cube from another. Here is the scenario: FACID has ZRPROFCTR as an attribute. FACID is in cube 1 and 2. 0PROFIT_CTR is an characteristic in cube 2.
-
Is there a way to beautify the code automatically?
Are there any utilities/toolkits or anything else that may automatically beautify the code (remove (or at least lessen the number of bends) bends in wires, increase the visual appeal of the code, space-out the code symmetrically, etc, you know the c
-
Hello All I am looking to create a rate card based on a simple table of calculations and would preferably like to do this in a PDF format to look more professional. Would anybody know if this is even possible and if so, is there a recommended progra