Problem about "proxy to web service"
Hi, I designed a scenario to test proxy2WS but faced a problem, my steps design are as follows:
1. import the WSDL file
2. create 2 message types (request and response)
3. create a outbound service interface which use the message types
4. create a inbound service interface which use the external message from imported WSDL file
5. create a request message mapping between the designed request message designed by myself and the external request message imported
6. create a response message mapping between the designed response message designed by myself and the external response message imported
7. create a interface mapping between the outbound and inbound messages and use the message mappings for them
8. config the necessary elements in the configuration time
9. generate ABAP proxy code to test proxy2WS
Exception raised: Während des Anwendungs-Mappings com/sap/xi/tf/_ZHello_Response_Mapping_ ist eine RuntimeException aufgetreten. com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns1:ZHello_Response. Values missing in queue context. Target XSD ~
when I used SXMB_MONI to see the trace of the calling, I found that the return result is correct, but failed when transforming the result to the message type that we designed by myself.
Could anyone help me to solve the problem? Thanks a lot.
Error message when I test transforming the response message to the MT in design time:
18:11:01 Start of test
Cannot create target element /ns0:ZHello_Response. Values missing in queue context. Target XSD requires a value for this element, but the target-field mapping does not create one. Check whether the XML instance is valid for the source XSD, and whether the target-field mapping fulfils the requirement of the target XSD com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:ZHello_Response. Values missing in queue context. Target XSD requires a value for this element, but the target-field mapping does not create one. Check whether the XML instance is valid for the source XSD, and whether the target-field mapping fulfils the requirement of the target XSD at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:328) at com.sap.aii.mappingtool.tf7.AMappingProgram.start(AMappingProgram.java:460) at com.sap.aii.mappingtool.tf7.Transformer.start(Transformer.java:137) at com.sap.aii.mappingtool.tf7.AMappingProgram.transform(AMappingProgram.java:579) at com.sap.aii.ibrep.server.mapping.exec.ExecuteXiMappingCommand.transformInternal(ExecuteXiMappingCommand.java:197) at com.sap.aii.ibrep.server.mapping.exec.ExecuteXiMappingCommand.execute(ExecuteXiMappingCommand.java:94) at com.sap.aii.ib.server.mapping.exec.CommandManager.execute(CommandManager.java:43) at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:40) at com.sap.aii.ibrep.server.mapping.MapServiceBean.execute(MapServiceBean.java:40) at sun.reflect.GeneratedMethodAccessor849_10001.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceed(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:101) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceed(RequestInvocationContext.java:92) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:26) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:101) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceed(RequestInvocationContext.java:92) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:28) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:101) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceed(RequestInvocationContext.java:92) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:109) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:15) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:101) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceed(RequestInvocationContext.java:92) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:20) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:101) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceed(RequestInvocationContext.java:92) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_RemoteExceptionConverter.invoke(Interceptors_RemoteExceptionConverter.java:24) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:101) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceed(RequestInvocationContext.java:92) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:14) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:101) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceed(RequestInvocationContext.java:92) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:128) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:174) at $Proxy274_10001.execute(Unknown Source) at sun.reflect.GeneratedMethodAccessor848_10001.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:196) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:227) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:140) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:227) Cannot create target element /ns0:ZHello_Response. Values missing in queue context. Target XSD requires a value for this element, but the target-field mapping does not create one. Check whether the XML instance is valid for the source XSD, and whether the target-field mapping fulfils the requirement of the target XSD
18:11:01 End of test
Similar Messages
-
Problem about Calling SQLplus Web Service on Aspen Watch Server
Hi all,
We're using MII 11.5 and trying to call a web service from a Aspen Watch server through the web service block in transaction. The web service enclosed a function call ExecuteSQL which will accept a sql query function and return a set of Data. Now, using the same web service on two different servers, we got a success(server A) and a failure(Server B). On the failed call, right in the first page of enter a URL, it will return a "SOAP Service could not be loaded: The element type 'META' must be terminated by the machine end-tag '</META>'" error.
According to the admin of the web server, the web service on both servers can be called correctly when he created two simple ASP pages. After serious testing, he thought that the only reason should be MII may not be compatible with .Net 2.0 binding web service. The following is some comparison we made to the two servers.
Server A / Server B / Error, if applicable
.Net Framework installed on MII server: 1.1, 2.0 / 1.1, 2.0
.Net Binding: 1.1 / 2.0
IIS version on MII server: 6 / 6
From MII server broser to Server A web service: Yes / Yes
From MII server browser to Server B web service: No / No / Return on web "The test form is only available for requests from the local machine"
From localhost browser to Server A web service: n/a // Yes
From localhost browser to Server B web service: Yes // n/a
From PC browser to Server B web service: No / Yes / Return on web "The test form is only available for requests from the local machine"
Credentials required to run web service: No / Yes /
The following are the SOAP generated:
Server A
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.aspentech.com/SQLplus.WebService/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://www.aspentech.com/SQLplus.WebService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
- <wsdl:types>
- <s:schema elementFormDefault="qualified" targetNamespace="http://www.aspentech.com/SQLplus.WebService/">
- <s:element name="ExecuteSQL">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="command" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
- <s:element name="ExecuteSQLResponse">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="ExecuteSQLResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="string" nillable="true" type="s:string" />
</s:schema>
</wsdl:types>
- <wsdl:message name="ExecuteSQLSoapIn">
<wsdl:part name="parameters" element="tns:ExecuteSQL" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLSoapOut">
<wsdl:part name="parameters" element="tns:ExecuteSQLResponse" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLHttpGetIn">
<wsdl:part name="command" type="s:string" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLHttpGetOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLHttpPostIn">
<wsdl:part name="command" type="s:string" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLHttpPostOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
- <wsdl:portType name="SQLplusWebServiceSoap">
- <wsdl:operation name="ExecuteSQL">
<wsdl:input message="tns:ExecuteSQLSoapIn" />
<wsdl:output message="tns:ExecuteSQLSoapOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:portType name="SQLplusWebServiceHttpGet">
- <wsdl:operation name="ExecuteSQL">
<wsdl:input message="tns:ExecuteSQLHttpGetIn" />
<wsdl:output message="tns:ExecuteSQLHttpGetOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:portType name="SQLplusWebServiceHttpPost">
- <wsdl:operation name="ExecuteSQL">
<wsdl:input message="tns:ExecuteSQLHttpPostIn" />
<wsdl:output message="tns:ExecuteSQLHttpPostOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="SQLplusWebServiceSoap" type="tns:SQLplusWebServiceSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ExecuteSQL">
<soap:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:binding name="SQLplusWebServiceSoap12" type="tns:SQLplusWebServiceSoap">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ExecuteSQL">
<soap12:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
- <wsdl:input>
<soap12:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap12:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:binding name="SQLplusWebServiceHttpGet" type="tns:SQLplusWebServiceHttpGet">
<http:binding verb="GET" />
- <wsdl:operation name="ExecuteSQL">
<http:operation location="/ExecuteSQL" />
- <wsdl:input>
<http:urlEncoded />
</wsdl:input>
- <wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:binding name="SQLplusWebServiceHttpPost" type="tns:SQLplusWebServiceHttpPost">
<http:binding verb="POST" />
- <wsdl:operation name="ExecuteSQL">
<http:operation location="/ExecuteSQL" />
- <wsdl:input>
<mime:content type="application/x-www-form-urlencoded" />
</wsdl:input>
- <wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="SQLplusWebService">
- <wsdl:port name="SQLplusWebServiceSoap" binding="tns:SQLplusWebServiceSoap">
<soap:address location="http://clkaspenwatch:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
- <wsdl:port name="SQLplusWebServiceSoap12" binding="tns:SQLplusWebServiceSoap12">
<soap12:address location="http://clkaspenwatch:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
- <wsdl:port name="SQLplusWebServiceHttpGet" binding="tns:SQLplusWebServiceHttpGet">
<http:address location="http://servera:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
- <wsdl:port name="SQLplusWebServiceHttpPost" binding="tns:SQLplusWebServiceHttpPost">
<http:address location="http://servera:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Server B
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.aspentech.com/SQLplus.WebService/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://www.aspentech.com/SQLplus.WebService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
- <wsdl:types>
- <s:schema elementFormDefault="qualified" targetNamespace="http://www.aspentech.com/SQLplus.WebService/">
- <s:element name="ExecuteSQL">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="command" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
- <s:element name="ExecuteSQLResponse">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="ExecuteSQLResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
- <wsdl:message name="ExecuteSQLSoapIn">
<wsdl:part name="parameters" element="tns:ExecuteSQL" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLSoapOut">
<wsdl:part name="parameters" element="tns:ExecuteSQLResponse" />
</wsdl:message>
- <wsdl:portType name="SQLplusWebServiceSoap">
- <wsdl:operation name="ExecuteSQL">
<wsdl:input message="tns:ExecuteSQLSoapIn" />
<wsdl:output message="tns:ExecuteSQLSoapOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="SQLplusWebServiceSoap" type="tns:SQLplusWebServiceSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ExecuteSQL">
<soap:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:binding name="SQLplusWebServiceSoap12" type="tns:SQLplusWebServiceSoap">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ExecuteSQL">
<soap12:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
- <wsdl:input>
<soap12:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap12:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="SQLplusWebService">
- <wsdl:port name="SQLplusWebServiceSoap" binding="tns:SQLplusWebServiceSoap">
<soap:address location="http://serverb:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
- <wsdl:port name="SQLplusWebServiceSoap12" binding="tns:SQLplusWebServiceSoap12">
<soap12:address location="http://serverb:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Please advise me on how to fix the probelm. And please let me know any additional information is needed. Greatly appreciated~
Best regards,
Lawrence
Edited by: UMeng Lai on Feb 6, 2009 4:07 PMHi all,
We're using MII 11.5 and trying to call a web service from a Aspen Watch server through the web service block in transaction. The web service enclosed a function call ExecuteSQL which will accept a sql query function and return a set of Data. Now, using the same web service on two different servers, we got a success(server A) and a failure(Server B). On the failed call, right in the first page of enter a URL, it will return a "SOAP Service could not be loaded: The element type 'META' must be terminated by the machine end-tag '</META>'" error.
According to the admin of the web server, the web service on both servers can be called correctly when he created two simple ASP pages. After serious testing, he thought that the only reason should be MII may not be compatible with .Net 2.0 binding web service. The following is some comparison we made to the two servers.
Server A / Server B / Error, if applicable
.Net Framework installed on MII server: 1.1, 2.0 / 1.1, 2.0
.Net Binding: 1.1 / 2.0
IIS version on MII server: 6 / 6
From MII server broser to Server A web service: Yes / Yes
From MII server browser to Server B web service: No / No / Return on web "The test form is only available for requests from the local machine"
From localhost browser to Server A web service: n/a // Yes
From localhost browser to Server B web service: Yes // n/a
From PC browser to Server B web service: No / Yes / Return on web "The test form is only available for requests from the local machine"
Credentials required to run web service: No / Yes /
The following are the SOAP generated:
Server A
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.aspentech.com/SQLplus.WebService/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://www.aspentech.com/SQLplus.WebService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
- <wsdl:types>
- <s:schema elementFormDefault="qualified" targetNamespace="http://www.aspentech.com/SQLplus.WebService/">
- <s:element name="ExecuteSQL">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="command" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
- <s:element name="ExecuteSQLResponse">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="ExecuteSQLResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="string" nillable="true" type="s:string" />
</s:schema>
</wsdl:types>
- <wsdl:message name="ExecuteSQLSoapIn">
<wsdl:part name="parameters" element="tns:ExecuteSQL" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLSoapOut">
<wsdl:part name="parameters" element="tns:ExecuteSQLResponse" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLHttpGetIn">
<wsdl:part name="command" type="s:string" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLHttpGetOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLHttpPostIn">
<wsdl:part name="command" type="s:string" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLHttpPostOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
- <wsdl:portType name="SQLplusWebServiceSoap">
- <wsdl:operation name="ExecuteSQL">
<wsdl:input message="tns:ExecuteSQLSoapIn" />
<wsdl:output message="tns:ExecuteSQLSoapOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:portType name="SQLplusWebServiceHttpGet">
- <wsdl:operation name="ExecuteSQL">
<wsdl:input message="tns:ExecuteSQLHttpGetIn" />
<wsdl:output message="tns:ExecuteSQLHttpGetOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:portType name="SQLplusWebServiceHttpPost">
- <wsdl:operation name="ExecuteSQL">
<wsdl:input message="tns:ExecuteSQLHttpPostIn" />
<wsdl:output message="tns:ExecuteSQLHttpPostOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="SQLplusWebServiceSoap" type="tns:SQLplusWebServiceSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ExecuteSQL">
<soap:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:binding name="SQLplusWebServiceSoap12" type="tns:SQLplusWebServiceSoap">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ExecuteSQL">
<soap12:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
- <wsdl:input>
<soap12:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap12:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:binding name="SQLplusWebServiceHttpGet" type="tns:SQLplusWebServiceHttpGet">
<http:binding verb="GET" />
- <wsdl:operation name="ExecuteSQL">
<http:operation location="/ExecuteSQL" />
- <wsdl:input>
<http:urlEncoded />
</wsdl:input>
- <wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:binding name="SQLplusWebServiceHttpPost" type="tns:SQLplusWebServiceHttpPost">
<http:binding verb="POST" />
- <wsdl:operation name="ExecuteSQL">
<http:operation location="/ExecuteSQL" />
- <wsdl:input>
<mime:content type="application/x-www-form-urlencoded" />
</wsdl:input>
- <wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="SQLplusWebService">
- <wsdl:port name="SQLplusWebServiceSoap" binding="tns:SQLplusWebServiceSoap">
<soap:address location="http://clkaspenwatch:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
- <wsdl:port name="SQLplusWebServiceSoap12" binding="tns:SQLplusWebServiceSoap12">
<soap12:address location="http://clkaspenwatch:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
- <wsdl:port name="SQLplusWebServiceHttpGet" binding="tns:SQLplusWebServiceHttpGet">
<http:address location="http://servera:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
- <wsdl:port name="SQLplusWebServiceHttpPost" binding="tns:SQLplusWebServiceHttpPost">
<http:address location="http://servera:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Server B
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.aspentech.com/SQLplus.WebService/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://www.aspentech.com/SQLplus.WebService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
- <wsdl:types>
- <s:schema elementFormDefault="qualified" targetNamespace="http://www.aspentech.com/SQLplus.WebService/">
- <s:element name="ExecuteSQL">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="command" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
- <s:element name="ExecuteSQLResponse">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="ExecuteSQLResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
- <wsdl:message name="ExecuteSQLSoapIn">
<wsdl:part name="parameters" element="tns:ExecuteSQL" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLSoapOut">
<wsdl:part name="parameters" element="tns:ExecuteSQLResponse" />
</wsdl:message>
- <wsdl:portType name="SQLplusWebServiceSoap">
- <wsdl:operation name="ExecuteSQL">
<wsdl:input message="tns:ExecuteSQLSoapIn" />
<wsdl:output message="tns:ExecuteSQLSoapOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="SQLplusWebServiceSoap" type="tns:SQLplusWebServiceSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ExecuteSQL">
<soap:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:binding name="SQLplusWebServiceSoap12" type="tns:SQLplusWebServiceSoap">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ExecuteSQL">
<soap12:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
- <wsdl:input>
<soap12:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap12:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="SQLplusWebService">
- <wsdl:port name="SQLplusWebServiceSoap" binding="tns:SQLplusWebServiceSoap">
<soap:address location="http://serverb:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
- <wsdl:port name="SQLplusWebServiceSoap12" binding="tns:SQLplusWebServiceSoap12">
<soap12:address location="http://serverb:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Please advise me on how to fix the probelm. And please let me know any additional information is needed. Greatly appreciated~
Best regards,
Lawrence
Edited by: UMeng Lai on Feb 6, 2009 4:07 PM -
Can anybody give me complete guideance & code about using j2me web service?
Hi to all !
I have posted problem about using j2me web service ...
but still nobody have give me at least one response..
can anybody give me complete example about using webservice in j2me?
premalHi to all !
I have posted problem about using j2me web service
but still nobody have give me at least one
response..
can anybody give me complete example about using
webservice in j2me?
premal-----------------------------------
Hi, You may find help using netBean IDE.In netBean IDE help, there you should find step by step solusion for web service as well soap messang technology
your best regard
http://www.techbd.com
[email protected] -
Question about document/literal web service
Hello every body.
I have some question about document/literal web service.
I’ve been working with Axis before.
Axis has four valid signatures for your message-style service methods:
public Element [] method(Element [] bodies);
public SOAPBodyElement [] method (SOAPBodyElement [] bodies);
public Document method(Document body);
public void method(SOAPEnvelope req, SOAPEnvelope resp);
The same I am trying to do with WebLogic API for webservices.
But when I am trying to test web service (public Document method (Document body); )
I have serialized exceptions for org.w3c.dom.Document.
Do I have to write a custom class for org.w3c.dom.Document serialization?
If yes can you give me some idea or example?
The all idea behind this web service is. I have just one web service and mane classes for XML processing. Depends what xml document will be during runtime, web service will be using different class for xml processing. It works fine with Axis, but in case of WebLogic I have some problem.
One more question… How I have to call this web service from java client?
I have seen this example http://www.manojc.com/?sample31 ,
but this web service looks like (Document helloDom()). I need to send Document.
This example works for Dynamic Proxy, but does not work for static call.
Any ideas?? Thank in advance.Hi,
I am getting a similar issue. I created a Document-style/literal webservice and deployed on Weblogic 9.2 . Then I generated client stubs using clientgen. I get the following exception stack trace:
java.rmi.RemoteException: web service invoke failed: javax.xml.soap.SOAPException:
failed to serialize class java.lang.Objectweblogic.xml.schema.binding.SerializationException: type mapping lookup failure on
class=class com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl TypeMapping=TYPEMAPPING SIZE=3
ENTRY 1:
class: java.lang.Object
xsd_type: ['http://xmlns.ozarkexpress.com/business/sell']:stns:echoDocumentResponse
ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@1125127
deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@18dfef8
ENTRY 2:
class: java.lang.Object
xsd_type: ['http://xmlns.ozarkexpress.com/business/sell']:stns:echoDocument
ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@15e83f9
deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@2a5330
ENTRY 3:
class: java.lang.Object
xsd_type: ['http://www.w3.org/2001/XMLSchema']:xsd:anyType
ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@bb7465
deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@d6c16c -
SOA - real time proxy to web service scenario
Hello Experts,
I am working on PI but really very much new to the SOA concept.
But i have to prepare document which explains about all steps that we need to follow (technicallly) for the SOA implementation.
We are going to implement one Proof of Concept for SOA before going for the real project.
Can someone please help me and tell me what all the things i need to do for Proxy to Web Service Scenario in PI.
I hope i have made myself clear about it.
Thanks,
HetalHi Gaurav,
Thanks for your advice.
I have one more question and i tried to explore SDN alot but didnt get satisfactory answer.
here is the situation:
My scenario is like :
.Net application = consumer
ECC = Provider
PI = broker
SR = Publish ES
I am using the Outside - In approach, where i am creating proxy structure in ESR and then creating/ Generating Proxy in ECC.
I am exposing my Inbound Interface on SR, so that the WSDL is available on SR.
Now the situation is, our consumer is asking data from us in different format.
I read on help.sap.com that via PI mapping it is possible.
But i am not understanding that consumer is using ECC WSDL to make a call, then even though mapping is there, how can they get response in their required format.
They are even providing us their WSDL. I am totally confused that in one interface how come two different WSDLs can work?
Or is there a way for this?
I am even ready to use the same structure for my ECC which is provided by consumer, but then i dont see any outcome using PI.
I also have question, that for standard service also, ECC Enterprise service structure is fixed which we expose, then using PI how can we provide consumers response in their desired way.
I know that m asking this question again and again, but still it is not getting clear to me... might be m not understanding that how it works in SOA.
If possible can you tell me the steps that i need to follow technically to develope this interface? so that i can get better understanding?
Thanks,
Hetal -
Proxy to Web Service Communication doesn't work
Hi,
We configured the XI demo example Checking Flight Seat Availability (Proxy to Web Service Communication) (chapter 6.2) and everything works fine until we try to execute the szenario (chapter 6.2.3).
When we try to execute the szenario, we get an error displayed in the runtime Workbench. In the component Integration Server, we get a systemfailure with code ADAPTER.SOAP_EXCEPTION of category PARSING. The Adapter Engine also displays an error in the audit log:
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Authority check failed
The User XIAFUSER has SAP-All-authorizations.
Has anybody an idea, whats the problem is?
Greetings
Hildegard
Message was edited by: Hildegard WinterCheck out, that the URL of the WebService is correct:
"http://<YourServer>:<<b>ABAP_Port</b>>/sap/bc/srt/xip/sap/SXIDAL_FLIGHTSEATAVAIL_CHECK?sap-client=<<b>YourClient</b>>"
Change the default values if necessary.
Check in the client, if the role SAP_XI_APPL_SERV_USER (which should be applied to your user) is generated and has no errors.
Regards
Stefan -
Hi ,
Please let me know about this error?
"" Error Exception caught by adapter framework: Exception in method process.??"
Its a proxy to web service scenario.
Thanks in advance.
Regards
SaiHi,
The best option for searching more information about the error is to use Netweaver Administrator application. In "log viewer application" you can find more detailed information about the error ocurred in your application.
Another option is to analize the trace information in XML Header.
Please, put the detail error text in this forum. It's very difficult for us to help you with this information.
Best regards
Ivá -
Problem while Introspecting a Web-Service in OBPM 10GR3 studio
I get the following problem while Introspecting a Web-Service in OBPM 10GR3 studio:-
Introspecting...
downloading /test-ws/testc?wsdl [Error] Instrospection exception: Web Service WSDL parse exception: HTTPS hostname wrong: should be <test-01.test.net>...
Any idea why?
It runs well in a browser, eclipse and SOAP UI?have you create the destination?
do you use the wizard to generate code?
usually there is catch clause for this line of code
wdContext.currentRequest_SERVICE_MDM_LOOKUPElement().modelObject().execute();
Edited by: John Wu on Dec 16, 2010 11:51 PM -
What the mechanism of the Java Proxy for Web Services in WLS 8.1
Hi, all;
I try to find out how the java proxy of web service in weblogic server 8.1
works. Suppose I use the java Proxy of a WebSerice in a client application whatever
whithin or outside the application of the web service, does the proxy actually:
1. translate my java arguments objects in XML to create SOAP msg,
2. then send the msg across the network, and web service also response SOAP msg,
3. then proxy translate it into return value of the method call ?
If that is true , the Java Proxy seems very inefficient, right?
Can any body tell me how the proxy works ?
regards,
shannonHi Shannon,
The type of proxy I'm familiar with is at the http connection level and
associated with the networking properties in the JDK, See:
http://java.sun.com/j2se/1.4.2/docs/guide/net/properties.html
Your question may be related to JWS proxies, See:
http://edocs.bea.com/workshop/docs81/doc/en/workshop/guide/howdoi/howUseTheJavaProxyForAWebService.html
You may want to ask this question in the workshop newsgroup.
Hope this helps,
Bruce
shannon lee wrote:
>
Hi, all;
I try to find out how the java proxy of web service in weblogic server 8.1
works. Suppose I use the java Proxy of a WebSerice in a client application whatever
whithin or outside the application of the web service, does the proxy actually:
1. translate my java arguments objects in XML to create SOAP msg,
2. then send the msg across the network, and web service also response SOAP msg,
3. then proxy translate it into return value of the method call ?
If that is true , the Java Proxy seems very inefficient, right?
Can any body tell me how the proxy works ?
regards,
shannon -
HELP!!! Problem of Calling external Web Service from a Java Stored Procedur
1.I read the topic on http://www.oracle.com/technology/sample_code/tech/java/jsp/samples/wsclient/Readme.html about Calling external Web Service from a Java Stored Procedur.
2.After I import .jar to Oracle what is required by the topic,som error occued.
Like: ORA-29521: javax/activation/ActivationDataFlavor class not found,
ORA-29545: badly formed class.
3.These is not enough .jar required on the topic? What can I do for ORA-29545: badly formed class?
Thany you!Try this
Re: HELP! Loading Java Classes into Oracle ERROR -
JMS Proxy to Web Service Problem
Hi All,
I have a JMS proxy that routes messages to a web service. I have set the delivery failure parameters on the JMS queue. When a message is put onto the queue and there is a problem within the message flow proper, the message is retried the appropriate number of times and put onto the Error Destination queue as necessary. However, if there is a problem calling the web service, message delivery is NOT retried, the message is NOT put onto the Error Destination queue, and the message is lost. The web service itself isn't throwing a SOAP Fault, but the business service can't reach the web service (firewall issue). My Route Error Handler in the message flow is hit and it performs a Reply With Failure.
Can anyone please explain to me if this is by design and, if so, why? Also, how does a person work around this? I need the message to be retried. I understand that a web service cannot participate in an XA transaction, but it seems to me any failure within the message flow should cause a retry on the JMS queue.
Thanks.
Edited by mvcg at 06/11/2008 1:57 PMYou should remove the Route Node since it should only be used in HttpProxy.
Instead use just the request pipeline for your routing.
if (condition1)
Service Callout (or publish) to Service1
else if (condition2)
Service Callout (or publish) to Service2
else
Rasie error?
You shouldn't need to reply with failure. Any errors in the service callout or publish should go to exception handling if you use QoS exactly-once. -
Problems while invoking a web service
Hi everybody,
I need to call a web service and treat its response data. So I'm using OdiInvokeWebService tool, and trying to export the response to an xml file, in order to be able to treat the information. The question is that I just can't get the response, because the response file is empty after doing the call. If I try with the "advanced" option of the tool, the result is the same, doesn't matter which mode of request (xml request or xml file request) I use. But I'm even more worried considering that the process works properly when I use a tool like soapUI, that means, I get a result when I call the web service with this tool. It looks very strange because I used ODI previously with the same goal, and I didn't have any problem working in the same way. So, could somebody help me with this issue?
Thanks in advance,
Hibai.> The problem is, when my application running in Netweaver tries to consume the webservice, it takes the external access to try to reach the webservice URL instead of take the VPN route to do that. ie. my application find an external IP of the webservice instead of finding the internal IP.
You're using a proxy?
Markus -
DNS problem when calling a web service
Hi,
when I try to call a web service from the Studio I get the following error message:
return code: 503
Network Error
Network Error (dns_server_failure)
Your request could not be processed because an error occurred contacting the DNS server.
The DNS server may be temporarily unavailable, or there could be a network problem.
Looks not like an OBPM problem, but I can access the web service via SoapUI and I can access it from an OBPM enterprise installation on a server here in the network. The problem is only when I try to access the service from OBPM Studio. I also tried accessing a local web service, also does not work.
Does anyone have a hint, what it could be? Thanks for your help!
Regards
MatthiasNo, it is in my local LAN, so it should work without proxy (and in SoapUI it also works without Proxy). But nevertheless I tried it also with a proxy, but unfortunately without success.
Regards
Matthias -
Error calling[Standalone proxy]uFF1Aexternal web service(SSL + anonymous)
hi SDNer
I use Standalone proxy to call external web service(SSL + anonymous)
web service Endpoint is : https://localhost:8443/HelloWorldService/services/HelloWorld
NWDS VERSION: NWDS-IDE-700SP12
Standalone SEI is :
HelloWorld
HelloWorldHttpBindingStub
HelloWorldImpl
HelloWorldPortType
Calling Code as following:
//1. Access the implementation class of the service interface
HelloWorldImpl ws = new HelloWorldImpl();
//2. Create the instance of a logical port
Remote remote = ws.getLogicalPort();
HelloWorldHttpBindingStub stub = (HelloWorldHttpBindingStub) remote;
//3.
SecurityProtocol securityProtocol =
(SecurityProtocol) stub._getGlobalProtocols().getProtocol(
"SecurityProtocol");
AuthenticationContext ac =
securityProtocol.getAuthenticationContext();
ac.setIgnoreSSLServerCertificate(true);
//4. invoke the business methods
String ver = stub.example(str1, str2);
Exception is :
java.rmi.RemoteException: Service call exception; nested exception is:
iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: handshake failure
at com.sap.ws.HelloWorldHttpBindingStub.example(HelloWorldHttpBindingStub.java:84)
at com.sap.ws.HelloWorldHttpBindingStub.example(HelloWorldHttpBindingStub.java:94)
at TestHelloWorld.wsHelloWorld(TestHelloWorld.java:55)
at TestHelloWorld.main(TestHelloWorld.java:24)
Caused by: iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: handshake failure
at iaik.security.ssl.r.f(Unknown Source)
at iaik.security.ssl.x.b(Unknown Source)
at iaik.security.ssl.x.a(Unknown Source)
at iaik.security.ssl.r.d(Unknown Source)
at iaik.security.ssl.SSLTransport.startHandshake(Unknown Source)
at iaik.security.ssl.SSLTransport.getOutputStream(Unknown Source)
at iaik.security.ssl.SSLSocket.getOutputStream(Unknown Source)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:669)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:470)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:427)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getRequestStream(HTTPTransport.java:355)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:550)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1432)
at com.sap.ws.HelloWorldHttpBindingStub.example(HelloWorldHttpBindingStub.java:77)
... 3 moreHi
Answer is pure assumption
The error "iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: handshake failure" is mentioned in the the OSS note
Note 1157248 - SAP Business Connector with SSL / Common Problems
Pls take opinion from SAP / Basis before implementing the note
Regards
Madhan D -
Problems while consuming a web-service through Netweaver using VPN
Hi all
I'm facing a problem while I'm attempting to consume a .NET web-service that is located in a remote server. We've estabished a VPN connection between our Netweaver CE in Linux to the remote office where the web-service is running.
The problem is, when my application running in Netweaver tries to consume the webservice, it takes the external access to try to reach the webservice URL instead of take the VPN route to do that. ie. my application find an external IP of the webservice instead of finding the internal IP.
When I ping the webservice URL in linux, it brings me the internal IP, but for some unknown reason, the Netweaver don't find the correct route to reach the webservice.
Does anyone have any idea or suggestion on what to do?
Thanks in advance!> The problem is, when my application running in Netweaver tries to consume the webservice, it takes the external access to try to reach the webservice URL instead of take the VPN route to do that. ie. my application find an external IP of the webservice instead of finding the internal IP.
You're using a proxy?
Markus
Maybe you are looking for
-
Using a variable in Spry conditional tests included in a Spry Tooltip
I have the following code: <div spry:region="company" id="tooltip"> <div spry:repeat="company" spry:choose="spry:choose"> <div spry:when="'{name}'==memberName"> <table> <tr> <td align="center"><h2>{name}</h2></td> </tr> <tr> <td align="center"><img s
-
Network connection to Deskjet 3050A keeps dropping out for a few seconds
Every few minutes (sometimes only a couple of minutes, sometimes a fair bit longer) an alert pops up in the Notification area of my Windows 7 computer telling me that "Scan to computer is no longer activated. The network connection has been lost" (at
-
The music player always reverts back to where I started the day before at a low volume and it's driving me mad! On a previous phone with earlier IOS there was the option to play from where the track left off when stopped - how do I find this option n
-
Standard report showing Permitted Payees linked to vendor
Hello, Does anyone know if there is a standard SAP report that shows the permitted payees linked to a vendor without having to go to table LFZA? For example, I have a vendor 112222 ABC company and on the payment transactions global screen, I have def
-
How to connect Essbase/Shared Services 11.1.1.1.3 to LDAP
Hi, I just installed Essbase 11.1.1.1.3 with Shared Services. I have never connected it to a corporate LDAP environment before. I remember in the past version 6/7 etc.. there was a CSS file that needed edited. Is that still the case or do I have to g