ICI v3.00.63007 Specification Doc/Wsdl files

Hi,
    I am working on Development of ICI Interface.
    But I don't have the latest Specification Document and the wsld files. I have opend as OSS message but I still couldn't get the response. (My ICI version is 3.00.63007).
    If anybody could provide me the latest WSDL files or Specification Document then that will be of Greate Help.
     Or even if you could tell me from where should I get that Documents/files.
    Please.
     Thanks.
    Saurabh.
[email protected]
[email protected]

I found the documentation in one of the cookbooks of SAP CRM CIC.Once I get the filei shall forward to yr emailid
Thanks
Surya
Message was edited by: Surya Kuchibotla

Similar Messages

ICI adaptor development--need spec and WSDL file

Hi, I'm trying to develop a adaptor between ICI and our contact center software. I have the V3.0.3 spec for ICI but couldn't find the WSDL file anywhere.
Thanks

Hello Beigen,
You can find the newest ICI document at:
SAP CRM Integrated Communication Interface (CA-ICI) [original link is broken] > Integrated Communication Interface
or directly
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b075ad90-0201-0010-6a99-fac1a256ac39
However, we only have the WSDL as part of version 3.01. The newer version is being worked on but no plan date yet.
With the ICI version that you can access above, you will be able to see more examples and detail how to implement the ICI adapter. The most efficient way would be to contact the SAP certification center to get more information. Hope this helps.
Best Regards,
Satit Nuchitsiripattara
SAP CRM Development

ICI WSDL Files and logon Information handed over

Hello,
We need to integrate a couple of call-centers, each working with its own telephone switch into one CRM-System.
Thus we plan to develop a specific ICI-adapter which connects the CRM to all switches.
To start we need the WSDL files for the ICI-descriptions, but cannot find them.
Can anybody help me, about where to find these WSDL files?
Also I wonder if the logon process from the CRM-IC hands over some site information to Adapter, so that he knows with which switch the agent is linked.
Thanks for your help
Michael

Hello Michael,
I'm not sure if this is what you are looking for, but section 8.4 of the ICI specification contains the following info:
8.4 WSDL description of the interface
The following list contains the names of the files which contain the WSDL based description of
the Integrated Communication Interface:
ICI Object WSDL file
IciActionItem (see 12 in 3.1) IciActionItem.xml
IciChatLine (see 10 in 3.1) IciChatLine.xml
IciChatSession (see 11 in 3.1) IciChatSession.xml
IciContainer (see 4 in 3.1) IciContainer.xml
IciEvent (see 3 in 3.1) IciEvent.xml
IciFolder (see 8 in 3.1) IciFolder.xml
IciItem (see 5 in 3.1) IciItem.xml
IciMessage (see 9 in 3.1) IciMessage.xml
IciMonitor (see 13 in 3.1) IciMonitor.xml
IciPhoneCall (see 7 in 3.1) IciPhoneCall.xml
IciPhoneLine (see 6 in 3.1) IciPhoneLine.xml
IciSystem (see 1 in 3.1) IciSystem.xml
IciUser (see 2 in 3.1) IciUser.xml
Regards,
John

Creation of WSDL file & import it in the creation of automated activity

Hi Friends,
I want to create BPM process for automated activity.I have created task for human activity. I have created CAF Application,but I dont know how to ceate/import WSDL file(This WSDL file is used to assign the interface to the automated activity).Can anyone explain about WSDL file creation and it's significance.
(I am following one document 'Creating BPM Process with Human and Automated Activities' from this link ' https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/501bd56f-a5a6-2b10-4fbf-a61a64055fe4')
Regards,
Pranjali

Hi Pranjali,
WSDL is a document written in XML. The document describes a Web service. It specifies the location of the service and the operations (or methods) the service exposes. WSDL types are used to describe the data. XML Schema is used (inline or referenced) for this purpose.
Refer to the below link for more deatils on WSDL:
http://en.wikipedia.org/wiki/Web_Services_Description_Language
Also there are numerous documents avaiable on this topic, just do a google search.
Hope this helps!!
Cheers,
Arafat

C# Proxy Classes from SAP WSDL files

We are trying to generate proxy classes for SAP eSOA web services using C# and Visual Studio 2005.
When we try to run Microsoft's proxy class generation utility, WSDL.exe, errors are generated that attribute incorrect syntax to the SAP WSDL file:
> Microsoft (R) Web Services Description Language Utility [Microsoft (R)
> .NET Framework, Version 2.0.50727.42] Copyright (C) Microsoft
> Corporation. All rights reserved.
> Warning: This web reference does not conform to WS-I Basic Profile v1.1.
> R2028, R2029: A DESCRIPTION using the WSDL namespace and the WSDL SOAP
> binding n amespace MUST be valid according to the XML Schemas found at
> http://schemas.xmls oap.org/wsdl/2003-02-11.xsd and http://schemas.xmlsoap.org/wsdl/soap/2003-02-11.
> xsd.
> - Warning: The element 'definitions' in namespace
> 'http://schemas.xmlsoap.org /wsdl/' has invalid child element 'properties' in namespace 'urn:com-sap:ifr:v2:
> wsdl'. List of possible elements expected: 'import, types, message,
> portType, bi nding, service' in namespace
> 'http://schemas.xmlsoap.org/wsdl/'. Line 1748, posi tion 4.
>
> SOAP 1.1 binding was not found: WS-I's Basic Profile 1.1 consists of
> implementat ion guidelines that recommend how a set of core Web
> services specifications shou ld be used together to develop
> interoperable Web services. For the 1.1 Profile, those specifications are SOAP 1.1, WSDL 1.1, UDDI 2.0, XML 1.0 and XML Schema.
>
> For more details on the WS-I Basic Profile v1.1, see the specification
> at http://www.ws-i.org/Profiles/BasicProfile-1.1.html.
The WSDL file is obtained from the SAP ES Workplace, from the following URL:
http://erp.esworkplace.sap.com/socoview(bD1lbiZjPTgwMCZkPW1pbg==)/render.asp?&id=4FFC1A97663611DA36BB000F20DAC9EF&fragID=&packageid=DBBB6D8AA3B382F191E0000F20F64781&iv=
We have already tried both SAP files available from this location; neither works.
Any insight you can offer to help us generate these proxy classes is welcome. Note that the SAP PDF file, "ESOA-Roadmap-Workshop.PDF" talks about one syntactic incompatibility with Microsoft WSDL (on page 70), but this solution does not work, and indeed the token 'parameters' does not appear anywhere in either SAP WSDL file for Create Maintenance Request eSOA.
Thanks for any help you can offer!
-- Julian Mensch

I have the same problem after renaming "parameters" to "parameter" and I'm using the same example ES that's in the document:
http://erp.esworkplace.sap.com/sap/bc/srt/xip/sap/ECC_EMPLOYEEBASICDBYEMPLOYEEQR/version3?sap-client=800&wsdl=1.1
wsdl.exe from .NET Framework 2.0.50727.42 gives me
Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 2.0.50727.42]
Copyright (C) Microsoft Corporation. All rights reserved.
Warning: This web reference does not conform to WS-I Basic Profile v1.1.
SOAP 1.1 binding was not found: WS-I's Basic Profile 1.1 consists of implementat
ion guidelines that recommend how a set of core Web services specifications shou
ld be used together to develop interoperable Web services. For the 1.1 Profile,
those specifications are SOAP 1.1, WSDL 1.1, UDDI 2.0, XML 1.0 and XML Schema.
For more details on the WS-I Basic Profile v1.1, see the specification
at http://www.ws-i.org/Profiles/BasicProfile-1.1.html.
Warning: no classes were generated.
Warnings were encountered. Review generated source comments for more details.
I'm sure it's something really stupid since this example worked at some point for whoever wrote the doc...
It's sad that there is basically no .NET support from the SAP side and apart from a few documents there is basically no developer documentation or samples...

WSDL file not generated from wscompile using jwsdp-1.2.

Hi,
I used following config.xml file to generate the WSDL file.......but it didn't got genereted. Other artifacts got generated. I'm using jwsdp-1.2.
<?xml version="1.0" encoding="UTF-8"?>
<configuration
xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
<service name="PersonWebService"
typeNamespace="http://rahuls_person_service.org/type"
targetNamespace="http://rahuls_person_service.org/wsdl"
packageName="rahul.ws.test">
<interface name="rahul.ws.test.PersonWS"
servantName="rahul.ws.test.PersonWSImpl"/>
</service>
</configuration>
And I have following entry in the build.xml file.........
<target name="generate-server_wsdl" depends="prepare">
<antcall target="edit-config">
<param name="config.rpcenc.file" value="${config.rpcenc.file}"/>
</antcall>
<wscompile
keep="true"
base="${samplesbuild}/${appname}/classes/server"
xPrintStackTrace="true"
gen="true"
verbose="false"
model="${samplesbuild}/${appname}/${model.rpcenc.file}"
classpath="${compile.classpath}"
config="${config.rpcenc.file}">
<classpath>
<path refid="compile.classpath"/>
</classpath>
</wscompile>
<antcall target="unedit-config">
<param name="config.rpcenc.file" value="${config.rpcenc.file}"/>
</antcall>
</target>
Can any body point me what may be the problem.
thanks in advance.
Rahul

The following is from the jwsdp-1.1 tutorial at http://java.sun.com/webservices/docs/1.1/tutorial/doc/
The tutorial for 1.2 is not available yet.
Seems you need to modify your config.xml to have a <service> element.
The wscompile tool reads the configuration file (config.xml), which contains information that describes the web service. The basic structure of config.xml follows:
<?xml version="1.0" encoding="UTF-8"?>
<configuration
xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
<service> or <wsdl> or <modelfile>
</configuration>
The <configuration> element may contain exactly one <service>, <wsdl>, or <modelfile> element.
The <service> Element
If you specify this element, wscompile reads the RMI interface that describes the service and generates a WSDL file. In the <interface> subelement, the name attribute specifies the service's RMI interface, and the servantName attribute specifies the class that implements the interface. For example:
<service name="CollectionIF_Service"
targetNamespace="http://echoservice.org/wsdl"
typeNamespace="http://echoservice.org/types"
packageName="stub_tie_generator_test">
<interface name="stub_tie_generator_test.CollectionIF"
servantName="stub_tie_generator_test.CollectionImpl"/>
</service>
The <wsdl> Element
If you specify this element, wscompile reads the service's WSDL file and generates the service's RMI interface. The location attribute specifies the URL of the WSDL file, and the packageName attribute specifies the package of the classes generated by wscompile. For example:
<wsdl
location="http://tempuri.org/sample.wsdl"
packageName="org.tempuri.sample" />

Error while uploading WSDL file in Interactive Form Data Connection!

I have created we service to return some data based on user input.
I am trying to link this webservice to Interactive adobe form! and While creating new data connection->uploading WSDL file--> I am receiving error i.e. Invalid File.
Please help me in resolving this issue.
I have created this WSDL file copy/pasting XML code generates from "Open WSDL document for selected binding" link in SOAMANAGER.
Regards,
Naveen.I

Hello,
This is a Webservice created for the FM : HRXSS_PER_READ_EMERGENCY_AR
Here is the sample of the WSDL file generated, as asked by you.
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="urn:sap-com:document:sap:soap:functions:mc-style" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:n1="urn:sap-com:document:sap:rfc:functions">
- <wsdl:documentation>
<sidl:sidl xmlns:sidl="http://www.sap.com/2007/03/sidl" />
</wsdl:documentation>
<wsp:UsingPolicy wsdl:required="true" />
- <wsp:Policy wsu:Id="BN_BN_ZHR_READ_EMERGENCY">
<saptrnbnd:OptimizedXMLTransfer uri="http://xml.sap.com/2006/11/esi/esp/binxml" xmlns:saptrnbnd="http://www.sap.com/webas/710/soap/features/transportbinding/" wsp:Optional="true" />
<saptrnbnd:OptimizedXMLTransfer uri="http://www.w3.org/2004/08/soap/features/http-optimization" xmlns:saptrnbnd="http://www.sap.com/webas/710/soap/features/transportbinding/" wsp:Optional="true" />
- <wsp:ExactlyOne xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:sapsp="http://www.sap.com/webas/630/soap/features/security/policy" xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility">
- <wsp:All>
- <sp:TransportBinding>
- <wsp:Policy>
- <sp:TransportToken>
- <wsp:Policy>
<sp:HttpsToken />
</wsp:Policy>
</sp:TransportToken>
- <sp:AlgorithmSuite>
- <wsp:Policy>
<sp:TripleDesRsa15 />
</wsp:Policy>
</sp:AlgorithmSuite>
- <sp:Layout>
- <wsp:Policy>
<sp:Strict />
</wsp:Policy>
</sp:Layout>
</wsp:Policy>
</sp:TransportBinding>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
- <wsp:Policy wsu:Id="IF_IF_ZHR_READ_EMERGENCY">
- <sapsession:Session xmlns:sapsession="http://www.sap.com/webas/630/soap/features/session/">
<sapsession:enableSession>false</sapsession:enableSession>
</sapsession:Session>
<sapcentraladmin:CentralAdministration xmlns:sapcentraladmin="http://www.sap.com/webas/700/soap/features/CentralAdministration/" wsp:Optional="true" />
</wsp:Policy>
- <wsp:Policy wsu:Id="OP_IF_OP_HrxssPerReadEmergencyAr">
<sapcomhnd:enableCommit xmlns:sapcomhnd="http://www.sap.com/NW05/soap/features/commit/">false</sapcomhnd:enableCommit>
<sapblock:enableBlocking xmlns:sapblock="http://www.sap.com/NW05/soap/features/blocking/">true</sapblock:enableBlocking>
<saptrhnw05:required xmlns:saptrhnw05="http://www.sap.com/NW05/soap/features/transaction/">no</saptrhnw05:required>
<saprmnw05:enableWSRM xmlns:saprmnw05="http://www.sap.com/NW05/soap/features/wsrm/">false</saprmnw05:enableWSRM>
</wsp:Policy>
- <wsdl:types>
- <xsd:schema attributeFormDefault="qualified" targetNamespace="urn:sap-com:document:sap:rfc:functions">
- <xsd:simpleType name="char1">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
</xsd:restriction>
</xsd:simpleType>
"More simple types
<xsd:pattern value="\d*" />
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>
- <xsd:schema attributeFormDefault="qualified" targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style" xmlns:n0="urn:sap-com:document:sap:rfc:functions">
<xsd:import namespace="urn:sap-com:document:sap:rfc:functions" />
- <xsd:complexType name="Bapiret2">
- <xsd:sequence>
"More element names
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="Messages" type="tns:Bapirettab" />
<xsd:element name="Records" type="tns:HcmtBspPaArR0006Tab" />
<xsd:element name="Records2" type="tns:HcmtBspPaArR0021Tab" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
- <wsdl:message name="HrxssPerReadEmergencyAr">
<wsdl:part name="parameters" element="tns:HrxssPerReadEmergencyAr" />
</wsdl:message>
- <wsdl:message name="HrxssPerReadEmergencyArResponse">
<wsdl:part name="parameter" element="tns:HrxssPerReadEmergencyArResponse" />
</wsdl:message>
- <wsdl:portType name="ZHR_READ_EMERGENCY">
- <wsp:Policy>
<wsp:PolicyReference URI="#IF_IF_ZHR_READ_EMERGENCY" />
</wsp:Policy>
- <wsdl:operation name="HrxssPerReadEmergencyAr">
- <wsp:Policy>
<wsp:PolicyReference URI="#OP_IF_OP_HrxssPerReadEmergencyAr" />
</wsp:Policy>
<wsdl:input message="tns:HrxssPerReadEmergencyAr" />
<wsdl:output message="tns:HrxssPerReadEmergencyArResponse" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="ZHR_READ_EMERGENCY" type="tns:ZHR_READ_EMERGENCY">
- <wsp:Policy>
<wsp:PolicyReference URI="#BN_BN_ZHR_READ_EMERGENCY" />
</wsp:Policy>
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
- <wsdl:operation name="HrxssPerReadEmergencyAr">
<soap:operation soapAction="" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="service">
- <wsdl:port name="ZHR_READ_EMERGENCY" binding="tns:ZHR_READ_EMERGENCY">
<soap:address location="http://cieh4-srvr.collabera.com:8000/sap/bc/srt/rfc/sap/zhr_read_emergency/900/zhr_read_emergency/zhr_read_emergency" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Cheers,
Remi

Not able to read the wsdl file from server Premature EOF encounter

Hi All,
I am facing issue while accessing a web Service from server. Here is the clear view about it.
I created a simple SyncBpel process in a composite and deployed in to the server and it is working fine. Later i created a new Asyn bpel process in a composite and in the external reference i dragged a web Service and imported the wsdl url from server of the SyncBpel and wired the Asynbpel process to webserive .
Now here i am facing peculiar behavior which i am not able to trace it out.
1) For the first time when i import the url of syncBpel from the server i am not facing any error and it is working fine as expected but when i close the Jdeveloper and open it i am not able to user the web Service and it is saying as "Not able to read the wsdl file from server Premature EOF encounter"
2)When i close and open the Jdeveloper i can see the url of the wsdl which imported in webserver is changing from http://stcfmw03.satyam.com:8021/soa-infra/services/Tarak/synchronousBpel/bpelsync_client_ep?WSDL to http://stcfmw03.satyam.com:8021/soa-infra/services/Tarak/synchronousBpel/BPELsync.wsdl
3)when I open and see the url http://stcfmw03.satyam.com:8021/soa-infra/services/Tarak/synchronousBpel/bpelsync_client_ep?WSDL I can see the soap address as *<soap:address location="http://stcfmw03.satyam.com:8021/soa-infra/services/Tarak/synchronousBpel!1.0*soa_5cfb8416-c106-40a2-a53b-9054bbe04b9c/bpelsync_client_ep"/>*
I don’t understand why the soap end contains “*soa_5cfb8416-c106-40a2-a53b-9054bbe04b9c” and this kind of url for soap address is coming to all the bpel process which I am deploying in the server.
I checked the in Jdeveloper where webproxy is uncheck and the server is also up but still I am facing issue of reading the error.
Can someone please help in resolving the issue.
I am using SOA 11g 11.1.1.5 and Jdeveloper 11.1.1.5
Many thanks.
Tarak
Edited by: user11896572 on Jan 17, 2012 5:22 PM

Hi,
Setting default from the jdeveloper -
During composite deployment from Jdeveloper (wizard driven), you will be given an option to choose the version of the composite and there will also be an option for you to choose if the composite needs to be deployed as default.
Setting default from the em console -
After deploying a composite, login to the em console and click on the composite that you want to set as default, and you will find a tab - "Set as Default". please note that this tab will not be seen, if the composite is already set as default.
Refer -
http://docs.oracle.com/cd/E12839_01/integration.1111/e10226/soacompapp_mang.htm
8.2 Managing the State of Deployed SOA Composite Applications
Thanks

How do I support multiple custom WSDL files in one application?

I am developing an application that will integrate with SOD. This application will be run at multiple customers - each of which could have their own set of custom fields defined for the various objects that we're interested in. Is there a web service that allows you to access custom objects and fields in a generic fashion or am I going to have to obtain each customer's custom WSDL file and write some sort of adapter for each that plugs into our main integration logic?
Based on everything I've tried and read, it seems like the latter is true.
Edited by: user3029444 on Mar 27, 2009 5:11 AM

Hi !
As I am developing many customer applications with OCOD interface, I confirm that the only way I see is to have an adapter. For example, having a folder WSDL containing one sub folder for each customer. And these sub folders will contain the customer specific wsdl.
Then you'll have to run your application in a customer context, I mean knowing who is running the application and then set your wsdl path regarding this identification.
Hoep this will help, feel free to ask more !
Max

Netbeans creating wsdl file having message with more than one part...

Hi,
I am using netbeans 6.0.1. I made an xml schema, then I wanted to make an wsdl that uses that schema.
I wanted to put in a message more parts(3), and it would not let me. Then, i made the message with just one part, and added the other parts afterwards.
But now, when I try to make a web service from that wsdl, it says that there is no service in the specified wsdl file.
And if i let that message with just one part, it will make the Web Service.
here is the xml schema and the wsdl file:
XML Schema:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://xml.netbeans.org/schema/Abruf38"
xmlns:tns="http://xml.netbeans.org/schema/Abruf38"
elementFormDefault="qualified">
<xsd:complexType name="FormRequest">
<xsd:sequence>
<xsd:element name="newRequest" type="xsd:boolean"/>
<xsd:element name="requestNumber" type="xsd:int"/>
<xsd:element name="vehicleClass" type="xsd:string"/>
<xsd:element name="vehiclesNumber" type="xsd:int"/>
<xsd:element name="prefferedType" type="xsd:string"/>
<xsd:element name="kombi" type="xsd:boolean"/>
<xsd:element name="usageMission" type="xsd:boolean"/>
<xsd:element name="usageEducation" type="xsd:boolean"/>
<xsd:element name="usageGeneral" type="xsd:boolean"/>
<xsd:element name="usageOthers" type="xsd:string"/>
<xsd:element name="eqVehicle" type="xsd:boolean"/>
<xsd:element name="eqDangerous" type="xsd:boolean"/>
<xsd:element name="eqPlaneSpriegel" type="xsd:boolean"/>
<xsd:element name="eqBegrstll" type="xsd:boolean"/>
<xsd:element name="eqMSitzBTruck" type="xsd:boolean"/>
<xsd:element name="eqVerzurrAusst" type="xsd:boolean"/>
<xsd:element name="eqOthers" type="xsd:string"/>
<xsd:element name="bringService" type="xsd:boolean"/>
<xsd:element name="holService" type="xsd:boolean"/>
<xsd:element name="chauffService" type="xsd:boolean"/>
<xsd:element name="otherService1" type="xsd:string"/>
<xsd:element name="otherService1Chk" type="xsd:boolean"/>
<xsd:element name="otherService2" type="xsd:string"/>
<xsd:element name="otherService2Chk" type="xsd:boolean"/>
<xsd:element name="otherService3" type="xsd:string"/>
<xsd:element name="otherService3Chk" type="xsd:boolean"/>
<xsd:element name="activity" type="xsd:string"/>
<xsd:element name="costPayer" type="xsd:string"/>
<xsd:element name="costCenter" type="xsd:string"/>
<xsd:element name="vehicleCost" type="xsd:float"/>
<xsd:element name="chauffServiceCost" type="xsd:float"/>
<xsd:element name="holBringServiceCost" type="xsd:float"/>
<xsd:element name="totalCost" type="xsd:float"/>
<xsd:element name="tripPurpose" type="xsd:string"/>
<xsd:element name="fixTermin" type="xsd:boolean"/>
<xsd:element name="justificationFix" type="xsd:string"/>
<xsd:element name="requestID" type="xsd:string"/>
<xsd:element name="rentalPeriod" type="tns:RentalPeriod"/>
<xsd:element name="carPool" type="tns:CarPool"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="CarPool">
<xsd:sequence>
<xsd:element name="poolID" type="xsd:string"/>
<xsd:element name="poolName" type="xsd:string"/>
<xsd:element name="orgNumber" type="xsd:string"/>
<xsd:element name="vehicle" maxOccurs="unbounded" type="tns:Vehicle"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="RentalPeriod">
<xsd:sequence>
<xsd:element name="rentalPeriodID" type="xsd:string"/>
<xsd:element name="startDate" type="xsd:date"/>
<xsd:element name="endDate" type="xsd:date"/>
<xsd:element name="startTime" type="xsd:time"/>
<xsd:element name="endTime" type="xsd:time"/>
<xsd:element name="startLocation" type="xsd:string"/>
<xsd:element name="endLocation" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Vehicle">
<xsd:sequence>
<xsd:element name="vehicleID" type="xsd:string"/>
<xsd:element name="vehicleClass" type="xsd:string"/>
<xsd:element name="vehicleRegisterNo" type="xsd:int"/>
<xsd:element name="vehicleType" type="xsd:string"/>
<xsd:element name="seatsNumber" type="xsd:int"/>
<xsd:element name="cost" type="xsd:float"/>
<xsd:element name="available" type="xsd:boolean"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Contact">
<xsd:sequence>
<xsd:element name="contactID" type="xsd:string"/>
<xsd:element name="contactName" type="xsd:string"/>
<xsd:element name="telNumber" type="xsd:int"/>
<xsd:element name="faxNumber" type="xsd:int"/>
<xsd:element name="loNo" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Person">
<xsd:sequence>
<xsd:element name="personID"/>
<xsd:element name="department" type="xsd:string"/>
<xsd:element name="serviceNumber" type="xsd:int"/>
<xsd:element name="contact" type="tns:Contact"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Department">
<xsd:sequence>
<xsd:element name="departmentID" type="xsd:string"/>
<xsd:element name="fundsDepartment" type="xsd:string"/>
<xsd:element name="mvwdst" type="xsd:int"/>
<xsd:element name="distributionNumber" type="xsd:int"/>
<xsd:element name="contact" type="tns:Contact"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="formRequestElement" type="tns:FormRequest"/>
<xsd:element name="personElement" type="tns:Person"/>
<xsd:element name="departmentElement" type="tns:Department"/>
<xsd:element name="vehicle" type="tns:Vehicle"/>
<xsd:element name="loadFormReturn" type="xsd:boolean"/>
<xsd:element name="editFormReturn" type="xsd:boolean"/>
</xsd:schema>
Wsdl File:
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="userWS" targetNamespace="http://j2ee.netbeans.org/wsdl/userWS"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns="http://xml.netbeans.org/schema/Abruf38" xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype" xmlns:tns="http://j2ee.netbeans.org/wsdl/userWS" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types>
<xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/userWS">
<xsd:import namespace="http://xml.netbeans.org/schema/Abruf38" schemaLocation="Abruf38.xsd"/>
</xsd:schema>
</types>
<message name="loadFormRequest">
<part name="formRequest" element="ns:formRequestElement"/>
<part name="person" element="ns:personElement"/>
<part name="department" element="ns:departmentElement"/>
</message>
<message name="loadFormReply">
<part name="retVal" element="ns:loadFormReturn"/>
</message>
<portType name="userWSPortType">
<operation name="loadForm">
<input name="input1" message="tns:loadFormRequest"></input>
<output name="output1" message="tns:loadFormReply"/>
</operation>
</portType>
<binding name="userWSBinding" type="tns:userWSPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="loadForm">
<soap:operation/>
<input name="input1">
<soap:body use="literal"/>
</input>
<output name="output1">
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="userWSService">
<port name="userWSPort" binding="tns:userWSBinding">
<soap:address location="http://localhost:18181/userWSService/userWSPort"/>
</port>
</service>
<plnk:partnerLinkType name="userWS1">

<plnk:role name="userWSPortTypeRole" portType="tns:userWSPortType"/>
</plnk:partnerLinkType>
</definitions>
The message that Netbeans says when trying to put more parts to the message is:
WS-I Basic Profile Rule R2210: If a document-literal binding in a DESCRIPTION does not specify the parts attribute on a soapbind:body element, the corresponding abstract wsdl:message MUST define zero or one wsdl:parts.
Please...I am desperate, cause I am pressed by time!
Can anyone tell me how can I make it work. Cause it is very common to use a Web service operation that has more than ONE parameter.
I am waiting for your replys!

Hi,
Change the <soap:binding style="document"... to <soap:binding style="rpc"... and see if that works.
I'm not sure how to get <soap:binding style="document"... working yet - I'm not that experienced in web services yet.
Hope this helps and is not too late.
Regards,
Greg Nye

How to generate a specific size txt file?

Hey guys,
I'm working with a system wich reads txt files. These files have to be 100kb of size.
Is it possible to generate specific size txt files in abap? I'm trying to do this but i cant get exactly 100kb.
Best regards

[Character Streams|http://java.sun.com/docs/books/tutorial/essential/io/charstreams.html]

?WSDL for Business Service or WSDL File

I know that you can append a ?WSDL to the end of a Proxy Service to access the WSDL File for the Service.
Is there a REST/GET way to do the same thing to access a Business Service or a WSDL or a Schema directly?
Thanks,
Jay

See if this might help.
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15867/configuringandusingservices.htm#i1143285Is
Thanks
Manoj

Web Service WSDL File Generation

hello everybody, I have an outbound interface with sender soap adapter to work as a web service, I tested it by generating the wsdl file in the integration directory, and I tested it with altova xmlspy and it works really fine, but now I have a problem another aplication needs to call the webservice, but when they try to import the wsdl file it turns out that in their system they can only import rpc files and not document style files, is there a way to generate a RPC file from an xi interface, or is there a third tool to do this conversion, or what needs to be done, has anyone found this problem before??? thanks in advance.
Regards,
Julio Cesar

Hi ,
As far as I am aware of ...
3 SOAP encoding styles are there :
SOAP Remote Procedure Call (RPC) encoding, also known as Section 5 encoding, as defined by the SOAP 1.1 specification and later defined in SOAP 1.2 as RPC encodings and conventions
SOAP Remote Procedure Call Literal encoding (SOAP RPC-literal,) uses RPC methods to make the call but uses an XML do-it-yourself method for mar-shaling the data.
SOAP document-style encoding, also known as message-style or document-literal encoding.
Kindly Check this Link out
http://msdn.microsoft.com/msdnmag/issues/03/05/XMLFiles/

How to write won WSDL file for SOAP adapter ?

Hi experts
Can any one expalin me how to write WSDL file for SOAP adapter ?
What and all things i need to know ? i have no idea on this....
I got the business but to WSDL ...i am very new to this
Adv...thanks
Rakesh

HI,
Please see the below links,
Consuming XI Web Services using Web Dynpro Part II-/people/riyaz.sayyad/blog/2006/05/08/consuming-xi-web-services-using-web-dynpro-150-part-ii
Consuming XI Web Services using Web Dynpro Part I -/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0d7349b6-0901-0010-ddbe-ec43178a61ff
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
/people/kevin.liu/blog/2006/04/12/wsdl-11-binding-extension-for-soap-12
Regards
Chilla..

Problem with Axis Adapter endpoint url in WSDL file.

Dear experts,
We are using PI 7.1 ehp1 with a SOAP to RFC scenarios using the Axis adapter.
We have the XIAxisAdapter as sender Communication Channel and the related Sender Agreement.
When i am looking into the WSDL file of the Sender Agreement than the endpoint contains ...location="host:port/ XISOAPAdapter /MessageServlet"... in stead of ...location="host:port/ XIAxisAdapter /MessageServlet"...
The url with "XISOAPAdapter " will not work. When i export the WSDL file and manually adjust the location to "XIAxisAdapter " everything works fine.
Is it possible to directly generate a correct WSDL with calling the url http://host:50000/dir/wsdl?p=xxxx?
Thanks in advance!
Best regards,
Joost Weghorst

Hi Sonya,
You can use configuration plan while deploying composite.
The configuration plan enables you to define the URL and property values to use in different environments. During process deployment, the configuration plan is used to search the SOA project for values that must be replaced to adapt the project to the next target environment.
Please refer this doc. for getting introduced to config plan.
http://docs.oracle.com/cd/E29542_01/dev.1111/e10224/sca_lifecycle.htm#SOASE10908
To deploy soa composite with config plan refer this doc:
http://docs.oracle.com/cd/E29542_01/dev.1111/e10224/sca_lifecycle.htm#SOASE85469

ICI v3.00.63007 Specification Doc/Wsdl files

Similar Messages

Maybe you are looking for