Problem in calling BW Web Reporting

Hi.
I installed EP 60 SP4 sneak preview and I want to call bw web reporting in EP.
So, I defined BW system in System Landscape and create iview using BW Web reporting template.
(BW web reporting URL is "http://laphabw.lapha.net:8100/sap/bw/BEx?sap-language=EN&bsplanguage=EN&CMD=LDOC&TEMPLATE_ID=TESTWEB" in WAD)
If I call this url in browser, It works.
When I create iview, I inserted "sap-language=EN&bsplanguage=EN&CMD=LDOC&TEMPLATE_ID=TESTWEB" for query string but It doesn't work.
I created again iview using Simple URL template and It works.
Why doesn't work for BW Web Reporting template ?
Regards, Arnold.

Hi Arnold,
I don't know a way to test the url the portal creates. If you have the plug-in installed, it must be a connection parameters. I can't remember if it was in EP5 or EP6 and I don't have an EP6 systems I can check right at the moment. If I had to guess, you are probably missing the http port of the BW system
From your url, laphabw.lapha.net:8100, the port would be 8100. In the connection properties, I don't believe there is a parameter for the port, you have to specify the port in the system name. Also make sure it is fully qualified, not just laphabw.
If this doesn't help, send the connection string parameters and we'll take a look
John

Similar Messages

Problem in calling BW web templates from Netscape 7.0

Hi all
I have a problem in calling BW web template from Netscape 7.0, it gives an error " port number not accepted for security reasons" .
It works on Netscape 8.0 and ie.
regards
Paul

This is the very frequently asked question about Netscape.
http://ilias.ca/netscape/browserfaq/#portaccess
Solution is:
find the file c:\Program Files\Netscape\Netscape\defaults\pref\all.js
and append the following string to this file:
pref("network.security.ports.banned.override", "1080");

How to call jsp web report from forms 9i

Dear fellows,
How can i call a jsp report from forms 9i.
Thanx
Mochoo

Use web.show_document instead of Run_Report_Object. If the jsp contains a paper layout you can still use Run_Report_Object, but you have to specify the filename extension .jsp along with the filename.

ERR_WIS_30270 ..when calling a Webi Report ..

Hello,
after having installed Webi Clients Tools in XI 3.1 SP2 Version on WIN XP. Every time i try to open a webi Report with the rich Client i get following Error: openDocumentMDP-API (Error: ERR_WIS_30270)
I reinstalled Client Tools XI 3.1 and SP2 (without success)
BOE Version is 12.2.0.290
Client also 12.2.0.290
Any suggestions .. Thanks ..
Edited by: MM on Oct 4, 2010 5:43 PM
Edited by: MM on Oct 4, 2010 5:52 PM

HI ,
This error might due to various reasons , may be you can try searching for SAP notes with this error code ,
here are some of them for your reference
Note 1497849 - "An internal error occured while calling 'executeDrillAction' API. (Error: ERR_WIS_30270)" when drilling up on a dimension of a webi report based on BW
Note 1290720 - Error: An Internal error occured while calling 'SubmitReport' API (Error: ERR_WIS_30270) while refreshing migrated WebIntelligence reports in edit mode
Note 1436964 - An internal error occured while calling 'processDPCommands' API. (Error: ERR_WIS_30270)
Regards,
Sathya

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

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

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

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?

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.

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

Problem in Calling a Web Service

Hi All,
I created an Adaptive Web Service Model by selecting a wsdl file in one of my Web Dynpro Project. Deployment of project is successful but when i run the application i am getting the following error:
The initial exception that caused the request to fail, was:
com.sap.engine.services.webservices.espbase.discovery.BaseIOException: Invalid Response Code 404 while accessing URL: http://paritas.sap.com:8000/sap/bc/srt/wsil/. Response Message: Not Found. Content Type: text/html. Body Content: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Error Report</title> <style> td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active </style> </head> <body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0"> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"> 404 &nbsp Not Found</td> </tr> <tr bgcolor="#3F73A3"> <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td> <td height="23"><img width=1 height=1 border=0 alt=""></td> <td align="right" height="23">SAP J2EE Engine/7.01 </td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"> The requested resource does not exist.</td> </tr> <tr bgcolor="#FFFFFF"> <td align="left" valign="top" height="48"> Details:</td> <td align="left" valign="top" height="48"><pre> Go to <A HREF="/" target="_parent">main page</A> of this application!</pre></td> </tr> </body> </html>
Can anyone tell me how to solve this issue??
regards,
Ramakanth

Hi Lavanya,
Thanks for the reply..
As u said i tried from webservices navigator.. It is giving a message as
Cannot download WSDL from http://paritas.sap.com:8000/sap/bc/srt/wsdl/bndg_DF69792F4B606DF1B168001CC0F24CF0/wsdl11/allinone/ws_policy/document?sap-client=101: It is not allowed to access this service. If you believe you should be able to, please contact your system administrator.
But I am the administrator and i logged in as administrator only..
regards,
Ramakanth

Book mark problem in SAP Bi web report with internet explorer 8

Hi
we recently started usig internet exlpore 8.0 for BI report, in that when we are click the book mark button it was not doing nothing. the same book mark option is working fine with Ineternet Exlpore 6.0
Note:we are allowing the Popup in IE8.0
thanks
Sudha

Hi Sudha,
We had had the same issue, and we solved it reintalling the internet explorer (that was the faster and easier solution).
[1159538|https://websmp130.sap-ag.de/sap(bD1lcyZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1100707] this note explain some errors with i-explorer 6 and 7, but it also happens with ie 8. In the note you have a "script" to be executed in the computer that have the error, but we didn't tested, we reinstall the ie directly.
Regards and I hope it helps, Federico

Problem in call onpremise web service from o365 using jquery ajax

I am trying
to consume an onpremise web service from the o365 site page using
jquery ajax and it's giving me following error:<o:p></o:p>
"Error:
Operation aborted<o:p></o:p>
Here is the
code:<o:p></o:p>
<o:p></o:p>
jQuery.support.cors
= true;<o:p></o:p>
 $.ajax<o:p></o:p>
({ <o:p></o:p>
type: "POST",
 <o:p></o:p>
url: 'http://**************/WebService.asmx/CreateFolder',
 <o:p></o:p>
data: "{'PartId':'"+partnerid+"'}",
 <o:p></o:p>
contentType: "application/jsonp; charset=utf-8",
 <o:p></o:p>
dataType: "jsonp",
 <o:p></o:p>
username: "*****************",
 <o:p></o:p>
password: "******************",<o:p></o:p>
 success:
function (msg) { $("#divResult").html("Success"); },
 <o:p></o:p>
 error:
function (xhr, status, error){ console.log(error);
console.log(status); }
 <o:p></o:p>
});<o:p></o:p>
Any
help would be greatly appreciated.Thanks.<o:p></o:p>

Where exactly you are trying to create folder
This will work on both Office 365 and on prem
http://www.c-sharpcorner.com/UploadFile/0e18a8/create-a-folder-in-document-library-in-sharepoint-2013-using/
var context = SP.ClientContext.get_current();
//gets the current context
var web = context.get_web();
//gets the web object
var list = web.get_lists();
//gets the collection of lists
var targetList;
var itemCreation;
function createFolder() {
 targetList = list.getByTitle("MyDocumentLibrary");
 itemCreation =
new SP.ListItemCreationInformation();
 itemCreation.set_underlyingObjectType(SP.FileSystemObjectType.folder);
 itemCreation.set_leafName("MyCustomFolder");
 var folderItem = targetList.addItem(itemCreation);
 folderItem.update();
 context.load(folderItem);
 context.executeQueryAsync(onFolderCreationSuccess, onFolderCreationFail);

Problem in calling XI generated Web Service via Java Web Dynpro

Hi experts,
I have problems with calling a web service, which was created by XI. I have already tested the web service with Altova XMLSpy. The Web Service works fine.
But when embedding this web service into Java Web dynpro application no message flow is given. I have two views one Selection View and one Result View which should show the answer sent by RFC-Call.
My Settings in NWDS:
During configuration of web dynpro I have choosen 'Import adaptive Web Service Model' --> Select wsdl file via local file system --> 'no logical destinations - use WSDL URL for metadata retrieval and web service execution'.
The model is also not shown in diagram view although I have added into the diagram.
The web service was created on XI 7.0.
Should I do any other settings e.g. in Visual Administrator, Web Dynpro Content Administrator?
So can anybody help me.
Thanks a lot.
Regards,
Mario

Hi Aviad,
thanks for your fast reply.
But in Web Service Navigator my Web Service is not shown, because I used the SOAP Adapter.
My Web Service link:
http://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:SRV_GBD_WS_GET_DEB_DETAIL:CC_GBD_WEBSERVICE_SENDER&version=3.0&Sender.Service=&Interface=%5E*
During executing Web Dynpro I got following errors:
1. 'The system cannot find the path specified'.
2. com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL
Regards,
Mario

Problem in calling BW Web Reporting

Similar Messages

Maybe you are looking for