WSDL bindings

Hi Experts,
I would like to use the following bindings in WSDL.
1. HTTP GET/POST
2. MIME
Usually we can do the SOAP binding through our XI's Integration Directory.
Could you please tell me, from where we can do the HTTP GET/POST and MIME bindings?
Regards
Sara

HI Sara
The XI cannot send out-of-the-box multipart/form-data. In fact the HTTP adapter cannot deal with MIME type multipart at all.
Maybe you can add the required data to the prolog and epilog parameters when you know the exact HTTP stream that the server requires.
refer the below links ....
Re: Mail Adapter Send Mail with Attachment
http://help.sap.com/saphelp_nw04/helpdata/en/23/c093409c663228e10000000a1550b0/content.htm
Thanks !

Similar Messages

How do I create only SOAP WSDL bindings when deploying my ESB?

Currently when I use either jDeveloper or the ant deployESBSuitcase task to deploy the ESB that is the entry point to my application I get two bindings in the deployed wsdl. One soap binding that my client will be using and another esb binding. Is it possible to modify the deployment plan to only generate the SOAP binding? Do I need to have the esb binding for an esb that is only used as the entry point to my application? I would prefer to have the wsdl that is exposed to my clients to not have the vendor extensions if possible.
thanks

I have experienced the exact same problem. There is no good solution to these poorly designed and overly complex login protocols. After unsuccessfully trying to retrieve my password or change my password I finally set up a new email account, a new Apple ID and a new iTunes account.
I know it is not a good solution, but it worked.

Non-SOAP WSDL bindings? (GET/POST?)

Hi,
I would like to know if Aqualogic Service Bus can transform SOAP requests into GET/POST requests?
My organization has several legacy services, which are really just CGIs that accept GET query parameters and return XML results in the HTTP response body.
I would like to integrate those services into an SOA based environment.
I hoped that I could model my legacy services as Web Services using an HTTP GET binding (using WSDL). Then I could import them into Aqualogic and design a transforming proxy in front of them. Is that possible?
Thanks,
Erik

Erik,
just define a SOAP based proxy service and before calling the CGI based business service extract data from the SOAP body and add it to the http transport headers for the outgoing business service call. We have done this succesfully in some projects.
-Kai

DB Polling not picking up Inserts

Hi, Perhaps you could help me troubleshoot a DB Polling senario? I first installed the DBPolling example which uses the sequncing "Helper" table. This worked fine. I now have implemented an deployed another DBPolling process which uses another DB schema and different helper sequencing table.
The Schema definitions are:
SQL> desc af_ora2xel
TRANSACTION_ID NOT NULL NUMBER
EVENT_TYPE_ID NOT NULL NUMBER
EXPORT_DATE NOT NULL DATE
EXPORT_STATUS NOT NULL NUMBER
ITEM_NUMBER VARCHAR2(30)
ORGANIZATION_CODE VARCHAR2(3)
MTL_TRANSACTION_ID NUMBER
MTL_TRANSACTION_TYPE NUMBER
MTL_TRANSACTION_QUANTITY NUMBER
MTL_SUBINVENTORY_CODE VARCHAR2(10)
SQL> desc af_ora2xel_sequencing;
TABLE_NAME VARCHAR2(32)
LAST_READ_ID NUMBER
LAST_UPDATED DATE
My process .wsdl bindings are:
<binding name="ECSS_AF_ORA2XEL_binding" type="tns:ECSS_AF_ORA2XEL_ptt">
<pc:inbound_binding/>
<operation name="receive">
<jca:operation
ActivationSpec="oracle.tip.adapter.db.DBActivationSpec"
DescriptorName="ECSSOratoXelus.AfOra2xel"
QueryName="ECSS_AF_ORA2XEL"
PollingStrategyName="SequencingPollingStrategy"
SequencingFieldName="TRANSACTION_ID"
SequencingTableName="XELUS.AF_ORA2XEL_SEQUENCING"
SequencingTableNameFieldName="TABLE_NAME"
SequencingTableNameFieldValue="XELUS.AF_ORA2XEL"
SequencingTableValueFieldName="LAST_READ_ID"
MaxRaiseSize="1"
PollingInterval="10"
MappingsMetaDataURL="ECSSOratoXelusMappings.xml" />
<input/>
</operation>
</binding>
The procees is deployed OK ( end of console output ):
<2005-03-21 07:58:39,649> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - successfully completed endpointActivation for portType=ECSS_AF_ORA2XEL_ptt, operation=receive
<2005-03-21 07:58:39,808> <INFO> <default.collaxa.cube.engine.deployment> Process "ECSS_Ora_to_Xelus" (revision "1.1") successfully loaded.
<2005-03-21 07:58:39,812> <INFO> <default.collaxa.cube.engine> <CubeEngine::loadAllProcesses>
8 processes have been loaded for BPEL domain "default".
<ServerManager::loadProcesses> Done loading processes for all domains
When I insert records into the AF_ORA2XEL table no process is ever fired off. The interval is set to every 10 seconds. I don't see any output in the OC4J BPEL PM process ether....
What would you suggest to help troubleshoot this further?
Thanks, Matt

Hi Mark,
for beta3 you will see a warning if the helper table is not set up correctly.
Better documenting the need to pre-seed the helper table is good too.
As for your second problem, I tried:
CREATE TABLE "SMCRITCH"."TESTINTEGERANDINT"
"KEY" NUMBER (8,0) NOT NULL,
"BIGKEY" NUMBER (38,0),
"LONGKEY" LONG
ALTER TABLE "SMCRITCH"."TESTINTEGERANDINT"
ADD CONSTRAINT "TESTINTEGERANDINT_PK1" PRIMARY KEY
"KEY"
ENABLE
and the xsd I got back was:
<xs:sequence>
<xs:element name="bigkey" type="xs:double" minOccurs="0" nillable="true"/>
<xs:element name="key" type="xs:double"/>
<xs:element name="longkey" type="xs:long" minOccurs="0" nillable="true"/>
</xs:sequence>
I see. I will enter a bug for sure, but there is a lot you can do after running the wizard to correct this.
Recommended is:
-In jdev open up the offline database table.
-change the column to be of type LONG. Save.
-edit a partnerlink and hit next then finish at the end.
-close and reopen your xsd file.
You should now see something like:
<xs:element name="transactionId" type="xs:long" minOccurs="0" nillable="true"/>
Also you can manually add tags like:
<attribute-classification>java.lang.Integer</attribute-classification>
to your mappings.xml file and update the xsd too. You can always just edit the generated files directly.
Thanks
Steve

SOAP in XI: message use="encoded" and binding/@style="rpc"

Hi
Hope somebody who is familiar with XIs SOAP implementation could give the answer for my questions. Problem is that the SOAP server is not working but I am afraid that the reasons are not really simple.
In our company we have to provide some SOAP services. I have entered as much as I could in IR ... including a simple scenario. Then imported the scenario to ID and the wizard created a number of agreements and determinations...
As I need to describe the service to external parties, then I used IDs Web Service definition tool to generate the WSDL.
But as the external messaging framework (for us a preprogrammed SOAP client) is fixed, I noticed that there are some differences that might matter.
XI generated WSDL where SOAP binding has
wsdl:binding/soap:binding/@style="document" but I would need it to be "rpc"
And the second thing is that in binding message bodies have attribute @use="literal" but as the messages should have several parts then it should be "encoded" (and encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
also is needed then).
Could somebody explain if these may be the reasons why the soap server does not work. And if there is a way to define soap interface so that it would have above mentioned properties as needed.
A easy question also... I would need for a method to have an empty message... inside soap body there should be just a tag with the message name and no content. But I can not figure out how to create a message type with no datatype.
Thanks for any input!

Hi, Stefan
Thanks for the answer. To clear my questions: we want to deploy XI as the SOAP server (sry I have not figured out if it is a sender or receiver channel by name - all this inbound-outbound naming in XI is quite complex). Our SOAP server/XI is actually just one part of a big SOAP network and MAFIA it uses rpc styled SOAP messages.
The note is really useful, but still it does not give any hint how to make a RPC styled SOAP interface. So the problem is still up for me. As I am not very familiar with WSDL bindings and SOAP... for the message it self, is there any difference as for the RPC vs DOCUMENT style is discussed? Is it possible that the physical structure of a SOAP envelope could be the same?
And the second question: is there a way in IR to define several parts for a message. Something like:
<message name="isiku_andmed">
<part name="paring" type="tns:isiku_andmed_paring" />
<part name="keha" type="tns:isiku_andmed_keha" />
</message>

Message Based Trigger

Hello
I am creating a message based trigger to trigger my process with webservice operation. While creating the trigger, the EndPoint Name field is uneditable. So I cannot edit the host name and port.
When I deploy the process I am getting an exception saying WSDL port bindings are not present. My WSDL is working fine.
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. The passed WSDL is not supported by the proxy generator. It does not contain any WSDL bindings.
     at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.initInterfaceMappings(ProxyGeneratorNew.java:915)
     at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.generateAll(ProxyGeneratorNew.java:342)
     at com.sap.engine.services.webservices.server.deploy.ws.WSAltConvertor.convertServiceAltDescriptor(WSAltConvertor.java:228)
     at com.sap.engine.services.webservices.server.deploy.ws.WSAltConvertor.convertServiceAltDescriptors(WSAltConvertor.java:202)
     at com.sap.engine.services.webservices.server.deploy.ws.WSAltConvertor.convertWebServicesJ2EEEngineAltDescriptors(WSAltConvertor.java:182)
     at com.sap.engine.services.webservices.server.deploy.ws.WSAltConvertor.convert(WSAltConvertor.java:128)
     at com.sap.engine.services.webservices.server.deploy.ws.WSDeployProcess.extractWebServicesJ2EEEngineDescriptors(WSDeployProcess.java:276)
     ... 27 more
atcom.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException.writeReplace(WSDeploymentException.java:60)
What could be cause of the issue?
Is there any other way to pass an input parameter to a process?
Thanks
Vidyadhar

Hi Mireille,
I don't think this can be done using Default data. You need to implement BADI /SAPSLL/PRN_DET. You will find method MSG_DET_RESULT_MODIFY, where you need to write your conditions to activate or deactivate a message. But please note this is not going to bypass the standard Activity sequence flows unless and until you do something related to that.
Regards
Dhilipan

WSDLException!

Dear All,
i got the following error while trying to build a project using JCAPS 5.1.0.
( In the project, I've to create a WSDL file & publish it to UDDI Server. I receive a WSDL file from client, implement it, map & validate before invoking business logic in Business Process.)
Annotation: Caught Compilation Error(s).
Please fix before proceeding.
com.stc.codegen.framework.model.CodeGenException
at com.stc.wsserver.design.codegen.impl.WSServerCodelet.generateFiles(WSServerCodelet.java:504)
at com.stc.codegen.frameworkImpl.model.CodeGenFrameworkImpl.processCodelets(CodeGenFrameworkImpl.java:602)
at com.stc.codegen.frameworkImpl.model.CodeGenFrameworkImpl.process(CodeGenFrameworkImpl.java:1263)
at com.stc.codegen.frameworkImpl.model.DeploymentVisitorImpl.process(DeploymentVisitorImpl.java:395)
at com.stc.codegen.frameworkImpl.model.DeploymentVisitorImpl.process(DeploymentVisitorImpl.java:307)
at com.stc.codegen.frameworkImpl.model.DeploymentVisitorImpl.traverseDeployment(DeploymentVisitorImpl.java:267)
at com.stc.codegen.driver.module.DeploymentBuildAction.loadCodeGen(DeploymentBuildAction.java:901)
at com.stc.codegen.driver.module.DeploymentBuildAction.access$700(DeploymentBuildAction.java:173)
at com.stc.codegen.driver.module.DeploymentBuildAction$1.run(DeploymentBuildAction.java:590)
at org.openide.util.Task.run(Task.java:136)
at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:599)
Caused by: com.stc.codegen.framework.model.CodeGenException
at com.stc.wsserver.design.codegen.impl.JaxRpcCodelet.generateFiles(JaxRpcCodelet.java:954)
at com.stc.wsserver.design.codegen.impl.GenerateAndPublish.genAndPublish(GenerateAndPublish.java:118)
at com.stc.wsserver.design.codegen.impl.WSServerCodelet.generateFiles(WSServerCodelet.java:498)
... 10 more
Caused by: com.stc.codegen.framework.model.CodeGenException
at com.stc.wsserver.design.codegen.impl.JaxRpcCodelet.generateFileForWar(JaxRpcCodelet.java:1132)
at com.stc.wsserver.design.codegen.impl.JaxRpcCodelet.generateFiles(JaxRpcCodelet.java:929)
... 12 more
Caused by: com.stc.codegen.framework.model.CodeGenException
at com.stc.wsserver.design.codegen.impl.JaxRpcCodelet.overWriteWSDLBindings(JaxRpcCodelet.java:2656)
at com.stc.wsserver.design.codegen.impl.JaxRpcCodelet.generateFileForWar(JaxRpcCodelet.java:1031)
... 13 more
Caused by: WSDLException: faultCode=OTHER_ERROR: Can't find prefix for 'http://10.116.64.19:12000/repository/JavaCAPSOMX/Project2/WebServiceDefinition1'. Namespace prefixes must be set on the Definition object using the addNamespace(...) method.:
at com.ibm.wsdl.util.xml.DOMUtils.getPrefix(Unknown Source)
at com.ibm.wsdl.util.xml.DOMUtils.getQualifiedValue(Unknown Source)
at com.ibm.wsdl.util.xml.DOMUtils.printQualifiedAttribute(Unknown Source)
at com.ibm.wsdl.xml.WSDLWriterImpl.printBindings(Unknown Source)
at com.ibm.wsdl.xml.WSDLWriterImpl.printDefinition(Unknown Source)
at com.ibm.wsdl.xml.WSDLWriterImpl.writeWSDL(Unknown Source)
at com.stc.wsserver.design.codegen.impl.JaxRpcCodelet.overWriteWSDLBindings(JaxRpcCodelet.java:2651)
[catch] ... 14 more
Plz suggest!

Double check the WSDL bindings in your connectivity map to be sure that the namespaces are populated and match your WSDL.

Clientgen with JAXWS -- how to bind with JAXB?

I'm using WLS 10.0 "clientgen" to generate Java classes from my WSDL files. All goes well for the simpler WSDL files. Since I'm new to JAXB, I don't quite understand now how to bind the output files using JAXB. It seems this would have been done in the 'clientgen' process, but I don't see any parameters for this in the documentation/help output.
Here's the ant snippet:
<target name="wsdl2java" depends="init" >
<clientgen
type="JAXWS"
wsdl="${sitedata.wsdl.file}"
destDir="${generated.class}"
serviceName="SiteData"
packageName="${output.package}.sitedata"/>
</target>
How can this be done?

The <binding> child element of the WLS 10.0 wsdlc Ant task, does in fact allow you to pass a .xjb file to the wsimport Ant task. wsdlc calls wsimport internally.
When you do this, you want to do all of your namespace-to-Java-package mapping in the .xjb file, and not specify the packageName attribute on the wsdlc Ant task. In fact, doing the latter will override the mapping specified in the .xjb file.
Here's a sample Ant target that shows what this looks like:
<target name="run-wsdlc" depends="clean">
<taskdef name="wsdlc" classname="weblogic.wsee.tools.anttasks.WsdlcTask" classpathref="compile.classpath" />
<mkdir dir="${src.dir}"/>
<property name="client.binding" value="custom-client.xjb"/>
<wsdlc
type="JAXWS"
srcWsdl="etc/${wsdl.file.name}.wsdl"
destJwsDir="WebContent/WEB-INF/lib"
destImplDir="${src.dir}"
explode="false"
verbose="${verbose}"
debug="${debug}"
failonerror="true"
>
<binding dir="etc" includes="${client.binding}"/>
<classpath>
<path refid="compile.classpath"/>
</classpath>
</wsdlc>
</target>
And here's the contents of the custom-client.xjb file:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<bindings
xmlns:jxb="http://java.sun.com/xml/ns/jaxb"
xmlns="http://java.sun.com/xml/ns/jaxws"
wsdlLocation="DataStagingService2.wsdl"
>
<bindings
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
node="wsdl:definitions"
>
<package name="services.datastaging">
<jxb:javadoc>
<![CDATA[<body>Package level documentation for generated package services.datastaging.</body>]]>
</jxb:javadoc>
</package>
<jxb:schemaBindings>
<jxb:package name="com.acmeworld.irad.services.datastaging"/>
</jxb:schemaBindings>
</bindings>
</bindings>
The targetNamespace attribute for the DataStagingService is http://www.acmeworld.com/irad/services/datastaging. The above .xjb file says to map this to the services.datastaging Java package, but the skeleton JAX-WS service endpoint implementation class that wsdlc generates, doesn't currently honor this. The JAXB generated classes will be as specified in the .xjb file, but you'll need to manually refactor the Java package name of the wsdlc generated JAX-WS skeleton class, to be services.datastaging.
I'll be publishing a series of articles on using JAXB and JAX-WS with WebLogic 10.0, so look out for them in the coming months :-)
HTH,
Mike Wooten

Consume portal WSNavigator WS

Hi,
I'm trying to consume portal (KM) WS, published at the WSNavigator.
1. i browsed to portal's "Web Services Navigator".
2. WS was selected (out of Available Web Services).
3. click on the "WSDLs" link
4. downloaded wsdl.
my questions are:
1. what is the differted between WSDL and SAP WSDL ? which should i prefered?
2. both WSDL are actually composed outof: "main.wsdl", bindings (i.e., "Config1_document.wsdl") and porttypes (i.e., "Config1_KMIndexSvcStdrWSVi_document.wsdl" and "Config1_KMNodeServiceSnrdWSVi_document.wsdl"). in oreder to import wsdl definisions into my PI i must used single WSDL file (correct?) and therefore i have to assemble these files into one WSDL. what tool can i used to do so? is there a better way to handle these muliple WSDL files?
Regards
Uri

If your WSDL file is referring multiple files then you should import all the files in XI.
If you try opening your WSDL does it open without any error....if yes then the reference is done properly.

Exposing RFC as Web Service in XI

Hi,
I want to expose RFC of an external R/3 System as a Web Service in XI. I do not have much Idea about XI.
It will be great help If I can get some documentation on step by step tutorial of the same type of Scenario.
Thanks
Naresh

Technically it can be done though.
I have done it in Xi 3.0. You create a synchronous interface in XI. Generate the WSDL from the repository. The calling systems consumes it using SOAP. The destination system does not need to be WAS. It can be 4.6C, or even non-Sap.
I have tested this for Asynch postings into 4.6C and it works fine so it should work for synch also however, XI has some problems with the bindings in the WSDL at this stage. You may need to manipulate the WSDL generated in the repository to create SOAP bindings. I understand the problem is being resolved in SP4....
If you do not know about WSDL bindings go to: http://www.w3schools.com/wsdl/default.asp
Regards,
Jason

Sub Processes -- BPM

Hi,
    I have designed a Process havins a sub process and a human Activity , the output of the subprocess will be displayed in the human activity. the subprocess has a human activity and a automated activity .the automated activity returns a string which needs to be passed out of the sub process .
I have assigned a corresponding process to the sub process., but still i could not get any output from the sub process. the end process event is assigned to default service in the subprocess.the output from the subprocess is always the empty response.
Also i could not expand the subprocess in the main process.
How can i acheive communication between main process and sub process.
Thanks and Regards
Fazal

hi,
    I have changed the service for the event end in the sub process from default service to some other service which will get the input the automated activity and gives the response .
now i am able to get the Output response for the sub process in the main process , but when i try to deploy , i am getting deployment exception
full trace of the exception :
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [demo.sap.com_submission_process].
; nested exception is:
     com.sap.engine.services.dc.gd.DeliveryException: <Localization failed: ResourceBundle='com.sap.engine.services.dc.util.exception.resources.ResourceBundle', ID='dc_1207', Arguments: ['demo.sap.com_submission_process']> : Can't find bundle for base name com.sap.engine.services.dc.util.exception.resources.ResourceBundle, locale en
     at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:715)
     at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:226)
     at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:112)
     at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:251)
     at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:125)
     at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$3.run(DcDeployAction.java:224)
     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [demo.sap.com_submission_process].
; nested exception is:
     com.sap.engine.services.dc.gd.DeliveryException: <Localization failed: ResourceBundle='com.sap.engine.services.dc.util.exception.resources.ResourceBundle', ID='dc_1207', Arguments: ['demo.sap.com_submission_process']> : Can't find bundle for base name com.sap.engine.services.dc.util.exception.resources.ResourceBundle, locale en
     at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:188)
     at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
     at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.services.dc.gd.DeliveryException: <Localization failed: ResourceBundle='com.sap.engine.services.dc.util.exception.resources.ResourceBundle', ID='dc_1207', Arguments: ['demo.sap.com_submission_process']> : Can't find bundle for base name com.sap.engine.services.dc.util.exception.resources.ResourceBundle, locale en
     at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:118)
     at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:108)
     at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
     at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
     ... 7 more
Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
     com.sap.engine.services.deploy.container.DeploymentException:
     at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:4714)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:325)
     at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:104)
     ... 10 more
Caused by: com.sap.engine.services.deploy.container.DeploymentException:
     at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.deploy(WebServicesDeployManager.java:269)
     at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:195)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:526)
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:188)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2536)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:378)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:323)
     ... 11 more
Caused by: java.lang.Exception: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Exception occured during web services deployment. Unable to extract web services deployment data for archive demo.sap.com~_submission_process.wsar, application demo.sap.com/submission_process.
     at com.sap.engine.services.webservices.server.deploy.ws.WSDeployProcess.extractWebServicesJ2EEEngineDescriptors(WSDeployProcess.java:293)
     at com.sap.engine.services.webservices.server.deploy.ws.WSDeployProcess.extractWebServicesJ2EEEngineDescriptors(WSDeployProcess.java:254)
     at com.sap.engine.services.webservices.server.deploy.ws.WSDeployProcess.init(WSDeployProcess.java:149)
     at com.sap.engine.services.webservices.server.deploy.WSBaseAbstractDProcess.makeProcess(WSBaseAbstractDProcess.java:308)
     at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.deployWebServices(WebServicesDeployManager.java:1092)
     at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.deploy(WebServicesDeployManager.java:257)
     at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:195)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:526)
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:188)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2536)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:378)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:323)
     at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:104)
     at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:108)
     at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
     at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
     at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
     at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. The passed WSDL is not supported by the proxy generator. It does not contain any WSDL bindings.
     at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.initInterfaceMappings(ProxyGeneratorNew.java:994)
     at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.generateAll(ProxyGeneratorNew.java:425)
     at com.sap.engine.services.webservices.server.deploy.ws.WSAltConvertor.convertServiceAltDescriptor(WSAltConvertor.java:208)
     at com.sap.engine.services.webservices.server.deploy.ws.WSAltConvertor.convertServiceAltDescriptors(WSAltConvertor.java:182)
     at com.sap.engine.services.webservices.server.deploy.ws.WSAltConvertor.convertWebServicesJ2EEEngineAltDescriptors(WSAltConvertor.java:162)
     at com.sap.engine.services.webservices.server.deploy.ws.WSAltConvertor.convert(WSAltConvertor.java:111)
     at com.sap.engine.services.webservices.server.deploy.ws.WSDeployProcess.extractWebServicesJ2EEEngineDescriptors(WSDeployProcess.java:276)
     ... 25 more
     at com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException.writeReplace(WSDeploymentException.java:60)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:1004)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1036)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
     at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:391)
     at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:1033)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
     at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:391)
     at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:1033)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
     at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:135)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:358)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:977)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
     ... 2 more
Please help on this
Thanks and Regards
Edited by: Fazal Ahamed on Dec 17, 2008 3:22 PM

Publication of process failed

I am trying to depoly a process project on a Netweaver 7.11 CE ehp1 server. I get this error when I am defing a web service for interface of a start/stop event :
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Exception occured during web services deployment. Unable to extract web services deployment data for archive demo.sap.comcolwflwreq_pm.wsar, application demo.sap.com/colwflw~req_pm.
at com.sap.engine.services.webservices.server.deploy.ws.WSDeployProcess.extractWebServicesJ2EEEngineDescriptors(WSDeployProcess.java:293)
at com.sap.engine.services.webservices.server.deploy.ws.WSDeployProcess.extractWebServicesJ2EEEngineDescriptors(WSDeployProcess.java:254)
at com.sap.engine.services.webservices.server.deploy.ws.WSDeployProcess.init(WSDeployProcess.java:149)
at com.sap.engine.services.webservices.server.deploy.WSBaseAbstractDProcess.makeProcess(WSBaseAbstractDProcess.java:308)
at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.deployWebServices(WebServicesDeployManager.java:1092)
at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.deploy(WebServicesDeployManager.java:257)
at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.makeUpdate(WebServicesDeployManager.java:501)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:279)
at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:490)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2536)
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:523)
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:422)
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. The passed WSDL is not supported by the proxy generator. It does not contain any WSDL bindings.
at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.initInterfaceMappings(ProxyGeneratorNew.java:994)
at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.generateAll(ProxyGeneratorNew.java:425)
at com.sap.engine.services.webservices.server.deploy.ws.WSAltConvertor.convertServiceAltDescriptor(WSAltConvertor.java:208)
at com.sap.engine.services.webservices.server.deploy.ws.WSAltConvertor.convertServiceAltDescriptors(WSAltConvertor.java:182)
at com.sap.engine.services.webservices.server.deploy.ws.WSAltConvertor.convertWebServicesJ2EEEngineAltDescriptors(WSAltConvertor.java:162)
at com.sap.engine.services.webservices.server.deploy.ws.WSAltConvertor.convert(WSAltConvertor.java:111)
at com.sap.engine.services.webservices.server.deploy.ws.WSDeployProcess.extractWebServicesJ2EEEngineDescriptors(WSDeployProcess.java:276)

Yes,
It seams that this is a bug. I'm in touch with the developer team. If something like that happens to one of your project you can try this :
1) Remove the web services wsdl and reimport it to the project
2) Erase the process composer project and build a new one
3) Change the web service name on the server ie deploy a new version with a different name.
These work arounds solved many times my problems.
If someone knows what's really the problem, feel free to reply !

External Definition - PortType and Bindings missing in WSDL tab

I have created a valid wsdl - document type and imported it into the IR. Almost everything looks OK. No errors on the import, messages show in the message tab. However, when I look at the wsdl tab, I notice that only about half of my orginal wsdl is displayed. The PortType and Bindings nodes are missing. Is there a reason why XI might be stripping this off?
Edited by: Mark Ortiz on Sep 4, 2008 6:42 PM

Hi
when u import the wsdl file in IR, It will treat as the structure and when u see in the wsdl file in wsdl tab all the methods and namespace are equal but the system information differs.It takes the info of the Xi server.
But u need to give the wsdl info in ID , It reads system info from ID only not from IR( IR acts as skeleton)
Regards,
Jayasimha jangam

Multiple bindings in WSDL

Is there any way to specify which binding to use if your wsdl contains multiple entries. e.g. soap binding and java binding.
Toby

Hi,
I've taken a look at the dynamic binding section of the cookbook, however I don't see anything that deals with choosing between which binding should be used when more than one is available.
Could you point me to the right area?
Thanks
Toby

Export bindings for WSDL data connection bug

Looks like Adobe cannot handle complex types when using repeating data sets (for exporting to a wsdl connection). I try binding a complex type (containing a number of text elements) to a repeating subform but it only ever exports the last element. If I remove the complex type and replace it with a single element, it works. I have even tried dragging the entire data structure onto the form but it still won't recognise the repeating dataset. Any help? Thanks..

Hi Jeremy, I wrote to Stephan Cameron (an Adobe Forms guru) and he said that its a bug with Adobe, but that it is fixed in the next release of Acrobat. Which means if you update your Acrobat to the latest version it may work now. I haven't tried this though as we ended up doing something different (just exporting multiple single elements which seems to work). You can check out his comment here: http://forms.stefcameron.com/bug-list/

WSDL bindings

Similar Messages

Maybe you are looking for