WSDL doubt!

Hi all,
Im trying to configure a Web Service scenario. I have few messages interfaces in this scenario, so my doubt is: I need publish one wsdl per message interface? If I put an asterisk (*) in wsdl interface name it assumes that is for all interfaces that I have in XI?
With adapters I need to create a sender soap adapter per message interface too? Im asking this because when I try to define a sender soap adapter, I have a Default Interface Namespace and Default Interface name to fill
Thanks in advance,
Ricardo.

Hi Ricardo -
You can have the client dynamically set the interface name and namespace and override the default. Please check Note 856597 - SOAP Adapter FAQ. Relevant portion below:
Q: Can I set the interface name dynamically from the client?
Yes. You can overwrite these XI parameters from the client. To activate this overwriting mode, you need to turn on option "Use Encoded Header" and "Use Query String" in the channel. Then your client can append the interface name using parameter Interface.
For example, interface namespace http://sap.com/test and interface Test can be represented by the url-encoded form of http://sap.com/test^Test as in
#&version=3.0&Interface=http%3A%2F%2Fsap.com%2Ftest%5ETest
Regards,
Jin

Similar Messages

Web Services - WSDL doubt.

Hi all,
Im sorry to repeat this subject again, but I continue with some doubts
I read almost SDN web logs about web services. All they teach, how to configure and develop a simple web services but the steps to create a web service connection between XI, continues a little bit confused to me
To clarify my objective, look at this scenario: With an iview with an upload form, I want to upload an xml file to XI trough web service (soap adapter). NW Portal <-> (web services) <-> XI.
I dont have sure what I need to do to configure a scenario like that. Tell me if Im correct: First I need to create an outbound interface to connect Portal via web services to XI, with a soap adapter?
In the web logs that Im read, (/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi) I need to download wsdl files but who make these wsdl files? I need to make it before configure my soap adapter?
I dont understand what is the propose of wsdl files and what is used for!!! I never worked with web services Im come from ABAP programming and Im trying to do the first steps in web technologies. So, Im sorry if said some mistakes
Please, can anybody clarify my doubts? Documentation to help is appreciated.
Thanks in advance,
Ricardo.

Hi Ricardo,
>>>I dont have sure what I need to do to configure a scenario like that. Tell me if Im correct: First I need to create an outbound interface to connect Portal via web services to XI, with a soap adapter?
yes that's what you have to do:
1. create an outbound interface
2. publish a web service based on this interface (sender SOAP adapter)
>>>In the web logs that Im read, (/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi) I need to download wsdl files but who make these wsdl files? I need to make it before configure my soap adapter?
you need to download wsld file if you want to call
a web service from XI, since you only want to do Portal -> xi and not XI -> web service then you don't need any
wsld files
>>>but who make these wsdl files?
you will, once you'll define your web service
on the XI - your Portal iview will use this file
Regards,
michal

Basic doubts regarding ssl with tomcat 5.5 and netbeans 5.5 for WSDL?

I've just started my preparation of web services. I'm using JAX-WS to create my web services and client. I'm using Tomcat 5.5(not apache axis) to deploy my web services over https and i'm able to do that. I've configured my keystore and keystorepassword in tomcat's server.xml. After i've configured my web.xml to choose security type(choosen CLIENT-CERT). I'm able to run my web services over https. I'm using IDE as netbeans 5.5.
But to access this web service from core java client, i'm unable to do it. I've configure my jvmargs in the project-properties-run tab of netbeans and have given keystore,keystorepassword,keytrust,keytrustpassword. After all this i've also export it to the trustcacerts of tomcat. I want to run this using jax-ws. I've searched for many tutorials of this jax-ws , but all were in vain. Eventhough i've checked in java.dev.net site for tutorial but didn't find for my need. Everywhere they metioned on glassfish,wsit or some other technologies.
Right now i'm totally confused. I've read some little bit things of all these things and finally land it in the middle of the sea. Could anyone provide me the basic concepts or any url for this.
After all this i'm getting exception as : https hostname should be <localhost>. I'm totally confused what to do.
One more thing i just wanted to know that i'm diving into the jax-ws technology, is that right to buil an application on this or should i use JAX-RPC. Which one is better for accessing the url and should be secured from security propects. Also tell me is that possible to build web services on https with using tomcat5.5,jax-ws and netbeans 5.5 or should i need some technology for start up.

Any kind of help are welcome.

Error during generation of the WSDL: BUILD FAILED java.lang.NoClassDefFoundError: com/sun/javadoc/Type

When I create an EJB Transport Business Service, after selecting the jar that has the EJB 2.1 artefacts (Remote, Home, etc) the oepe plugin fails and can't continue.
As I understand it seems that there is a problem with the classpath of ant build.xml that oepe creates inside folder /tmp/alsbejbtransport/ to compile the bs and generate the wsdl. I checked if tools.jar is in the classpath (in eclipse) and is included, so I can't figure out wich is the problem.
I found this in Oracle, but not helps solve the problem:
BEA-398120
Error: The WSDL for the typed transport endpoint could not be accessed.
Description
There was a problem retrieving the WSDL from the typed transport service endpoint at the time of service registration
Action
Contact technical support
This is the the full stacktrace that shows eclipse.
Generate : Error during generation of the WSDL:
BUILD FAILED
java.lang.NoClassDefFoundError: com/sun/javadoc/Type
 at com.bea.util.jam.provider.JamServiceFactoryImpl.createSourceBuilder(JamServiceFactoryImpl.java:205)
 at com.bea.util.jam.provider.JamServiceFactoryImpl.createBuilder(JamServiceFactoryImpl.java:158)
 at com.bea.util.jam.provider.JamServiceFactoryImpl.createClassLoader(JamServiceFactoryImpl.java:137)
 at com.bea.util.jam.provider.JamServiceFactoryImpl.createService(JamServiceFactoryImpl.java:78)
 at weblogic.wsee.util.JamUtil.parseSource(JamUtil.java:152)
 at weblogic.wsee.tools.anttasks.JwsLoader.loadJClasses(JwsLoader.java:186)
 at weblogic.wsee.tools.anttasks.JwsLoader.load(JwsLoader.java:75)
 at weblogic.wsee.tools.anttasks.JwsModule.loadWebServices(JwsModule.java:569)
 at weblogic.wsee.tools.anttasks.JwsModule.generate(JwsModule.java:369)
 at weblogic.wsee.tools.anttasks.JwsModule.build(JwsModule.java:256)
 at weblogic.wsee.tools.anttasks.JwscTask.execute(JwscTask.java:184)
 at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
 at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:601)
 at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
 at org.apache.tools.ant.Task.perform(Task.java:348)
 at org.apache.tools.ant.Target.execute(Target.java:357)
 at org.apache.tools.ant.Target.performTasks(Target.java:385)
 at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
 at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
 at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
 at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
 at org.apache.tools.ant.Main.runBuild(Main.java:758)
 at org.apache.tools.ant.Main.startAnt(Main.java:217)
 at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
 at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
Caused by: java.lang.ClassNotFoundException: com.sun.javadoc.Type
 at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1400)
 at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1341)
 at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1088)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
 ... 27 more
Total time: 0 seconds
Eclipse Installation details:
*** System properties:
eclipse.application=org.eclipse.ui.ide.workbench
eclipse.buildId=M20110909-1335
eclipse.commands=-os
linux
-ws
gtk
-arch
x86_64
-showsplash
-launcher
{home}/Development/oepe-indigo/eclipse
-name
Eclipse
--launcher.library
{home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.v20110505/eclipse_1407.so
-startup
{home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.overrideVmargs
-exitdata
1e418010
-vm
/usr/bin/java
eclipse.home.location=file:{home}/Development/oepe-indigo/
eclipse.launcher={home}/Development/oepe-indigo/eclipse
eclipse.launcher.name=Eclipse
[email protected]/../p2/
eclipse.p2.profile=PlatformProfile
eclipse.product=org.eclipse.platform.ide
eclipse.startTime=1374623921455
eclipse.vm=/usr/bin/java
eclipse.vmargs=-Xms256m
-Xmx768m
-XX:MaxPermSize=512m
-Dsun.lang.ClassLoader.allowArraySyntax=true
-Dweblogic.home={home}/Oracle/Middleware/wlserver_10.3
-Dharvester.home={home}/Oracle/Middleware/Oracle_OSB1/harvester
-Dosb.home={home}/Oracle/Middleware/Oracle_OSB1
-Dosgi.bundlefile.limit=750
-Dosgi.nl=en_US
-Dmiddleware.home={home}/Oracle/Middleware
-jar
{home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
equinox.use.ds=true
file.encoding=UTF-8
file.encoding.pkg=sun.io
file.separator=/
guice.disable.misplaced.annotation.check=true
harvester.home={home}/Oracle/Middleware/Oracle_OSB1/harvester
http.nonProxyHosts=localhost
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.awt.printerjob=sun.print.PSPrinterJob
java.class.path={home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
java.class.version=50.0
java.endorsed.dirs=/usr/lib/jvm/jdk1.6.0_45/jre/lib/endorsed
java.ext.dirs=/usr/lib/jvm/jdk1.6.0_45/jre/lib/ext:/usr/java/packages/lib/ext
java.home=/usr/lib/jvm/jdk1.6.0_45/jre
java.io.tmpdir=/tmp
java.library.path=/usr/lib/jvm/jdk1.6.0_45/jre/lib/amd64/server:/usr/lib/jvm/jdk1.6.0_45/jre/lib/amd64:/usr/lib/jvm/jdk1.6.0_45/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
java.protocol.handler.pkgs=null|com.bea.wli.sb.resources.url|com.bea.wli.sb.resources.jca.upgrade.url|weblogic.utils|weblogic.utils|weblogic.utils|weblogic.net|weblogic.net
java.runtime.name=Java(TM) SE Runtime Environment
java.runtime.version=1.6.0_45-b06
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.6
java.vendor=Sun Microsystems Inc.
java.vendor.url=http://java.sun.com/
java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi
java.version=1.6.0_45
java.vm.info=mixed mode
java.vm.name=Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=Sun Microsystems Inc.
java.vm.version=20.45-b01
javax.rmi.CORBA.PortableRemoteObjectClass=weblogic.iiop.PortableRemoteObjectDelegateImpl
javax.rmi.CORBA.UtilClass=weblogic.iiop.UtilDelegateImpl
jna.platform.library.path=/usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib
line.separator=
middleware.home={home}/Oracle/Middleware
oracle.eclipse.tools.weblogic.ui.isWebLogicServer=true
org.apache.commons.logging.Log=org.apache.commons.logging.impl.NoOpLog
org.eclipse.equinox.launcher.splash.location={home}/Development/oepe-indigo/plugins/org.eclipse.platform_3.7.1.v201109091335/splash.bmp
org.eclipse.equinox.simpleconfigurator.configUrl=file:org.eclipse.equinox.simpleconfigurator/bundles.info
org.eclipse.m2e.log.dir={home}/workspace/pragma/.metadata/.plugins/org.eclipse.m2e.logback.configuration
org.eclipse.update.reconcile=false
org.omg.CORBA.ORBClass=weblogic.corba.orb.ORB
org.omg.CORBA.ORBSingletonClass=weblogic.corba.orb.ORB
org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,OSGi/Minimum-1.2,JRE-1.1,J2SE-1.2,J2SE-1.3,J2SE-1.4,J2SE-1.5,JavaSE-1.6
org.osgi.framework.language=en
org.osgi.framework.os.name=Linux
org.osgi.framework.os.version=3.8.0
org.osgi.framework.processor=x86-64
org.osgi.framework.system.capabilities=osgi.ee; osgi.ee="OSGi/Minimum"; version:List<Version>="1.0, 1.1, 1.2",osgi.ee; osgi.ee="JavaSE"; version:List<Version>="1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6"
org.osgi.framework.system.packages=javax.accessibility,javax.activation,javax.activity,javax.annotation,javax.annotation.processing,javax.crypto,javax.crypto.interfaces,javax.crypto.spec,javax.imageio,javax.imageio.event,javax.imageio.metadata,javax.imageio.plugins.bmp,javax.imageio.plugins.jpeg,javax.imageio.spi,javax.imageio.stream,javax.jws,javax.jws.soap,javax.lang.model,javax.lang.model.element,javax.lang.model.type,javax.lang.model.util,javax.management,javax.management.loading,javax.management.modelmbean,javax.management.monitor,javax.management.openmbean,javax.management.relation,javax.management.remote,javax.management.remote.rmi,javax.management.timer,javax.naming,javax.naming.directory,javax.naming.event,javax.naming.ldap,javax.naming.spi,javax.net,javax.net.ssl,javax.print,javax.print.attribute,javax.print.attribute.standard,javax.print.event,javax.rmi,javax.rmi.CORBA,javax.rmi.ssl,javax.script,javax.security.auth,javax.security.auth.callback,javax.security.auth.kerberos,javax.security.auth.login,javax.security.auth.spi,javax.security.auth.x500,javax.security.cert,javax.security.sasl,javax.sound.midi,javax.sound.midi.spi,javax.sound.sampled,javax.sound.sampled.spi,javax.sql,javax.sql.rowset,javax.sql.rowset.serial,javax.sql.rowset.spi,javax.swing,javax.swing.border,javax.swing.colorchooser,javax.swing.event,javax.swing.filechooser,javax.swing.plaf,javax.swing.plaf.basic,javax.swing.plaf.metal,javax.swing.plaf.multi,javax.swing.plaf.synth,javax.swing.table,javax.swing.text,javax.swing.text.html,javax.swing.text.html.parser,javax.swing.text.rtf,javax.swing.tree,javax.swing.undo,javax.tools,javax.transaction,javax.transaction.xa,javax.xml,javax.xml.bind,javax.xml.bind.annotation,javax.xml.bind.annotation.adapters,javax.xml.bind.attachment,javax.xml.bind.helpers,javax.xml.bind.util,javax.xml.crypto,javax.xml.crypto.dom,javax.xml.crypto.dsig,javax.xml.crypto.dsig.dom,javax.xml.crypto.dsig.keyinfo,javax.xml.crypto.dsig.spec,javax.xml.datatype,javax.xml.namespace,javax.xml.parsers,javax.xml.soap,javax.xml.stream,javax.xml.stream.events,javax.xml.stream.util,javax.xml.transform,javax.xml.transform.dom,javax.xml.transform.sax,javax.xml.transform.stax,javax.xml.transform.stream,javax.xml.validation,javax.xml.ws,javax.xml.ws.handler,javax.xml.ws.handler.soap,javax.xml.ws.http,javax.xml.ws.soap,javax.xml.ws.spi,javax.xml.ws.wsaddressing,javax.xml.xpath,org.ietf.jgss,org.omg.CORBA,org.omg.CORBA_2_3,org.omg.CORBA_2_3.portable,org.omg.CORBA.DynAnyPackage,org.omg.CORBA.ORBPackage,org.omg.CORBA.portable,org.omg.CORBA.TypeCodePackage,org.omg.CosNaming,org.omg.CosNaming.NamingContextExtPackage,org.omg.CosNaming.NamingContextPackage,org.omg.Dynamic,org.omg.DynamicAny,org.omg.DynamicAny.DynAnyFactoryPackage,org.omg.DynamicAny.DynAnyPackage,org.omg.IOP,org.omg.IOP.CodecFactoryPackage,org.omg.IOP.CodecPackage,org.omg.Messaging,org.omg.PortableInterceptor,org.omg.PortableInterceptor.ORBInitInfoPackage,org.omg.PortableServer,org.omg.PortableServer.CurrentPackage,org.omg.PortableServer.POAManagerPackage,org.omg.PortableServer.POAPackage,org.omg.PortableServer.portable,org.omg.PortableServer.ServantLocatorPackage,org.omg.SendingContext,org.omg.stub.java.rmi,org.w3c.dom,org.w3c.dom.bootstrap,org.w3c.dom.css,org.w3c.dom.events,org.w3c.dom.html,org.w3c.dom.ls,org.w3c.dom.ranges,org.w3c.dom.stylesheets,org.w3c.dom.traversal,org.w3c.dom.views,org.w3c.dom.xpath,org.xml.sax,org.xml.sax.ext,org.xml.sax.helpers
org.osgi.framework.uuid=901615cd-f3f3-0012-11b6-a3bca4d97ac1
org.osgi.framework.vendor=Eclipse
org.osgi.framework.version=1.6.0
org.osgi.supports.framework.extension=true
org.osgi.supports.framework.fragment=true
org.osgi.supports.framework.requirebundle=true
os.arch=amd64
os.name=Linux
os.version=3.8.0-26-generic
osb.home={home}/Oracle/Middleware/Oracle_OSB1
osgi.arch=x86_64
osgi.bundlefile.limit=750
osgi.bundles=reference:file:javax.transaction_1.1.1.v201105210645.jar,reference:file:org.eclipse.equinox.simpleconfigurator_1.0.200.v20110502-1955.jar@1:start
osgi.bundles.defaultStartLevel=4
osgi.bundlestore={home}/Development/oepe-indigo/configuration/org.eclipse.osgi/bundles
osgi.configuration.area=file:{home}/Development/oepe-indigo/configuration/
osgi.framework=file:{home}/Development/oepe-indigo/plugins/org.eclipse.osgi_3.7.1.R37x_v20110808-1106.jar
osgi.framework.extensions=reference:file:javax.transaction_1.1.1.v201105210645.jar
osgi.framework.shape=jar
osgi.framework.version=3.7.1.R37x_v20110808-1106
osgi.frameworkClassPath=., file:{home}/Development/oepe-indigo/plugins/javax.transaction_1.1.1.v201105210645.jar
osgi.install.area=file:{home}/Development/oepe-indigo/
osgi.instance.area=file:{home}/workspace/pragma/
osgi.instance.area.default=file:{home}/workspace/
osgi.logfile={home}/workspace/pragma/.metadata/.log
osgi.manifest.cache={home}/Development/oepe-indigo/configuration/org.eclipse.osgi/manifests
osgi.nl=en_US
osgi.nl.user=en_US
osgi.os=linux
osgi.splashLocation={home}/Development/oepe-indigo/plugins/org.eclipse.platform_3.7.1.v201109091335/splash.bmp
osgi.splashPath=platform:/base/plugins/org.eclipse.platform
osgi.syspath={home}/Development/oepe-indigo/plugins
osgi.tracefile={home}/workspace/pragma/.metadata/trace.log
osgi.ws=gtk
path.separator=:
securerandom.source=file:/dev/./urandom
socksNonProxyHost=localhost
sun.arch.data.model=64
sun.boot.class.path=/usr/lib/jvm/jdk1.6.0_45/jre/lib/resources.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/rt.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/sunrsasign.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/jsse.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/jce.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/charsets.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/modules/jdk.boot.jar:/usr/lib/jvm/jdk1.6.0_45/jre/classes
sun.boot.library.path=/usr/lib/jvm/jdk1.6.0_45/jre/lib/amd64
sun.cpu.endian=little
sun.cpu.isalist=
sun.desktop=gnome
sun.io.unicode.encoding=UnicodeLittle
sun.java.command={home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar -os linux -ws gtk -arch x86_64 -showsplash -launcher {home}/Development/oepe-indigo/eclipse -name Eclipse --launcher.library {home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.v20110505/eclipse_1407.so -startup {home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.overrideVmargs -exitdata 1e418010 -vm /usr/bin/java -vmargs -Xms256m -Xmx768m -XX:MaxPermSize=512m -Dsun.lang.ClassLoader.allowArraySyntax=true -Dweblogic.home={home}/Oracle/Middleware/wlserver_10.3 -Dharvester.home={home}/Oracle/Middleware/Oracle_OSB1/harvester -Dosb.home={home}/Oracle/Middleware/Oracle_OSB1 -Dosgi.bundlefile.limit=750 -Dosgi.nl=en_US -Dmiddleware.home={home}/Oracle/Middleware -jar {home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
sun.java.launcher=SUN_STANDARD
sun.jnu.encoding=UTF-8
sun.lang.ClassLoader.allowArraySyntax=true
sun.management.compiler=HotSpot 64-Bit Tiered Compilers
sun.os.patch.level=unknown
svnkit.http.methods=Basic
svnkit.library.gnome-keyring.enabled=false
user.country=AR
user.dir={home}/Development/oepe-indigo
user.home={home}
user.language=es
user.name={username}
user.timezone=America/Argentina/Buenos_Aires
weblogic.home={home}/Oracle/Middleware/wlserver_10.3
Thanks!!

run this one in command prompt and then convert the applet using converter tool
JC_HOME = C:\java_card_kit-2_2_2\bin\
set CLASSES=%JCHOME%\lib\apduio.jar;%JC_HOME%\lib\apdutool.jar;%JC_HOME%\lib\jcwde.jar;%JC_HOME%\lib\converter.jar;%JC_HOME%\lib\scriptgen.jar;%JC_HOME%\lib\offcardverifier.jar;%JC_HOME%\lib\api.jar;%JC_HOME%\lib\installer.jar;%JC_HOME%\lib\capdump.jar;
D:\NareshPalle\jcardRE\Smart\src>java -classpath %_CLASSES% com.sun.javacard.con
verter.Converter -out EXP JCA CAP -exportpath .\exp -applet 0x0a:0x00:0x00:0x00:0x0e:0x01:0x02:
0x03:0x04:0x05:0x06 PackageName appletName 0x01:0x02:0x03:0x04:0x05:0x0
6:0x07:0x08 1.0
or
go to following directory and run the converter tool in command prompt
step 1: cd C:\java_card_kit-2_2_2\bin\
then run this command under the above directory
step 2:converter -classdir E:\Pathof Your applet class file -out EXP JCA CAP -exportpath E:\path of exp files folder -applet AID PackageName AppletName PackAID major.minor no
For more doubts mail me....
*[removed by moderator]*
Thanks and Regards
NareshPalle
Edited by: EJP on 31/03/2012 20:09: removed your email address. Unless you like spam and unless you think these forums are provided for your personal benefit only, posting an email address here serves no useful purpose whatsoever.

PI 7.1 ,WSDL

Hi,
Have a PI 7.1 system , need to do soap to proxy sync scenario.
Created a wsdl in PI ,and saved in Altova XML spy ,trying to send a request to server : i see an erro : WSDL document has to begin with a < definitions> element in namespace:http :..schemas.xmlsoap.org/wsdl/(WSDL 1.1) or a <description> elsement in namespace :http:..www.w3.org/ns/(WSDL 2.0
is my WSDL not good ? it is generated via PI 7.1.
Can someone suggest?
Thnx

Hi,
Try using other xml tools ..
Do you have soap UI . or MS-Office 2007( Infopath) - this can also be used to send XML message .
If you have doubt on XML structure .
1. Try Test XML in TEST tab in message mapping.
2. Try test scenario from Runtime work bench / Components / Integration engine ( Test Message) .
Hope this will help .
regards
Prabhat Sharma .

Need some clarification in WSDL based Proxy & Business Services

Hi,
Whenever we configure a Proxy service or Business service based on a WSDL, we use to select Port option instead of Binding when selecting our WSDL for the proxy/business service. Now my ques is why we go for a port instead of binding? what is the difference between them?
My ques may seem very basic but i have this doubt for long time so i am postin this.
Thanks,
Arun

Hi Arun,
In my opinion that is not such a big deal, and in most of the cases you can choose any of the options...
I usually prefer port because it keeps the service name... If you are proxying someone else's service it is better to keep it in a way that the service consumer doesn't notice the difference...
I'm guessing there are cases out there where the service consumer client requires that the binding operations be unchanged... But I've never came across with one of them...
Hope that clarifies...
Cheers,
Vlad

How client will give WSDL File to PI

Hi,
My scenario is webservice to SAP and using SAP 7.1.
I have following doubts.Request you to clarify on this.
1.The way client is going to provide WSDL to PI 7.1. I know that they will be giving WSDL by sending mail,giving URL. and i would like to know other alternate posbbile ways to get WSDL from them.
2. Approach to be followed by the client to trigger the WSDL request (ex: SOAP GUI).
appreciate your help.
Thanks
Hamja

Hi Hamja,
What you have understand is the difference between:
- When you use a sender SOAP Adapter, in this case.. you publish the webservice to be hosted in your PI server; so, you generate the URL and the WSDL File. And you give this file to everyone who wants to consume that WS.
For example, an interfaces that is WS -> PI -> RFC. (Sync Communication)
- And in the other case, is when is a receiver SOAP. With this scenario, and external party provides you a WSDL and a URL in order to PI invoke that URL to be the consumer of the WebService.
Example: RFC -> PI -> WS (Sync Communication)
Which scenario are you going to do?
rgds

Create XI web service from a WSDL with several operations

Hi,
We would like to implement a web service --> XI --> RFC Scenario.
A external vendor has provided us the WSDL that we have to implement in XI, so they can make the web sevice call.
The problem is that the WDSL that they provided to us implements 4 operations, and they are asking us to implement all 4 operations in the same web service.
Is it possible to do such a thing in XI?
Thanks in advance to all.
Jorge Fernandez

Hi Chilla,
The receiver side will support alll 4 operations. Actually we will use only one operation, but the external vendor has as a requirement to implement all operations in the same web service.
However, the other 3 operations that we won't use will be threated by the RFC receiver.
Any help of how to implement this scenario? Actually my doubts are in building the web service that implements all operations.
Thanks in advance.
Jorge Fernandez

Generating Inbound WSDL files.

Hi i am unable to generate inbound WSDL files for JDE. could anyone help me out regarding this please?
Also i have doubts regarding channel creation.
in tcp listener basic configuration under host name and port what do we specify? it asks for database host adn port but when i give the enterprise server details (thats where my db resides) i get JVM_BIND exception. but on speifying a random value for port, it works. (bugs me!!)
thanks in advance

Host:local host (the machine where you are listeneing or AE running)
Port:you need specify the port number which is specifed in config file on the JDE enterprise server

Outbound message ,http sender doubt

Hi
1. i had created a bo,attached it to outboundmessagetype
2.created a xai sender which references realtime http sender xaiclass
3.Now i created a servicescript which creates outbound message
4.created a uimap with a button and a textfield , onclick of that button i invoked that servicescript which should send the field value to the external webservice and send a response
To achieve this i had created a wsdl file which returns hello on receiving hi as a message
and i had added that wsdl hosted url in xai sender context fields
q1.
==>Now whats my doubt is how can i send the textbox value to the webservice and receive a response ,i know that by invoking a bo with
F1-OUTMSG MO i can send the outbound message but what should i write in bo and how can i map it to webservice?
q2.==>Do i need a xsd file ?
q3.==>is it compulsory for using xsl files in an external system for an http sender xaiclass?
q4.==>mapXML="businessObjectRequest" what does this actually mean,to which xml it maps to ?
these are the context values i used for my sender
http url1 :http://172.25.145.35:7001/test/testing
http header:Soapaction:receivecall
http method:post
httptimeout:45
character encoding:ISO-8859-1
any extra fields needed to be set?
help me guys..
Edited by: shanker on Apr 11, 2011 10:31 AM
Edited by: shanker on Apr 11, 2011 10:33 AM

One update
i am able to create a message but i am getting this error
Message from webpage
HTTP status code (500) was returned.
<?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope"><faultcode>S:Client</faultcode><faultstring>Couldn't create SOAP message due to exception: unexpected XML tag. expected: {http://schemas.xmlsoap.org/soap/envelope/}Envelope but found: {}sayHello</faultstring></S:Fault></S:Body></S:Envelope>....
i had not attached an xsl file to an external system either for an request or response ,is it mandatory?
what are the essential context fields for an httpsender?
these are what i used for my xai sender
http url1 :http://172.25.145.35:7001/test/testing
http header:Soapaction:receivecall
http method:post
httptimeout:45
character encoding:ISO-8859-1
plz help me

Digital Sign into payload and other security doubts

Hello experts,
I have a RFC_to_SOAP scenario, and I have to digitally sign the information of the outbound payload (comming from the RFC sender) AND add it to the inbound payload (send it to the target web service, which imported wsdl file is forcing me to include that sign).
In order to do so, can I use the receiver agreement option for digitally sign the document? I guess I can't because it would be added to the payload. So how to do it? Should it be done in message mapping as java mapping? Any indications about how to do that?
Besides I have a doubt about the certification settings in the receiver soap channel and the sign settings in receiver determination. What's exactly the difference? What does each of them with the message?
Thanks in advance.

Hi Ivan, thank you for your response.
I'm trying to develope a module for the soap adapter as you suggested, however I have a question about what you said.
If you only want to sign the content of the XML and not sing the whole payload you can use a Java Mapping
What exactly do you mean with signing the whole payload or just the content?
If I have this xml
<?xml version="1.0" encoding="UTF-8" ?>
<ListaDecV3Ent xmlns="https://www3.aeat.es/ADUA/internet/es/aeat/dit/adu/adht/banent/ListaDecP3Ent.xsd">
<declarante>
<NifDeclarante>27456992N</NifDeclarante>
<NombreDeclarante>José Gutierrez</NombreDeclarante>
</declarante>
</ListaDecV3Ent>
with signing only the content you mean that it would only make the digest and encription of the text 27456992N and José Gutierrez, and signing the whole payload would digest and encritp the xml tags too? If so I need the whole payload to be signed.
Couldn't be that done in java mapping?
By the way I've seen documentation indicating that in order to program an adapter module, a J2EE Java Bean must be developed and deployed to the server. However I'm working in PI 7.1 and in the module tab of the channel I see the option to use a Java Library instead (the options are local enterprise bean, remote enterprise bean and java library). Is it possible? Any info on how it works?
About my doubts in the previous post, if I use the receiver agreement sign option, where would exactly be the sign be placed in the message, and what would it exactly sign?
Any forum mate who can answer is welcome
PD: Ivan I'll open a thread in the spanish forum too if you want to talk there

Obtaining the WSDL and sending a message (like Web Services)

Hi All,
Is it possible to use a service interface defined in XI as any other web service? Consider the following scenario.
1. Create an async service interface (outbound) in XI (This has a message mapping and the message goes to some inbound interface).
2. Can we write an external application (a Java swing client or something) which can send a message to this service interface?
3. While writing a normal web services client we specify the url of the WSDL and then send a SOAP message using some APIs.
4. Can this be achieved in XI? If so could you provide me some links or blogs etc to have some idea about this. Also how do we specify the URL of the interface.
5. I have seen a similar application (an HTML file) which takes the XML payload (conforming to the message type of the interface) and sends the message to the interface. In this case the URL is formed from sender namespace, server name, port etc. The name of this HTML is XIHttp_adapter.html.
6. Can somebody give me more inputs in this direction?
Many Thanks,
Sandeep

Hi Sandeep,
The Info below should surely help you find an answer.
If you're on WAS 6.20 and up, you can expose an RFC as a webservice directly from WAS.
Or if youre on Basis layer 4.6D, you'll need to use XI (or some other integration tool) to expose the RFC as a webservice.
To do this in XI you'll need to:
Integration Repository
1) Import the RFC
2) Define a message and datatype for the SOAP interface
3) Create inbound and outbound interfaces
4) Create maps between the RFC and SOAP messages
5) Create an interface map
Integration Directory
1) Create an RFC Receiver Channel
2) Create a SOAP Sender Channel
3) Generate the WSDL (Tools->Define Web Service)
You can then handoff the WSDL and a login username and password to your developer and they will have everything they need to make the WS call.
Here are answers to a few doubts u might have:
1) Do I need to actually create a WS that calls the RFC ? Isnt the virtual interface exposed by the XI sufficient?
Yes, you need to create a WS in XI that calls the RFC.
2) If I really have to create the WS and deploy it in order to expose it with the XI, then what is my benefit of exposing it with the XI, why not just exposing it as a normal WS ?
You don't have WAS 6.20 or up. Even if you did, you may still want to expose it using XI in order to have all of your integration go through the same application.
3) If I expose my web service through the XI, how does the client application executes one of its methods? To which url does it have to access (the XI or the actual WS)?
You expose a SOAP interface in XI by generating a WSDL file. This file contains all of the information a developer will need to call the webservice including the URL.
You actually specify the URL when you generate the WSDL. Be sure to read the documentation to get the correct format because the URL that the wizard suggests isn't correct.
Also check this Pdf for the Receiever SOAP Adapter configuration:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/40728f7b-0401-0010-d9bc-8c73884a3789
Also the target URL must be the URL to the WSDL. So, if you try putting it in your browser you must see the wsdl code.Please do ensure the same.....
I hope this helps.
Regards,
Abhy

Modify content of wsdl file

I saw from some threads where problem with wsdl file importing is solved by deleting some parts of the wsdl.
Is that safe to do that? Why the format of 'request' or 'response' file changed from the one defined by web services (original wsdl), it could still work? I have doubt about that.
Please advise

Hi Rokie !
It all depends on what are you exactly modifying or deleting in the WSDL file. Sometimes, there are declarations that are not fully compatible with XI. If you don't make structural changes, it may still work. For example, if the WDSL request has an optional field, and its declaration is giving any kind of error while importing in XI, you could try to remove that declaration in WSDL and try that way to debug.
Regards,
Matias.

Doubt About Soap Adapter

Hi Experts,
I have one doubt Here iam Implementing SOAP To RFC Scsnario Using EP(WebDynpro).
Here Should I Generate WSDL File in Integration Directory of XI.
Or Can we generate In WebDynpro Appln.
Please let me know
Regards
Khanna

Hi,
Look into this article, It describes exactly what you want,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5f3ee9d7-0901-0010-1096-f5b548ac1555
Create the WSDL for your message interface in the integration directory and then create a Webservice Model in WebDynpro and finally deploy this on your portal.
Regards
Bhavesh

"Invalid Thread Access" - Consuming WSDL in OSB

Hi,
Creating a business service I am trying to define the service type by consuming WSDL. I get the error "Invalid Thread Access" with no additional details.
The URI is accessible in my browser and works when i import it into jdeveloper. through soapUI, I can able to test this service.
The interesting point here is I am not able to ping that server. (cmd-->ping service name). Here my doubt is do they(as Am invoking third party service) need to open any port for us or not.
Please advice me
Thanks,

Thank you Vlad, I want to tell you some thing about this WSDL.
Size of the wsdl : 5.60 MB and It has 93,671 lines of coding in that file. Is it causes problem
or
Am invoking CRM Web Service and they clearly mention in my mail that "Please use HTTPS because SSL has been applied to your sites"
do I need to create key store for their Certificates.
Please Advise me.
Thanks,
Viswas

WSDL doubt!

Similar Messages

Maybe you are looking for