Import SAP WSDL into External Definition

Hi Friends,
I'd like to import a WSDL into XI External Definition. However, the WSDL is gained from Web AS Web Service Navigator. So it is a zip file and consists of three WSDL files. How can I import them into the external definition?
Thanks + Regards
Jerome

Hi Jerome,
If you have three wsld files then aren't those three messages?
have you tried importing them as external definitions one by one?
you can check how the message structre looks like
when you try to use the external definition inside a
message mapping (remember you don't create message type from external definitions)
Futher reference:
http://help.sap.com/saphelp_nw04/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm
BTW
while creating external defnitions (WSDL)
you can only choose wsld file or XML - nothing else
Regards,
michal

Similar Messages

Importing WSDL into External Definitions

Hi,
I got WSDLs from WAS WS Navigator, I have imported the WSDL from porttypes folder but I don't see any messages in the messages tab of External Definitions.
See below my WSDL
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns0="urn:xEM_MeasurementImportVi" targetNamespace="urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document" xmlns:tns="urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document">
<wsdl:types>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:java/lang" xmlns:tns="urn:java/lang" elementFormDefault="qualified">
 <xs:complexType name="ArrayOfint">
 <xs:sequence>
 <xs:element maxOccurs="unbounded" minOccurs="0" name="int" type="xs:int" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="ArrayOfString">
 <xs:sequence>
 <xs:element maxOccurs="unbounded" minOccurs="0" name="String" type="xs:string" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:schema>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:com.technidata.em.imp.consumption" xmlns:tns="urn:com.technidata.em.imp.consumption" elementFormDefault="qualified">
 <xs:complexType name="ReturnCode">
 <xs:sequence>
 <xs:element name="code" type="xs:int"/>
 <xs:element name="description" type="xs:string" nillable="true" minOccurs="0"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="ArrayOfReturnCode">
 <xs:sequence>
 <xs:element maxOccurs="unbounded" minOccurs="0" name="ReturnCode" type="tns:ReturnCode" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:schema>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:com.technidata.em" xmlns:tns="urn:com.technidata.em" elementFormDefault="qualified">
 <xs:complexType name="Measurement">
 <xs:sequence>
 <xs:element name="pSystemId" type="xs:string" nillable="true" minOccurs="0"/>
 <xs:element name="pSystemTagId" type="xs:string" nillable="true" minOccurs="0"/>
 <xs:element name="pDate" type="xs:dateTime" nillable="true" minOccurs="0"/>
 <xs:element name="pValue" type="xs:double"/>
 <xs:element name="pUnit" type="xs:string" nillable="true" minOccurs="0"/>
 <xs:element name="pDescription" type="xs:string" nillable="true" minOccurs="0"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="ArrayOfMeasurement">
 <xs:sequence>
 <xs:element maxOccurs="unbounded" minOccurs="0" name="Measurement" type="tns:Measurement" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:schema>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:xEM_MeasurementImportVi" xmlns:tns="urn:xEM_MeasurementImportVi" elementFormDefault="qualified" xmlns:s1="urn:java/lang" xmlns:s2="urn:com.technidata.em.imp.consumption" xmlns:s0="urn:com.technidata.em">
 <xs:import namespace="urn:java/lang"/>
 <xs:import namespace="urn:com.technidata.em.imp.consumption"/>
 <xs:import namespace="urn:com.technidata.em"/>
 <xs:element name="checkConnection">
 <xs:complexType>
 <xs:sequence/>
 </xs:complexType>
 </xs:element>
 <xs:element name="checkConnectionResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="xs:string" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="doMeasurementImport">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="pSystemId" type="xs:string" nillable="true"/>
 <xs:element name="pSystemTagId" type="xs:string" nillable="true"/>
 <xs:element name="pDate" type="xs:dateTime" nillable="true"/>
 <xs:element name="pValue" type="xs:double"/>
 <xs:element name="pUnit" type="xs:string" nillable="true"/>
 <xs:element name="pDescription" type="xs:string" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="doMeasurementImportResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="xs:int"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="doMeasurementsImport">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="pMeasurements" type="s0:ArrayOfMeasurement" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="doMeasurementsImportResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="s1:ArrayOfint" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="getErrorCodes">
 <xs:complexType>
 <xs:sequence/>
 </xs:complexType>
 </xs:element>
 <xs:element name="getErrorCodesResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="s2:ArrayOfReturnCode" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="getSupportedUnits">
 <xs:complexType>
 <xs:sequence/>
 </xs:complexType>
 </xs:element>
 <xs:element name="getSupportedUnitsResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="s1:ArrayOfString" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 </xs:schema>
</wsdl:types>
<wsdl:message name="checkConnectionIn_doc">
 <wsdl:part name="parameters" element="ns0:checkConnection"/>
</wsdl:message>
<wsdl:message name="checkConnectionOut_doc">
 <wsdl:part name="parameters" element="ns0:checkConnectionResponse"/>
</wsdl:message>
<wsdl:message name="doMeasurementImportIn_doc">
 <wsdl:part name="parameters" element="ns0:doMeasurementImport"/>
</wsdl:message>
<wsdl:message name="doMeasurementImportOut_doc">
 <wsdl:part name="parameters" element="ns0:doMeasurementImportResponse"/>
</wsdl:message>
<wsdl:message name="doMeasurementsImportIn_doc">
 <wsdl:part name="parameters" element="ns0:doMeasurementsImport"/>
</wsdl:message>
<wsdl:message name="doMeasurementsImportOut_doc">
 <wsdl:part name="parameters" element="ns0:doMeasurementsImportResponse"/>
</wsdl:message>
<wsdl:message name="getErrorCodesIn_doc">
 <wsdl:part name="parameters" element="ns0:getErrorCodes"/>
</wsdl:message>
<wsdl:message name="getErrorCodesOut_doc">
 <wsdl:part name="parameters" element="ns0:getErrorCodesResponse"/>
</wsdl:message>
<wsdl:message name="getSupportedUnitsIn_doc">
 <wsdl:part name="parameters" element="ns0:getSupportedUnits"/>
</wsdl:message>
<wsdl:message name="getSupportedUnitsOut_doc">
 <wsdl:part name="parameters" element="ns0:getSupportedUnitsResponse"/>
</wsdl:message>
<wsdl:portType name="xEM_MeasurementImportVi_Document">
 <wsdl:operation name="checkConnection">
 <wsdl:input message="tns:checkConnectionIn_doc"/>
 <wsdl:output message="tns:checkConnectionOut_doc"/>
 </wsdl:operation>
 <wsdl:operation name="doMeasurementImport">
 <wsdl:input message="tns:doMeasurementImportIn_doc"/>
 <wsdl:output message="tns:doMeasurementImportOut_doc"/>
 </wsdl:operation>
 <wsdl:operation name="doMeasurementsImport">
 <wsdl:input message="tns:doMeasurementsImportIn_doc"/>
 <wsdl:output message="tns:doMeasurementsImportOut_doc"/>
 </wsdl:operation>
 <wsdl:operation name="getErrorCodes">
 <wsdl:input message="tns:getErrorCodesIn_doc"/>
 <wsdl:output message="tns:getErrorCodesOut_doc"/>
 </wsdl:operation>
 <wsdl:operation name="getSupportedUnits">
 <wsdl:input message="tns:getSupportedUnitsIn_doc"/>
 <wsdl:output message="tns:getSupportedUnitsOut_doc"/>
 </wsdl:operation>
</wsdl:portType>
</wsdl:definitions>
Appreciate your quick response.
Srini Sandaka

Hi,
I diagnose the problem, the problem with the name space length.
Orginal NameSpace: urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document
Modified NameSpace: urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/documen
The External Definitions is recognizing only 60 characters namespace. If the namespace exceed 60 characters it is not showing any messages in the messages tab.
Will make any problem to call the WebService from XI since we are changing the original namespace in the WSDL and imported into XI.
How can we overcome this problem, is it a limitation.
Thanks
Srini Sandaka

Problem Loading WSDL in External Definition

Hello people,
i'm having some problems When i'm Importing the WSDL in external definitions, the Messages are not being Recognized, it doesnt load the message structures, if i try in any other program that uses the WSDL like SoapUI, the wsdl works fine.
Here is the WSDL links
http://siatepqa.suseso.cl:8888/Siatep/WSToken?wsdl
http://siatepqa.suseso.cl:8888/Siatep/WSIngreso?wsdl
http://siatep.suseso.cl:8888/SusesoSiatep/WSToken?wsdl
http://siatep.suseso.cl:8888/SusesoSiatep/WSIngreso?wsdl
anyone can help?

Hi,
http://siatepqa.suseso.cl:8888/Siatep/WSToken?wsdl
I checked the WSDL from the above link. The issue that I noticed is that you are importing the schema structure in your above WSDL. PI is unable to recognize the external reference. SOAPUI (or similar tool) will recognize the external reference.
Best option is that you should re-modify your above WSDL and provide the schema in this WSDL itself. It should then work just fine.
Hope this helps.
Regards,
Neetesh

"Messages" problem after importing .xsd file as external definition

Hello,
I received an .xsd file from a customer and need to import it as an "External Definition" in order to create the "Message Interface". The structure of the xsd looks like this:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:px="http://www.opentrans.org/XMLSchema/1.0" targetNamespace="http://www.opentrans.org/XMLSchema/1.0" elementFormDefault="qualified">
<xsd:element name="ORDER">
</xsd:element>
<xsd:element name="ADDRESS">
</xsd:element>
<xsd:element name="ARTICLE_ID">
</xsd:element>
</xsd:schema>
After importing and looking at the tab "Messages" I get numerous entries, for each <xsd:element> I get one message! But I basically only need one "Message" that holds my complete xsd-file.
I tried inserting <xsd:element name="COMPLETEORDER"> right after the <xsd:schema>-Tag but that didn't work either. Somehow I need to sum up all the <xsd:elements>.
Does anyone have an idea? Thank you very much!
Peter

Hello Prateek, Hello everyone,
I now know what the problem is. I downloaded XMLspy and checked on the structure:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:px="http://www.opentrans.org/XMLSchema/1.0" targetNamespace="http://www.opentrans.org/XMLSchema/1.0" elementFormDefault="qualified">
<xsd:element name="ORDER">
</xsd:element>
<xsd:element name="ADDRESS">
</xsd:element>
<xsd:element name="ARTICLE_ID">
</xsd:element>
<xsd:simpleType name="dtBOOLEAN">
</xsd:simpleType>
<xsd:simpleType name="dtCOUNTRIES">
</xsd:simpleType>
<xsd:element name="SUPPLIER_AID">
</xsd:element>
<xsd:simpleType name="typeSUPPLIER_AID">
</xsd:simpleType>
</xsd:schema>
Between the long list of <xsd:element> tags there are some simpleTypes on the same
level. Now if I insert
<xsd:element name="COMPLETEORDER">
<xsd:complexType>
<xsd:sequence>
on top, the <xsd:sequence> would be on the same level as the simpleTypes - which is not valid!
But can I just move all the simpleTypes, e.g. into an <xsd:element>??
That would be changing the customer's structure which I think is not a good thing!?
Thank you again for your help! I really appreciate it!
Best regards,
Peter

Problem while importing the wsdl into Dynpro ?

HI Guys,
I have developed a webservice within xi in the integration directory and while importing this wsdl into webdynpro i am getting the following error
!ENTRY com.sap.ide.ws.proxygenerator 4 -1 Okt 10, 2007 19:02:23.788
!MESSAGE com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Problem with WSDL file parsing. See nested message.
!STACK 0
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.getDefaultSchemaMapping(ProxyGenerator.java:110)
at com.sap.ide.ws.proxygenerator.ProxyHelperFunctions.createNamespacePackageMappingFile(ProxyHelperFunctions.java:103)
at com.sap.ide.ws.proxygenerator.ProxyHelperFunctions.createNamespacePackageMappingFile(ProxyHelperFunctions.java:86)
at com.sap.ide.ws.proxygenerator.ProxyHelperFunctions.createNamespacePackageMappingFile(ProxyHelperFunctions.java:82)
at com.sap.ide.wsproxy.wizards.prx.pages.NamespacePackageMappingPage$1.run(NamespacePackageMappingPage.java:114)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:357)
at com.sap.ide.wsproxy.wizards.prx.pages.NamespacePackageMappingPage.initTable(NamespacePackageMappingPage.java:170)
at com.sap.ide.wsproxy.wizards.prx.pages.NamespacePackageMappingPage.setVisible(NamespacePackageMappingPage.java:295)
at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:959)
at org.eclipse.jface.wizard.WizardDialog.access$1(WizardDialog.java:940)
at org.eclipse.jface.wizard.WizardDialog$3.run(WizardDialog.java:929)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:927)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:684)
at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelDialog.nextPressed(ModelDialog.java:218)
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 com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
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.lib.xml.util.NestedException: Parser exception occurred:Fatal Error: com.sap.engine.lib.xml.parser.ParserException: = expected in attlist(C:\Paymetric Transfer\PaymentAuthorisationcard.wsdl, row:3, col:992) -> com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: = expected in attlist(C:\Paymetric Transfer\PaymentAuthorisationcard.wsdl, row:3, col:992)(C:\Paymetric Transfer\PaymentAuthorisationcard.wsdl, row=3, col=992) -> com.sap.engine.lib.xml.parser.ParserException: = expected in attlist(C:\Paymetric Transfer\PaymentAuthorisationcard.wsdl, row:3, col:992)
at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1032)
at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadWSDLDocument(WSDLDOMLoader.java:1125)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.getDefaultSchemaMapping(ProxyGenerator.java:107)
... 63 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: = expected in attlist(C:\Paymetric Transfer\PaymentAuthorisationcard.wsdl, row:3, col:992)(C:\Paymetric Transfer\PaymentAuthorisationcard.wsdl, row=3, col=992) -> com.sap.engine.lib.xml.parser.ParserException: = expected in attlist(C:\Paymetric Transfer\PaymentAuthorisationcard.wsdl, row:3, col:992)
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)
at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1022)
... 65 more
Caused by: com.sap.engine.lib.xml.parser.ParserException: = expected in attlist(C:\Paymetric Transfer\PaymentAuthorisationcard.wsdl, row:3, col:992)
at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1565)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1710)
at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841)
at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841)
at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841)
at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841)
at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:204)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:263)
at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
... 67 more
any help would be appreciated
Thanks,
srini

Hi,
If the import fails with the message that certain instances of the CIM class SAP_AssociatedContext were not imported, repeat the import. These errors are caused by an incorrect sort order in the export file. When starting the import again ignore the warning that data already exists. Choose Import anyway.
Also go through this Document.
http://help.sap.com/bp_bpmv130/Documentation/Operation/SystemContentCopy.pdf
Regards,
Akshay Jamgaonkar.
Reward points if find useful.

No messages under the 'Messages' tab for imported WSDL in External Definitions

Dear All,
I import this WSDL to the External Definitions but it is not showing any messages in the 'Messages' tab while WSDL clearly has message interfaces in it. Attached is the WSDL. You help is very much appreciated.
Regards,
Adil Khalil

Hi, imported wsdl shouldn't have any import instruction.
All import instruction should be changed to content of importing file.
I see the code <xsd:import namespace="http://ouaf.oracle.com/"/> in your file.
Hmm. but I imported you file and everything is fine
Message was edited by: Mikhail Koshkin

How can I import my DVD into extern Hardisk to save them?

How can I import my Dvd (iM ovie) into extern Harddisk to save them?

Hi
Disk Utility tool should be able to make a DiskImage of Your DVD (only work for non commercial DVDs)
Yours Bengt W

Error While importing SAP query into quality system

Hi,
When Itried to import the dataset(Transport Request) generated in develoment system into Quality system I am getting the following error.
Query already exists and Infoset contains a structures which is not there in data dictionary .
How to oversome this error to import successfully into quality system
thanks

hi,
You need to transport your Z tables to the quality.
Make sure you transport all the data elements , domain.. etc to the quality.
Thats why its giving you the error.
It does not find the Z tables in Quality
Regards,
Vinod

Erro when importing SAP roles into BO Edge XI 3.1

Hello,
I'm currently setting up the SAP Best Practices on a BO Edge XI 3.1 system (32 bit) and trying to link up with an SAP ECC 6 EHP 4 system (64-bit).
When getting to the authorisation step I go to the CMC > Authentication > SAP > Role IMport.
There I receive following error:
JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC' JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc. Found version "2.1.9 (2010-01-28)" but required version "2.1.8 (2006-12-11)".
After closing and re-entering the same tab I receive following message: org.apache.jasper.JasperException
I have not even the possibility to enter the roles manually. The system doesn't allow me.
There is no specific SNC security set up for my SAP system.
I have been able to connect to the logical system of SAP because when I updated on the tab: "Entitlement Systems" it proposed my logical system name that I created in SAP.
As I found on another SAP forum the version 2.1.9 should also be the good version.
Can someone help me out with this one (does anyone has still the older SAP Java connector version 2.1.8)?
thanks in advance
Thierry

Hello,
That's what i did but didn't help.
I finally managed to find the problem. I had also to install a file named librfc32.dll in the same directory. When installing the necessary files apparently the version of this file librfc32.dll was not the correct one because it didn't match with the version that is installed together with the Sap gui (I presume). So by re-installing the former version of this file librfc32.dll it finally worked.
thanks anyway

"Connection Interruped" frequently while importing xsd into External Defini

Hi All,
Whenever I try to create a new External Definition and try to import an XSD into it from my local system or share drive the connection gets interrupted. Afterthat even I provide right credentials I am not able to log into the server successfully.
I am able to successfully create other objects but only when I am importing an XSD into External Definition I am getting this issue.
If anyone came across similar situation earlier and were able to overcome this please let me know how to handle this situation.
Thanks in advance.
Regards,
Sarat

Hi Sarat,
Are you getting any error message ? If so what is the error message?
This is weird one which I never heard.
Check SAP Note: 1255351
Thanks,

File to multiple Idocs using external definitions.

Hi all,
I have to create multiple idocs based on one field from source side.
Inorder to do this..I have decided to change the occurance of Idoc from 1 to 1..unbounded , in the xsd i have downloaded from standard Idoc.
which i have a plan to map to the filed , based on that i need to create new Idoc.
I have tried importing the modified xsd into external definition. but how i should relate it to standard idoc which I have mapped earlier?.
Thanks,
venu.

HI Venu,

I have tried importing the modified xsd into external definition. but how i should relate it to standard idoc which I have mapped earlier?.
After changing the Idoc occurence , you have imported the xsd into external definition. So this will act as as new message type for you in the mapping.
You can not use old mapping here.
Regards,
Moorthy

WSDL With External References

Hello,
I need to import a wsdl in external definition ,that has 2 xsds as external references.
But when I import the wsdl,I am not able to find the wsdl pointing to the two xsds .
Can anyone help me with the this?
Thanks in advance.
Regards,
Sriparna

Hello,
The xsds will stay as is. What you can do is:
1.) Open the WSDL ED
2.) Go to the External References Tab
3.) You will see a source and a name column
4.) Click on the name(column) of any xsd that you want to be referenced
5.) Press ctrl+c
6.) Open the XSD ED
7.) Click the edit button
8.) Under the Source field, press ctrl+v
9.) Save and activate
Hope this helps,
Mark

External definitions import into Message mapping

Hi,
I have a DTD message in external definitions to be imported into the message mapping. But I am not able to choose the object in the mapping editor. It does not allow even if the message is a valid WSDL. The only time it allows to import into the message editor is when its an XSD.I am not sure why the external definitions in DTD or WSDL formats are not able to be imported or am I missing something??
-Ken

Hi,
A conversion of the downloaded cXML DTD into XSD by using XMLSPY yields 3 XSD files. Using the initial XSD(which has the major fields) yields the same error(i.e cannot create messages or valid WSDL) in external definitions.
I also tried using one of the standard xml's from the cXML site and the funny part was XMLSPY validated them without errors and while importing them directly into the mapping editor, XI throws an error "XML NOT WELL FORMED". Its so weird.
Also is there a possibility to write a script to manipulate the payload message after passing through the adapters? For eg : Creating a script which will delete a valid tag in payload before it reaches the 3rd party. ...By adding the DOCTYPE in the prolog, the message would look like this :
"<?xml...utf-8>
<!DOCTYPE......'Cxml.org'>
<?xml.....utf-8>
<start tag></start tag>
Therefore some kind of a script that would remove the second <?xml tag on line 3>..
This is just a round about thinking
Any ideas..

Import of SAP Objects into Integration Repository in XI 3.0

Hi all,
I am not able to import SAP objects into the Integration Repository in XI 3.0. This option is under any Software Component Version. I have selected the radio button "Import of RFC and IDoc interfaces from SAP systems permitted", in the Software Component Version settings. After the connection data is specified for the SAP system nothing appears under the IDoc, Whereas the import of RFCs is successfull.
We also have another installation of SAP XI 3.0, here this option is working properly. Can anyone tell me what is the problem, is is there something else to be configured inorder to do this.
Best regards,
Norway

Hi Stephan
Thank you for your answer. We have followed your instructions but did only get half a success. Here is what we have done:
1) Created "External Definitions" for all related xsd-files with the same name as the xsd-filename and in our own namespace. Our namespace is different from those specified in the xsd-files. We have not change the namespaces in the xsd-files.
2) Maintained the "source"-field with the name for the xsd-file and not the url as specified in our answer. When we used the filename only we got a value the field "name" in the "External References".
3) We made a message mapping and imported the "top-level-xsd-element" from the "External Definition". This resulted in only the top level element and nothing else. What we expected was the possibility to drill down through the complete structure.
What did we doe wrong? Perhaps I could talk you into spending 10 min. and try it your self? This url leads to a zip file with all the related xsd files: http://rep.oio.dk/ubl/xml/schemas/0p71/documentation/resources.html
Do you know if it will be possible to make references across namespaces in a later version of XI?
Regards
Christian

External definition

Hi All,
I have imported xsd files as external definitions. They are showing messaages list without any space.While using them in message mapping they are not showing the fields. Even in the case of direct import into message mapping also the same result.I am not getting the problem. Any suggestions to solve this..
Thanks in advance,
Kartikeya

hi,
i think this helps..
some of the tags are not supported by message mapping...like choice and complex..
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2089f29b-b10a-2a10-5297-e258df0c1bfc
Thanks,
vijaya.

Import SAP WSDL into External Definition

Similar Messages

Maybe you are looking for