Reg: WSDL

HI all,
I have created a WSDL for a RFC function mudule. I am new to the WSDL could you please clarify my questions.
1. What is WSDL number ?
2. How to get WSDL number ?
2. How to test WSDL assigned to BAPI ( Can we test it from R3 ) ?
Please help me...
Thanks,
Nagaraju

Most of this information is in the help files. I'm going to assume that you have NW7.0 SP14 or higher...
1. What is WSDL number ?
I don't know what you mean by 'number'. Look up the definition for WSDL in Google or Wikipedia, but in simple terms, a WSDL document is a document that specifies the definition of your web service in a universal format so that others may use it.
2. How to get WSDL number ?
You get the url for a WSDL document from SOAMANAGER for the endpoint binding definition for your web service. There is a link in there that allows you to open the document and capture the url. The url is used for creating a project and testing from SOAPUI (as Jon suggested) or is given to your external app team for development purposes.
2. How to test WSDL assigned to BAPI ( Can we test it from R3 )
You don't test a WSDL, you test a web service method. You can test from SOAPUI or from the Web Service Navigator in SOAMANAGER (Java stack required).

Similar Messages

Reg:WSDL publish

Hi All,
My scenario is Soap-RFC(Syn) .I have published the WSDL in service registry and need to use the same in CE7.2 system.
Could anyone explain me the steps to publish the wsdl from PI(7.1) to CE7.2 .
Thanks in Advance
Regards,
Lavanya

Hi Lavanya,
CHeck this blog this might be usefull for you...
/people/bv.pillai/blog/2007/09/18/configuring-publishing-enterprise-services-from-sap-business-suite-system-into-nwce-netweaver-composition-environment-services-registry
Regards,
Naveen

Reg WSDL URL

Hi All,
Currently i am using a sample wsdl file which i am using in soap receiver adapter :as target url:
but my pi server is in citrix ,will the path http://webservice.aspsms.com/aspsms.asmx from citrix
will it be accessible ,because i am not able to see any messages in the message monitoring area for the particular soap receiver.

Hi ,
What is receiver SOAP communication channel status in channel monitoring ?
Thanks
Hari.

ProviderException No service defined in the WSDL

I use WebLogic 10.3.4 with JDeveloper 11g Release 1 and the current Oracle SOA Suite 11g.
I can deploy a simple composite with a BPEL service. However, If I use my complex BPEL composite, I always get the following stack trace on deployment (it validates perfectly within the editor):
<02.02.2011 10:38 Uhr MEZ> <Error> <oracle.integration.platform.blocks.deploy.se
rvlet> <SOA-21537> <Fehlermeldung wird zur³ckgesendet: Fehler beim Deployment vo
n Composite auf AdminServer: Deployment Failed: Service kann nicht registriert w
erden...>
INFO: SSLSocketFactoryManagerImpl.getKeystoreLocation Expected SOA Keystore loca
tion: C:/dev/server/Ora11g/USER_P~1/domains/BASE_D~1/config/fmwconfig/default-ke
ystore.jks
INFO: SSLSocketFactoryManagerImpl.getSSLSocketFactory Cannot locate the default
or configured keystore at C:/dev/server/Ora11g/USER_P~1/domains/BASE_D~1/config/
fmwconfig/default-keystore.jks. However, the keystore and related parameters are
used for composite-related SSL communications and not required if SSL communica
tion is not used.
<02.02.2011 10:39 Uhr MEZ> <Error> <oracle.integration.platform> <SOA-20003> <Se
rvice kann nicht registriert werden.
oracle.webservices.provider.ProviderException: oracle.webservices.provider.Provi
derException: No service {http://lspi.wiai.uniba.de/prototype/wsdl/collaboration
/SimpleUseCase/role-1/transaction/bta-1-bt-example/master/client/1-0}ToMonitorin
g defined in the WSDL
at oracle.j2ee.ws.server.provider.ProviderConfigImpl.addService(Provider
ConfigImpl.java:455)
at oracle.j2ee.ws.server.provider.ProviderConfigImpl.addService(Provider
ConfigImpl.java:285)
at oracle.integration.platform.blocks.soap.FabricProviderConfig.addServi
ce(FabricProviderConfig.java:115)
at oracle.integration.platform.blocks.soap.FabricProviderConfig.addServi
ce(FabricProviderConfig.java:204)
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingCompone
nt.load(WebServiceEntryBindingComponent.java:171)
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingCompone
nt.load(WebServiceEntryBindingComponent.java:98)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnecti
on.deployServices(CompositeDeploymentConnection.java:160)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnecti
on.deploy(CompositeDeploymentConnection.java:91)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerI
mpl.initDeployment(CompositeDeploymentManagerImpl.java:149)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerI
mpl.load(CompositeDeploymentManagerImpl.java:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflecti
on(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJo
inpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:149)
at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.in
voke(DeploymentEventPublisher.java:69)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
cAopProxy.java:204)
at $Proxy307.load(Unknown Source)
at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeployme
ntCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoo
rdinatorImpl.java:33)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor
.deployNewComposite(BaseDeployProcessor.java:367)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor
.deploySARs(BaseDeployProcessor.java:219)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doD
eployWork(DeployProcessor.java:160)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doD
eployWork(DeployProcessor.java:109)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doD
eploy(DeployProcessor.java:96)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.pro
cess(DeployProcessor.java:78)
at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerSe
rvlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:191)
at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerSe
rvlet.doPost(CompositeDeployerServlet.java:114)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run
(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecuri
tyHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
a:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:31
3)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUt
il.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.jav
a:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:1
61)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:31
3)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUt
il.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.jav
a:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:1
61)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:13
6)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppS
ervletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletC
ontext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.j
ava:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused By: oracle.webservices.provider.ProviderException: No service {http://lsp
i.wiai.uniba.de/prototype/wsdl/collaboration/SimpleUseCase/role-1/transaction/bt
a-1-bt-example/master/client/1-0}ToMonitoring defined in the WSDL
at oracle.j2ee.ws.server.provider.ProviderConfigImpl.getServiceName(Prov
iderConfigImpl.java:624)
at oracle.j2ee.ws.server.provider.ProviderConfigImpl.addService(Provider
ConfigImpl.java:346)
at oracle.j2ee.ws.server.provider.ProviderConfigImpl.addService(Provider
ConfigImpl.java:285)
at oracle.integration.platform.blocks.soap.FabricProviderConfig.addServi
ce(FabricProviderConfig.java:115)
at oracle.integration.platform.blocks.soap.FabricProviderConfig.addServi
ce(FabricProviderConfig.java:204)
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingCompone
nt.load(WebServiceEntryBindingComponent.java:171)
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingCompone
nt.load(WebServiceEntryBindingComponent.java:98)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnecti
on.deployServices(CompositeDeploymentConnection.java:160)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnecti
on.deploy(CompositeDeploymentConnection.java:91)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerI
mpl.initDeployment(CompositeDeploymentManagerImpl.java:149)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerI
mpl.load(CompositeDeploymentManagerImpl.java:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflecti
on(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJo
inpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:149)
at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.in
voke(DeploymentEventPublisher.java:69)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
cAopProxy.java:204)
at $Proxy307.load(Unknown Source)
at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeployme
ntCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoo
rdinatorImpl.java:33)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor
.deployNewComposite(BaseDeployProcessor.java:367)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor
.deploySARs(BaseDeployProcessor.java:219)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doD
eployWork(DeployProcessor.java:160)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doD
eployWork(DeployProcessor.java:109)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doD
eploy(DeployProcessor.java:96)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.pro
cess(DeployProcessor.java:78)
at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerSe
rvlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:191)
at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerSe
rvlet.doPost(CompositeDeployerServlet.java:114)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run
(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecuri
tyHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
a:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:31
3)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUt
il.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.jav
a:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:1
61)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:31
3)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUt
il.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.jav
a:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:1
61)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:13
6)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppS
ervletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletC
ontext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.j
ava:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
>
<02.02.2011 10:39 Uhr MEZ> <Error> <ServletContext-/soa-infra> <BEA-000000> <Err
or during deployment
oracle.fabric.common.FabricException: Deployment Failed: Service kann nicht regi
striert werden.
at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeployme
ntCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoo
rdinatorImpl.java:38)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor
.deployNewComposite(BaseDeployProcessor.java:367)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor
.deploySARs(BaseDeployProcessor.java:219)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doD
eployWork(DeployProcessor.java:160)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doD
eployWork(DeployProcessor.java:109)
Truncated. see log file for complete stacktrace
Caused By: oracle.fabric.common.FabricDeploymentException: Service kann nicht re
gistriert werden. {rootCauses=[]}
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingCompone
nt.load(WebServiceEntryBindingComponent.java:227)
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingCompone
nt.load(WebServiceEntryBindingComponent.java:98)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnecti
on.deployServices(CompositeDeploymentConnection.java:160)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnecti
on.deploy(CompositeDeploymentConnection.java:91)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerI
mpl.initDeployment(CompositeDeploymentManagerImpl.java:149)
Truncated. see log file for complete stacktrace
>
<02.02.2011 10:39 Uhr MEZ> <Error> <oracle.integration.platform.blocks.deploy.se
rvlet> <SOA-21537> <Fehlermeldung wird zur³ckgesendet: Fehler beim Deployment vo
n Composite auf AdminServer: Deployment Failed: Service kann nicht registriert w
erden...>
h1. Essentials parts of the Component.xml
<reference name="SimpleUseCaserole1bta1btexampleMonitoring" ui:wsdlLocation="wsdl/SimpleUseCaserole1bta1btexampleMonitoring.wsdl">
<interface.wsdl interface="http://lspi.wiai.uniba.de/prototype/wsdl/collaboration/SimpleUseCase/role-1/transaction/bta-1-bt-example/monitoring/1-0#wsdl.interface(SimpleUseCaserole1bta1btexampleMonitoringPortType)" />
<binding.ws port="http://lspi.wiai.uniba.de/prototype/wsdl/collaboration/SimpleUseCase/role-1/transaction/bta-1-bt-example/monitoring/1-0#wsdl.endpoint(SimpleUseCaserole1bta1btexampleMonitoringService/SimpleUseCaserole1bta1btexampleMonitoringPort)" soapVersion="1.1"/>
</reference>
h1. Essential parts of the componentType
          <reference name="ToMonitoring" ui:wsdlLocation="wsdl/SimpleUseCaserole1bta1btexampleMonitoring.wsdl">
               <interface.wsdl interface="http://lspi.wiai.uniba.de/prototype/wsdl/collaboration/SimpleUseCase/role-1/transaction/bta-1-bt-example/monitoring/1-0#wsdl.interface(SimpleUseCaserole1bta1btexampleMonitoringPortType)"/>
          </reference>
h1. the WSDL file
<?xml version="1.0" encoding="UTF-8"?>
<definitions
     xmlns="http://schemas.xmlsoap.org/wsdl/"
     name="SimpleUseCaserole1bta1btexampleMonitoringService"
     xmlns:tns="http://lspi.wiai.uniba.de/prototype/wsdl/collaboration/SimpleUseCase/role-1/transaction/bta-1-bt-example/monitoring/1-0"
     targetNamespace="http://lspi.wiai.uniba.de/prototype/wsdl/collaboration/SimpleUseCase/role-1/transaction/bta-1-bt-example/monitoring/1-0"
     xmlns:event="http://lspi.wiai.uniba.de/prototype/xsd/event/1-0"
     xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
     xmlns:vprop="http://docs.oasis-open.org/wsbpel/2.0/varprop"
     xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype"
     xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
     xmlns:xsd="http://www.w3.org/2001/XMLSchema"
     xmlns:header="http://lspi.wiai.uniba.de/prototype/xsd/header/1-0"
     >
<types>
<xsd:schema targetNamespace="http://lspi.wiai.uniba.de/prototype/wsdl/collaboration/SimpleUseCase/role-1/transaction/bta-1-bt-example/monitoring/1-0">
               <xsd:import namespace="http://lspi.wiai.uniba.de/prototype/xsd/event/1-0" schemaLocation="xsd/Event.xsd"/>
</xsd:schema>
</types>
<message name="EventMessage">
<part name="EventPart" element="event:Event"/>
</message>
<portType name="SimpleUseCaserole1bta1btexampleMonitoringPortType">
<operation name="EventOperation">
<input name="input1" message="tns:EventMessage"/>
</operation>
</portType>
<binding name="SimpleUseCaserole1bta1btexampleMonitoringBinding" type="tns:SimpleUseCaserole1bta1btexampleMonitoringPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="EventOperation">
<soap:operation/>
<input name="input1">
<soap:body use="literal"/>
</input>
</operation>
</binding>
<service name="SimpleUseCaserole1bta1btexampleMonitoringService">
<port name="SimpleUseCaserole1bta1btexampleMonitoringPort" binding="tns:SimpleUseCaserole1bta1btexampleMonitoringBinding">
<soap:address location="http://localhost:8091/ode/processes/SimpleUseCaserole1bta1btexampleMonitoringService"/>
</port>
</service>
     <plnk:partnerLinkType name="SimpleUseCaserole1bta1btexampleMonitoring">
     <plnk:role name="SimpleUseCaserole1bta1btexampleMonitoringPortTypeRole" portType="tns:SimpleUseCaserole1bta1btexampleMonitoringPortType"/>
     </plnk:partnerLinkType>
</definitions>
Edited by: user2595377 on 02.02.2011 01:46

there is a text table defined for FAGL_SEGM. Start SE11, display the table and menu: GoTo => text table

Not able to display WSDL

Dear All,
In PI 7.1 while dispalying WSDL we are getting the following error:
<err>
Object Service Interface BAPI_CUSTOMER_GETDETAIL2 | urn:sap-com:document:sap:rfc:functions not found in Enterprise Services Repository
</err>
I have checked the object in ESR and it is available and active in SWCV but it is still giving this error.
Please let me know the steps to remove this erro.
Warm Regards,
NJ

hi,
BAPI is available and active in IR but in ID i am not able to generate its WSDL. I am not able to generate WSDL for an of the object available in IR.
reg,
nj

How to delete the WSDL folder in DS (t-code : WSADMIN)?

Hi,
Can anyone advise how to delete the WSDL files and folder in DS client 200, t-code : WSADMIN?
We mainly use this Discovery system for our users to practice and now seem there are a lot WSDL files and folders which are not used anymore, then we like to delete some unused folders.
Please kindly advise.
Thanks you very much.
Urisa

Please use tCode WSCONFIG and delete the variants that you do not want.

Javax.xml.rpc.soap.SOAPFaultException: "Server Error" while calling a WSDL

Hi
I am using a WSDL in my java code by creating proxy.
I am getting an exception on below line of code
XX_RESPONSE res = port.XX_XX_Forecast(req);
exception :
javax.xml.rpc.soap.SOAPFaultException: "Server Error"
hat could be the possibility.
is it from XI side or Java side.
Shall I catch a XI person on my floor to solve this !!
To be more specific :
Error is
<detail xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>ADAPTER.JAVA_EXCEPTION</code>
<text>com.sap.aii.af.service.cpa.CPAException: invalid channel (party:service:channel) = <null>
at com.sap.aii.af.mp.soap.web.MessageServlet.getChannel(MessageServlet.java:499)
at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:409)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</text>
</s:SystemError>
</detail>
Thanks

Hi...
WSDL forwarded by my manager was wong
I tested it and it threw same exception.
nyways...1 more help..
Now, is there any way in NWDS to replace contents of used WSDL.
Because only 1 "=" is missing in WSDL..
Thanks

Invoking a WS from BPEL - WS URL is hardcoded in the WSDL

I have published a PL/SQL package as a webservice and deployed it successfully to a development instance (say DEV).
I created a BPEL process and used a Partner Link to invoke the above web service. When I deploy the BPEL process to the DEV instance, it works fine. However when I deployed the above WS and BPEL process to another instance (say TEST), the BPEL process still calls the WS in the original (DEV) instance. I verified by invoking the WS in the TEST instance and it is working fine.
When I created the partner link in the BPEL process, I had to provide the actual WS url from the DEV instance and it created the WSDL for me. This probably is causing the issue as the DEV WS url is hardcoded in the WSDL. However I do not know how to provide the WSDL in the partner link so that url/server name is not hardcoded.
Any help with this is greatly appreciated.
JDev - 10.1.3.4
SOA Suite - 10.1.3.4
Thanks.
Edited by: user13163442 on Jul 21, 2011 1:10 PM

Naren,
Thanks for looking into this.
Yes, the web service is calling a packaged procedure which is available in both the environments. This web service is independent and may be used by other BPEL processes or other applications too.
I developed the WS & BPEL process in the dev environment and then deployed to the TEST environment. I did not make any changes to the BPEL & WS before deploying to TEST. The only change I did after deploying the WS to the TEST environment is to map the jndi.
I am not calling the package directly -- I want to consume the WS.
I am not sure about the Composite? Is this something in SOA 11g? I am still on SOA 10.1.3.4
Is this helpful? Did I answer your questions correctly?
Thanks again.

Error while invoking the WSDL service of EBS from BPEL process

Hi Team,
when we are calling webservice client to call WSDL service which is published in Oracle EBS integrated SOA Gateway from BPEL process.
After invoking, we are getting the below error
<bpelFault><faultType>0</faultType><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>FND_SOA_SERVICE_EXECUTION_ERR:oracle.apps.fnd.soa.util.SOAException: ServiceExecutionError: Error while executing the service Exception returned from JCA Service Runtime. Exception returned from JCA Service Runtime. null :Please see service monitor logs for full error trace</summary></part><part name="detail"><detail>oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault from server : FND_SOA_SERVICE_EXECUTION_ERR:oracle.apps.fnd.soa.util.SOAException: ServiceExecutionError: Error while executing the service Exception returned from JCA Service Runtime. Exception returned from JCA Service Runtime. null :Please see service monitor logs for full error trace</detail></part><part name="code"><code>{http://schemas.xmlsoap.org/soap/envelope/}Server</code></part></remoteFault></bpelFault>
API Name : OE_ORDER_PUB.PROCESS_ORDER
could you please let me know the exact problem and provide the solution.
Thanks
Phani Ch.

Hi Phani,
Are you able to reproduce issue as below:
1. Login to Application as sysadmin.
2. Navigate to Intergrated SOA Gateway > Integration Repository.
3. Click on search on right hand side of the page.
4. In the Internal Name type "FND_USER_PKG" and click Go.
5. Click on the User link.
6. Under the "Web Service - SOA Provider", click in the "View WSDL". Copy the complete URL "http://test:8003/webservices/SOAProvider/plsql/fnd_user_pkg/?wsdl"
7. Open the soapUI.
8. Click File > new soapUI Project.
9. Test the web service.
If yes,
I think you might be need to execute a patch:
solution:
To implement the solution, please execute the following steps:
1. Download and review the readme and pre-requisites for iAS Patch 18855074.
Note: Above Merge Label Request (MLR) is build for EBS 12.1.3 having OC4J 10.1.3.5.
2. Enable the profile option "EBS Adapter for BPEL, Function Security Enabled".
a. Login as SYSADMIN user and Navigate to System >Profile and Search for "EBS Adapter for BPEL, Function Security Enabled" (Internal name :EBS_ADAPTER_FUNCTION_SEC_ENABLED)
b. Set the Value to 'Y' at SITE level . This means function security feature is enabled and all API calls for PL/SQL APIs, Oracle e-Commerce Gateway, and concurrent programs will be checked for user security before they are invoked.
3. Retest the issue by Generating and Deploying the required package.
4. Migrate the solution as appropriate to other environments.
Thanks
Ranjan

Error while creating a web proxy service using wsdl

Hi folks,
In my use case I should create a web service proxy using the wsdl. While I am creating the
web service proxy I am getting some error like the binding method does not have the SOAP extension.
I am giving the error below for more clarity
Caused by: oracle.j2ee.ws.common.tools.api.WsdlValidationException: input message of binding operation "createReference" does not have a SOAP body extensionCaused by: oracle.j2ee.ws.common.tools.api.WsdlValidationException: input message of binding operation "createReference" does not have a SOAP body extension
What could be the problem? Kindly help me on this.
Thanks,
Phani

Hi,
I guess wsdl URL for Data source is not working as expected
See
http://blogs.oracle.com/middleware/entry/calling_web_services_using_adf_11g
http://st-curriculum.oracle.com/obe/jdev/obe11jdev/ps1/webservices/ws.html

WSDL Files in the Solution Composer

Hi Guys!
I am trying to use the WSDL Files for a Enterprise Service Operation from the Solution Composer, but I am always requiered to enter an account and password to get the file.
Where can I get the authorization to use these WSDL files and how?
I will really appreciate any hint!

Hi Edgardo,
If you go to the ESA Preview System Page https://www.sdn.sap.com/sdn/esapreview.sdn?node=linkDnode12-2 you will notice that there is a form to request participation in the ESA Preview System access. Only those Partners and Employees defining a very valid business case for building and testing client applications that consume enterprise services will be accepted to this "limited" capacity program.
At a later date, these WSDL files will be more widely available. For the time being only those accepted as part of this preview system program will have access.
cheers,
Marilyn

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

Can not open the WSDL in a Deployed web service

I finished a JAXRPC based web service, packaged a war file and then using WSDEPLOY to produce a new war file. The new war file was deployed to Sun APP Server and everything seemed to be fine. But when I tried to open the url, the page displayed many question marks (not encoding problem, I tried many encodings but no change). The following is a copy from the browser (originally in a table, becomes mess here)
Web ??
MetSoapEndpoint ???
??? http://localhost:8080/MyWS/mysoap/MyWSEndpoint
WSDL? http://localhost:8080/MyWS/mysoap/MyWSEndpoint?WSDL
?? QName? {http://www.agmodel.org/Schema/MyWS/2006/02/MyWSEndpoint}MyWSEndpointPort
????? net.agmodel.myws.mysoap.jaxrpc.MyWSEndpoint
???? net.agmodel.myws.mysoap.MyWSEndpoint_Impl
??? http://localhost:8080/MyWS/mysoap/MyWSEndpoint???
And I tried to open the WSDL by clicking on the above WSDL address, but get the following error message:
XML Parsing Error: no element found
Location: http://localhost:8080/MyWS/mysoap/MyWSEndpoint?WSDL
Line Number 1, Column 39:<?xml version="1.0" encoding="UTF-8"?>
I also tried to deploy the service to JBOSS 4.0.4, got exactly the same result.
Anyone can help me?
Thanks a lot.
xinwen

Nobody answered...
May bcoz it was on AXIS2.... no issues guys..here is the solution
Webservice technology is also based on Servlet based techology only
so in AXIS2 webservice class, implement org.apache.axis2.engine.ServiceLifeCycle interface. You'll get 2 methods here -
void startUp(ConfigurationContext arg0, AxisService arg1) and
void shutDown(ConfigurationContext arg0, AxisService arg1)
these are nothing but init() and destroy() of the servlet.
Inside these methods u can get servlet context parameters by getAttribute(string) and initial parameters of the servlet by getInitParameter(string)
Edited by: Neo2001 on Feb 18, 2008 2:31 PM

The WSDL data cannot be retrieve from remote site

I am a new guy learning web services with NetBeans 5.5 and meet some problem in retrieving wsdl data from remote site.
I create a web service "WSTestServer" at Sun Application Server PE8.2 with real IP, say 111.110.11.10:8888, and there's a class "TestWS" with a method "getWS" to return a String. The server (or machine) name is ultra20. So, by following steps in NetBeans, I can get a wsdl file after generating the web service and it can be viewed at
http://111.110.11.10:8888/WSTestServer/TestWS?WSDL
Then, I create a web service client at the same machine, it is available to test this method by clicking Web Service Reference item in NetBeans and select "getWS" method to get that String.
However, when I create a web service client at remote site, it doesn't work and show exception message like
cannot find domain http://ultra20:8888/WSTestServer/TestWS....
I go back to check wsdl file, at the last line, it prints like
<soap:address location="http://ultra20:8888/WSTestServer/TestWS".....
If I test this case in LAN, e.g., the server IP becomes 192.168.1.2 and client IP is 192.168.1.3, then it works since machine name can be recognized within the same local area network. I try to revise the wsdl file above to replace machine name as real IP, but it is automatically changed back with machine name while deploying and copy the revised one as xxx.wsdl__orig.
Should I do additional configuration setup for server site? Such as, registering a domain name like aaa.bbb.edu instead of 111.110.11.10?
Any comment and help for this subject is appreciated!!
Thank you so much!

Works as designed,from documentation:
The database also retrieves all triggers and constraints defined on the table except for referential integrity constraints that reference other tables.
The retrieved indexes, triggers, and constraints have recycle bin names. Therefore it is advisable to query the USER_RECYCLEBIN view before issuing a FLASHBACK TABLE ... TO BEFORE DROP statement so that you can rename the retrieved triggers and constraints to more usable names.
For details see the FLASHBACK TABLE command description for your unknown database version.
Werner

Mail can't send email from 123-reg accounts

Hi all,
I've got an issue with Mac Mail can’t send email from 123-reg accounts.
I know there is a lot of articles on simular matters and some I have tried out with no luck, others are just speaking a whole other language.
Any help would be greatly recived, here's my situation below:
Running a iMac 2.8GHz Intel Core i5 on OS X 10.8.3
I’m using 3 accounts on Macs Mail client, one is my iCloud account that is working fine and the other two are my 123-reg accounts that I use for business purposes. I’ve been working like this for a couple of years now and about 6 months ago I upgrade my operating system from Snow Leopard to Mountain Lion.
2 or 3 months ago I randomly got a problem where I was unable to send any emails from my 123-reg account, I could only receive emails. I checked my settings and they were all correct and unchanged so I attempted to delete them and recreate the account but with no such luck.
I then decided to check if it was a problem at 123-regs end and attempted to log into web mail. This worked and was able to both send and receive emails so eliminated that possibility.
I also have these accounts set up on my iPhone, so checked if there was any issues and everything was working fine. I then checked my iphone details and made sure the same was on my desktop and still no such luck.
I’ve tried out some of the articles I’ve found on here (the ones written in plain English) still no results. I’m not very IT illiterate and just wondered if anyone else has got any ideas, whether there is something specific with 123-reg accounts and Mac Mail?
Many thanks.

Thanks
I just had another hunt around looking at posts and discovered that it was because I recently changed to BT Infinity and they had a block on.
I didn't even think to question the ISP.
https://discussions.apple.com/message/21173608#21173608

Reg: WSDL

Similar Messages

Maybe you are looking for