Wsdl deplyment in ws navigator

Hi all.
We are provided with a WSDL File which has a excel attachment
I have two questions.
How/where to deploy this Wsdl to be tested using WSNavigator with attachments.
I have gone through
"How to send SOAP Message with attachments?
is this blog enough to read an send attachment from wsdl?
any other pre-requisites for achieving the same?
Question two:
Do we have any tools to create the web service client?
Could you pass me on the Code for creating /deploying WS client.
Thanks,

>Do we have any tools to create the web service client?
>Could you pass me on the Code for creating /deploying WS client.
Use Apache Axis software to code web service client logic. It has even samples code for it. This is one of the ways to do it.

Similar Messages

Error "Empty list of services in WSDL" at Web Services Navigator

Hello all,
I have a problem when trying to test my web service in the Web Services Navigator. I will have to call this web service from a web dympro.
This is the error I get when selecting my destination in the search form:
Empty list of services in WSDL http://wsdl_url
(( [See screenshot|http://img402.imageshack.us/img402/6381/errorwebservice2xh9.png] ))
What I've done until now is:
1) I published a web service based on a custom ABAP RFC using the creation wizard and finally I published it in our services registry.
2) I created "metadata" and "execution" destinations using the Destination Template Management in CE.
I haven't done any configuration in transactions WSCONFIG/WSADMIN or SOAMANAGER. (Could I have something missing here?)
BTW, I am new at CE and web dympro...

Hi,
I've the same problem when calling a self defined WebService from Web Dynpro.
I created the service by using a proxy, creating an endpoint with SOAMANAGER and publishing it via WSPUBLISH.
The errormessage 'Empty list of services in WSDL' is right cause the section
<wsdl:service name="...
after the binding-section at the end of the WSDL is missing.
I tried the same with a SAP-CRM-service (CRM_BPBASICDATABYNAMEADDRQR) and here all is fine cause in the WSDL the service-section is existent.
I'm using the Services Registry of SAP PI (SAPKB71006)
May be this help somebody to help us.
Regards
Christoph

Import WSDL imported from WS Navigator.

Hi Everybody,
First, sorry for my English. I'm from Brazil.
I've done an EJB in Developer Studio, generated a WebService in the same tools and deployed then in Application Server. After that, I run the WS Navigator and exported the WSDL to a zip file.
So, I imported this WSDL in PI (External Definition) but I can't use this "External Definition" because when I try to use then in Message Mapping or Message Interface, the following error is showed: "Has no message".
Do I have to convert the WSDL to XSD format?
How can I use a WSDL as an External Definition?
Does anybody could help me?
Best Regards,
Hyalen.

Hello Sunil,
Thank you for the quick response.
I managed to import the WSDL. The problem is that I can not use the External Definition in the Message Mapping because the system said that has no message.
In fact, after importing the WSDL Message tab is empty.
Thanks a lot for the help.
Hyalen.

Testing WSDL through webservice navigator

HI All,
Please elaborate on how to test the WSDL link though webservice navigator.
Di we require some different installations or what exactly is webservice navigator
Edited by: solutionProvider on Dec 24, 2010 8:43 PM

HI All,
Please elaborate on how to test the WSDL link though webservice navigator.
Di we require some different installations or what exactly is webservice navigator
Edited by: solutionProvider on Dec 24, 2010 8:43 PM

How to find the WSDL URLs in NW CE 7.1 EhP1?

Hi,
I have upgraded my dev system from NW CE 7.1 SP5 to NW CE 7.1 EhP1. In this new version, the layout of the Web Service Navigator changed.
I used to use the old WS Navigator to find out the URLs where the WSDLs for services are available. I deployed my components (EJB projects with web services implemented by Enterprise Beans), located them in the WS Navigator and used the WSDLs there to generate Java clients to that services.
However, the new WS Navigator does not show the WSDL URL any more if you choose "Vendor System (Anwendersystem)" and then "Local AS Java (Lokaler AS Java)".
Any ideas where I can get the WSDL URLs? I have been searching the whole NW Administrator, but could not find that information.
Best regards,
Patrik
Edited by: Patrik Spiess on Feb 18, 2009 3:58 PM
Edited by: Patrik Spiess on Feb 18, 2009 3:59 PM

Patrik, you can also view the WSDL url in WS Navigator:
1 - In "Service Test" tab, choose your service, and follow all steps until to get the result of the service execution (step 4);
2 - In Step 4 (Result), click in "Add to Test Scenario";
3 - In "Test Scenario" tab, choose the test scenario of your service and click in "Change Services Access";
4 - Now, you can see the WSDL url in the popup.
Best regards,
Fabiano Rosa

Error while testing via WS Navigator.

Hi,
My scenario is SOAP>PI>FTP.
I was trying to post the data via WS Navigator tool.
I have generated wsdl URL as per the forum comments. http://host:port /XISOAPAdapter/MessageServlet?channel=:s:c
Also I can see when we do display WSDL in ID object, it will also generate a wsdl url with http://host:port /<alphanumeric number>. When we use the system generated wsdl url, the WS Navigator can recognize the sender interface and request for input parameter and post the data and the message processed successfully. But this url cannot be used for positing the data via any other SOAP UI.
I would like to know, why WS navigator cannot recognize the wsdl URL which is generated in the soap address HTTP port tab of the WSDL file.
Any pointers regarding this will be very much helpful
Thanks
Ray.

PI generating WSDL is not able to test in XMLSPY. But I tested the same wsdl works in SOAPSONAR. Manually generating WSDL works in all the tools. I think the bug might be in some tools to interpret WSDL properly at this time.

Testing WSDL

Hi,
I have a simple scenario SOAP->XI->RFC.
SAP/XI created a WSDL using option "define web service" present in integration directory.
Now I try to test this wsdl using web service navigator page.
What are the steps to use this tool?
This tool ask a WSDL URL.
What are this URL?
thanks,
Sérgio

hi,
did you have a look at this:
SAP SOAP Client Tool
https://www.sdn.sap.com/irj/sdn/downloaditem?rid=/webcontent/uuid/2fad3a59-0501-0010-7a92-dc43cd1cdf19 [original link is broken]
also have a look on how you can test web services with XML spy
(Testing section)
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

Cannot creat WSDL from......

Hi,
I am trying to download a WSDL file throught the webservices navigator. I get the error as
Cannot download WSDL from ...<URL>...Cannot connect to ...<URL>... Network is unreachable: connect
When i give the URL in the internet explorer, i can see the WSDL.
Please let me know what should be done to solve this.
Regards,
Raghu

i guess in your case the network would have a proxy. So in visual admistrator you need to do the proper settings to connect to the WSDL via the WS navigator link.
Note: From the WS navigator help page;
Enter WSDL
Web Services Navigator is a tool that gives you a short overview for a specific Web service, based on its WSDL and allows you to create and send a client request to the real endpoint.
In order to continue specify the location of the WSDL. Note the WSDL URL must be reachable from the server where this Web Services Navigator is installed. If http proxy is needed, be sure it is configured properly from the Visual Administrator.
A tree with the local for the server web services is shown too. Expand it in order to get the WSDL in a specific style.

Importing WSDL into External Definitions

Hi,
I got WSDLs from WAS WS Navigator, I have imported the WSDL from porttypes folder but I don't see any messages in the messages tab of External Definitions.
See below my WSDL
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns0="urn:xEM_MeasurementImportVi" targetNamespace="urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document" xmlns:tns="urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document">
<wsdl:types>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:java/lang" xmlns:tns="urn:java/lang" elementFormDefault="qualified">
 <xs:complexType name="ArrayOfint">
 <xs:sequence>
 <xs:element maxOccurs="unbounded" minOccurs="0" name="int" type="xs:int" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="ArrayOfString">
 <xs:sequence>
 <xs:element maxOccurs="unbounded" minOccurs="0" name="String" type="xs:string" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:schema>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:com.technidata.em.imp.consumption" xmlns:tns="urn:com.technidata.em.imp.consumption" elementFormDefault="qualified">
 <xs:complexType name="ReturnCode">
 <xs:sequence>
 <xs:element name="code" type="xs:int"/>
 <xs:element name="description" type="xs:string" nillable="true" minOccurs="0"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="ArrayOfReturnCode">
 <xs:sequence>
 <xs:element maxOccurs="unbounded" minOccurs="0" name="ReturnCode" type="tns:ReturnCode" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:schema>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:com.technidata.em" xmlns:tns="urn:com.technidata.em" elementFormDefault="qualified">
 <xs:complexType name="Measurement">
 <xs:sequence>
 <xs:element name="pSystemId" type="xs:string" nillable="true" minOccurs="0"/>
 <xs:element name="pSystemTagId" type="xs:string" nillable="true" minOccurs="0"/>
 <xs:element name="pDate" type="xs:dateTime" nillable="true" minOccurs="0"/>
 <xs:element name="pValue" type="xs:double"/>
 <xs:element name="pUnit" type="xs:string" nillable="true" minOccurs="0"/>
 <xs:element name="pDescription" type="xs:string" nillable="true" minOccurs="0"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="ArrayOfMeasurement">
 <xs:sequence>
 <xs:element maxOccurs="unbounded" minOccurs="0" name="Measurement" type="tns:Measurement" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:schema>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:xEM_MeasurementImportVi" xmlns:tns="urn:xEM_MeasurementImportVi" elementFormDefault="qualified" xmlns:s1="urn:java/lang" xmlns:s2="urn:com.technidata.em.imp.consumption" xmlns:s0="urn:com.technidata.em">
 <xs:import namespace="urn:java/lang"/>
 <xs:import namespace="urn:com.technidata.em.imp.consumption"/>
 <xs:import namespace="urn:com.technidata.em"/>
 <xs:element name="checkConnection">
 <xs:complexType>
 <xs:sequence/>
 </xs:complexType>
 </xs:element>
 <xs:element name="checkConnectionResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="xs:string" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="doMeasurementImport">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="pSystemId" type="xs:string" nillable="true"/>
 <xs:element name="pSystemTagId" type="xs:string" nillable="true"/>
 <xs:element name="pDate" type="xs:dateTime" nillable="true"/>
 <xs:element name="pValue" type="xs:double"/>
 <xs:element name="pUnit" type="xs:string" nillable="true"/>
 <xs:element name="pDescription" type="xs:string" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="doMeasurementImportResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="xs:int"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="doMeasurementsImport">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="pMeasurements" type="s0:ArrayOfMeasurement" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="doMeasurementsImportResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="s1:ArrayOfint" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="getErrorCodes">
 <xs:complexType>
 <xs:sequence/>
 </xs:complexType>
 </xs:element>
 <xs:element name="getErrorCodesResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="s2:ArrayOfReturnCode" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="getSupportedUnits">
 <xs:complexType>
 <xs:sequence/>
 </xs:complexType>
 </xs:element>
 <xs:element name="getSupportedUnitsResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="s1:ArrayOfString" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 </xs:schema>
</wsdl:types>
<wsdl:message name="checkConnectionIn_doc">
 <wsdl:part name="parameters" element="ns0:checkConnection"/>
</wsdl:message>
<wsdl:message name="checkConnectionOut_doc">
 <wsdl:part name="parameters" element="ns0:checkConnectionResponse"/>
</wsdl:message>
<wsdl:message name="doMeasurementImportIn_doc">
 <wsdl:part name="parameters" element="ns0:doMeasurementImport"/>
</wsdl:message>
<wsdl:message name="doMeasurementImportOut_doc">
 <wsdl:part name="parameters" element="ns0:doMeasurementImportResponse"/>
</wsdl:message>
<wsdl:message name="doMeasurementsImportIn_doc">
 <wsdl:part name="parameters" element="ns0:doMeasurementsImport"/>
</wsdl:message>
<wsdl:message name="doMeasurementsImportOut_doc">
 <wsdl:part name="parameters" element="ns0:doMeasurementsImportResponse"/>
</wsdl:message>
<wsdl:message name="getErrorCodesIn_doc">
 <wsdl:part name="parameters" element="ns0:getErrorCodes"/>
</wsdl:message>
<wsdl:message name="getErrorCodesOut_doc">
 <wsdl:part name="parameters" element="ns0:getErrorCodesResponse"/>
</wsdl:message>
<wsdl:message name="getSupportedUnitsIn_doc">
 <wsdl:part name="parameters" element="ns0:getSupportedUnits"/>
</wsdl:message>
<wsdl:message name="getSupportedUnitsOut_doc">
 <wsdl:part name="parameters" element="ns0:getSupportedUnitsResponse"/>
</wsdl:message>
<wsdl:portType name="xEM_MeasurementImportVi_Document">
 <wsdl:operation name="checkConnection">
 <wsdl:input message="tns:checkConnectionIn_doc"/>
 <wsdl:output message="tns:checkConnectionOut_doc"/>
 </wsdl:operation>
 <wsdl:operation name="doMeasurementImport">
 <wsdl:input message="tns:doMeasurementImportIn_doc"/>
 <wsdl:output message="tns:doMeasurementImportOut_doc"/>
 </wsdl:operation>
 <wsdl:operation name="doMeasurementsImport">
 <wsdl:input message="tns:doMeasurementsImportIn_doc"/>
 <wsdl:output message="tns:doMeasurementsImportOut_doc"/>
 </wsdl:operation>
 <wsdl:operation name="getErrorCodes">
 <wsdl:input message="tns:getErrorCodesIn_doc"/>
 <wsdl:output message="tns:getErrorCodesOut_doc"/>
 </wsdl:operation>
 <wsdl:operation name="getSupportedUnits">
 <wsdl:input message="tns:getSupportedUnitsIn_doc"/>
 <wsdl:output message="tns:getSupportedUnitsOut_doc"/>
 </wsdl:operation>
</wsdl:portType>
</wsdl:definitions>
Appreciate your quick response.
Srini Sandaka

Hi,
I diagnose the problem, the problem with the name space length.
Orginal NameSpace: urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document
Modified NameSpace: urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/documen
The External Definitions is recognizing only 60 characters namespace. If the namespace exceed 60 characters it is not showing any messages in the messages tab.
Will make any problem to call the WebService from XI since we are changing the original namespace in the WSDL and imported into XI.
How can we overcome this problem, is it a limitation.
Thanks
Srini Sandaka

Cannot seem to register any of my web services in OWSM, v10.1.3.1

Hi All -
I am using Oracle Web Services Manager, v10.1.3.1 build [2006.10.06.06.37]
Whenever I try to use OWSM management console to register a web service with my gateway I get the following error:
"Service information cannot be added because of the following reason(s):
Cannot read WSDL: Failed to retrieve the Service WSDL from WSDL URL with HTTP Status 401"
I have verified the service's WSDL is accessible by navigating to its URL. The web service is hosted in weblogic and is on the same machine as OWSM.
Any suggestions?
Thanks.
-greg

Hi,
I had the same problem, but using HTTP. Check if the gateway ID that exist in your gateway settings is the same that exist in gateway configuration file (gateway.component.id argument): <ORACLE_HOME>/owsm/config/gateway/gateway-config-installer.properties.
If isn't, you must enter the gateway ID from OWSM settings in gateway.component.id argument into this file and redeploy de gateway application.
Let me know if it will work. because I tried do set my OWSM do accept HTTPS requests from my client application and it didn't work.
Thanks,
Rodrigo

Creating and consuming web service

Hello Everyone,
Please help me in creating a webservice which can be consumed in a button in Excel sheet i.e. I have to create a button in Excel sheet and on click of that button i have to consume a web service deployed in AS. Also I have to pass the data in Excel sheet to that web service.
PS: This is just a business logic no other view or UI is required here.
Thanks in advance.
Regards
Pranav

Hi Pranav
>2. I know I can download WSDL files from server using the test page. Downloaded zip file has these three wsdl files Config1_document.wsdl, Config1_TestVi_document.wsdl and main.wsdl. But which wsdl to use while consuming.
Actually all the .wsdl files are part of single WSDL document which describes your Web service. Starting/root point here is main.wsdl which references two other .wsdl. You can access any time the root WSDL part by URL like
"http://<host>:<port>/BcfRemoteCheck/Config1?wsdl&style=document&mode=standard".
Hope you know where to see the WSDL URL (in Webservice Navigator or in Single Service Administration where you downloaded the ZIP).
When you are consuming web-service you need all the parts. Usually when a Web-service is consumed the remote WSDL is used for generation of WS Client Proxy. But, the WSDL files can be also downloaded and used locally for generation of the WS Client Proxy.
Sometimes the WSDL is not necessary at all for WS consuming on run-time. In the case it's used only on design-time just to know WS names, ports, operations, etc, for writing the code of WS Client.
BR, Sergei

Service Registry documentation URL and deleting published services?

Hello,
We are using SAP NetWeaver PI 7.1 SP 7. Do anyone know how you can control the published Documentation URL for published Service Interfaces in the Service Registry when you publish service interfaces directly from the ESR (from the WSDL tab on a Service Interface)?
Do anyone know if you can delete published service interfaces in the Service Registry if a service interface have been deactivated/deleted/is not used any more?
Regards,
Markus Johansson

Hi Markus,
There is anothre approach to delete services using API's.
Determine the WSDL Url of your Services Registry.
- Open SAP NetWeaver Administrator and choose SOA Management Application and Scenario Communication Single Service Administration .
- Search for ServicesRegistrySi and copy the Services Registry WSDL.
Open WS Navigator.
- In the WSDL Url field, enter the Services Registry WSDL and choose Next.
- All Services Registry API operations are displayed.
- Select operation hideServiceDefinitions and choose Next.
- Enter either the UDDI key or the logical key of the service definition you want to delete and choose Execute.
Both keys are displayed on the General tab in the Services Registry.
In case SR shows you as having no logical key for the service you are interested in removing.
There is another operation, findServiceDefintions, that can be used to search a name that will return the UDDI key. Take that value and plug it into the hideServiceDefintions uddiKey value.
Regards,
Jitender

Create Service CAF for send email

Friends,
I've to create a service-CAF that send email.
I'll disable the default of BPM email notifications and put one WS for do it.
Does anyone have any experience with it?
[]´

Hi Tulio,
Why not implementing a simple JEE5 web service for this? AFAIK there is no need to warp this into CAF as the CE stack would also allow you doing so with a simple POJO + annotations.
Within your implementation you could access the standard java.mail APIs. Simply make sure that you set its properties accordingly in the java mail service setttings of the engine (NWA > Configuration Management > Infrastructure > Java System Properties - if I recap this correctly).
So in theory (I did not do it myself yet) this should be a "no-brainer"
As soon as it is deployed and set up correctly on the CE stack you could access the WSDL via the WS navigator (or via the SOA configuration), import it to your process project and make use of it in automated activities.
Another - interesting - option would be using the EJB functions for this. I would imagine modelling the interface this way:
boolean sendMail(String to, String title, String subject, String body)
You could then use this in some (input or output) mapping and pass in some values. In addition the function will return a boolean (or maybe a String) that could tell you the outcome of sending out the mail (so that you know if it worked technically - this does not necessarily mean that the mail reached the recipient - that's depending on infrastructure and SPAM filters
The more I type the more I like this idea - maybe I find two minutes to write some short document for this
Cheers,
Martin

Recursive Parent Child relationship in JPA

@Entity
@Table(name = "OBJECTCATEGORY")
public class ObjectCategory implements Serializable {
 @Id
 private String categoryId;
 private String categoryName;
 private String description;
 private static final long serialVersionUID = 1L;
 @ManyToMany(fetch = FetchType.EAGER)
 @JoinTable(name = "MAP_CATEGORY", joinColumns = @JoinColumn(name = "CATEGORYID"), inverseJoinColumns = @JoinColumn(name = "OBJECTID"))
 private List<MapC> mapList = new ArrayList<MapC>();
// Recursion
 @OneToMany(fetch = FetchType.LAZY, mappedBy = "fqQuesCatagory")
 List<ObjectCategory > categoryList = new ArrayList<ObjectCategory>();
 @ManyToOne
 @JoinColumn(name = "PARENTCATEGORY")
 private ObjectCategory fqQuesCatagory
// Recursion
 public FqQuesCatagory() {
 super();
 public String getCategoryname() {
 return this.categoryname;
 public void setCategoryname(String categoryname) {
 this.categoryname = categoryname;
 public String getDescription() {
 return this.description;
 public void setDescription(String description) {
 this.description = description;
 public List<MapC> getMapList() {
 return faqList;
 public void setFaqList(List<MapC> faqList) {
 this.mapList = mapList ;
 public String getCategoryid() {
 return categoryId;
 public void setCategoryid(String categoryid) {
 this.categoryid = categoryId;
 public List<ObjectCategory> getFqCategoryList() {
 return categoryList;
 public void setFqCategoryList(List<ObjectCategory> categoryList) {
 this.categoryList = categoryList;
 public ObjectCategory getFqQuesCatagory() {
 return fqQuesCatagory;
 public void setFqQuesCatagory(ObjectCategory fqQuesCatagory) {
 this.fqQuesCatagory = fqQuesCatagory;
Doesn't SAP JPA support recursive parent-child relationship (highlighted by "// Recursion"). The same model works in TopLink perfectly.

Sorry for the delayed update..
I see an issue in the WSNavigator. I have a method in my EJB exposed as a web service. This method has a single argument, which is a serializable class containing a few string variables and the above-mentioned Entity with suitable getters and setters for all the class variables.
When I try to select this operation under the WSDL in the Webservice Navigator, I get a stack overflow error. I think it is because WD4J run-time is not able to build the nested tree. Not sure though...I've attached the stack trace below:
Cannot send an HTTP error response [500 "Application error occurred during the request procession." (details: java.lang.StackOverflowError
at java.lang.String.lastIndexOf(String.java:1496)
at java.lang.String.lastIndexOf(String.java:1458)
at com.sap.dictionary.runtime.StringUtil.getPackageName(StringUtil.java:143)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:179)
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler._getScalarType(DictionaryHandler.java:447)
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getDataType(DictionaryHandler.java:159)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:447)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addAttribute(NodeInfo.java:746)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addAttribute(NodeInfo.java:759)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder.createParameterNodeInfo(DWSContextBuilder.java:984)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder.access$400(DWSContextBuilder.java:88)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1591)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
Any thoughts on this will be highly appreciated.
BR.

Cognos navigator iview - WSDL error

Hi All,
I am trying to use cognos navigator ivie win my portal. Populated CPS:Connection Server property with a wsdl link . When I previewed the iview, it gives me below error:
WSDLException: faultCode=OTHER_ERROR: Unable to locate document at 'http://cognosdev.afis.chevron.net:6100/cognos841dev/cgi-bin/cognosisapi.dll/wsrp/cps4/portlets/nav?wsdl&b_action=cps.wsdl'.
Is it something to do with connection setup between Cognos server and portal ?
can anyone please suggest on this issue asap.
Regards,
Jalpa Shukla

Hey Kris,
I know this sounds obvious, but I'd say the Portal can't find that wsdl file and therefore has no idea how to get at those web services.
Have you seen this entry from IBM support?
http://www-01.ibm.com/support/docview.wss?uid=swg21339355
Are you using a proxy server in front of the Cognos server?
-Kevin
PS: The message suggests there's more info in the log file... any way to get a snippet from that log?

Wsdl deplyment in ws navigator

Similar Messages

Maybe you are looking for