Missing type information when importing external web service

Hello,
using the SAP NetWeaver Developer Studio SAP NetWeaver 7.1 Composition Environment SP06 PAT0003, I have imported a number of RFCs from an R/3. The import succeeded as expected (see [here|http://img25.imageshack.us/my.php?image=importrfc.png]) and I am able to invoke the RFCs as intended.
Now, we have imported these RFCs into a PI 7.1 and published them as web services.
However, when I import these web services rather than the RFCs, the type information for parameters is lost as shown [here|http://img25.imageshack.us/my.php?image=importwebservice.png]. The missing type information is included in the provided wsdl files, though.
Note: Using the current version of the NWDS for the CE 7.1 EhP1 does not solve this problem!
Does anyone has an idea what is going wrong?
Best regards
Alexander

The type information is actually not missing. However, the used types carry no names. Therefore, the types are displayed as "anonymous" in the NWDS.

Similar Messages

  • Error when importing a web service from ES Workplace to NWDS

    Hi guys,
    I'm working with SAP NetWeaver Developer Studio (SAP NetWeaver 7.1 Composition Environment SP03 PAT0000 Build id: 200710302120)
    The connection (through Services Registry) to the ES Workplace was successful. I found the service definition and the endpoint for the selected service definition I wanted. But when I clicked "Finish", I got a "Web Service Import Error":
    Web Service can not be imported due to some errors.
    java.lang.reflect.InvocationTargetException
    java.lang.NullPointException
    error detail:
    java.lang.reflect.InvocationTargetException
         at com.sap.caf.designer.ui.actions.es.WSImportAction$1.run(WSImportAction.java:188)
         at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
    Caused by: java.lang.NullPointerException
         at com.sap.caf.foundation.mfw.types.CoreTypes.getAllTypesForApplication(CoreTypes.java:353)
         at com.sap.caf.foundation.mfw.types.CoreTypes.initializeCoreTypes(CoreTypes.java:197)
         at com.sap.caf.foundation.mfw.types.CoreTypes.getType(CoreTypes.java:227)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.getBuiltInSimpleType(WSImportManager.java:849)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createSimpleType(WSImportManager.java:712)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createSimpleTypeWithRestrictions(WSImportManager.java:883)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createSimpleType(WSImportManager.java:728)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createAttribute(WSImportManager.java:663)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createField(WSImportManager.java:1059)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createFields(WSImportManager.java:1046)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createComplexType(WSImportManager.java:967)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createAttribute(WSImportManager.java:671)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createField(WSImportManager.java:1059)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createFields(WSImportManager.java:1046)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createComplexType(WSImportManager.java:967)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createAttribute(WSImportManager.java:671)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createField(WSImportManager.java:1059)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createFields(WSImportManager.java:1046)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createComplexType(WSImportManager.java:967)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createAttribute(WSImportManager.java:671)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createMessage(WSImportManager.java:630)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createInputMessage(WSImportManager.java:605)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createOperation(WSImportManager.java:569)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createOperations(WSImportManager.java:518)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.importInterface(WSImportManager.java:495)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.importWebService(WSImportManager.java:265)
         at com.sap.caf.rt.connectivity.ImportManager.importWebService(ImportManager.java:53)
         at com.sap.caf.designer.ui.actions.es.WSImportAction$1.run(WSImportAction.java:180)
         ... 1 more
    java.lang.NullPointerException
         at com.sap.caf.foundation.mfw.types.CoreTypes.getAllTypesForApplication(CoreTypes.java:353)
         at com.sap.caf.foundation.mfw.types.CoreTypes.initializeCoreTypes(CoreTypes.java:197)
         at com.sap.caf.foundation.mfw.types.CoreTypes.getType(CoreTypes.java:227)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.getBuiltInSimpleType(WSImportManager.java:849)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createSimpleType(WSImportManager.java:712)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createSimpleTypeWithRestrictions(WSImportManager.java:883)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createSimpleType(WSImportManager.java:728)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createAttribute(WSImportManager.java:663)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createField(WSImportManager.java:1059)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createFields(WSImportManager.java:1046)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createComplexType(WSImportManager.java:967)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createAttribute(WSImportManager.java:671)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createField(WSImportManager.java:1059)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createFields(WSImportManager.java:1046)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createComplexType(WSImportManager.java:967)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createAttribute(WSImportManager.java:671)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createField(WSImportManager.java:1059)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createFields(WSImportManager.java:1046)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createComplexType(WSImportManager.java:967)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createAttribute(WSImportManager.java:671)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createMessage(WSImportManager.java:630)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createInputMessage(WSImportManager.java:605)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createOperation(WSImportManager.java:569)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.createOperations(WSImportManager.java:518)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.importInterface(WSImportManager.java:495)
         at com.sap.caf.rt.connectivity.ws.WSImportManager.importWebService(WSImportManager.java:265)
         at com.sap.caf.rt.connectivity.ImportManager.importWebService(ImportManager.java:53)
         at com.sap.caf.designer.ui.actions.es.WSImportAction$1.run(WSImportAction.java:180)
         at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
    Thanks in advance
    Wenhao

    Hi Wenhao,
    I did face something similar ....but when i tried it again...it worked..
    In case it does not then before u try to start the procedure to dwnld the Enterprise service wsdl....
    uncheck the wsdl validator check box in NWDS...
    I suggest u first try to consume the wsdl by importing it locally...
    just follow this blog by Boris step by step..
    /people/boris.mohr/blog/2007/01/23/how-to-guide-for-consuming-a-web-service-with-a-standalone-client-using-sap-netweaver-application-server-javatm-ee-5-edition
    Once u r able to do this..then u can try to consume it from service registry
    Edited by: Mohd Tauseef Ibrahim on Jun 26, 2008 2:28 PM
    Edited by: Mohd Tauseef Ibrahim on Jun 26, 2008 2:30 PM

  • Sun BPEL engine sets wrong Content-Type on calling an external web service

    I have a WSDL for an external web service (which as it happens is running in Websphere locally) and have implemented it as a
    partnerlink on a BPEL diagram in an SOA composite project. The binding style is Document and if you use SOAPUI to test it it
    works fine. Tracing on the web service's server shows the SOAP request coming in. It has a content-type of text/xml, as expected. If I do a JUnit test from NetBeans based on this WSDL alone it also works - same result. BUT if I do
    a full test and call my BPEL process the invocation of this service from BPEL fails.
    On the Test result you see
    BPCOR-6135:A fault was not handled in the process scope; Fault Name is http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault;
    (This happens because I did not handle the fault in the BPEL.)
    On the trace I see it now has Content-type of application/xop+xml. Why would the Sun BPEL engine change this? I just
    accepted the usual defaults when I created the PartnerLink and the Invoke. Anyway, the format of the request doesn't match what the WS server expects, so it fails.
    As far as I'm aware I'm just using SOAP1.1. This is NetBeans 6.5 with Glassfish 2.1. I tried with NetBeans 6.7 and it got worse, not better. I would certainly appreciate any advice?
    Thanks

    Perhaps when the BPEL file based process calls the WSDL file to execute,their message communication is not correct.
    the head part in the WSDL file should be manually set to "text/xml", or the IDE or Server will use the default value;
    for example as follow:
    SOAPUI tool would use the default value "text/xml" to request.(depends the tool support).
    NetBeans tool would use the default value "text/xml" to request.
    when you do a full test and you do not set the head "context-type" value ,the WSDL file use the server's default head
    value"application/xop-xml" so that return the contents under the control of the server's default value.
    I hope these will be useful for you.

  • BPEL engine sets wrong Content-Type on calling an external web service

    I have a WSDL for an external web service (which as it happens is running in Websphere locally) and have implemented it as a
    partnerlink on a BPEL diagram in an SOA composite project.
    The binding style is Document and if you use SOAPUI to test it it
    works fine. Tracing on the web service's server shows the SOAP request
    coming in. It has a content-type of text/xml, as expected. If I do a
    JUnit test from NetBeans based on this WSDL alone it also works - same result. BUT if I do
    a full test and call my BPEL process the invocation of this service
    from BPEL fails.
    On the Test result you see
    BPCOR-6135:A fault was not handled in the process scope; Fault Name is http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault;
    (This happens because I did not handle the fault in the BPEL.)
    On the trace I see it now has Content-type of
    application/xop+xml. Why would the Sun BPEL engine change this? I just
    accepted the usual defaults when I created the PartnerLink and the
    Invoke. Anyway, the format of the request doesn't match what the WS server expects, so it fails.
    As far as I'm aware I'm just using SOAP1.1. This is NetBeans 6.5 with
    Glassfish 2.1. I tried with NetBeans 6.7 and it got worse, not better.
    I would certainly appreciate any advice?
    Thanks

    Perhaps when the BPEL file based process calls the WSDL file to execute,their message communication is not correct.
    the head part in the WSDL file should be manually set to "text/xml", or the IDE or Server will use the default value;
    for example as follow:
    SOAPUI tool would use the default value "text/xml" to request.(depends the tool support).
    NetBeans tool would use the default value "text/xml" to request.
    when you do a full test and you do not set the head "context-type" value ,the WSDL file use the server's default head
    value"application/xop-xml" so that return the contents under the control of the server's default value.
    I hope these will be useful for you.

  • Importing external web service with SSL certificate security

    Hello,
    I'm trying to import an external web service (that resides in another server, independent of ours). However, right after I enter the WSDL in the import window I get the following error in the NWDS:
    sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target      [Error: com.sap.ide.es.core.ui.internal.wizards.fragments  Thread[ModalContext,6,main]]
    javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
              at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
              at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1649)
              at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:241)
              at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:235)
              at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1206)
              at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:136)
              at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:593)
              at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:529)
              at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:893)
              at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1138)
              at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1165)
              at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1149)
              at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:434)
              at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:166)
              at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
              at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234)
              at com.sap.ide.es.core.ui.internal.wizards.fragments.UrlValidationRunnable.getURLAsStream(UrlValidationRunnable.java:137)
              at com.sap.ide.es.core.ui.internal.wizards.fragments.UrlValidationRunnable.validate(UrlValidationRunnable.java:75)
              at com.sap.ide.es.core.ui.internal.wizards.fragments.UrlValidationRunnable.run(UrlValidationRunnable.java:55)
              at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
    Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
              at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:323)
              at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:217)
              at sun.security.validator.Validator.validate(Validator.java:218)
              at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:126)
              at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:209)
              at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:249)
              at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1185)
              ... 15 more
    Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
              at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:174)
              at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:238)
              at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:318)
              ... 21 more
    Has anyone ever consumed an external web service with SSL certificate security? How do you import this in your Web Dynpro project?
    Cheers!

    Hi Alain,
    I just checked on a newer NW environment (NW 7.2) and was presented an empty list as well... It seems the mapping procedure I described is deprecated since NW 7.11, and the modeled CAF application service is already exposed as a web service.
    You may want to have a look at http://help.sap.com/saphelp_nwce711/helpdata/en/43/f173947bbb025be10000000a1553f7/content.htm or http://scn.sap.com/message/7852996 for more info

  • Configurations to be done when calling external web service

    Hi,
    Do we need to do any configurations in SAP when we want to call any external web service from sap.
    I have created a proxy based on URL (WSDL) and I have searched this consumer proxy in soamanager transaction.
    I found the result and when I click on Apply Selection it is giving some errors in the soamanager screen at the top.
    The error is " Error : Internal error" . When I click this error link no error text is available.
    How to check the errors displayed in soamanager.
    Can anyone explain on how to resolve this issue. Once these errors are rectified then only I can create a logical port.

    You have problems with authorizations when you try to create logical port.

  • Managing cookies when consuming external web services

    I am trying to use an external webservice from within an Oracle 10g database (i.e. database is client).
    I have the WSDL for the web service, and have successfully imported the JPub-generated Java classes and PL/SQL wrappers to the database.
    I am also able to use the web service, but a small detail is missing:
    The web service returns a cookie, that has to be set for all subsequent calls to the web service.
    How (if at all possible) is this achieved, when I only have the limited PL/SQL wrappers at my disposal?
    I have tried to call the (object).setMaintainSession(), and set the value to true (=1 for PL/SQL), but no help there...
    I have tried the OWA_COOKIE, OWA, UTL_HTTP packages to see if I can retrieve the cookie from the response in any way, but so far without success.
    Any help would be greatly appreciated.
    System-info: Oracle 10.2.0.3 (Sun Unix)

    After working offline with Chew Ling on this issue, the cause was found to be a mismatch between the java archive files that are loaded when the local OC4J or embedded JDeveloper OC4J runs, and the database driver JAR file that exists in the c:\e900\MISC folder. This is a configuration problem which particularly affects development clients that use a local Oracle database, including the Standalone Oracle DB install that Chew Ling is using, and is a known problem (ref: https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=PROBLEM&id=859688.1).
    The list of jars that are loaded by the OC4J is held in the C:\e900\system\Classes\SBFProjects.library file, and the solution is to add the ojdbc5.jar Oracle DB driver file to the list.
    Dave

  • Error while trying to import external web service in webdynpro java

    Hi,
    I am trying to import external webservice in webdynpro java using adaptive webservice model, but i am getting below error..i tried some other external webservices but those are working fine....I wanted to know if there is any issue with this wsdl?? any suggestions?
    com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_SearchService?wsdl' and service factory configuration '{DynamicProxy.ClassPath=C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi_1.0.0/_cmi_api.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception_2.0.0/lib/exception.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime_2.0.0/lib/SapDictionaryTypesRuntime.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services_2.0.0/lib/SapDictionaryTypeServices.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/logging.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/loggingStandard.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/jARM.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;, DynamicProxy.Javac.path=C:\j2sdk1.4.2_19, DynamicProxy.TempDir=C:\Users\sakkav01\AppData\Local\Temp\}'
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:414)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:306)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:316)
    at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.PageRenameWS.loadNameSpacesAndModelClasses(PageRenameWS.java:435)
    at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelDialog.nextPressed(ModelDialog.java:105)
    at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:316)
    at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
    at org.eclipse.jface.window.Window.open(Window.java:563)
    at com.sap.ide.webdynpro.modeleditor.ModelEditorCallback.createModel(ModelEditorCallback.java:52)
    at com.sap.ide.webdynpro.service.modeleditor.ModelService.createModelWithUI(ModelService.java:70)
    at com.sap.ide.webdynpro.service.modeleditor.ServiceWithUI.createModel(ServiceWithUI.java:49)
    at com.sap.ide.webdynpro.tsmodel.application.provider.ModelNodeProvider.createUniqueName(ModelNodeProvider.java:55)
    at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntityUin(EntityImpl.java:936)
    at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntity(EntityImpl.java:502)
    at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.runInternal(CreationAction.java:76)
    at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.access$000(CreationAction.java:24)
    at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction$1.run(CreationAction.java:51)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
    at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.run(CreationAction.java:57)
    at com.sap.ide.webdynpro.projectbrowser.actions.PBCreateModelAction.run(PBCreateModelAction.java:95)
    at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:224)
    at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)
    at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1407)
    at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)
    at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)
    at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
    at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)
    at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
    at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
    at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
    at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
    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:324)
    at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
    at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
    at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
    at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:157)
    at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:56)
    at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:88)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:412)
    ... 52 more
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Problem with WSDL file parsing. See nested message.
    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:182)
    at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:154)
    ... 55 more
    Caused by: com.sap.engine.lib.xml.util.NestedException: IO Exception occurred while parsing file:Invalid Response Code: (-1) null. The requested URL was:"https//:xxxxxxxxxxxxxxxxxxxxx_SearchService?wsdl" -> com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (-1) null. The requested URL was:"https://xxxxxxxxxxxxxxxxxxxxxxxxxx_SearchService?wsdl"
    at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1039)
    at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadWSDLDocument(WSDLDOMLoader.java:1126)
    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:178)
    ... 56 more
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (-1) null. The requested URL was:"https://xxxxxxxxxxxxxxxxxxxx/HCP_SearchService?wsdl"
    at com.sap.engine.services.webservices.tools.WSDLDownloadResolver.resolveEntity(WSDLDownloadResolver.java:180)
    at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1019)
    ... 58 more

    Hi Vijay,
    There was some issues with the wsdl url itselft, now i got the right wsdl url and i tried with wsnavigator , i tested it works fine from there...
    but when i try to import using adaptive web service model it is throwing error..pls find the error log below...i am getting cannot load namespaces and model classes error and also some proxy error..i am giving proxy and 8080 as default...pls let me know what exact proxy settings i have to give here..
    com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'https://xxxxxxxxxxxxxxxxxxchService?wsdl' and service factory configuration '{DynamicProxy.ClassPath=C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi_1.0.0/_cmi_api.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception_2.0.0/lib/exception.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime_2.0.0/lib/SapDictionaryTypesRuntime.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services_2.0.0/lib/SapDictionaryTypeServices.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/logging.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/loggingStandard.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/jARM.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Program Files (x86)/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;, DynamicProxy.INetProxy.Bypass="*.sap.corp"|usc1-dpid01|, DynamicProxy.INetProxy.Port=8080, DynamicProxy.Javac.path=C:\j2sdk1.4.2_19, DynamicProxy.TempDir=C:\Users\sakkav01\AppData\Local\Temp\, DynamicProxy.INetProxy.Host=proxy'
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:414)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:306)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:316)
    at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.PageRenameWS.loadNameSpacesAndModelClasses(PageRenameWS.java:435)
    at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelDialog.nextPressed(ModelDialog.java:105)
    at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:316)
    at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
    at org.eclipse.jface.window.Window.open(Window.java:563)
    at com.sap.ide.webdynpro.modeleditor.ModelEditorCallback.createModel(ModelEditorCallback.java:52)
    at com.sap.ide.webdynpro.service.modeleditor.ModelService.createModelWithUI(ModelService.java:70)
    at com.sap.ide.webdynpro.service.modeleditor.ServiceWithUI.createModel(ServiceWithUI.java:49)
    at com.sap.ide.webdynpro.tsmodel.application.provider.ModelNodeProvider.createUniqueName(ModelNodeProvider.java:55)
    at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntityUin(EntityImpl.java:936)
    at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntity(EntityImpl.java:502)
    at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.runInternal(CreationAction.java:76)
    at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.access$000(CreationAction.java:24)
    at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction$1.run(CreationAction.java:51)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
    at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.run(CreationAction.java:57)
    at com.sap.ide.webdynpro.projectbrowser.actions.PBCreateModelAction.run(PBCreateModelAction.java:95)
    at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:224)
    at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)
    at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1407)
    at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)
    at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)
    at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
    at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)
    at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
    at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
    at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
    at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
    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:324)
    at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
    at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
    at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
    at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:158)
    at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:56)
    at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:92)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:412)
    ... 52 more
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Problem with WSDL file parsing. See nested message.
    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:182)
    at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:155)
    ... 55 more
    Caused by: com.sap.engine.lib.xml.util.NestedException: IO Exception occurred while parsing file:Cannot connect to https://xxxxxxxxxxxxxxxxx_SearchService?wsdl, passing via http proxy: https://usc1-dpid01:21000: Peer sent alert: Alert Fatal: illegal parameter -> java.io.IOException: Cannot connect to https://xxxxxxxxxxxx_SearchService?wsdl, passing via http proxy:proxy: Peer sent alert: Alert Fatal: illegal parameter
    at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1039)
    at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadWSDLDocument(WSDLDOMLoader.java:1126)
    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:178)
    ... 56 more
    Caused by: java.io.IOException: Cannot connect to https://xxxxxxxxxxxxxxx_SearchService?wsdl, passing via http proxy:: Peer sent alert: Alert Fatal: illegal parameter
    at com.sap.engine.services.webservices.tools.WSDLDownloadResolver.resolveEntity(WSDLDownloadResolver.java:175)
    at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1019)
    ... 58 more

  • Proxy error when consuming External Web Service (WSDL) in ABAP

    Hi all,
    I am trying to consume an external WS in ABAP but I have some issues :
    1. Is it allows to use tag <xsd:complexcontent> with restrictions and extensions in it ? If not, how can I replace it ?
    2. Do we need to still change the <complexType> structure such as :
    Coding, not working:
    <xsd:complexType name="OrderRequestMsg">
    <xsd:sequence>
    <xsd:element name="shop" type="xsd:string"/>
    u2026
    </xsd:sequence>
    </xsd:complexType>
    <message name="OrderRequest">
    <part name="input" type=" tns:OrderRequestMsg"/>
    </message>
    Coding, working::
    <xsd:element name="OrderRequestMsg">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="shop" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <message name="OrderRequest">
    <part name="input" element="tns:OrderRequestMsg"/>
    </message>
    3. When I am testing the WSDL they send me in SOAPUI, I don't have any issue but when I am trying to integrate in ABAP, it is blocking on an URL saying it cannot find it  (the URL http://fk.se/SHS/xsd/tanden)
    <xsd:schema version="20110317" targetNamespace="http://fk.se/SHS/xsd/tanden" xmlns:tns="http://fk.se/SHS/xsd/tanden" xmlns:xmime="http://www.w3.org/2005/05/xmlmime" elementFormDefault="qualified" attributeFormDefault="unqualified">
    Do I need to change something ? Since when I am modifying it, it cannot find the type reference afterwards...
    Thanks in advance for your answer.

    Hy Brad, I got the same error by trying to generate a 'Consumer Proxy' from a external WSDL. u2019Incorrect value: XSD name space not available'. I have solved it in this way: The report RSSIDL_DESERIALIZE_DEMO has the same check routines as the R3-Proxy Generator. I debugged this report using a saved external WSDL and compared it with using a saved WSDL (Server) generated under /nse80.
    -> In the WSDL, in part message the "type" isnu2019t allowed, because the dezerialization is done already.
    Coding, not working:
    <xsd:complexType name="OrderRequestMsg">
      <xsd:sequence>
         <xsd:element name="shop" type="xsd:string"/>
          u2026
      </xsd:sequence>
    </xsd:complexType>
    <message name=" OrderRequest">
      <part name="input" type=" tns:OrderRequestMsg"/>
    </message>
    Coding, working::
    <xsd:element name="OrderRequestMsg">
        <xsd:complexType>
           <xsd:sequence>
            <xsd:element name="shop" type="xsd:string"/>
       </xsd:sequence>
      </xsd:complexType>
    </xsd:element>
    <message name="OrderRequest">
         <part name="input" element="tns:OrderRequestMsg"/>
    </message>

  • Error when calling an external web service (blank soap action)

    I did a lot of searching on this message and did not find an answer. Most of the issues i found related to XI/PI, which we are not using.
    There is a web service created outside of SAP for which i generated (from the WSDL) a proxy class in my DEV system, client 050, a few years ago. This was subsequently moved to QA and production, and all is working fine.
    Now, i want the same web service to work in client 100. I created the logical port, and the RFC destination, but when i try to call the web service, i get the following error
    Server did not recognize the value of HTTP Header SOAPAction
    Since only the basis group around here can access the logical port definition,and rfc destination, i have no idea where this information should be set up. I should not have to reimport the WSDL, since the proxy was imported from DEV to QA and it is working in QA client 050. There is something i need to set up, specific to client 100, and i am missing it. I looked in SOAMANAGER, and i didnt see anything even set up  there for client 050, so i did set up anything for client 100.
    Any help would be appreciated.

    I tried adding the web reference in a console app and works fine. In the plugins this can't be done, because the plugins are deploy in database.
    I tried another basic test using ChannelFactory. Only want to retrieve some entity through the external web services:
    IPluginExecutionContext context = localContext.PluginExecutionContext;
    IOrganizationService service = localContext.OrganizationService;
    ITracingService tracer = localContext.TracingService;
    try
    BasicHttpBinding binding = new BasicHttpBinding();
    binding.Name = "BasicHttpBinding_IAxxisWcfServices";
    binding.Security.Mode = BasicHttpSecurityMode.None;
    binding.Security.Transport.ProxyCredentialType = HttpProxyCredentialType.None;
    binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.None;
    EndpointAddress endpoint = new EndpointAddress(@"http://*****.svc");
    ChannelFactory<IAxxisWcfServices> factory = new ChannelFactory<IAxxisWcfServices>(binding, endpoint);
    IAxxisWcfServices channel = factory.CreateChannel();
    var entity = channel.FindByEntities(new CRM.Application.Context.Dtos.Asegurado( { CrmGuid = "7C3E96C6-C3BC-E411-80DF-0A736AE14667" }, null, new CRM.Framework.Session() { User = "***", Password = "***" });
    catch (Exception ex)
    throw new InvalidPluginExecutionException(ex.Message);
    That test threw the following exception on the GenericParameterAttributes of channelType of factory object:
    http://s27.postimg.org/4wf3er8up/Error.png

  • Issue when calling an external web service - CRM 2013

    Hello everyone.
    This is my scenario:
    I'm doing a real time data integration from CRM to another software. I deployed several plugins, mostly in create/update messages, for the entities i want to sync. The developers of the other software gave me the endpoint of the web service and I created the
    client using svcutil. I manually created the binding and gave it to the generated client, along with the endpoint. At the first tests I could sync some registries, but I had some mapping errors. I debugged the plugin, corrected the errors, and when I
    want to tests again, the plugin is throwing me an exception when calls any method of the web service. Let me explain the issue:
    The exception:
    I instantiated the client for the web service (passing to it the binding and the endpoint). And when I'm trying to call any method (ex. Add), it throws the exceptions "InvalidOperationException". I started to debug the code and I notice that
    just before to call the web service method, the state of the client stills in "Opening". Of course that is generating the exception. 
    The complete exception is: "The communication object, System.ServiceModel.ChannelFactory`1[IAxxisWcfServices], cannot be modified while it is in the Opening
    state."} System.SystemException {System.InvalidOperationException}
    I did a test, outside the CRM environment, on a console app with the same conditions of the web services client (generating with svcutil, manually passing the same binding and endpoint), and the same order of the plugin code, and everything works well; The
    state of the client never stills in 'Opening', so I discarded any problem with the web service.
    Anyone knows if I'm missing something in the code? or some configuration?
    The CRM is 2013 On-premise with last updates.
    Thanks in advance.

    I tried adding the web reference in a console app and works fine. In the plugins this can't be done, because the plugins are deploy in database.
    I tried another basic test using ChannelFactory. Only want to retrieve some entity through the external web services:
    IPluginExecutionContext context = localContext.PluginExecutionContext;
    IOrganizationService service = localContext.OrganizationService;
    ITracingService tracer = localContext.TracingService;
    try
    BasicHttpBinding binding = new BasicHttpBinding();
    binding.Name = "BasicHttpBinding_IAxxisWcfServices";
    binding.Security.Mode = BasicHttpSecurityMode.None;
    binding.Security.Transport.ProxyCredentialType = HttpProxyCredentialType.None;
    binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.None;
    EndpointAddress endpoint = new EndpointAddress(@"http://*****.svc");
    ChannelFactory<IAxxisWcfServices> factory = new ChannelFactory<IAxxisWcfServices>(binding, endpoint);
    IAxxisWcfServices channel = factory.CreateChannel();
    var entity = channel.FindByEntities(new CRM.Application.Context.Dtos.Asegurado( { CrmGuid = "7C3E96C6-C3BC-E411-80DF-0A736AE14667" }, null, new CRM.Framework.Session() { User = "***", Password = "***" });
    catch (Exception ex)
    throw new InvalidPluginExecutionException(ex.Message);
    That test threw the following exception on the GenericParameterAttributes of channelType of factory object:
    http://s27.postimg.org/4wf3er8up/Error.png

  • Consuming an External Web Service using HTTPS and WS Security

    Hello everyone,
    I'm having a problem setting the security information in a SOAP header using a generated ABAP Client Proxy to consume an external web service that requires a User ID and Password in the Header section of the SOAP message.  I need to use HTTPS. I'm on a WAS 7.01 SP08 system so from my readings, SAP is supposed to be able to add the username and password into the header section of the message.  I can't seem to get SAP to add this information added to the header.
    Here are the steps that I have taken to set the security values.
    1) Created the client proxy from the WSDL in SE80.  Basic Authentication on the Configuration tab was turned on automatically.
           Note, Transport Security is set to None.  I cannot change it.
    2) Created an outbound set user name profile in transaction WSPROFILE with the appropriate username and password.
    3) Added the profile to the default port in transaction LPCONFIG as an outbound under the WS Security section of the screen.
    When I called the external Web Service, I got back the following error message:
    com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC5509E: A security token whose type is [http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#UsernameToken] is required.
    So, after reading through this Forum, I saw that I needed to use the SOAMANAGER.  I set up a Proxy in the SOAMANAGER and manually created the Logical Port.  This was the only way I could figure out how to set the Authentication Settings in the Logical Port to "User ID / Password".  I then entered the User ID and Password.
    However, I am still getting the same error message.  I feel I am close but missing some small configuration to tell SAP to use WS Security with a Username token.
    I'm not sure what I'm doing wrong, so any help would be appreciated.
    Thanks,
    Stephen

    I had this error again so I thought I would post my solution:
    The issue is SAP needs to know the certificates being used by the web site being called.  These certificates are automatically installed in your browser but need to be manually installed in SAP.  This is what I did:
    How to find/install new certificates
    Make sure you run Internet Explorer as an Administrator so you can export the certificates
    Go to the web site that SAP is trying to call in Internet Explorer
    Double click on the lock in the address bar
    View certificates
    Find the certificates that are being used
    Tools --> Internet Options --> Content --> Certificates
    Click on the “Trusted Root Certification Authorities” tab
    Find the certificate identified in step iii
    Export as a CER certificate
    Click on the “Intermediate Certification Authorities” tab
    Find the certificate identified in step iii
    Export as a CER certificate
    Go to STRUST in SAP
    Import the Certificates in the “Anonymous” or “Standard” SSL client
    Save
    RESTART the ICM via t-code SMICM  <-- Critical!!!
    Test

  • Use BizTalk 2006 as a proxy for an external Web Service

    Hi
    We have a solution that is going to work just as a proxy for an external Web Service.
    It works like this:
    1. We have a Request-Response receive port that receives the calls for the WS.
    2. Different Static Solicit-Response ports that have filters for each method in the WS receive the requests and then send them to the external WS.
    3. The response from the external WS is then sendt back to the caller via the Request-Response port in point 1.
    This generally works like it should. The only problem i have is when the external WS returns a Fault message. I get this fault from the external WS:
    <s:Fault xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>s:Client</faultcode><faultstring xml:lang="nb-NO">Some error message the caller should see.</faultstring><detail><GenericFault
    xmlns="http://register.test.com/Common" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><ErrorCode>SomthingWentWrong</ErrorCode><Message>Some error message the caller should see.</Message></GenericFault></detail></s:Fault>
    This message then failes on BizTalk and BizTalk returns this Fault message to the caller:
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP:Body><SOAP:Fault><faultcode>Microsoft BizTalk Server Negative Acknowledgment
    </faultcode><faultstring>An error occurred while processing the message, refer to the details section for more information </faultstring><faultactor>/Hemit.BizTalk.NHN.Position.ws/IPositionService.asmx</faultactor><detail><ns0:NACK
    Type="NACK" xmlns:ns0="http://schema.microsoft.com/BizTalk/2003/NACKMessage.xsd"><NAckID>{7AC314FE-2CA3-44AE-8208-180495500481}</NAckID><ErrorCode>0xc0c016b7</ErrorCode><ErrorCategory>0</ErrorCategory><ErrorDescription>There
    is an error in XML document (1, 2).</ErrorDescription><ErrorDetail>&lt;Fault xmlns='http://schemas.xmlsoap.org/soap/envelope/'&gt; was not expected.</ErrorDetail></ns0:NACK></detail></SOAP:Fault></SOAP:Body></SOAP:Envelope>
    So the problem seems to be that the Request-Response port in point one will ONLY accept the real response that is specified in the response schema for that particular method, and not a Fault. And when it receives a fault, it generates its own Fault saying
    a Fault message was not expected.
    Does anyone know how i can be able to send the actual fault from the external WS all the way back to the caller on the inside?
    I know how to do it with an orchestration, but can not figure out how to get it done just with the ports.
    Kind regars
    John Viggo

    Hi John,
    Enable Propagate fault message
    on the WCF solict –response port.
    For the two-way send port, you can choose whether to forward
    SOAP fault messages on to the original caller over a solicit-response send port by selecting
    Propagate fault message. If this option is not selected, BizTalk Server will generate a NACK. What you see is the NACK.
    If it is selected, BizTalk Server will treat the message as a valid WCF response message from the external service and the response message will not be suspended because it is propagated.
    Then you need to map the fault message to the actual response in the map. Set this Fault-Message to Caller-Response map in the outbound map of the Requeust-Response port.
    In this case of messaging-only scenario, this method shall help in handling the fault message and passing fault details back to the caller. Refer the following articles for more details.
    Synchronous web services calls and Faults
    BizTalk and
    SOAPFault
    version issues
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.

  • Error testing external web service ICM_HTTP_CONNECTION_FAILED

    Hi All,
    I have created proxy class to consume external web service also created logical port but while testing the service through SE80, I am facing error "SOAP:1,023 SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED")" I have gone through many threads for similar error but not able to resolve the issue. I have tried various WSDL from samples given in sdn but still facing same error. Also tried to access any external URL through sample program as follows, but it gives same error while receive method (400 ICM_HTTP_CONNECTION_FAILED)
    sample used program to call URL : gets dump with error(400 ICM_HTTP_CONNECTION_FAILED)
    report zsant.
    DATA: client TYPE REF TO if_http_client,
          html TYPE string.
    ****Create the HTTP client
    TRY.
        CALL METHOD cl_http_client=>create_by_url
          EXPORTING
            url    = 'http://www.google.com/'
          IMPORTING
            client = client
          EXCEPTIONS
            OTHERS = 1.
        client->send( ).
        client->receive( ).
        html = client->response->get_cdata( ).
        write: / html.
        client->close( ).
      CATCH cx_root.
        WRITE: / 'HTTP Connection error'.
    ENDTRY.
    also tried activating services in SICF, didnt worked. so please suggest if any solution for this, are there any basic settings we need to do to the SAP system before cosuming or working on web services?
    SAP version: EHP4 FOR SAP ERP 6.0 / NW7.01
    Edited by: santrosh on Feb 27, 2010 10:21 AM

    <p>Hello,</p>
    <p> </p>
    <p>The first thing you should do is to check that your application server can reach the service your are trying to call. I suggest to try a:</p>
    <p> </p>
    <p>telnet &lt;remote_service_url&gt; &lt;remote_service_port&gt;</p>
    <p> </p>
    <p>from the command line of your server.</p>
    <p> </p>
    <p>You should get a blank screen if your server reaches the remote server and something like connecting to &lt;remote_service_url&gt; if you don't.</p>
    <p> </p>
    <p>Yours,</p>
    <p> </p>
    <p>Joseba M. Iturbe</p>

  • Error while trying to call external  web service from oracle PL/SQL 10.2 g

    Hi I am trying to call an external web service from oracle PL/SQL .I am getting following run time error when I try to set the opeartion style.
    But as per the oracle documentation this is one of the 2 valid values.
    ORA-29532: Java call terminated by uncaught Java exception: operation style: "document" not supported.Teh webservice does expect the operation style as document.
    Following is the code I am executing.
    FUNCTION email
    return varchar2
    AS
    service_ SYS.utl_dbws.SERVICE;
    call_ SYS.utl_dbws.CALL;
    service_qname SYS.utl_dbws.QNAME;
    port_qname SYS.utl_dbws.QNAME;
    operation_qname SYS.utl_dbws.QNAME;
    string_type_qname SYS.utl_dbws.QNAME;
    retx ANYDATA;
    retx_string VARCHAR2(1000);
    retx_double number;
    retx_len number;
    params SYS.utl_dbws.ANYDATA_LIST;
    l_input_params SYS.utl_dbws.anydata_list;
    l_result ANYDATA;
    l_namespace VARCHAR2(1000);
    begin
    -- open internet explorer and navigate to http://webservices.imacination.com/distance/Distance.jws?wsdl
    -- search for 'targetNamespace' in the wsdl
    l_namespace := 'http://service.xmlservices.global.freedomgroup.com/';
    -- search for 'service name' in the wsdl
    service_qname := SYS.utl_dbws.to_qname(l_namespace, 'ClientCoreWebServiceBeanService');
    -- this is just the actual wsdl url
    service_ := SYS.utl_dbws.create_service(HTTPURITYPE('http://hostname/GlobalWebServices/services/ClientCoreWebService?wsdl'), service_qname);
    -- search for 'portType name' in the wsdl
    port_qname := SYS.utl_dbws.to_qname(l_namespace, 'ClientCoreWebServiceBeanPort');
    -- search for 'operation name' in the wsdl
    -- there will be a lot, we will choose 'getCity'
    operation_qname := SYS.utl_dbws.to_qname(l_namespace, 'postalCodelookup');
    -- bind things together
    call_ := SYS.utl_dbws.create_call(service_, port_qname, operation_qname);
    -- default is 'FALSE', so we make it 'TRUE'
    SYS.utl_dbws.set_property(call_, 'SOAPACTION_USE', 'TRUE');
    -- search for 'operation soapAction' under <wsdl:operation name="getCity">
    -- it is blank, so we make it ''
    SYS.utl_dbws.set_property(call_, 'SOAPACTION_URI', '');
    -- search for 'encodingstyle' under <wsdl:operation name="getCity">
    SYS.utl_dbws.set_property(call_, 'ENCODINGSTYLE_URI', 'http://schemas.xmlsoap.org/soap/encoding/');
    -- search for 'binding style'
    SYS.utl_dbws.set_property(call_, 'OPERATION_STYLE', 'DOCUMENT');
    -- search for 'xmlns:xs' to know the value of the first parameter
    -- under <wsdl:message name="getCityResponse"> you will see the line <wsdl:part name="getCityReturn" type="xsd:string" />
    -- thus the return type is 'string", removing 'xsd:'
    string_type_qname := SYS.utl_dbws.to_qname('http://www.w3.org/2001/XMLSchema', 'string');
    -- in the line <wsdl:operation name="getCity" parameterOrder="zip">
    -- the parameterOrder is 'zip', thus we put in 'zip'
    -- the 'ParameterMode.IN' is used to specify that we will be passing an "In Parameter" to the web service
    -- the 'ParameterMode.IN' is a constant variable in the sys.utl_dbws package
    --vj this cud be either params or xml
    SYS.utl_dbws.add_parameter(call_, 'param1', string_type_qname, 'ParameterMode.IN');
    SYS.utl_dbws.add_parameter(call_, 'param2', string_type_qname, 'ParameterMode.IN');
    SYS.utl_dbws.set_return_type(call_, string_type_qname);
    -- supply the In Parameter for the web service
    params(0) := ANYDATA.convertvarchar('<TFGGlobalBasicXMLDO><systemCd>GLOBAL</systemCd><username>GlobalAdmin</username><password>GlobalAdmin</password><localID>1</localID></TFGGlobalBasicXMLDO>');
    params(1) := ANYDATA.convertvarchar('<TFGGlobalPostalCodeLookupIDDO><postalCode>02446</postalCode><countryCode>USA</countryCode><stateCode>MA</stateCode><cityDisplay>BROOKLINE</cityDisplay><countyDisplay>NORFOLK</countyDisplay><include_inactive_flag>True</include_inactive_flag></TFGGlobalPostalCodeLookupIDDO>');
    -- invoke the web service
    retx := SYS.utl_dbws.invoke(call_, params);
    dbms_output.put_line(retx.gettypename);
    -- access the returned value and output it to the screen
    retx_string := retx.accessvarchar2;
    dbms_output.put_line('done' || retx_string);
    dbms_output.put_line('PL/SQL DII client return ===> ' || retx_string);
    -- release the web service call
    SYS.utl_dbws.release_service(service_);
    return retx_string;
    end email;

    thsi is urgent anybody ????

Maybe you are looking for

  • QS 867 Mhz processor in a QS 2002 motherboard??

    Hi there. I'm trying to get a Quicksilver 867 Mhz processor (with L3 cache) to run in a Quicksilver 2002 motherboard, but it ain't working. I've been pretty consistent in my troubleshooting, but before I toss it out (or try soldering the L3 cache ont

  • WebLogic Datasources : Automatically Shutdown and Start up

    Hi there, I have a problem with my datasources, I have WLST script which shutdown and start automatically some datasources in my environment, all of them in my crontab ! Follow exactly my script ! [weblogic@wls_server restartDS]$ cat shutdownDS1.py |

  • PO Value exceeded the ION Budget Value

    We are able to add more value to the PO than the budgeted ION value attached to the PO .This is a standard SAP  functionality that it should not allow the PO value to be more than the ION budget .Not able to arrive  how this can happen .If some one c

  • Function module in ST03N for user to transaction info

    Hi, we are running ECC 5.0 and have a requirement to find out which users have executed certain transactions in a period of time (e.g. month, week). ST03N gives these details, however, we need to run this for several transactions and multiple periods

  • Change Software Updates deployment priority

    Hi We use SCCM 2012 R2 CU2. whenever a new client is being installed and registered it gets its policies and deployments. our problem is that there are many software updates that being deployed and it takes a very long time until they finish their in