Link to WSDL

Hi,
When defining an webservice i go to the Integration Directory and calls the function Tools->Define Web Service and the i get an WSDL which i can download and send to somebody.
But is there no option for the developers to call a link where they can get the same WSDL? Just like all other tools including direct access to a WEB AS function module??
/Jakob

Hi Steen,
What is the use of creating a good Web Service and if nobody can find it !!!
You can publish your Web Service on a UDDI server where others can consume your Web Service or find its WSDL file.
Go through the link for Publishing ABAP Webservices to an external UDDI(Universal Description,Discovery and Integration)Server
/people/thomas.jung3/blog/2005/01/11/publishing-abap-webservices-to-an-external-uddi-server
Regards
Pravesh

Similar Messages

Partner Link URL/WSDL or Dynamic Partner link

We are using a service similar to CreditRatingService in orderBooking Tutorial as a partner link.
The partner has different test vs production service.
I was wondering during deplyment on production is it possible to specify the URL in config file or do I have to change the designtime location in jdev and then deploy it in prod.
Can experienced folks here point me to deployment best practices ?
Part2 : Where does dynamic partner link fit in ?

JDeveloper is using ANT and is using a properties file during the compilation. You can change the properties when you want to deploy.
http://orasoa.blogspot.com/2006/08/using-ant-in-bpel-environment.html
Dyn PL are usefully when you want to call multiple/various web services that all take the same payload, but are using different end-points and operation. This reduces the code to make for every interface an PL.

How to fix 'Unexpected error: Incorrect value: Location URL' in WSDL

Hi All,
Using SOAMANAGER transaction, I created a service ECC_CUSTOMERQUOTEERPCRTRC and its binding 'ECC_CUSTOMERQUOTEERPCRTRC_binding' using the Create Service option under the tab Configurations and using the web service definition 'ECC_CUSTOMERQUOTEERPCRTRC'. When I click on the link "Open WSDL document for selected binding" under the tab 'Overview', I get the following XML code in the popup window for the WSDL.
- <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
- <soap:Body>
- <soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>Unexpected error: Incorrect value: Location URL for subject IF {http</faultstring>
- <detail xmlns:slibfault="http://xml.sap.com/2005/11/esi/slib/fault/">
<slibfault:timestamp>Wed, 17 Nov 2010 22:29:02 GMT</slibfault:timestamp>
- <slibfault:exception>
<slibfault:text>Incorrect value: Location URL for subject IF {http://sap.com/xi/APPL/Global2}:CustomerQuoteERPCreateRequestConfirmation_In not found</slibfault:text>
<slibfault:position program="CL_SIDL_SUBJECT_ADAPTER=======CP" include="CL_SIDL_SUBJECT_ADAPTER=======CM006" line="47" />
</slibfault:exception>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>
The XML code for nthe WSDL displays an error 'Unexpected error: Incorrect value: Location URL for subject IF '. It looks like the code could find the required URL. Please let me know how to fix this error.
Thanks in advance.
--R D

Hello.
In SOAMANAGER delete your "unexpected" service (endpoint).
Then create it again.
If same error will occurs - try to delete all definitions of this service (include sicf-transaction) and then create it completely again.
Hope it helps.

WSDL without endpoint in Services Registry

Hi,
I have successfully configured an enterprise service from ECC 6.0 by following this tutorial ([Configuration of Enterprise Services using SICF and SOAMANAGER|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/20b723f8-a422-2c10-aca5-fe64eeda1ff2&overridelayout=true]). After the configuration, I published the enterprise service to the Services Registry using WSPUBLISH.
However, when I tried to consume the service in Visual Composer, I got a connection error. Later, I discovered that it was due to the binding WSDL generated in SOAMANAGER in which the endpoint port was automatically set to 443 instead of 8001 (my http port). Luckily enough, I have found an identical problem posted to SDN forum ([soamanager referencing wrong port number in wsdl document |soamanager referencing wrong port number in wsdl document;). From there I learned that an SAPNOTE 1263112 must be uploaded to my ERP. Now, this problem is solved.
Nevertheless, after I have built a VC model that consumes the service, which is now found in the Services Registry, deployed and run it, I got this error message "Error in connection: Could not execute Web service, consult your administrator". To investigate the source of the problem, I copied the URL of the WSDL generated in SOAMANAGER from the link Open WSDL document for selected binding and created a logical destination in NWA for the direct consumption in VC. This time, the VC model worked!
This lead me to think that the problem lies in the binding WSDL in Services Registry. So, I checked the SR again and found that the URL for the binding WSDL in the "Endpoint" tab is different from the one in SOAMANAGER:
1. In SR
http://myserver:8001/sap/bc/srt/wsdl/bndg_4AAD0B64E0BC0263E1008000C0A8A53D/wsdl11/binding/ws_policy/document?sap-client=800
2. In SOAMANAGER
http://myserver:8001/sap/bc/srt/wsdl/bndg_4AAD0B64E0BC0263E1008000C0A8A53D/wsdl11/allinone/ws_policy/document?sap-client=800
The binding WSDL in SR does not contain the endpoint. However, the endpoint is shown in the 2nd column "Target Address" of the endpoint table in "Endpoint" tab.
To summarize, I could not consume service that was configured in SOAMANAGER and subsequently published to SR. But, with the WSDL in SOAMANAGER, the service could be directly consumed.
Does anyone have idea about this problem?
Thanks in advance.
Regards,
Joon Meng

Hi,
Usually endpoint in SR is published as per SOAMANAGER (allinone/ws_policy/document?sap-client=800). Try to republish service again using "WSPUBLISH" with endpoint and chose "force publication" option.
You can also publish service using url directly from SR (goto "publish" tab).
Regards,
Gourav

Simple SOA application, but error in load of wsdl wont compile

Hi all,
I've come to the end of the line with this one, so I hope someone can help. I have a very simple business rules application - one function, one rule, one decision service - and the deployment descriptor (wsdl) copied at the bottom. When I try to compile the application I get:
Error: Load of wsdl "TrainDeliveryServiceCancelledNotificationRules_TrainDeliveryServiceCancelledNotificationRule_DecisionService_1.wsdl with Message part element undefined in wsdl [file:/C:/_dev/NROL3/Soa/Nrol3BusinessRulesPoc/TrainDeliveryServiceCancelledNotificationRules_TrainDeliveryServiceCancelledNotificationRule_DecisionService_1.wsdl] part name = payload type = {http://xmlns.oracle.com/TrainDeliveryServiceCancelledNotificationRules/TrainDeliveryServiceCancelledNotificationRules_TrainDeliveryServiceCancelledNotificationRule_DecisionService_1}callFunctionStateful" failed
I am sure its me being thick, but I can't see what I'm doing wrong. I have a feeling my schema def headers for my data are wrong:
<xs:schema
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.customersharepoint.co.uk:8090/trac/TS1331_NROL3/wiki/xsd"
targetNamespace="http://www.customersharepoint.co.uk:8090/trac/TS1331_NROL3/wiki/xsd" elementFormDefault="qualified">
My wsdl is as follows. Jdev is giving me a warning on my custom application imports, but I dont think thats the problem.
Please help!
<wsdl:definitions
name="TrainDeliveryServiceCancelledNotificationRules_TrainDeliveryServiceCancelledNotificationRule_DecisionService_1"
targetNamespace="http://xmlns.oracle.com/TrainDeliveryServiceCancelledNotificationRules/TrainDeliveryServiceCancelledNotificationRules_TrainDeliveryServiceCancelledNotificationRule_DecisionService_1"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://xmlns.oracle.com/TrainDeliveryServiceCancelledNotificationRules/TrainDeliveryServiceCancelledNotificationRules_TrainDeliveryServiceCancelledNotificationRule_DecisionService_1"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:java="http://schemas.xmlsoap.org/wsdl/java/"
xmlns:format="http://schemas.xmlsoap.org/wsdl/formatbinding/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:rules="http://xmlns.oracle.com/bpel/rules"
xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
>
<wsdl:types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://xmlns.oracle.com/TrainDeliveryServiceCancelledNotificationRules/TrainDeliveryServiceCancelledNotificationRules_TrainDeliveryServiceCancelledNotificationRule_DecisionService_1"
attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:tns="http://xmlns.oracle.com/TrainDeliveryServiceCancelledNotificationRules/TrainDeliveryServiceCancelledNotificationRules_TrainDeliveryServiceCancelledNotificationRule_DecisionService_1"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:bpelpm="http://xmlns.oracle.com/bpel"
xmlns:rules="http://xmlns.oracle.com/bpel/rules">
<include schemaLocation="xsd/TrainDeliveryServiceCancelledNotificationRules_TrainDeliveryServiceCancelledNotificationRule_DecisionService_1Types.xsd"/>
</schema>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://xmlns.oracle.com/bpel/rules"
attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:tns="http://xmlns.oracle.com/bpel/rules"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:bpelpm="http://xmlns.oracle.com/bpel"
xmlns:rules="http://xmlns.oracle.com/bpel/rules">
<element name="int" type="xsd:int"/>
<element name="double" type="xsd:double"/>
<element name="string" type="xsd:string"/>
<element name="boolean" type="xsd:boolean"/>
<element name="byte" type="xsd:byte"/>
<element name="short" type="xsd:short"/>
<element name="long" type="xsd:long"/>
<element name="float" type="xsd:float"/>
<element name="integer" type="xsd:integer"/>
<element name="decimal" type="xsd:decimal"/>
<element name="dateTime" type="xsd:dateTime"/>
<element name="duration" type="xsd:duration"/>
</schema>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://xmlns.oracle.com/TrainDeliveryServiceCancelledNotificationRules/TrainDeliveryServiceCancelledNotificationRules_TrainDeliveryServiceCancelledNotificationRule_DecisionService_1"
attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:tns="http://xmlns.oracle.com/TrainDeliveryServiceCancelledNotificationRules/TrainDeliveryServiceCancelledNotificationRules_TrainDeliveryServiceCancelledNotificationRule_DecisionService_1"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:bpelpm="http://xmlns.oracle.com/bpel"
xmlns:rules="http://xmlns.oracle.com/bpel/rules">
<import namespace="" schemaLocation="xsd/NotificationSpecificationMock.xsd"/>
<import namespace="" schemaLocation="xsd/Organisation.xsd"/>
<import namespace="" schemaLocation="xsd/TrainDeliveryService.xsd"/>
<import namespace="http://xmlns.oracle.com/bpel/rules"/>
<import namespace="http://xmlns.oracle.com/bpel"/>
<element name="callFunctionStateless">
<complexType>
<sequence>
<element name="configURL" type="string" minOccurs="0" maxOccurs="1"/>
<element name="bpelInstance" type="bpelpm:tBpelProcess" minOccurs="0" maxOccurs="1"/>
<element name="parameterList" minOccurs="1" maxOccurs="1">
<complexType>
<sequence>
<element ref="TrainDeliveryService"/>
<element ref="Nrol3User"/>
</sequence>
</complexType>
</element>
</sequence>
<attribute name="name" type="NCName" use="required"/>
</complexType>
</element>
<element name="callFunctionStatelessDecision">
<complexType>
<sequence>
<element name="resultList" minOccurs="1" maxOccurs="1">
<complexType>
<sequence>
<element ref="NotificationSpecification"/>
</sequence>
</complexType>
</element>
</sequence>
</complexType>
</element>
<element name="callFunctionStateful">
<complexType>
<sequence>
<element name="configURL" type="string" minOccurs="0" maxOccurs="1"/>
<element name="bpelInstance" type="bpelpm:tBpelProcess" minOccurs="0" maxOccurs="1"/>
<element name="parameterList" minOccurs="1" maxOccurs="1">
<complexType>
<sequence>
<element ref="TrainDeliveryService"/>
<element ref="Nrol3User"/>
</sequence>
</complexType>
</element>
</sequence>
<attribute name="name" type="NCName" use="required"/>
</complexType>
</element>
<element name="callFunctionStatefulDecision">
<complexType>
<sequence>
<element name="resultList" minOccurs="1" maxOccurs="1">
<complexType>
<sequence>
<element ref="NotificationSpecification"/>
</sequence>
</complexType>
</element>
</sequence>
</complexType>
</element>
</schema>
</wsdl:types>
<wsdl:message name="callFunctionStatelessMessage">
<wsdl:part name="payload" element="tns:callFunctionStateless"/>
</wsdl:message>
<wsdl:message name="callFunctionStatelessDecisionMessage">
<wsdl:part name="payload" element="tns:callFunctionStatelessDecision"/>
</wsdl:message>
<wsdl:message name="callFunctionStatefulMessage">
<wsdl:part name="payload" element="tns:callFunctionStateful"/>
</wsdl:message>
<wsdl:message name="callFunctionStatefulDecisionMessage">
<wsdl:part name="payload" element="tns:callFunctionStatefulDecision"/>
</wsdl:message>
<wsdl:message name="decisionServiceError">
<wsdl:part name="payload" element="tns:errorInfo"/>
</wsdl:message>
<wsdl:portType name="IDecisionService">
<wsdl:operation name="callFunctionStateless">
<wsdl:input name="callFunctionStatelessInput" message="tns:callFunctionStatelessMessage"/>
<wsdl:output name="callFunctionStatelessOutput" message="tns:callFunctionStatelessDecisionMessage"/>
<wsdl:fault name="operationErroredFault" message="tns:decisionServiceError"/>
</wsdl:operation>
<wsdl:operation name="callFunctionStateful">
<wsdl:input name="callFunctionStatefulInput" message="tns:callFunctionStatefulMessage"/>
<wsdl:output name="callFunctionStatefulOutput" message="tns:callFunctionStatefulDecisionMessage"/>
<wsdl:fault name="operationErroredFault" message="tns:decisionServiceError"/>
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>

Well, after burning a half a day on this I've discovered that deleting and recreating the decision service makes the problem go away. This is not the first time that inexplicable problems in JDeveloper 11 have gone away after 'turning it off and on again'.
Anyone have any ideas?
Rory

Faulty WSDL Generated by SOAMANAGER

Hi,
I have created a service for the service definition "ECC_SALESORDER009QR" in SOAMANAGER. After that, I tried to open the generated WSDL from the link "Open WSDL document for selected binding". Unfortunately, it contains only the following data:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
   <soap:Fault>
       <faultcode>soap:Server</faultcode>
       <faultstring>Unexpected error: Incorrect value: Location URL for subject IF
{http</faultstring>
       <detail xmlns:slibfault="http://xml.sap.com/2005/11/esi/slib/fault/">
        <slibfault:timestamp>Mon, 14 Sep 2009 22:42:38 GMT</slibfault:timestamp>
        <slibfault:exception>
           <slibfault:text>Incorrect value: Location URL for subject IF
{http://sap.com/xi/APPL /Global2}:
SalesOrderERPBasicDataByElementsQueryResponse_In not found</slibfault:text>
<slibfault:position program="CL_SIDL_SUBJECT_ADAPTER=======CP"
include="CL_SIDL_SUBJECT_ADAPTER=======CM006" line="47" />
      </slibfault:exception>
     </detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>
To further investigate the problem, I created few additional services for the other service definitions and discovered that only those with the namespace "http://sap.com/xi/APPL/Global2" have the same problem, while the others with the namespace "http://sap.com/xi/APPL/SE/Global" are free of the faulty WSDL.
Could anyone shed some light into this matter?
Regards,
Joon Meng

Goto t-code WSCONFIG, search for the service in field service definition, then add a variant name ( same name as service ) and save. Goto wsadmin , there just browse for the service and click on button "WSDL file" to extract and open wsdl file in ypour webbrowser. This file can then be implemented into your portal environment or soapui as I use to test them with before development starts on portal.

Difference betwee "Binding" and "Partner Link"

Hi Forum - Could you please explain the difference between Binding and Partner Link and when to use which one?
Thanks!

Thanks for the explanations. Can I create a service with just the SOAP binding without usnig BPEL partner links in Oracle BPEL?
I have tried this however BPEL is adding a reference to my WSDL and then creating a partner link by itself in the reference binding. How can I stop it from doing that?
The reason I want to do that is becasue I have a BPEL project which has two processes, which I expose as web sevices by creating the WSDL file manually (not using auto wizard).
I have deployed this project on weblogic soa domain but its giving me two endpoints for it and two links to wsdl file, one for each process. Is this normal?
Thanks!

RunTimeFault.wsdl -FaultVariable: not initialized

I created a copy of RunTimeFault.wsdl locally in JDev/mywork/myApplication/BPELProject/RunTimeFault.wsdl
I added import between Partner Link and wsdl types in BPELProcess wsdl:
<wsdl:import namespace="http://schemas.oracle.com/bpel/extension" location="RuntimeFault.wsdl"/>
I created a FaultVariable in my BPEL.
But I get warning FaultVariable: not initialized in Assign Activity when I use remoteFault in catch block.
what is the common location (soa server),if I have to place RunTimeFault.wsdl ,so that I can import in any BPEL process.
RunTimeFault.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="RuntimeFault"
targetNamespace="http://schemas.oracle.com/bpel/extension"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<message name="RuntimeFaultMessage">
<part name="code" type="xsd:string"/>
<part name="summary" type="xsd:string"/>
<part name="detail" type="xsd:string"/>
</message>
</definitions>
Also, can anyone please tell me the location (soa server) where I should put faultpolicies.xml and faultbindings.xml
I am using SOA 11G .
Thanks

If you use the following statement to import the runtimefault.wsdl, you dont have to copy your RunTimeFault.wsdl any where
<wsdl:import namespace="http://schemas.oracle.com/bpel/extension" location="oramds:/soa/shared/bpel/RuntimeFault.wsdl"/>
faultpolicy.xml, fault-bindings.xml can be placed in the same folder as the composite.xml. I this case this policy would apply to the composite in the same directory.
If you want to palce them in different locaiton, you need to set two properties in composite.xml
oracle.composite.faultPolicyFile
oracle.composite.faultBindingFile
Thanks
--Sreeny

Wat is WSDL File?

Wat is WSDL File?wat is the purpose of it?Can anyone brief abt it?
Rgds
Ruchitha.

Hi,
Hope now u have enough link for WSDL:) See the below link which tell u how it works in XI..how to consume and expose Web Service in XI>
hi !
Go thru this Blog Invoke Webservices using SAPXI By Siva Maranani
idoc to web services scenario
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
How to use webservices in XI
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit - refer that blog and use the SOAP adapter and the WS instead of the RFC part.
see this blog from Robert Chu, but it might give you a good start to creating web services:
/people/sap.user72/blog/2005/12/29/service-enable-your-sap-application-component
File to Webservices
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a
Yes please look at following weblogs
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
How to Develop a Webservice Using NWDS and SAP XI.30
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5f3ee9d7-0901-0010-1096-f5b548ac1555
How to Set Up a Web Service-Related Scenario with SAP XI
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/befdeb90-0201-0010-059b-f222711d10c0
Exposing BAPI as Web Services through SAP XI
/people/community.user/blog/2006/10/24/exposing-bapi-as-web-services-through-sap-xi
Testing XI exposed Web-Services
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
How XML Encryption can be done using web services security in SAP NetWeaver XI
/people/aparna.chaganti2/blog/2007/01/23/how-xml-encryption-can-be-done-using-web-services-security-in-sap-netweaver-xi
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
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 UI Design (Part III)
Thanks!!!
Rewards points if u find it useful:-)

Jdev11.1.1.6.0-Error while translating message to native format-FileWrite

Im reading a file from a service and transforming the data and writing them into a file through the external reference using a Mediator component.
I have no problem while building or deploying.
But while executing I get an error as follows:
Non Recoverable System Fault :
Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'WriteAppointmentRequestInLogFile' failed due to: Translation Error. Translation Error. Error while translating message to native format. Please make sure that the payload for the outbound interaction conforms to the schema. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
My input is a File Adpater Read operation and output is File Adapter Write operation.
The schemas are as below:
Input schema:
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
xmlns:tns="http://stmatthews.hospital.com/ReadFileDoctorsAppointmentRequest"
targetNamespace="http://stmatthews.hospital.com/ReadFileDoctorsAppointmentRequest"
elementFormDefault="qualified"
attributeFormDefault="unqualified"
nxsd:version="NXSD"
nxsd:stream="chars"
nxsd:encoding="US-ASCII"
<xsd:element name="doctorAppointmentRequestRoot"><xsd:complexType>
<xsd:sequence>
<xsd:element name="doctorAppointmentRequest" minOccurs="1" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="C1" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C2" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C3" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C4" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C5" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C6" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C7" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C8" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C9" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C10" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C11" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C12" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C13" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C14" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C15" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="${eol}" nxsd:quotedBy=""" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
Output Schema:
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
xmlns:tns="http://stmatthews.hospital.com/LogDoctorAppointmentRequests"
targetNamespace="http://stmatthews.hospital.com/LogDoctorAppointmentRequests"
elementFormDefault="qualified"
attributeFormDefault="unqualified"
nxsd:version="NXSD"
nxsd:stream="chars"
nxsd:encoding="US-ASCII"
<xsd:element name="AppointmentRequestsLog"><xsd:complexType>
<xsd:sequence>
<xsd:element name="AppointmentRequest" minOccurs="1" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="C1" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C2" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C3" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C4" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C5" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C6" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C7" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C8" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="C9" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="${eol}" nxsd:quotedBy=""" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>


Transformation XSL used in Mediator:
<?xml version="1.0" encoding="UTF-8" ?>
<xsl:stylesheet version="1.0"
xmlns:tns="http://xmlns.oracle.com/pcbpel/adapter/file/DoctorsAppointmentRequestProcessor/DoctorAppointmentRequestProcessor/ReadFileDoctorsAppointmentRequest"
xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:bpel="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:pc="http://xmlns.oracle.com/pcbpel/"
xmlns:bpm="http://xmlns.oracle.com/bpmn20/extensions"
xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:socket="http://www.oracle.com/XSL/Transform/java/oracle.tip.adapter.socket.ProtocolTranslator"
xmlns:mhdr="http://www.oracle.com/XSL/Transform/java/oracle.tip.mediator.service.common.functions.MediatorExtnFunction"
xmlns:oraext="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc"
xmlns:imp1="http://stmatthews.hospital.com/ReadFileDoctorsAppointmentRequest"
xmlns:dvm="http://www.oracle.com/XSL/Transform/java/oracle.tip.dvm.LookupValue"
xmlns:hwf="http://xmlns.oracle.com/bpel/workflow/xpath"
xmlns:med="http://schemas.oracle.com/mediator/xpath"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:jca="http://xmlns.oracle.com/pcbpel/wsdl/jca/"
xmlns:ns1="http://stmatthews.hospital.com/LogDoctorAppointmentRequests"
xmlns:ids="http://xmlns.oracle.com/bpel/services/IdentityService/xpath"
xmlns:xdk="http://schemas.oracle.com/bpel/extension/xpath/function/xdk"
xmlns:xref="http://www.oracle.com/XSL/Transform/java/oracle.tip.xref.xpath.XRefXPathFunctions"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:bpmn="http://schemas.oracle.com/bpm/xpath"
xmlns:ns0="http://xmlns.oracle.com/pcbpel/adapter/file/DoctorsAppointmentRequestProcessor/DoctorAppointmentRequestProcessor/LogDoctorAppointmentRequests"
xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap"
exclude-result-prefixes="xsi xsl tns pc plt wsdl imp1 jca xsd ns1 ns0 xp20 bpws bpel bpm ora socket mhdr oraext dvm hwf med ids xdk xref bpmn ldap">
<xsl:template match="/">
<ns1:AppointmentRequestsLog>
<ns1:AppointmentRequest>
<ns1:C1>
<xsl:value-of select="xp20:current-date()"/>
</ns1:C1>
<ns1:C2>
<xsl:value-of select='substring-before("doctor1234_20120926_helloworld","_")'/>
</ns1:C2>
<ns1:C4>
<xsl:value-of select="concat(/imp1:doctorAppointmentRequestRoot/imp1:doctorAppointmentRequest/imp1:C2,/imp1:doctorAppointmentRequestRoot/imp1:doctorAppointmentRequest/imp1:C3)"/>
</ns1:C4>
<ns1:C5>
<xsl:value-of select="/imp1:doctorAppointmentRequestRoot/imp1:doctorAppointmentRequest/imp1:C4"/>
</ns1:C5>
<ns1:C6>
<xsl:value-of select="/imp1:doctorAppointmentRequestRoot/imp1:doctorAppointmentRequest/imp1:C5"/>
</ns1:C6>
<ns1:C7>
<xsl:value-of select="/imp1:doctorAppointmentRequestRoot/imp1:doctorAppointmentRequest/imp1:C12"/>
</ns1:C7>
<ns1:C8>
<xsl:value-of select="/imp1:doctorAppointmentRequestRoot/imp1:doctorAppointmentRequest/imp1:C14"/>
</ns1:C8>
<ns1:C9>
<xsl:value-of select="/imp1:doctorAppointmentRequestRoot/imp1:doctorAppointmentRequest/imp1:C15"/>
</ns1:C9>
</ns1:AppointmentRequest>
</ns1:AppointmentRequestsLog>
</xsl:template>
</xsl:stylesheet>
Just in case if you are aware, Im trying the example in Lucas Jellema's book Chapter 7 and Im getting the error there in the first example project.
I have seen few very old threads on this problem in the forum but none of them had any answers so opening up a new one.
Thanks.

Your transformation with for-each look is incorrect.
This is what you have right now:
<ns1:AppointmentRequestsLog>
<xsl:for-each select="/imp1:doctorAppointmentRequestRoot/imp1:doctorAppointmentRequest">
<ns1:AppointmentRequest>
<ns1:C1>
<xsl:value-of select="xp20:current-date()"/>
</ns1:C1>
<ns1:C2>
<xsl:value-of select='substring-before("doctor1234_20120926_helloworld","_")'/>
</ns1:C2>
<ns1:C3>
<xsl:value-of select="/imp1:doctorAppointmentRequestRoot/imp1:doctorAppointmentRequest/imp1:C2"/>
</ns1:C3>This is the correct way to write for-each within XSLT:
<ns1:AppointmentRequestsLog>
<xsl:for-each select="/imp1:doctorAppointmentRequestRoot/imp1:doctorAppointmentRequest">
<ns1:AppointmentRequest>
<ns1:C1>
<xsl:value-of select="xp20:current-date()"/>
</ns1:C1>
<ns1:C2>
<xsl:value-of select='substring-before("doctor1234_20120926_helloworld","_")'/>
</ns1:C2>
<ns1:C3>
<xsl:value-of select="imp1:C2"/>
</ns1:C3>Also, check the flow trace in the EM console for the instance which errored out and paste here the data which is being sent to the FileWrite Adapter. Also, you need to ensure that any elements which are defined as xs:int should not have empty string as values. For example in your write schema C3 has int. So you should map C3 in XSLT like following:
<xsl:choose>
<xsl:when test="imp1:C2 and string-length(imp1:C2) > 0">
<ns1:C3>
<xsl:value-of select="imp1:C2"/>
</ns1:C3>
</xsl:when>
<xsl:otherwise>
<ns1:C3>0</ns1:C3>
</xsl:otherwise>
</xsl:choose>

Reg: Runtime exception occurred during application mapping

Dear SAP Gurus,
This is Amar Srinivas Eli working currently on SOAP to SOAP Scenario on PI 7.1 Server.
I Would like to inform you that I have done all steps regarding DESIGN and CONFIG and also regarding SERVICE REGISTRY part successfully.
While Testing the data in the WS Navigator by giving the input parameters I am getting an error that
*<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
*- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_HRS_LISTReferral_Response_MM_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns1:PI_ListRefer</SAP:P3>
<SAP:P4>ral_Response_MT. Values missing in queue context.~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_HRS_LISTReferral_Response_MM_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns1:PI_ListReferral_Response_MT. Values missing in queue context.~</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
These are the steps I did while implementing..
1. Importing the XSD's successfully
2. Developed the design and config part and also checked nearly 3-4 times regarding both REQ and
    RESPONSE Mappings.
3. I already checked the link of WSDL once again...
4. Even I found REsponse Interface once again...
Still I am not getting where the error was ? Please guide me in detail in a right way in this issue.
Regards:
Amar Srinivas Eli
Edited by: Amar Srinivas Eli on Jan 13, 2009 7:53 AM

Hello,
I already checked all those queues and context fields////
Based on my Observation I found
1) As I am unable to view the SOAP BODY I increased the RUN TIME Trace Level to 3 and LOG_VAlue to 3
2) ANother most Important that I found later doing these settings are....
    I found Receiver Pay LOAD and I copied that entire pay load and pasted it in
    REceiver Message Mapping> Test Tab and Code->PASTED...and compared all those parameters
    in the TEST TAB and DEFINITION TAB in Tree View whether all the mandatory receiver mapped
    elements are coming I mean passing from source or not...
OBSERVATION::
I found that for nearly 3 fields there is a difference when I compared on Tree View in DEFINITION TAB and also parallely in the TEST TAB Tree View which I got by copied from MONI,,,,
see for example ::
CENTRE <----
> DISCHARGE DATE..
For going to CENTRE..here I found that in DEfiniition TAB...
Control Act Event-->Subject->document-->Component>Structured body> component> Section>Component>PatientCareProvisionEvent->EffectiveTime-->CENTRE
But immediately I have gone to TEST TAB and TREE VIEW and I found that respective field CENTRE is posting I mean passing any value or parameter to Discharged Date or not...
But I found that...
Control Act Event-->Subject->document-->Component>Structured body> component> Section>Component-->_PatientCareProvisionEvent_
This Implies that Effective Time and Centre are missing in the XML and I mean no values are passing to receiver right..
In PI XSD 's it is there but in I think after Compiling REQUEST MAPPING and while in returning to RESPONSE MAPPING I mean whenever the Response is posting to SOAP WEBSERVICE it is unable to found those target elements and I think due to this...
Am I Correct ?
If that is the case...Let me know where the issue is whether in the data present in the WEBSERVICE created on target side or in PI Side..any issue...
Regards:
Amar Srinivas Eli
Edited by: Amar Srinivas Eli on Jan 13, 2009 10:00 AM

Dynamic file naming with File/FTP adapter

Hi all,
I have a requirement for writing files with names of the files based on a customer ID.... a dynamic name based on a value retrieved from the customer DB.
I have already tried using the dynamic file naming suggestion in the bpel dev guide, it does not work. I followed the instructions, the process fails to compile and throws "part" and "undefined variables" errors etc.
Has anyone succesfully used file/ftp adapter to write files with dynamic file names (using a varibale), not %SEQ% or %datetime% formats?
Thanks,
Hasan

You can create a header variable that will allow you to set the outbound file name inside the process. This variable is a message type. From the type chooser select:
Message Types
Partner Links
Outbound Partner Link
Outbound wsdl
Message Types
Imported WSDL
fileAdapterOutboundHeader.wsdl
OutboundHeader_msg
This variable will have a part filename.
Set this part to whatever you wish your file to be named.
Select the invoke to your outbound file/ftp partnerlink. Move to the adapters tab and select the header variable you created as the Input Header Variable.

Get File name using File Adapter

Does anyone know how to get the file name that has been picked up so it can be past to a variable so it can be used in the BPEL process.
cheers
James

Hi James,
Here the STEPS,
Create File Adapter.
Add File Adapter Service to Receive Activity.
Click Receive Activity and goto Adapters Tab.
Click "Tourch" to get variable names.
Select Variable -> Process -> Variables and Click on "Create New Variable" icon and give name.
Select "Message Type" and click "Tourch" icon.
Now you select "Partner Links" -> FileAdapter WSDL -> Imported WSDL -> Message Type -> InboundHeader_msg and select OK.
It's done.
now you can use this Global Variable to get Filename and Directory name.
Regards,
Bhavesh Thaker.

END point URL for ESB Routing service says NOT FOUND

Hi All,
For the routing services in ESB, The link of WSDL is opening up fine, but the link of endpoint URI for the routing service is failing with the message below message. When i invoke the WSDL using SOAP UI, i get back the the same error message. I tried bouncing the server , but of no help. I also notice that slide directory ESB_Projects gives 404 error on any browser.
So when i click below url for any of the routing service
http://<hostname>:<port>/event/<systemName>/<serviceGroupName>/AddressStandardizeRS
I get below error in browser-
Not Found
The requested URL /event/<System Name>/<Service Group Name>/<Routing Service Name> was not found on this server.
Oracle-Application-Server-10g/10.1.3.1.0 Oracle-HTTP-Server Server at odevsoa.local1.wbcgp.com Port 7777

Check if the port of ESB in your server is open.
I think that the port is: 7777
try from ESB server:
wget WSDLURI
if you got the file then the port is closed.

Target url for receiver soap adapter

Hi everybody
where will I get the target url to enter in the receiver soap adapter parameters? I got the link from wsdl under "address location"..But when I open the link from the internet explorer I could see an empty wsdl
<faultstring xml:lang="en">SRT: Wrong Content-Type and empty HTTP-Body received</faultstring>
thanks
Ramya

Hi Ramya,
When you try opening the URL using web browser, you are not sending any data and hence in response you get an empty message.
But at the same time, the message shows you that the service corresponding to that URL is invoked, activated and running.
Give the same URL in your receiver communication channel and try execcuting the scenario, as far as receiver URL is concerned, it should work.
-Tanaya.

Link to WSDL

Similar Messages

Maybe you are looking for