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
Matthias

No, 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

Similar Messages

Strange problem when calling a Web Service...

Hi,
First of all, I succeed calling a custom web service : I pass to this web service a table and retrieve a table.
Now, I am trying to do the same thing with the web service of BAPI_USER_GETLIST.
Here is the code in the Component Controller.
<i>
Request_BAPI_USER_GETLISTPortType_BAPI_USER_GETLIST    input =
     new Request_BAPI_USER_GETLISTPortType_BAPI_USER_GETLIST();
wdContext.nodeRequest_BAPI_USER_GETLISTPortType_BAPI_USER_GETLIST().bind(input);
ComplexType_BAPI_USER_GETLIST complex = new ComplexType_BAPI_USER_GETLIST();
complex.setMAX_ROWS(10);
complex.setWITH_USERNAME("X");
complex.addRETURN(new ComplexType_BAPIRET2());
complex.addSELECTION_EXP(new ComplexType_BAPIUSSEXP());
complex.addSELECTION_RANGE(new ComplexType_BAPIUSSRGE());
complex.addUSERLIST(new ComplexType_BAPIUSNAME());
input.setParameters(complex);
try {
     wdContext.currentRequest_BAPI_USER_GETLISTPortType_BAPI_USER_GETLISTElement()
          .modelObject().execute();
}catch(Exception e) {
     wdContext.currentContextElement().setException(e.getMessage());
wdContext.nodeResponse().invalidate();
</i>
I do not get any results.
When debugging in the ABAP code, I get something strange.
For everyone who looks in the BAPI_USER_GETLIST source code, you can notice
that there is a refresh in the initialization function for the retrun and userlist
tables.
But, all the other tables (SELECTION_EXP and SELECTION_RANGE) has an empty line added!
And this cause the problem.
How do I know that this is the problem ? Because, when debugging in ABAP, I delete
those lines in thoses 2 tables and everything works good.
Is there a way to solve this problem ?
Thanks in advance.

Hi
Again you are trying to add an empty line and then delete it. Well what i am saying is you dont have to do the lines
complex.addRETURN(new ComplexType_BAPIRET2());
complex.addUSERLIST(new ComplexType_BAPIUSNAME());
ComplexType_BAPIUSSEXP d1 = new ComplexType_BAPIUSSEXP();
complex.addSELECTION_EXP(d1);
ComplexType_BAPIUSSRGE d2 = new ComplexType_BAPIUSSRGE();
complex.addSELECTION_RANGE(d2);
complex.removeSELECTION_EXP(d1);
complex.removeSELECTION_RANGE(d2);
input.setParameters(complex);
Just write the following code and you are good to go.
Bapi_User_Getlist_Input complex = new Bapi_User_Getlist_Input();
wdContext.nodeBapi_User_Getlist_Input().bind(complex);
complex.setMax_Rows(10);
complex.setWith_Username("X");
try
wdContext.currentBapi_User_Getlist_InputElement().modelObject().execute();
catch(Exception e)
wdComponentAPI.getMessageManager().reportException ("Exception occured "+e,true);
Hope that helps you. You dont have to pass any values to the table structures. This specific bapi does not require data to be passed to the structures and by doing so empty lines are added and that is what i was saying when i explained in my previous post. Hope that clarifies your doubt. Do let me know in case u require further clarifications.
If you are getting a error saying Return and Selection_EXP are required check the mapping.
It is enough if you just select the nodes under
   Bapi_User_List_Input
      |_Output
      |    |_Return (Model Node)
      |    |_Selection_Exp (Model Node)
      |    |_Selection_Range (Model Node)
      |    |_Userlist (Model Node)
      |    |_Rows (Model Attribute)
      |_Max_Rows (Model Attribute)
      |_With_Username (Model Attribute)
and of course select the Model Attributes MAX_ROWS and With_Username
Let me know if you require any more information
regards
ravi

Error when calling Java Web Services from ABAP.

Hello experts:
    In my project, I will call Java Web Services with ABAP coding. With WSDL, I generated a proxy class and created a HTTP connection (t-code: SM59) and a logical port (t-code:lpconfig) for this proxy class. But when running, I would receive the folllowing errors:
   SOAP:1.023 SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: HTTP COMMUNICATION FAILURE")
   If I used HTTPS, there is no problem.
Regards
Bob

Hi Bob,
It might be the possibility that your java web server is configured to listen only on HTTPS.
If your HTTPS is working fine, then first check with your JAVA server for HTTP connectivity, then try it calling through ABAP.
Regards,
Piyush

Problem when defining a web service

Hello,
I have defined several BAPI that I am calling from an external application by exopsing those BAPI using the SOAP adaptor.
All goes well for all of them except one.
For the one having problems the Integrantion engine is routing that call to different webservice than the one I expect it to do it,
these are some of the paramenters I use when defining the web service in the Integration Builder:
Interface name: MI_BAPI_PPMSRVAPS_GETLIST
Communitcation chanel: CC_SOAP_BAPI_PPMSRVAPS_GETLIST
Address: http://sapxi:50000/xisoapadapter/messageservlet?channel=:BS_WEBSERVICE_GREYCON:CC_SOAP_BAPI_PPMSRVAPS_GETLIST
but instead when I test the generated wsdl using soapUI: the integration engine returns this error:
Canceled with Errors 02.06.2010 15:04:22 02.06.2010 15:04:23 [websericename] [namespace]MI_BAPI_PDSSRVAPS_GETLIST
My guess is that at some point I defined wrong the web service but I have no way to redefine it or revert how it was defined.
I redefined the webservice with correct parameters, but there is no change in behaviour.
I checked server address and port (it is the exact same of the other BAPIs that work)
Where can I see all defined web services when they are defined via the Integration builder define web service option?
How to delete a webservice published this way?
Any advise?
Any help is very much appreciated.
Regards,
Mauricio Pego

Hello there.
Error: 404 Not Found
Description: The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
Possible Tips:- for HTTP_RESP_STATUS_CODE_NOT_OK 404
u2022 404 is an HTTP response code that indicates that the resource in question couldn't be found. Usually this is due to an incorrect URL, so it is better to cross check all URLs. Check pipeline URL in the SLD in the business system of the Integration Server For this go to SLD->Business System-><yourIntegrtaion Server>->Pipeline URL: It should be like this http://<host>:<port>/sap/xi/engine?type=entry Where host is the host name of the Integration Server and port is the HTTP(8xxx) port. To verify this in Integration Server you can do like this. Go to SXMB_ADM->Integration Engine Configuration->Choose Edit from Menu -> Change Global Configuration Data to switch to change mode. Then select System Landscape - Load Configuration. (This is not required always)
u2022 Check that the port really is the ICM HTTP Port and not the J2EE port i.e SMICM then menu GOTO --> SERVICES and check the port number for HTTP. It should be HTTP port
u2022 If the error is Page cannot be displayed, cannot find server in https configurations Check and correct the SSL configuration for the ABAP and the J2EE side of the system
u2022 If the error is because of integration server when using Proxy communications then check these. i.e SXMB_ADM->Integration Engine Configuration->Corresponding Integration Server enrty should be dest://<Http Integration server-Destination> Where < Http Integration server -Destination > is the RFC destination (SM59) of type HTTP connection (type H) to the Integration Server. In this case, host name, port, and path prefix are saved in the RFC destination.
Try some of the recommendations that most apply to your case.
Hope it helps!
Regards,
Caio Cagnani

DCA-40000: internal error when calling a web service

Hello,
I would like to call a web service in Oracle UCM with basic authentication (CheckInUniversal). In JDeveloper 11.1.1.2 I can specify username and password for the WS at design time and the JSPX runs fine.
Now I have added some piece of code into a managed bean (CheckInBean) to use a specific username and password at runtime. When I run the page I get a DCA-40000 with the following error stack:
<Utils><buildFacesMessage> ADF: Adding the following JSF error message: The Web Service call failed due to an internal error.
oracle.adf.model.adapter.AdapterException: DCA-40000: The Web Service call failed due to an internal error.
     at oracle.adfinternal.model.adapter.webservice.WSDataControl.invokeOperation(WSDataControl.java:270)
     at oracle.adf.model.bean.DCBeanDataControl.invokeMethod(DCBeanDataControl.java:430)
     at oracle.adf.model.binding.DCInvokeMethod.callMethod(DCInvokeMethod.java:257)
     at oracle.jbo.uicli.binding.JUCtrlActionBinding.doIt(JUCtrlActionBinding.java:1625)
     at oracle.adf.model.binding.DCDataControl.invokeOperation(DCDataControl.java:2141)
     at oracle.adf.model.bean.DCBeanDataControl.invokeOperation(DCBeanDataControl.java:467)
     at oracle.adf.model.adapter.AdapterDCService.invokeOperation(AdapterDCService.java:307)
     at oracle.jbo.uicli.binding.JUCtrlActionBinding.invoke(JUCtrlActionBinding.java:730)
     at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.executeEvent(PageLifecycleImpl.java:394)
     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(AstValue.java:157)
     at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
     at integration.view.CheckInBean.execute(CheckInBean.java:134)
     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(AstValue.java:157)
     at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
     at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53)
     at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1245)
     at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183)
     at oracle.adf.view.rich.component.fragment.UIXRegion.broadcast(UIXRegion.java:148)
     at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:90)
     at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:309)
     at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:94)
     at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:102)
     at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:90)
     at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:309)
     at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:94)
     at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:96)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:812)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:292)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:177)
     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:292)
     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:191)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
     at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
     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:94)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:138)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326)
     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.run(WebAppServletContext.java:3592)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
With debugger I found that it happens when the iterator CheckInUniversalResultIterator is called.
HTTP Analyzer shows that there are only empty SOAP messages sent to UCM but the correct values are present in the the bean.
Here is the code of the bean:
package integration.view;
import java.util.HashMap;
import java.io.*;
import java.util.Properties;
import javax.el.ELContext;
import javax.el.ExpressionFactory;
import javax.el.MethodExpression;
import javax.el.ValueExpression;
import javax.faces.application.Application;
import javax.faces.context.FacesContext;
import javax.faces.event.ActionEvent;
import oracle.adf.model.BindingContainer;
import oracle.adf.model.BindingContext;
import oracle.adf.model.binding.DCBindingContainer;
import oracle.adf.model.binding.DCDataControl;
import oracle.adfinternal.model.adapter.webservice.WSDataControl;
import oracle.adfinternal.model.adapter.webservice.security.SecurityModel;
// import oracle.binding.BindingContainer;
import oracle.webservices.model.Port;
public class CheckInBean extends SecurityModel {
private String fileName;
private String fileContent;
private HashMap primaryFile;
String mSavedCSFKey = null;
public CheckInBean() {
public void setFileName(String fileName) {
this.fileName = fileName; }
public String getFileName() {
return fileName;
public void setFileContent(String fileContent) {
this.fileContent = fileContent;
public String getFileContent() {
return fileContent;
public void setPrimaryFile(HashMap primaryFile) {
this.primaryFile = primaryFile;
public HashMap getPrimaryFile() throws IOException {
FacesContext facesCtx = FacesContext.getCurrentInstance();
Application app = facesCtx.getApplication();
ExpressionFactory elFactory = app.getExpressionFactory();
ELContext elContext = facesCtx.getELContext();
// gets the value from the managed bean
fileName = elFactory.createValueExpression(elContext, "#{pageFlowScope.ReportBean.reportName}", Object.class).getValue(elContext).toString();
System.out.println(fileName);
// puts the file name and the content into a hash map
HashMap hashMap = new HashMap();
hashMap.put("fileName",fileName);
System.out.println(fileName);
hashMap.put("fileContent",getFileInBytes(ReportBean.reportPath, fileName));
return hashMap;
private static byte[] getFileInBytes(String reportOutputPath, String fileName) throws IOException {
File file = new File(reportOutputPath,fileName);
System.out.println(reportOutputPath + "+" + fileName);
InputStream inputStream = new FileInputStream(file);
// Get the size of the file
long size = file.length();
System.out.println("Size of the file: "+ size);
// Check that size is not larger than Integer.MAX_VALUE
if (size > Integer.MAX_VALUE) {
System.out.println("File too large !!");
return null;
// Read the bytes into the byte array
byte[] byteArray = new byte[(int)size];
System.out.println("New Byte Array");
int offset = 0;
int byteRead = 0;
while ((offset < byteArray.length)
((byteRead=inputStream.read(byteArray, offset, byteArray.length-offset)) >= 0)){
byteRead = offset + byteRead;
System.out.println(byteRead);
inputStream.close();
return byteArray;
public void execute(ActionEvent aev) {
FacesContext fctx = FacesContext.getCurrentInstance();
Application app = fctx.getApplication();
ExpressionFactory expF = app.getExpressionFactory();
ValueExpression ve = expF.createValueExpression(fctx.getELContext(), "#{bindings}", DCBindingContainer.class);
DCBindingContainer cont = (DCBindingContainer)ve.getValue(fctx.getELContext());
DCDataControl dc = cont.findDataControl("CheckInECM");
if(dc.getAdaptedDC() instanceof WSDataControl)
WSDataControl wsdc = (WSDataControl)dc.getAdaptedDC();
wsdc.getProvider().setSecurityModel(this);
// execute the data control method, that was bound to this
// button's action listener.
MethodExpression me = expF.createMethodExpression(fctx.getELContext(),
"${bindings.CheckInUniversal.execute}", Object.class,
new Class[0]);
me.invoke(fctx.getELContext(), null);
// public BindingContainer getBindings() {
// return (BindingContainer)BindingContext.getCurrent().getCurrentBindingsEntry();
// override security properties for any policy on the current port
// before the method execution.
public void initSecurity(Port thisPort) {
super.initSecurity(thisPort);
System.out.println(thisPort.hashCode());
Properties callP = (Properties)this.getCallProperties(thisPort);
callP.put("javax.xml.ws.security.auth.username", "sysadmin");
callP.put("javax.xml.ws.security.auth.password", "welcome1");
mSavedCSFKey = (String)callP.remove("csf-key");
this.saveCallProperties(thisPort, callP);
// Restore the config at the end of the request.
public void clearSecurityParameters(Port thisPort) {
super.clearSecurityParameters(thisPort);
Properties callP = (Properties)this.getCallProperties(thisPort);
callP.remove("javax.xml.ws.security.auth.username");
callP.remove("javax.xml.ws.security.auth.password");
//put back the saved csf key as default...
callP.put("csf-key", mSavedCSFKey);
this.saveCallProperties(thisPort, callP);
}

If you could enclose your code inside tag it will improve readability for us.
Anyways, first thing that I could think of is - what is the scope of your managed bean..? If its in request scope can you try changing it to higher scope level (session scope or page view scope).
regards,
~K

Got error when calling a web service, "XMLParametersToComHashtable:LoadXML failed"

Hi, I'm using vs2012, c# and asp.net.
In my asp.net web form project I got the error at the LOC when I call the web service's Search method. What does this error mean and how do I fix this? Am I to use some type of reader or loader? The Search method returns a XMLNode type.
But I thought using InnerText should be fine but I'm still getting the error.
thank you.
var restApi = new someWebServices.restApi();
strParm1 = restApi.Login(XXXXXXXXXXX);
var rtnSrv = (restApi.Search(strParm1, strParm2, 1, -1, false, @"<![CDATA[<parameters><parameter name=""XXXXXXXXX"" value=""XXXXXXXXXXXXXXXXXXXXX""/></parameters>]]>")).InnerText;
Thank you

There is a Web service section in the ASP.NET forum.
http://forums.asp.net/

Problem in calling a web service hosted on tomcat from BEA WebLogic portal

Hi,
I have a wsdl file for my web service which is hosted on apache tomcat 5.5(running on port : 8080). The contents of the wsdl file are-
*<?xml version="1.0" encoding="UTF-8"?>*
*<wsdl:definitions targetNamespace="http://soa.tutorials.serg.edu" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://soa.tutorials.serg.edu" xmlns:intf="http://soa.tutorials.serg.edu" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">*
*
*<wsdl:types>*
*<schema elementFormDefault="qualified" targetNamespace="http://soa.tutorials.serg.edu" xmlns="http://www.w3.org/2001/XMLSchema">*
*<element name="getNums">*
*<complexType>*
*<sequence>*
*<element name="n" type="xsd:int"/>*
*<element name="m" type="xsd:int"/>*
*</sequence>*
*</complexType>*
*</element>*
*<element name="getNumsResponse">*
*<complexType>*
*<sequence>*
*<element maxOccurs="unbounded" name="getNumsReturn" type="xsd:int"/>*
*</sequence>*
*</complexType>*
*</element>*
*<element name="getNums2">*
*<complexType>*
*<sequence>*
*<element name="n" type="xsd:int"/>*
*<element name="m" type="xsd:int"/>*
*</sequence>*
*</complexType>*
*</element>*
*<element name="getNums2Response">*
*<complexType>*
*<sequence>*
*<element maxOccurs="unbounded" name="getNums2Return" type="xsd:int"/>*
*</sequence>*
*</complexType>*
*</element>*
*</schema>*
*</wsdl:types>*
*<wsdl:message name="getNums2Request">*
*<wsdl:part element="impl:getNums2" name="parameters"/>*
*</wsdl:message>*
*<wsdl:message name="getNumsRequest">*
*<wsdl:part element="impl:getNums" name="parameters"/>*
*</wsdl:message>*
*<wsdl:message name="getNums2Response">*
*<wsdl:part element="impl:getNums2Response" name="parameters"/>*
*</wsdl:message>*
*<wsdl:message name="getNumsResponse">*
*<wsdl:part element="impl:getNumsResponse" name="parameters"/>*
*</wsdl:message>*
*<wsdl:portType name="Echo">*
*<wsdl:operation name="getNums">*
*<wsdl:input message="impl:getNumsRequest" name="getNumsRequest"/>*
*<wsdl:output message="impl:getNumsResponse" name="getNumsResponse"/>*
*</wsdl:operation>*
*<wsdl:operation name="getNums2">*
*<wsdl:input message="impl:getNums2Request" name="getNums2Request"/>*
*<wsdl:output message="impl:getNums2Response" name="getNums2Response"/>*
*</wsdl:operation>*
*</wsdl:portType>*
*<wsdl:binding name="EchoSoapBinding" type="impl:Echo">*
*<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>*
*<wsdl:operation name="getNums">*
*<wsdlsoap:operation soapAction=""/>*
*<wsdl:input name="getNumsRequest">*
*<wsdlsoap:body use="literal"/>*
*</wsdl:input>*
*<wsdl:output name="getNumsResponse">*
*<wsdlsoap:body use="literal"/>*
*</wsdl:output>*
*</wsdl:operation>*
*<wsdl:operation name="getNums2">*
*<wsdlsoap:operation soapAction=""/>*
*<wsdl:input name="getNums2Request">*
*<wsdlsoap:body use="literal"/>*
*</wsdl:input>*
*<wsdl:output name="getNums2Response">*
*<wsdlsoap:body use="literal"/>*
*</wsdl:output>*
*</wsdl:operation>*
*</wsdl:binding>*
*<wsdl:service name="EchoService">*
*<wsdl:port binding="impl:EchoSoapBinding" name="Echo">*
*<wsdlsoap:address location="http://localhost:8080/SOATest/services/Echo"/>*
*</wsdl:port>*
*</wsdl:service>*
*</wsdl:definitions>*
I created a client from the above wsdl file using ClientGen wizard in WebLogic. This client contains the follwoing classes-
Echo.java
EchoService.java
EchoService_Impl.java
Echo_Stub.java
I created a JSP portlet and the jsp content of it is-
String url = "http://localhost:8080/SOATest/services/Echo";
Echo echo = new EchoService_Impl(url).getEcho();
getNumsResponse = echo.getNums(getNums);
I tried to call that web service from BEA weblogic portal through a JSP potlet. I got an error saying -
*<An exception [javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element] was thrown while rendering the content at [TestEcho.jsp].*
*javax.servlet.ServletException: javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
*     at weblogic.servlet.jsp.PageContextImpl.handlePageException(PageContextImpl.java:420)*
*     at jsp_servlet.__testecho._jspService(__testecho.java:112)*
*     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)*
*     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)*
*     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)*
*     Truncated. see log file for complete stacktrace*
*javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
*     at weblogic.wsee.jaxrpc.ServiceImpl.throwServiceException(ServiceImpl.java:174)*
*     at weblogic.wsee.jaxrpc.ServiceImpl.loadWsdlDefinition(ServiceImpl.java:485)*
*     at weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:119)*
*     at edu.serg.tutorials.soa.EchoService_Impl.<init>(Unknown Source)*
*     at edu.serg.tutorials.soa.EchoService_Impl.<init>(Unknown Source)*
*     Truncated. see log file for complete stacktrace*
*weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
*     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:313)*
*     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:405)*
*     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:391)*
*     at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:79)*
*     at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:66)*
*     Truncated. see log file for complete stacktrace*
*java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
*     at weblogic.xml.domimpl.Loader.load(Loader.java:38)*
*     at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:122)*
*     at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)*
*     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)*
*     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:405)*
*     Truncated. see log file for complete stacktrace*
*javax.xml.stream.XMLStreamException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
*     at weblogic.xml.stax.XMLStreamReaderBase.advance(XMLStreamReaderBase.java:206)*
*     at weblogic.xml.stax.XMLStreamReaderBase.next(XMLStreamReaderBase.java:237)*
*     at weblogic.xml.domimpl.Loader.load(Loader.java:112)*
*     at weblogic.xml.domimpl.Loader.load(Loader.java:73)*
*     at weblogic.xml.domimpl.Loader.load(Loader.java:35)*
*     Truncated. see log file for complete stacktrace*
*Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
*     at weblogic.xml.babel.baseparser.BaseParser.parseProlog(BaseParser.java:417)*
*     at weblogic.xml.babel.baseparser.BaseParser.parseSome(BaseParser.java:328)*
*     at weblogic.xml.stax.XMLStreamReaderBase.advance(XMLStreamReaderBase.java:195)*
*     at weblogic.xml.stax.XMLStreamReaderBase.next(XMLStreamReaderBase.java:237)*
*     at weblogic.xml.domimpl.Loader.load(Loader.java:112)*
*     Truncated. see log file for complete stacktrace*
My web service is using soap binding. I have tested it with eclipse and other tools also. It is working well and good. But when I tried to call a web service which is created and hosted on WebLogic server(running on port : 7001), I got the correct output.
Can anyone help me out in calling a web service hosted on different server from WebLogic server.
Thanks in advance,
Tiijnar
Edited by: user8715057 on Aug 13, 2009 1:11 AM

Hi
1. The way you are invoking the WebService deployed on Tomcat server is looks suspicious. It may be valid by adding extra ?wsdl etc into the url, but still I have not seen this way to invoke the webservice.
2. So you used Weblogic ant task to generate client JARs by giving this WSDL. So looks like it generated the 4 classes (.java) and in addition any other classes for Request/Response xml objects.
3. Look at the source code of EchoService.java. It should have one default empty constructor. Internally it uses the default wsdl defined in this class. You will see another constructor that takes WSDL URL as one of the parameters (QName) etc. Echo.java is the class corresponding to the Port. In the same EchoService you should see an instance method like getEcho() something like that. This Echo.java class will have methods for all the Operations defined on this Port. So the standard code snippet we use most of the times will be like this:
EchoService myEchoService = new EchoService(); // Default it uses WSDL deployed on Tomcat at localhost:8080
Echo myEchoPort = myEchoService.getEchoPort(); // Something along these lines.
myEchoPort.xxxYYY(); // NOW this is the operation name that takes the input parameters and returns outputs defined as per the WSDL defintions. If the Input and Outputs are complex xml types, it will have corresponing .JAVA files with setters and getters.
Now if this WebService is deployed on same Tomcat but on different machine or different port, you just give the full WSDL URL with that host and port in the constructor for new EchoService(...). You may need to instantiate QName object. But look at the methods generated in EchoService.java class.
The way you are using with Impl and Stubs class may also work. I am not much famiiar with this APIs apporach. Still look at the methods generated in these classes.
Also if you latest Sun JDK 1.6, it also has one command like wsimport. Infact if you install WLS 10.3 with Sun JDK, it should have C:\beawlp103\jdk160_05\bin\wsimport command. This will also generate client jar given a WSDL URL.
Thanks
Ravi Jegga

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 PM

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 PM

Problem while calling a web service in BOBJ Data services

Hello Experts,
I am trying to call a web service in bobj data services. A real time job has been scheduled and published as a web service. I want to consume this service in web dynpro java.
I tried both the methods the adaptive web services and depricated version. I also tried calling the url directly and with the metadata and execution destinations.
No matter what I do, I keep getting the following error.
Exception on execution of web service with WSDL URL 'http://XXXXX:28080/DataServices/servlet/webservices?ver=2.0&wsdl' with operation 'SERVICE_<NAME>' in interface 'Real-time_Services'
The call never reaches data services system. If I try to call the service from soapUI (web service testing tool) it works fine.
I am using SAP NW 7.0 SP22 .
Here is my code in dynpro to call the service.
     AdaptiveModel mod = new AdaptiveModel();
     Request_SERVICE_MDM_LOOKUP request = new Request_SERVICE_MDM_LOOKUP(mod);
     Query1 query1 = new Query1(mod);
     Response_SERVICE_MDM_LOOKUP response = new Response_SERVICE_MDM_LOOKUP(mod);
     request.setQuery(query1);
     request.setResponse(response);
     List list = new ArrayList();
     DefinitionsTypes_XsdSchema_1__XsdElement_1__XsdComplexType_Sequence1 element = new DefinitionsTypes_XsdSchema_1__XsdElement_1__XsdComplexType_Sequence1(mod);
     element.setCustomer_Name(wdContext.currentContextElement().getCustomerName());
     element.setZip_Code(wdContext.currentContextElement().getZipcode());
     element.setAddr1("");
     element.setAddr2("");
     element.setCity("");
     element.setCountry("");
     element.setState("");
     list.add(element);
     query1.set$002fDefinitions$002fTypes$002fXsdSchema$005b1$005d$002fXsdElement$005b1$005d$002fXsdComplexType$0023Sequence1(list);
     wdContext.nodeRequest_SERVICE_MDM_LOOKUP().bind(request);
      wdContext.currentRequest_SERVICE_MDM_LOOKUPElement().modelObject().execute();
      wdContext.nodeResponse().invalidate();
      wdContext.nodeQueryResponse().invalidate();
      wdContext.nodeSequenceResponse().invalidate();
Please let me know if you have any pointers on how to solve this.
Thanks in advance
Praveen.

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

Basic authentication when calling a web service

I am attempting to call a web service using ActionScript. The
web service provider requires that I use HTTP Basic Authentication
to communicate my SOAP requests. I cannot seem to get this done in
ActionScript. If I instantiate a WebService object and call its
SetCredentials method, I get an error "Authentication not supported
on DirectHTTPChannel (no proxy)". I have the WebService object's
useProxy property set to true. HELP!

I know this is five years later on this forum but there's no solution here or on any other forum. So after two day's of hammering this out I was able to produce a workable solution. Create a new user account for testing.
Wu_Xiao's explanation of the issue was dead on. The WebService does a GET then a POST and for the GET we are unable to supply the Authorization in the header and this is why we get the popup. The POST has the Authorization but it already to late.
Take these actions
1 Create a new user on the machine with the web services. Start with a simple name and password (text only) I had issues with different users. Start clean and simple.
2 Copy your web services a second usable service. You'll see in my example below i have Ive copied ServicesSECURE/Services1.asmx?WSDL to ServicesDEFINITION/Services1.asmx?WSDL
3 Remove all of the code inside of your services making the new set of service like a definition service. Make sure all of the inputs and outputs are the same. ServicesDEFINITION will have no coding and empty returns.
Example
[WebMethod]
        public String CountUsers(string group)
            return "";
4 Implement the code below. Call the init() right away to instantiate the web service and wait until it loads to use any of the services. I use a button event to test.
private var testws:WebService = new WebService;
private function init():void
testws.wsdl="http://test.com/ServicesDEFINITION/Services1.asmx?WSDL";
var encoder:Base64Encoder= new Base64Encoder();
encoder.insertNewLines = false; // see below for why you need to do this
encoder.encode("USERNAME:PASSWORD");
testws.httpHeaders = {Authorization:" Basic " + encoder.toString()};
testws.loadWSDL();
testws.addEventListener("load", wsdlLoadHandler);
protected function test_clickHandler(event:MouseEvent):void
testws["CountUsers"].addEventListener(mx.rpc.events.FaultEvent.FAULT,testFaultHandler);
testws["CountUsers"].addEventListener(mx.rpc.events.ResultEvent.RESULT,testResultHandler) ;
testws.endpointURI="http://test.com/ServicesSECURE/Services1.asmx?WSDL";
testws.getOperation("CountUsers").send("Test");
protected function wsdlLoadHandler (event:LoadEvent) : void
//the service has to load before using the getOperation function
//you could try using mx.core.UIComponent.callLater from
//this listener and call the gettestws.getOperation("Co....
So you'll see that the ServicesDEFINITION (GET) is called and grabs the definition of the Service1 service but this unsecured services is useless because we've removed all of the code. After the definition GET is called we can change the end point using endpointURI and perform the POST against our secure ServicesSECURE.

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

UWL connector: problems with calling a web service with a SAPLOGONTICKET

Hi,
I want to implement a uwl connector that calls a web service to retrieve the uwl items data with a SAPLOGONTICKET. If I refresh the UWL I get the following error.
An error occured while reading data from the destination sap.com/com.xxxx.connector.RequestLeaveDP/com.xxxx.connector.RequestLeave/Config1Port_Document. The error was: com.sap.security.core.client.ws.SSO2Exception No SAP Logon Ticket was found for the user. Please ensure the user authenticated using HTTP/HTTPS and the JAAS login stack has been configured correctly. As an alternative, consider changing the authentication type to Assertion Ticket. .
If I call the Web Service in an iView I don't get this error. Maybe the UWL calls the web service not with the current authenticated user.
I tried the following code, to get the current SSO2 Ticket from the current user. It looks like, that is the current user, but the web service will not accept this. (testing purpose)
com.sap.security.api.IUser currentUser = com.sap.security.api.UMFactory.getAuthenticator().getLoggedInUser();
String logonTicketUwlUser = (String) context.getUser().getTransientAttribute("com.sap.security.core.usermanagement", "MYSAPSSO2_STRING");
String logonTicketCurrentUser = (String) currentUser.getTransientAttribute("com.sap.security.core.usermanagement", "MYSAPSSO2_STRING");
InitialContext contextWebService = new InitialContext();
RequestLeaveWebService requestLeaveWebService = (RequestLeaveWebService) contextWebService.lookup(wsClient);
RequestLeaveWebServiceViDocument webServiceEndPoint = requestLeaveWebService.getLogicalPort("Config1Port_Document");
UWLHolidayItem holidayItem = webServiceEndPoint.getHolidayItem("");
Any ideas?
Regards
Markus
Edited by: Markus Karsch on Oct 18, 2008 11:15 PM

Are you calling invoke()?
Do you have the port type in the servlet context?

Error when calling a web service in PLSQL, "the page could not be displayed

Hi, I have a simple web service based on a function returning the name of the employee, I tested it against the standalone oc4j instance and it's working fine, but when I try to call it from PLSQL the error "the page could not be displayed" appears.
What am I doing wrong?
CREATE OR REPLACE package body p_call_ws is
function f_query_ws( pIp varchar2 default '100') return varchar2 is
v_wsresponse varchar2(2000) := null;
begin
utl_http.set_proxy('pccproxy', NULL);
select utl_http.request( 'http://localhost:8888/ws/wsemp?invoke=pNombre&pId='||pIp)
into v_wsresponse
from dual;
return(v_wsresponse);
end f_query_ws;
procedure p_call is
v_wsresponse varchar2(2000) := null;
begin
v_wsresponse := f_query_ws('100');
dbms_output.put_line(v_wsresponse);
end p_call;
end p_call_ws;
=====================
Whe I call the function in SQLPLUS> select p_call_ws.f_query_ws from dual;
The output generated is
Problem-->The page cannot be displayed

Sorry I cannot help with this utility. What is your database version? In 10.1 and later, the recommended way is using JPublisher. Download JPublisher 10.2 and the webservice callout utility.
http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
http://www.oracle.com/technology/sample_code/tech/java/jsp/dbwebservices.html

Slow response when calling a web service from an ADF client in JDev 11g

I have generated a web service (WS) for a stored procedure package with 3 functions. The WS has less than 1 second response times when I use the standard WS testing facility. I then created a data control for the WS selecting the default values in the JDev wizard. When I test the functions from a very basic ADF client the response times for the same functions are between 3-4 seconds i.e. very SLOW compared to the actual response time of WS. I need some advice on how to investigate this performance degredation as seen from the ADF client.
Could the problem be that the data control was created from a web service in the same project? Maybe it is necessary to have them in separate projects or create a proxy?
I created and tested the web service with the standard WS test tool and then simply went on to create a data control from this web service for use from a ADF client.
Some background info:
I saw the following warning in step 8 of the WS creation wizard:
"The configured policy store location at "C:\Oracle\Middleware\jdeveloper\j2ee\home\gmds" is invalid. Application cannot read policies from this location. Check that the directory name is correct and the location exists."
Also I can confirm that there is no j2ee directory in my environment.
The application server logs the following for each call from the ADF client:
009-apr-01 15:55:22 oracle.adf.model.connection.webservice.impl.WebServiceConnectionMessages debugGetSaajInteraction
INFO: Creating a SaajInteraction for oracle.j2ee.ws.model.OperationImpl@1c81d2c
2009-apr-01 15:55:22 oracle.adf.model.connection.webservice.impl.WebServiceConnectionMessages debugGetSaajInteractionResult
INFO: Created [email protected]79edc for oracle.j2ee.ws.model.OperationImpl@1c81d2c
2009-apr-01 15:55:22 oracle.j2ee.ws.rm.LogMessages logExceptionAsWarning
VARNING: Internal error: oracle.wsm.policy.model.PolicyModelException: WSM-01647 : There are no policies that match the specified category wsrm and resource pattern {1}.
2009-apr-01 15:55:22 oracle.fabric.common.AbstractSecurityInterceptor init
INFO: AbstractSecurityInterceptor:init(), client.mode.jse==ture and isJEE==true, probably is a case of JEE client calling JSE client
2009-apr-01 15:55:22 oracle.wsm.agent.WSMAgent init
INFO: WSMAgent is initialized for category=management, function=agent.function.client, topologyNodePath=null, isJ2EE=true
2009-apr-01 15:55:22 oracle.fabric.common.AbstractSecurityInterceptor init
INFO: AbstractSecurityInterceptor:init(), client.mode.jse==ture and isJEE==true, probably is a case of JEE client calling JSE client
2009-apr-01 15:55:22 oracle.wsm.agent.WSMAgent init
INFO: WSMAgent is initialized for category=security, function=agent.function.client, topologyNodePath=null, isJ2EE=true
2009-apr-01 15:55:24 oracle.wsm.common.logging.WsmMessageLogger logSevere
ALLVARLIG: error in the Oracle WSM Policy Resolver Initialization, because incorrect configuration is passed: {0} {1}
Edited by: user10601664 on Apr 8, 2009 7:11 AM

Find solution. Check this thread:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/wdjava/faq%2b-%2bmodels%2b-%2badaptive%2bweb%2bservice
The com.sap.tc.webdynpro.model.webservice.api.IWDWSInvocationModifier interface can be implemented by an application using the Adaptive Web Service model in order to modify the web service invocation object just before it's execution. Invocation modifiers need to be registered with the executable model class for which invocation is to be modified:
Request_NumberToWords requestMO = new Request_NumberToWords(model);
requestMO.wdSetInvocationModifier(
new IWDWSInvocationModifier() {
    public void doModifyInvocation(Object port) {
      HTTPControlInterface httpItf = HTTPControlFactory.getInterface(port);
      //timeout for this WS invocation is 120 sec; don't use global config. setting of WS-Runtime
      httpItf.setSocketTimeout(120000);
    public void doModifyAfterInvocation() {}
Best regards.

ORA-01403: no data found when calling a web service from HTMLDB

I am working through Section 6 How to Implement a Web Service of the HTML DB 2 Day Developer tutorial. I can get the first example to work but not the second one. I am able to add the web reference and create the form and report. However, when I run the page and click submit, I get ORA-01403: no data found.
When I test the service, this is what shows in the Message Request:
<?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/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Header><namesp1:Header xmlns:namesp1="http://www.xignite.com/services/"><namesp1:Username xsi:type="xsd:string"></namesp1:Username><namesp1:Password xsi:type="xsd:string"></namesp1:Password><namesp1:Tracer xsi:type="xsd:string"></namesp1:Tracer></namesp1:Header></SOAP-ENV:Header><SOAP-ENV:Body><namesp1:ListFuturesByExchange xmlns:namesp1="http://www.xignite.com/services/"><namesp1:Exchange xsi:type="xsd:string">NYMEX</namesp1:Exchange></namesp1:ListFuturesByExchange></SOAP-ENV:Body></SOAP-ENV:Envelope>
Nothing shows in the Message Response.
I have also tried to call a simple web service that I created in .NET. It exhibits the same behavior. I am able to add the reference and create the form. But when I click the submit button, I get ORA-01403: no data found.
Windows 2000
HTMLDB 2.0.0.00.49
Oracle9i 9.2.0.6.0
Any help will be greatly appreciated.

I'm having a similar problem!, Although, distressing as it is to observe the lack of response this thread has had for 9 months, I'm still seeking help here!
I created a web service reference according to the following WSDL : "http://OgAppExpress:[email protected]:5555/invoke/OgAdminUtils.pub:WSDL_HLR" (operation name="getSubscriberInfoByMSISDN") and a form on that web service, all of which went very nicely. But! When I ran the form, inserted the value ("3546933599") into the parameter and pressed submit.... => "ORA-01403: no data found"
The debug action displays very limited information and sheds no light on the problem :( Multiple attempts, on recreating the project from scratch, have resulted in the same utter failure! Needless to say, this nulls the affect of my Prozac proscription....
Is there anybody out there who can help me and defend APEX's reputation?

DNS problem when calling a web service

Similar Messages

Maybe you are looking for