Xml (SOAP) message to inovke method in webService

Hi all,
i have a question for u...
how can anyone help me to create a Soap message to invoke some method in webservice?
or give me a link where it explain how can i do this...
thanks a lot..
cb4

the link u give is about all client descrived in j2ee tutorial and they are create all with stub...
my question is about a client that can invoke a method on the webservice created with jaxrpc via xml (soap)
i think i can create this client with saaj....
but i would know if it is true...
or if exist another techonologies to create this type of client...
thanks a lot
cb4

Similar Messages

Error while sending XML SOAP message to other network

Hi,
I have a java application using SOAP through which I am sending request to a machine in the same network. It is giving the response in xml and i am able to parse it.
But when I tried to give the IP in the destination i.e the IP in the other network.
Error message SAAJ 0009 i.e message sending failed is getting to me.can somebody help to me.
Thanks
Abhilash

Hi Ricardo ,
I have the correct port now.
the url looks like
http://<host>:50000/XISOAPAdapter/MessageServlet?channel=:SIEBEL_DEV:SOAP_CUST
when I am testing it in the XML spy. and send a soap server request. I am getting the popup for user authentication . once i put my user id it gives me a error saying
HTTP operation 'POST' could not be performed on URL
'/XISOAPAdapter/MessageServlet?channel=:SIEBEL_DEV:SOAP_CUST&version=3.0&Sender.Service=SIEBEL_DEV&Interface=http%3A%2F%2FOFCOM%2FUNIFY%2FCustomerMaster%5EMI_CUST' due to an error :
The connection to the server was terminated abnormally
Any Idea as to why is such a error is coming
Thanks for the help
Nikhil

How to get javax.xml.soap.SOAPMessage handler?

Hello,
I'm trying to evaluate WebLogic AS 10, especially evaluate it if it's possible to use our custom access control module build using JACC API inside it. The problem is, we're using SOAPMessage handler, but it seems WebLogic does not register any handler at all at least by default? That's at least what I see after example H:\bea\wlserver_10.0\samples\server\examples\src\examples\webservices\jaxws\java2wsdl\SimpleEjbImpl.java
modification:
public String sayHello(String s) throws SystemException {
System.err.println("CALL sayHello: " + s);
Object obj = null;
try {
System.err.println("registered handlers: " + PolicyContext.getHandlerKeys());
obj = PolicyContext.getContext("javax.xml.soap.SOAPMessage");
} catch (PolicyContextException ex) {
ex.printStackTrace();
if (obj != null) {
SOAPMessage msg = (SOAPMessage)obj;
System.err.println("SOAP msg: " + msg);
else
System.err.println("This is not SOAP message!");
other method code is unchanged. Anyway, when I run this example I see in example server console that there are no registered handlers and in such situation following call to PolicyContext to obtain SOAPMessage handler fails with the IllegalArgumentException: unknown handler
My question is, what I have to do in order to setup WebLogic to use standard handlers like SOAPMessage handler, EJBArguments handler etc.?
Thanks!
Karel

Hello,
it seems I've found the reason myself. At least WebLogic does not seems to support JACC by default and it needs to be switched on manually.
Thanks,
Karel

How to Call web service operation by creating plain SOAP message in client?

Hi
Thank you for reading my post.
I have some questions about using web methods of a web service which i would be very gratfull if you could answer.
I should implement a web service that should receive a file with some other parameters from client and another web service which should receive some parameters and return a file.
I used a mechanism like the following one to handle the condition and it just works. But I have a problem, I need to create dynamic invocation and I must create soap message and send it to webservice (no IDE generated code)
What i need is one or two tips or a sample that shows how we can send and receive files by web services.
I want to know how we can create the SOAP message ourself and then send it to the web service endpoint and it call the web method and ....
Imagine the following web method, How i can invoke it by creating soap message myself and sending it to end point.
@WebMethod
public String saveFile(@WebParam(name = "fileName") String fileName, @WebParam(name = "fileContent") byte[] fileContent) {
// TODO implement operation
return "Something";
Another question is :
Does this mechanism that i used to transfer files is OK?
Is it optimized or there are some other ways to do this job.
I should say that i put one week on handlers to use soap attachments and i get no result.
So, Please let me know if you know or have some sample that show me how to do the above job.
Thanks.

Hi
From NW04s SP8 you can create webservice systems from within VC , and you will have the option of adding a user and password to authenticate. You can find it at Tools>>Define web service system. You will see a check box url requires user and password.
If for some reason you can not do it in VC then you should create the system in the portal and fill out the usermapping screens.
Jarrod Williams

WSE3.0 encrpyt and sign soap message together with disabled WSAdressing

Good Morning,
my task is to develop client´s applications written in .net4 who calls webservice (written by other- foreign firm in Java). My application, which calls webservice of other firm are: (plugin of MS CRM 2013, windowservice, windowformsapp for testing this communication)..
I had to implement encrypt and sign comunication with this webservice by client and servers certifikate.
I implemented this functions from:
http://msdn.microsoft.com/en-us/library/aa528788.aspx
and
http://msdn.microsoft.com/en-us/library/aa529565.aspx
by WSE 3.0.
Now I have to implement to disable WSAdresing in soap messege. Is it possible to use encrypt and sign from WSE together with disabled WSadressing?
(Other firm needs so as nodes of WSA will not be in soap message). With nodes WSAdresing in soap message, my communication with other webservice do not works. They (other firm) require no WSA nodes in soap message
If it is posible, how to implement this functionality?

Hi Matesak,
I'm afraid this is not the most suitable forum for your question. Please open a new thread in this forum, you'll get more valuable responses.
ASP.NET Forums >
Advanced ASP.NET >
WCF, ASMX and other Web Services
Thanks for your understanding.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Guidance on getting started with XML/SOAP and JDeveloper

I am not a novice programmer, but I am new to Java and web services and I need to get up to speed very quickly on JDeveloper, XML, SOAP, WSDL, UDDI, etc. Nothing I have read so far is making any sense. Could anyone please suggest the best place to start getting grounded in XML/SOAP messaging. It is my task to send and receive messages to an existing SOAP service on the web conveying data from our E-Bis Suite. Thanks, Bill.

Thanks! I made it through the JDeveloper Tutorial. I see a tutorial on the list specifically for Web Service from WSDL, so that's next. Hopefully, as I study the pieces, it will become easier to see how they all fit together.

External WebService call from CAF Core returns Invalid soap message

I am trying to perform the very simple action of calling a WebService from a CAF Core app service.
1. I imported the WS (Axis Web service running on NW 2004s SP9 server) with WSDL (option 2 on import external service page).
2. I then assembled the call in an app service method and invoke it.
3. I made sure to configure the end point for the service and the method using the External Service configuration.
When I execute the CAF core method using a simple Callable Object test client, I get the following error:
com.sap.caf.mp.base.exception.EngineException: Invalid soap message received
 at com.sap.caf.mp.core.data.service.manager.wsdl11.SOAPToMessageValueConverter.processComplexTypeMode(SOAPToMessageValueConverter.java:290)
 at com.sap.caf.mp.core.data.service.manager.wsdl11.SOAPToMessageValueConverter.generateComplexTypeValue(SOAPToMessageValueConverter.java:179)
 at
truncated.
I have also captured the XML request/reponse trace using tcpmon :
REQUEST:
POST /NWTestExpressWAR/services/TestExpressService HTTP/1.1
Host: 192.168.99.120:8078
Content-Type: text/xml; charset=UTF-8
Content-Length: 348
SOAPAction: http://www.testsys.com/TestExpressService/getAvailableModels
<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Body><ns1:GetAvailableModels xmlns:ns1="http://www.testsys.com/TestExpressService"/></SOAP-ENV:Body></SOAP-ENV:Envelope>
RESPONSE:
HTTP/1.1 200 OK
Server: SAP J2EE Engine/7.00
Set-Cookie: saplb_*=(J2EE11743000)11743050; Version=1; Path=/
Content-Type: text/xml; charset=utf-8
Date: Mon, 04 Dec 2006 02:19:39 GMT
Transfer-Encoding: chunked
Set-Cookie: JSESSIONID=(J2EE11743000)ID1261187150DB11296929644926762709End; Version=1; Domain=192.168.99.120; Path=/
1f3
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><GetAvailableModelsResponse xmlns="http://www.testsys.com/TestExpressService"><modelNames><name>Great Oak Manufacturing-January03 Test</name><name>PriceCheck-default</name></modelNames><errorMessagesReturn/></GetAvailableModelsResponse></soapenv:Body></soapenv:Envelope>
0
The only problem I can think off is that the transfer-encoding is marked as chunked which is causing the characters '1f3' and '0' to appear after and before the response and that this is causing the app to crash.
192.168.99.120 is the server the hosts the WS. It is also a 2004s SP9 server. The client server that hosts the CAF core service is of the same configuration. 8078 is the port I redirect for tcpmon purposes.
Could anyone shed some light on my problem?
Thanks,
Pratap.

It looks like NW WS client cannot handle Transfer-encoding of chunked even though this is part of HTTP 1.1. What seems to be happening is that the NW WS client is creating a HTTP 1.1 request. The service (axis ws running on NW) seeing this is creating a HTTP 1.1 response w/ chunked encoding. However, the client cannot handle this encoding and barfs. The solution is to change the service to return a HTTP/1.0 response since NW cant handle HTTP 1.1.
Pratap.

Erro javax.xml.soap.SOAPException: Message send failed: t4-2-dev-fmw01vm

hi am having this error when i click the submite button,am in jdeveloper 11.1.1.6.0
Messages for this page are listed below.
Error
javax.xml.soap.SOAPException: Message send failed: t4-2-dev-fmw01vm
Error
Message send failed: t4-2-dev-fmw01vm
Error
t4-2-dev-fmw01vm
<af:commandButton text="Submit" id="cb3"
 action="#{pageFlowScope.InternalUserBean.onSaveRecord}">
 </af:commandButton>
 public void onSave(ActionEvent actionEvent) {
 ADFUtil.invokeEL("#{bindings.Commit.execute}");
 ADFUtil.invokeEL("#{bindings.start.execute}");
 System.out.println("Deleted");
the log error is
Caused by: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: t4-2-dev-fmw01vm
 at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call2(HttpSOAPConnection.java:231)
 at oracle.j2ee.ws.common.transport.HttpTransport.transmit(HttpTransport.java:75)
 at oracle.j2ee.ws.common.async.MessageSender.call(MessageSender.java:64)
 at oracle.j2ee.ws.common.async.Transmitter.transmitSync(Transmitter.java:134)
 at oracle.j2ee.ws.common.async.Transmitter.transmit(Transmitter.java:90)
 at oracle.j2ee.ws.common.async.RequestorImpl.transmit(RequestorImpl.java:273)
 at oracle.j2ee.ws.common.async.RequestorImpl.invoke(RequestorImpl.java:94)
 at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:811)
 ... 74 more
Caused by: javax.xml.soap.SOAPException: Message send failed: t4-2-dev-fmw01vm
 at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.post2(HttpSOAPConnection.java:520)
 at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection$PrivilegedPost.run(HttpSOAPConnection.java:1264)
 at java.security.AccessController.doPrivileged(Native Method)
 at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call2(HttpSOAPConnection.java:229)
 ... 81 more
Caused by: java.net.UnknownHostException: t4-2-dev-fmw01vm
 at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
 at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:850)
 at java.net.InetAddress.getAddressFromNameService(InetAddress.java:1201)
 at java.net.InetAddress.getAllByName0(InetAddress.java:1154)
 at java.net.InetAddress.getAllByName(InetAddress.java:1084)
 at java.net.InetAddress.getAllByName(InetAddress.java:1020)
 at HTTPClient.HTTPConnection$11.run(HTTPConnection.java:3641)
 at java.security.AccessController.doPrivileged(Native Method)
 at HTTPClient.HTTPConnection.getSocket(HTTPConnection.java:3638)
 at HTTPClient.HTTPConnection.doConnect(HTTPConnection.java:4477)
 at HTTPClient.HTTPConnection.sendRequest(HTTPConnection.java:3409)
 at HTTPClient.HttpOutputStream.closeImpl(HttpOutputStream.java:461)
 at HTTPClient.HttpOutputStream.access$000(HttpOutputStream.java:99)
 at HTTPClient.HttpOutputStream$1.run(HttpOutputStream.java:417)
 at HTTPClient.HttpClientConfiguration.doAction(HttpClientConfiguration.java:698)
 at HTTPClient.HttpOutputStream.close(HttpOutputStream.java:415)
 at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.sendMessage(HttpSOAPConnection.java:1062)
 at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.post2(HttpSOAPConnection.java:495)
 ... 84 more
<Utils> <buildFacesMessage> ADF: Adding the following JSF error message: javax.xml.soap.SOAPException: Message send failed: t4-2-dev-fmw01vm
javax.xml.ws.WebServiceException: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: t4-2-dev-fmw01vm
 at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:867)
 at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:235)
 at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:106)
 at oracle.adf.model.connection.webservice.impl.SaajInteractionImpl.execute(SaajInteractionImpl.java:81)
 at oracle.adfinternal.model.adapter.webservice.provider.soap.SOAPProvider.execute(SOAPProvider.java:327)
 at oracle.adfinternal.model.adapter.webservice.WSDataControl.invokeOperation(WSDataControl.java:259)
 at oracle.adf.model.bean.DCBeanDataControl.invokeMethod(DCBeanDataControl.java:432)
 at oracle.adf.model.binding.DCInvokeMethod.callMethod(DCInvokeMethod.java:261)
 at oracle.jbo.uicli.binding.JUCtrlActionBinding.doIt(JUCtrlActionBinding.java:1635)
 at oracle.adf.model.binding.DCDataControl.invokeOperation(DCDataControl.java:2150)
 at oracle.adf.model.bean.DCBeanDataControl.invokeOperation(DCBeanDataControl.java:469)
 at oracle.adf.model.adapter.AdapterDCService.invokeOperation(AdapterDCService.java:313)
 at oracle.jbo.uicli.binding.JUCtrlActionBinding.invoke(JUCtrlActionBinding.java:740)
 at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.executeEvent(PageLifecycleImpl.java:402)
 at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding._execute(FacesCtrlActionBinding.java:252)
 at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding.execute(FacesCtrlActionBinding.java:210)
 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:597)
 at com.sun.el.parser.AstValue.invoke(Unknown Source)
 at com.sun.el.MethodExpressionImpl.invoke(Unknown Source)
 at view.ADFUtil.invokeEL(ADFUtil.java:22)
 at view.ADFUtil.invokeEL(ADFUtil.java:14)
 at view.InternalBean.onSaveRecord(InternalBean.java:59)
 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:597)
 at com.sun.el.parser.AstValue.invoke(Unknown Source)
 at com.sun.el.MethodExpressionImpl.invoke(Unknown Source)
 at org.apache.myfaces.trinidad.component.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:46)
 at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
 at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:190)
 at oracle.adf.view.rich.component.fragment.UIXRegion.broadcast(UIXRegion.java:148)
 at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:1018)
 at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:386)
 at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:194)
 at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)
 at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
 at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
 at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
 at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
 at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
 at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
 at java.security.AccessController.doPrivileged(Native Method)
 at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
 at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
 at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
 at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
 at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: t4-2-dev-fmw01vm
 at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call2(HttpSOAPConnection.java:231)
 at oracle.j2ee.ws.common.transport.HttpTransport.transmit(HttpTransport.java:75)
 at oracle.j2ee.ws.common.async.MessageSender.call(MessageSender.java:64)
 at oracle.j2ee.ws.common.async.Transmitter.transmitSync(Transmitter.java:134)
 at oracle.j2ee.ws.common.async.Transmitter.transmit(Transmitter.java:90)
 at oracle.j2ee.ws.common.async.RequestorImpl.transmit(RequestorImpl.java:273)
 at oracle.j2ee.ws.common.async.RequestorImpl.invoke(RequestorImpl.java:94)
 at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:811)
 ... 74 more
Caused by: javax.xml.soap.SOAPException: Message send failed: t4-2-dev-fmw01vm
 at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.post2(HttpSOAPConnection.java:520)
 at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection$PrivilegedPost.run(HttpSOAPConnection.java:1264)
 at java.security.AccessController.doPrivileged(Native Method)
 at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call2(HttpSOAPConnection.java:229)
 ... 81 more
Caused by: java.net.UnknownHostException: t4-2-dev-fmw01vm
 at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
 at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:850)
 at java.net.InetAddress.getAddressFromNameService(InetAddress.java:1201)
 at java.net.InetAddress.getAllByName0(InetAddress.java:1154)
 at java.net.InetAddress.getAllByName(InetAddress.java:1084)
 at java.net.InetAddress.getAllByName(InetAddress.java:1020)
 at HTTPClient.HTTPConnection$11.run(HTTPConnection.java:3641)
 at java.security.AccessController.doPrivileged(Native Method)
 at HTTPClient.HTTPConnection.getSocket(HTTPConnection.java:3638)
 at HTTPClient.HTTPConnection.doConnect(HTTPConnection.java:4477)
 at HTTPClient.HTTPConnection.sendRequest(HTTPConnection.java:3409)
 at HTTPClient.HttpOutputStream.closeImpl(HttpOutputStream.java:461)
 at HTTPClient.HttpOutputStream.access$000(HttpOutputStream.java:99)
 at HTTPClient.HttpOutputStream$1.run(HttpOutputStream.java:417)
 at HTTPClient.HttpClientConfiguration.doAction(HttpClientConfiguration.java:698)
 at HTTPClient.HttpOutputStream.close(HttpOutputStream.java:415)
 at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.sendMessage(HttpSOAPConnection.java:1062)
 at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.post2(HttpSOAPConnection.java:495)
 ... 84 more
the application is on the taskflowEdited by: adf009 on 2013/04/26 9:10 AM

I found http://download-uk.oracle.com/docs/cd/B31017_01/integrate.1013/b28981/events.htm#BABGGADB
Setting Timeouts for Synchronous Processes
For synchronous processes that connect to a remote database, you must increase the syncMaxWaitTime timeout property in the SOA_Oracle_Home\bpel\domains\default\config\domain.xml file:
<property id="syncMaxWaitTime">
<name>Delivery result receiver maximum wait time</name>
<value>60000000</value>
<comment>
<![CDATA[The maximum time the process result receiver will wait for a
result before returning. Results from asynchronous BPEL processes are
retrieved synchronously via a receiver that will wait for a result from the
container.
 
 The default value is 60 seconds.]]>
</comment>
</property>
But this changes nothing...
Is this value ignored?

Reliable SOAP messaging problems - weblogic.webservice.saf.StoreForwardException

Hi Guys,
I'm playing with the new SOAP reliable message transport in WL 8.1 SP 1.
I have configured a simple web service, with void return, configured for
reliable messaging. I deploy the client to the same server as the server
hosting the webservice, and it uses the async invocation etc.
It wasn't obvious how to throw the exception in the backend implementation.
I simply grab the usertransaction
and call ut.setRollbackOnly(). Hope that's correct..
Whenever I invoke the operation, I get this:
weblogic.webservice.saf.StoreForwardException: Could not find MessageData
header in aknowledgement
I have a JMS file store setup, and I have it assigned to the server via the
services/webservice tab, and I do see some activity in the file store.
My client looks like this:
AsyncInfo asyncInfo = new AsyncInfo();
asyncInfo.setReliableDelivery(true);
FutureResult fr = port.startReliableOperation("hello World", asyncInfo);
System.err.println("Client: Made invocation, invoking async end now");
port.endReliableOperation(fr);
Any ideas?
Regards,
Jon
PS. [As an aside, aknowledgement needs a 'c']
Client: port.StartReliableOperation()
--S:In reliable TX operation
--S:Going to roll back
--S: Set setRolbackOnly()
--S: Finished Reliable operation
Client: Made invocation, invoking async end now
<26-Aug-2003 18:39:31 o'clock BST> <Info> <WebService> <BEA-220025> <Handler
web
logic.webservice.saf.SAFHandler threw an exception from its handleResponse
metho
d. The exception was:
javax.xml.rpc.JAXRPCException: Failed to handle the response.>
myserver:Info:Handler weblogic.webservice.saf.SAFHandler threw an exception
from
its handleResponse method. The exception was:
javax.xml.rpc.JAXRPCException: Failed to handle the response.
<26-Aug-2003 18:39:31 o'clock BST> <Info> <WebService> <BEA-220047> <A
exception
was thrown from callReceive in the Client Dispatcher.>
myserver:Info:A exception was thrown from callReceive in the Client
Dispatcher.
<26-Aug-2003 18:39:31 o'clock BST> <Info> <WebService> <BEA-220034> <A stack
tra
ce associated with message 220047 follows:
javax.xml.rpc.soap.SOAPFaultException: Exception during processing:
weblogic.web
service.saf.StoreForwardException: Could not find MessageData header in
aknowled
gement. (see Fault Detail for stacktrace)
at
weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.ja
va:285)
at
weblogic.webservice.core.ClientDispatcher.callReceive(ClientDispatche
r.java:119)
at
weblogic.webservice.saf.ConversationAssembler.getResponse(Conversatio
nAssembler.java:302)
at
weblogic.webservice.saf.ConversationAssembler.execute(ConversationAss
embler.java:536)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>

Hi Jon,
I've asked our WS RM guru to comment on your question, but I believe the
answer is going to be that you can explicitly roll back the transaction,
however only from the EJB application method, using the
EJBContext.setRollbackOnly() method.
Regards,
Bruce
Jon Mountjoy wrote:
>
Hi Bruce,
I looked at the example you pointed to, and it does what it says it does.
However, it doesn't attempt to rollback a transaction, which is what I am
doing.
The docs for reliable messaging say:
" If you want to roll back the transaction from the Java method, use the
Java Transaction API (JTA) to get the transaction object and then explicitly
roll back the transaction. "
They also indicate that the receiver executes in the context of a
transaction, which you may rollback.
For example, when the server is down, the transaction doesn't commit. This
behaviour is tested by your example, and it works.
However, when I modify your example to roll back the transaction in the web
service operation backend implementation,
then it doesn't. It yields the same exception that mine does.
For example, I modified your MarketService.java as indicated below to grab
the initial context and then during the operation grab the usertransaction
and call setRollbackOnly(). This causes WebLogic to throw a
weblogic.webservice.saf.StoreForwardException.
Any ideas?
Regards,
Jon
public final class MarketService {
private static boolean mustThrow = true;
InitialContext ctx = null;
public MarketService() {
try {
ctx = new InitialContext();
System.err.println("---InitialContext is set");
} catch (Exception e) {
System.err.println("---InitialContext is not set: " + e);
public void placeOrder(OrderInfo o) {
System.out.println("[MarketService] placing order: " + o);
mustThrow = !mustThrow;
if (mustThrow) {
System.out.println("--S:Going to roll back");
UserTransaction ut = null;
try {
ut = (UserTransaction) ctx.lookup(
"javax.transaction.UserTransaction");
System.out.println("--S: Set setRolbackOnly()");
ut.setRollbackOnly();
// <------------------------------------------
} catch (Exception e) {
System.err.println("--S: UT transaction error:" + e);
} else {
System.out.println("--S: -Not rolling back");
--S:In reliable TX operation
--S:Going to roll back
--S: Set setRolbackOnly()
--S: Finished Reliable operation
<29-Aug-2003 15:48:24 o'clock BST> <Info> <WebService> <BEA-220025> <Handler
weblogic.webservice.saf.SAFHandler threw an
exception from its handleResponse method. The exception was:
javax.xml.rpc.JAXRPCException: Failed to handle the response.>
myserver:Info:Handler weblogic.webservice.saf.SAFHandler threw an exception
from its handleResponse method. The exceptio
n was:
javax.xml.rpc.JAXRPCException: Failed to handle the response.
<29-Aug-2003 15:48:25 o'clock BST> <Info> <WebService> <BEA-220047> <A
exception was thrown from callReceive in the Clie
nt Dispatcher.>
myserver:Info:A exception was thrown from callReceive in the Client
Dispatcher.
<29-Aug-2003 15:48:25 o'clock BST> <Info> <WebService> <BEA-220034> <A stack
trace associated with message 220047 follow
s:
javax.xml.rpc.soap.SOAPFaultException: Exception during processing:
weblogic.webservice.saf.StoreForwardException: Could
not find MessageData header in aknowledgement. (see Fault Detail for
stacktrace)
at
weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:285)
at
weblogic.webservice.core.ClientDispatcher.callReceive(ClientDispatcher.java:
119)
at
weblogic.webservice.saf.ConversationAssembler.getResponse(ConversationAssemb
ler.java:302)
at
weblogic.webservice.saf.ConversationAssembler.execute(ConversationAssembler.
java:536)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
myserver:Info:A stack trace associated with message 220047 follows:

How to get full SOAP message in WebService

hi,
Is it possible to get SOAP message while Request operation during transaction in WebService.
I tried with Handler, while retreiving message it is having a MessageContext. How to initilize that like example
public boolean handleRequest(MessageContext mc) {
          SOAPMessageContext messageContext = (SOAPMessageContext) mc;
          System.out.println("** Request: "+ messageContext.getMessage().toString());
          return true;
     }while i make a class called SoapHdlr i have implemented all methods including the above.
In that from my class if i want to call the above method i need to pass MessageContext how to give that MessageContext or any other ways to get SOAPMessage fully.
plz can any one guide me there
ThanKQ

I think, there are some concepts missunderstood. First if you use JAX-WS- Metro framework, this kind of handlers will work. Also you should identify your SOAPHandler for your web service. For ex: in Netbeans 6, you can right click on service and select configure handlers. Then you decide your handler.
Then automatically, Metro framework directs SOAPMessages to your SOAPHandler to handle full SOAPs. HandleMessage() method will work.
If you have problem again, just ask.

Javax.xml.soap.SOAPException: Message send failed: Connection timed out

Hi,
where can i adjust the timeout for:
exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection timed out: connect
The webservice needs 5min to return a message....
I found a duplicate of this on thread:
error initiating a test instance
But no answer
Message was edited by:
HEWizard

I found http://download-uk.oracle.com/docs/cd/B31017_01/integrate.1013/b28981/events.htm#BABGGADB
Setting Timeouts for Synchronous Processes
For synchronous processes that connect to a remote database, you must increase the syncMaxWaitTime timeout property in the SOA_Oracle_Home\bpel\domains\default\config\domain.xml file:
<property id="syncMaxWaitTime">
<name>Delivery result receiver maximum wait time</name>
<value>60000000</value>
<comment>
<![CDATA[The maximum time the process result receiver will wait for a
result before returning. Results from asynchronous BPEL processes are
retrieved synchronously via a receiver that will wait for a result from the
container.

The default value is 60 seconds.]]>
</comment>
</property>
But this changes nothing...
Is this value ignored?

HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: String index out of range: -7

All -
I'm new to consuming web services in JDeveloper. I'm using Oracle JDEV 10.1.3.3/OC4J. I'm using this version since it is compatible with Oracle EBS 12.1.3. My intent is to pull data from our third party recruitment app (Success Factors) and load that data into Oracle HRIS. I'm already doing this through a .NET application. I'm converting it to be a Java Concurrent Program in EBS. The code listed below is a stub call to verify I'm on the right track. I created a JDeveloper Web Services proxy project. I'm testing it locally on my windows desktop. When I'm able to consume the service successfully, then I'll think about moving it to the EBS server.
I'm getting the following error when I invoke the following service:
HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: String index out of range: -7
End point is: https://api4.successfactors.com/sfapi/v1/soap?wsdl
Any help/assistance would be much appreciated.
Below is my code and output of my test:
package emsc.oracle.apps.emscper.sfapi.proxy;
import HTTPClient.HTTPConnection;
import emsc.oracle.apps.emscper.sfapi.proxy.types.sfobject_sfapi_successfactors_com.IsValidSession;
import emsc.oracle.apps.emscper.sfapi.proxy.types.sfobject_sfapi_successfactors_com.IsValidSessionResponse;
import emsc.oracle.apps.emscper.sfapi.proxy.types.sfobject_sfapi_successfactors_com.Login;
import emsc.oracle.apps.emscper.sfapi.proxy.types.sfobject_sfapi_successfactors_com.LoginResponse;
import emsc.oracle.apps.emscper.sfapi.proxy.types.sfobject_sfapi_successfactors_com.LoginResult;
import emsc.oracle.apps.emscper.sfapi.proxy.types.sfobject_sfapi_successfactors_com.Logout;
import emsc.oracle.apps.emscper.sfapi.proxy.types.sfobject_sfapi_successfactors_com.LogoutResponse;
import emsc.oracle.apps.emscper.sfapi.proxy.types.sfobject_sfapi_successfactors_com.SFCredential;
import emsc.oracle.apps.emscper.sfapi.proxy.types.sfobject_sfapi_successfactors_com.SFParameter;
import emsc.oracle.apps.emscper.sfapi.proxy.types.sfobject_sfapi_successfactors_com.Error;
import java.io.File;
import javax.xml.rpc.ServiceFactory;
import java.util.ArrayList;
import java.util.List;
import java.util.Date;
import javax.xml.ws.BindingProvider;
import javax.xml.soap.SOAPException;
import java.util.Map;
import oracle.security.ssl.OracleSSLCredential;
public class SFAPITest {
 // Declare members:
 private String companyId;
 private String userName;
 private String password;
 private String developerKey;
 private Date effDt;
 private String greaterThanEffDt;
 private String lessThanEffDt;
 // Declare constants:
 final static private String breakLine = "+---------------------------------------------------------------------------+";
 final static private String format = "yyyy-mm-dd";
 private enum ReqId {
 PrimaryReq(25),
 PrimaryReqCEO(26),
 EmCarePrimary(27),
 RTI(28),
 EmCareClinical(29);
 private int reqId;
 private ReqId() {
 private ReqId(int value) {
 reqId = value;
 public int getReqId() {
 return reqId;
 // Getters and Setters:
 protected String getCompanyId() {
 return this.companyId;
 protected void setCompanyId(String value) {
 this.companyId = value;
 protected String getUserName() {
 return this.userName;
 protected void setUserName(String value) {
 this.userName = value;
 protected String getPassword() {
 return this.password;
 protected void setPassword(String value) {
 this.password = value;
 protected String getDeveloperKey() {
 return this.developerKey;
 protected void setDeveloperKey(String value) {
 this.developerKey = value;
 protected Date getEffDt() {
 return this.effDt;
 protected void setEffDt(Date value) {
 this.effDt = value;
 protected String getGreaterThanEffDt() {
 return this.greaterThanEffDt;
 protected void setGreaterThanEffDt(String value) {
 this.greaterThanEffDt = value;
 protected String getLessThanEffDt() {
 return this.lessThanEffDt;
 protected void setLessThanEffDt(String value) {
 this.lessThanEffDt = value;
 public void runProgram()
 SFAPIService mySFAPIService;
 String CompletionText = "";
 String effDtStr2 = null;
 /* Code your program logic here.
 * Use getJDBCConnection method to get the connection object for any
 * JDBC operations.
 * Use CpContext provided commit,rollback methods to commit/rollback
 * data base transactions.
 * Don't forget to release the connection before returning from this
 * method.
 /* Call setCompletion method to set the request completion status and
 * completion text.
 * Status values are ReqCompletion.NORMAL,ReqCompletion.WARNING,
 * ReqCompletion.ERROR.
 * Use Completion text message of length 240 characters. If it is more
 * than 240 then full string will appear in log file and truncated 240
 * characters will be used as request completion text.
 try
 ServiceFactory factory = ServiceFactory.newInstance();
 mySFAPIService = (emsc.oracle.apps.emscper.sfapi.proxy.SFAPIService)factory.loadService(emsc.oracle.apps.emscper.sfapi.proxy.SFAPIService.class);
 SFAPI api = mySFAPIService.getSFAPI();
 /// SFAPI api = new SFAPI();
 //Map<String, Object> requestContext = ((BindingProvider) api).getRequestContext();
 //requestContext.put(BindingProvider.SESSION_MAINTAIN_PROPERTY, true);
 System.out.println("ServiceName => " + mySFAPIService.getServiceName().toString());
 System.out.println("End Point => " + mySFAPIService.getServiceName().toString());
 System.out.println(breakLine);
 // Authentication: Login to SFAPI:
 SFCredential credential = new SFCredential();
 // Fake credentials being passed in for this post:
 credential.setCompanyId("XXX");
 credential.setUsername("XXX");
 credential.setPassword("XXX");
 credential.setDeveloperKey("XXX");
 HTTPConnection httpsConnection = null;
 OracleSSLCredential _credential = new OracleSSLCredential();
 _credential.setWallet("\\\\\\C:\\Program Files\\Java\\jdk1.6.0_33\\jre\\lib\\security", "ParkEstes3");
 /*System.setProperty("javax.net.ssl.trustStore","C:\\\\\OraHome_1\\jdev\\jdevbin\\jdk\\jre\\lib\\security\\keystore");
 System.setProperty("javax.net.ssl.trustStorePassword","changeit");
 System.out.println(System.getProperty("javax.net.ssl.trustStore"));*/
 // SFParameter: Define a generic SFParameter List. This is a necessary parameter
 // to invoking calls in SFAPI:
 /*System.setProperty("javax.net.ssl.keyStore",
 "file:\\\C:\\jdk1.4.1\\jre\\lib\\security\\client.keystore");
 System.setProperty("javax.net.ssl.keyStorePassword","welcome"); */
 /* System.setProperty("oracle.net.wallet_location",
 "(SOURCE=(METHOD=file)(METHOD_DATA=(DIRECTORY=\\\C:\Users\dparrish\Oracle\WALLETS)))"); // (2) */
 File kstore = new File("C:\\OraHome_1\\jdev\\jdevbin\\jdk\\jre\\lib\\security\\jssecacerts");
 boolean exists = kstore.exists();
 if (!exists) {
 System.out.println("Keystore does not exist");
 else {
 System.out.println("Keystore does exist");
 System.setProperty("javax.net.ssl.trustStore", kstore.getAbsolutePath());
 System.setProperty("javax.net.ssl.trustStorePassword", "changeit");
 //System.setProperty("proxySet", "false");
 //System.setProperty("http.proxyHost", "127.0.0.1");
 //System.setProperty("http.proxyPort", "8080");
 System.out.println(kstore.getAbsolutePath());
 List<SFParameter> lst = new ArrayList<SFParameter>();
 SFParameter param = new SFParameter();
 param.setName("");
 param.setValue("");
 lst.add(param);
 SFParameter[] sfParam = lst.toArray(new SFParameter[lst.size()]);
 Login login = new Login();
 try {
 login.setCredential(credential);
 System.out.println("1");
 login.setParam(sfParam);
 System.out.println("2");
 LoginResponse loginResponse = new LoginResponse();
 LoginResult loginResult = new LoginResult();
 try {
 loginResponse = api.login(login);
 catch (Exception e ) {
 System.out.println(e.getMessage());
 System.out.println("3");
 try {
 loginResult = loginResponse.getResult();
 catch (Exception e ) {
 System.out.println(e.getMessage());
 System.out.println("4");
 IsValidSession vs = new IsValidSession();
 IsValidSessionResponse isValidSessionResponse = api.isValidSession(vs);
 System.out.println("5");
 if (isValidSessionResponse.isResult()) {
 System.out.println("Session is valid");
 System.out.println("Result => " + loginResult.getSessionId());
 System.out.println(breakLine);
 Logout logout = new Logout();
 LogoutResponse logoutResponse = api.logout(logout);
 if (logoutResponse.isResult()) {
 System.out.println("Logout of SFAPI Successful");
 else {
 System.out.println("Logout of SFAPI Unsuccessful");
 else {
 System.out.println("Session is invalid");
 List<Error> errors = new ArrayList<Error>();
 for (int i = 0; i < loginResult.getError().length; i++) {
 errors.add(loginResult.getError()[i]);
 for (int i = 0; i < errors.size(); i++) {
 System.out.println("Error Indice => " + i);
 System.out.println("Error Code: => " + errors.get(i).getErrorCode());
 System.out.println("Error Message: => " + errors.get(i).getErrorMessage());
 System.out.println(breakLine);
 } // end for loop of SFObject errors
 } // end InvalidSession
 catch (Exception e)
 System.out.println("Session Credential Exception");
 System.out.println("Exception => " + e.getMessage());
 System.out.println(breakLine);
 catch (Exception e)
 System.out.println("Parameter List Exception");
 System.out.println("Exception => " + e.getMessage());
 System.out.println(breakLine);
 } // end runProgram
 // Constructor:
 public SFAPITest() {
 } // end constructor
 public static void main (String args[]) {
 try
 SFAPITest test = new SFAPITest();
 test.runProgram();
 catch (Exception e) {
 System.out.println("main exception => " + e.getMessage());
} // SFAPITest
Here is the output with trace:
WARNING: Unable to connect to URL: https://api4.successfactors.com:443/sfapi/v1/soap due to java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: String index out of range: -7
Session Credential Exception
Exception => ; nested exception is:
 HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: String index out of range: -7
+---------------------------------------------------------------------------+
Process exited with exit code 0.

The other end is throwing back a programming error.
That might be because you are sending incorrect data and the other end fails to validate it.
You might be able to guess based on your C# code. But, since you are using soap one generic solution is available to you.
- Get an http proxy interceptor like wireshark.
- Run it while your C# app runs, collect the http requests from that.
- Run it while running your java code, collect the http requests from that.
Compare the two.

How to get SOAP Message while Request in WebService.. ?

i am working on Web Logic WebService. I have created Web service and deployed into server.
But now is there any ways to get the SOAP Message while request because i want to add some headers to the my SOAP Message before it sent to the backend.
SOAPMessageContext smc=null;
SOAPMessage soapMsg = smc.getMessage();
System.out.println("SOAP MESSAGE :"+soapMsg);
But I am getting NullPointerException.
any Help ??...
ThankQ.
Ajay

Hi
In your code the NullPointerException is expected as the message context is null and not initialized before you call getMessage method on it.
You can use soap handlers (client/server side handlers) to add the headers to the message before it is sent to the server.
Soap handler has methods like below in which you can add the headers.
* Handles incoming web service requests and outgoing callback requests
public boolean handleRequest(MessageContext mc)
System.out.println("Soap message is: \n " +
((SOAPMessageContext)mc).getMessage() + "\n");
return true;
More docs at http://e-docs.bea.com/wls/docs100/webserv_adv/handlers.html
Vimala-

Posting XML via HTTP post returns "Envelope missing in SOAP message header"

Hi,
I am trying to post a simple XML message directly to the integration server using an html document, where the form that contains the XML message is a simple
<FORM action="http://servername:8000/sap/xi/engine?type=entry" method="post">
So, I add my xml message like this:
<?xml version="1.0" encoding="UTF-8">
<ns:PlantMaintenanceMessageType xmlns:ns="http://sap.com/demo/plantmaintenance">
 <EquipmentID>SLIEQUIP5</EquipmentID>
 <FunctionalLocation>KB</FunctionalLocation>
 <Date/>
 <Time/>
</ns:PlantMaintenanceMessageType>
but I get a message back from the Integration Server as:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="PARSER">ITEM_MISSING</SAP:Code>
<SAP:P1>Envelope</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XML tag Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
</SAP:Error>
Seems like I am missing the Envelope so my Integration Server can understand my post. What does the Envelope look like or should conatain so that the Integration Server accepts my XML file ?
Thanks !

This is the trace
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external =</Trace>
<Trace level="1" type="T">Sender agency external =</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = sapqxh:8020</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 10.228.137.106</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="3" type="T">system-ID = QXH</Trace>
<Trace level="3" type="T">client = 220</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = PISUPER</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:19:04Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 4880474945AE67E2E10000000AE4896A</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = 4880474945AE67E2E10000000AE4896A</Trace>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBTL0000</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTL0000</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="3" type="T">Setup qRFC Scheduler</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = 4880474945AE67E2E10000000AE4896A</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">OK.</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface MIOA_US139_EmployeeData*</Trace>
<Trace level="1" type="T">select interface namespace urn:abbott-com:US139</Trace>
<Trace level="1" type="T">found interface MIOA_US139_EmployeeData</Trace>
<Trace level="1" type="T">found action ARCH</Trace>
<Trace level="1" type="T">set interface action to ARCH</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = QXH</Trace>
<Trace level="3" type="T">client = 220</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = PISUPER</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - BS_AIMS</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2008-07-18T14:19:11Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) BS_AIMS MIIA_US139_EmployeeData</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: MIIA_US139_EmployeeData</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:19:11Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
<Trace level="1" type="Timestamp">2008-07-18T14:19:14Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination</Trace>
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTM0000</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
<Trace level="2" type="T">Increment log sequence to 005</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = QXH</Trace>
<Trace level="3" type="T">client = 220</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = PISUPER</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:19:20Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-07-18T14:19:20Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
<Trace level="1" type="Timestamp">2008-07-18T14:19:20Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping already defined in interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping 3CCA7AE76D3F33F19F8D7A8DAD494E65</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping C387A5F00F8B11DCAB84C751AAE12E82</Trace>
<Trace level="1" type="T">Interface Mapping urn:abbott-com:US139 IM_US139_EmployeeData</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_US139_EmployeeData_</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_US139_EmployeeData_.</Trace>
<Trace level="3" type="T">Load c387a5f0-0f8b-11dc-ab84-c751aae12e82, urn:abbott-com:US139, -1, com/sap/xi/tf/_MM_US139_EmployeeData_.class.</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_MM_US139_EmployeeData_.class (urn:abbott-com:US139, -1) in swcv c387a5f0-0f8b-11dc-ab84-c751aae12e82.</Trace>
<Trace level="3" type="T">Loaded class com.sap.xi.tf._MM_US139_EmployeeData_</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_US139_EmployeeData_</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_US139_EmployeeData_ completed. (executeStep() of com.sap.xi.tf._MM_US139_EmployeeData_</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:22:07Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 005</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2008-07-18T14:22:12Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
<Trace level="2" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
<Trace level="2" type="T">-QEHCLNT230</Trace>
<Trace level="2" type="T">-BS_AIMS</Trace>
<Trace level="2" type="T">urn:abbott-com:US139.MIIA_US139_EmployeeData</Trace>
<Trace level="2" type="T">Channel found: - BS_AIMS - CC_BS_AIMS_File_Out_09</Trace>
<Trace level="2" type="T">no header mapping defined</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:22:12Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 006</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
- 
<Trace level="1" type="Timestamp">2008-07-18T14:22:18Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS =</Trace>
<Trace level="3" type="T">P_IFNAME =</Trace>
<Trace level="3" type="T">P_METHOD =</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Unknown channel type: File</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = AENGINE</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for adapter engine: File</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">old values in cache (no lock found) - start reading from SLD</Trace>
<Trace level="1" type="T">error reading SAP_XIAdapterFramework from SLD</Trace>
<Trace level="2" type="T">Adapter Framework(s) found</Trace>
<Trace level="2" type="T">Service Port(s) found - take first one</Trace>
<Trace level="2" type="T">URL found</Trace>
<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
<Trace level="3" type="T">URL = http://sapqxh:52000/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="3" type="T">User = PIISUSER</Trace>
<Trace level="3" type="T">Cached =</Trace>
<Trace level="3" type="T">Creating HTTP-client</Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="3" type="T">Security: Basic authentication</Trace>
<Trace level="3" type="T">Serializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="3" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="3" type="T">HTTP-client: status code = 200</Trace>
<Trace level="3" type="T">Deserializing message object...</Trace>
<Trace level="1" type="T">Empty response received!</Trace>
<Trace level="3" type="System_Error">HTTP-client: error response=</Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
</Trace>
</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 007</Trace>
<Trace level="3" type="T">Message version 007</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 008</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>

Web-services.xml for EJB component and SOAP Message Handler Chain

I have used the following example for my own web service with EJB component and SOAP
Message Handler Chain:
http://e-docs.bea.com/wls/docs70/webServices/dd.html#1058208
I have a deployment error:
javax.naming.NameNotFoundException: Unable to resolve 'app/ejb/DocumentService.j
ar#DocumentService/home' Resolved: 'app/ejb' Unresolved:'DocumentService.jar#Doc
umentService' ; remaining name 'DocumentService.jar#DocumentService/home'
In attachement is the ear file.
Is there a problem in web-services.xml?
Thanks
[ws_dox_sdi.ear]

It works. Thanks,
Ioana
"Neal Yin" <[email protected]> wrote:
The error means your EJB is not deployed.
Adding a EJB module to your application.xml file of the ear should fixe
it.
<application>
<display-name />
<module>
<web>
<web-uri>dox_sdi.war</web-uri>
</web>
</module>
<module>
<ejb>DocumentService.jar</ejb>
</module>
</application>
"Ioana Meissner" <[email protected]> wrote in message
news:3cf640cc$[email protected]..
I have used the following example for my own web service with EJBcomponent and SOAP
Message Handler Chain:
http://e-docs.bea.com/wls/docs70/webServices/dd.html#1058208
I have a deployment error:
javax.naming.NameNotFoundException: Unable to resolve'app/ejb/DocumentService.j
ar#DocumentService/home' Resolved: 'app/ejb'Unresolved:'DocumentService.jar#Doc
umentService' ; remaining name 'DocumentService.jar#DocumentService/home'
In attachement is the ear file.
Is there a problem in web-services.xml?
Thanks

Xml (SOAP) message to inovke method in webService

Similar Messages

Maybe you are looking for