Unable to see Messages in External Definitions
I imported the WSDL below and created a Message Interface based on JobSubmitRequest but, when I come to map to it, all I see in the tree structure is node 'JobSubmitRequest' with elements 'parameter' and 'request_header'.
I also cannot see any messages in External Definitions.
Can anyone help with a solution?
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xoa="http://xoa.xpedite.com/2004/11/xoa" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://xoa.xpedite.com/2004/11/xoa">
<types>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://xoa.xpedite.com/2004/11/xoa" xmlns="http://xoa.xpedite.com/2004/11/xoa">
<!-- address type enum -->
<xs:simpleType name="AddressType">
<xs:restriction base="xs:string">
<xs:enumeration value="fax"/>
<xs:enumeration value="internet"/>
<xs:enumeration value="mbox"/>
<xs:enumeration value="x400"/>
<xs:enumeration value="telex"/>
<xs:enumeration value="cablegram"/>
<xs:enumeration value="mailgram"/>
<xs:enumeration value="ddd"/>
<xs:enumeration value="dedLine"/>
<xs:enumeration value="softswitch"/>
<xs:enumeration value="voice"/>
<xs:enumeration value="sms"/>
<xs:enumeration value="fod"/>
<xs:enumeration value="list"/>
<xs:enumeration value="smQuery"/>
</xs:restriction>
</xs:simpleType>
<!--includes for standalone validation
<xs:include schemaLocation="StatusType.xsd"/>
================ -->
<xs:element name="AuthenticateRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="Domain" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- The authenticate result (used to send back results for synchronous and asynchronous requests) -->
<xs:element name="AuthenticateResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="StatusType.xsd"/>
================ -->
<xs:element name="CFSCreateDirRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSCreateDirResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="StatusType.xsd"/>
================ -->
<xs:element name="CFSDeleteRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
<xs:element minOccurs="0" name="DeleteDir" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSDeleteResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
================ -->
<xs:element name="CFSDownloadRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSDownloadResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
<xs:element minOccurs="0" name="FileData" type="xoa:DocDataType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
================ -->
<xs:element name="CFSListRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
<xs:element minOccurs="0" name="IncludeSubDir" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:simpleType name="EntryType">
<xs:restriction base="xs:string">
<xs:enumeration value="file"/>
<xs:enumeration value="directory"/>
</xs:restriction>
</xs:simpleType>
<xs:element name="CFSListResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="DirectoryEntry" type="xoa:DirectoryEntryType">
<xs:annotation>
<xs:documentation>content of
DirectoryEntry is path relative to
the RelativePath</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="DirectoryEntryType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="type" type="xoa:EntryType" use="required"/>
<xs:attribute name="modified" type="xs:dateTime" use="optional"/>
<xs:attribute name="size" type="xs:integer" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!-- includes for standalone validation
<xs:include schemaLocation="StatusType.xsd"/>
================ -->
<xs:element name="CFSRenameRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="OldRelativePath" type="xs:string"/>
<xs:element name="NewRelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSRenameResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="OldRelativePath" type="xs:string"/>
<xs:element minOccurs="0" name="NewRelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
================ -->
<xs:element name="CFSUploadRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
<xs:element name="FileData" type="xoa:DocDataType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSUploadResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- ===============================
<xs:include schemaLocation="AddressType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
<xs:include schemaLocation="EncodableStringType.xsd"/>
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
=============================== -->
<!-- Type definitions -->
<!-- Phone element -->
<xs:element name="Phone">
<xs:simpleType>
<xs:restriction base="xs:string">
<!-- <xs:pattern value="[0-9+x\-() ]{5,20}"/> -->
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- Email element -->
<xs:element name="Email">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="2"/>
<!-- <xs:pattern value="[@]{1,64}@([@\.]{1,64}\.){1,10}[^@\.]{1,64}"/> -->
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- Eformat type -->
<xs:simpleType name="EformatType">
<xs:annotation>
<xs:documentation> Only used in messageREACH.
Indicates the preferred email format of the
message body the recipient will receive.
Leaving the field empty or setting it to
"default" will send a multipart message body
rather than just a single message body if
it would do so normally. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="text"/>
<xs:enumeration value="html"/>
<xs:enumeration value="htmllite"/>
<xs:enumeration value="default"/>
</xs:restriction>
</xs:simpleType>
<!-- insert list element -->
<xs:element name="InsertList">
<xs:complexType>
<xs:choice>
<xs:element maxOccurs="unbounded" name="Insert">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="number" type="xs:integer"/>
<xs:attribute name="b64charset" type="xs:string" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
<!-- extension element -->
<xs:complexType name="SegmentType">
<xs:choice>
<xs:element maxOccurs="unbounded" name="Property">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="name" type="xs:string"/>
<xs:attribute name="b64charset" type="xs:string" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:choice>
<xs:attribute name="name" type="xs:string"/>
</xs:complexType>
<xs:element name="Extension">
<xs:complexType>
<xs:choice maxOccurs="unbounded">
<xs:element name="Segment" type="xoa:SegmentType"/>
</xs:choice>
</xs:complexType>
</xs:element>
<!-- field mapping type -->
<xs:complexType name="FieldMappingType">
<xs:annotation>
<xs:documentation> Describes the correspondence
between the segment/keyword pairs in the
XDDS header file and columns in a table. Only
two table formats currently supported: CSV
(comma-separated values) and XSL (Excel
spreadsheet). The mapping may go either
from field name to the segment/keyword pair
or vice versa. In both cases, the same
structure may be used. </xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="Map">
<xs:complexType>
<xs:sequence>
<xs:element name="FieldName" type="xs:string"/>
<xs:element minOccurs="0" name="SegmentName" type="xs:string"/>
<xs:element name="PropertyName" type="xs:string"/>
<xs:element minOccurs="0" name="IsBase64Encoded" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
<!-- class definitions -->
<!-- delivery item base class -->
<xs:element abstract="true" name="DeliveryItem" type="xoa:DeliveryItemType"/>
<xs:complexType abstract="true" name="DeliveryItemType">
<xs:attribute name="ref" type="xs:string" use="optional"/>
<xs:attribute name="refb64" type="xs:string" use="optional"/>
</xs:complexType>
<!-- new branch -->
<!-- delivery item container class -->
<xs:element abstract="true" name="DeliveryItemContainer" type="xoa:DeliveryItemContainerType"/>
<xs:complexType abstract="true" name="DeliveryItemContainerType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemType"/>
</xs:complexContent>
</xs:complexType>
<!-- list delivery item class -->
<xs:element name="List" type="xoa:ListType"/>
<xs:complexType name="ListType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemContainerType">
<xs:sequence>
<xs:element name="Name" type="xs:string"/>
</xs:sequence>
<xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- SmQuery delivery item class -->
<xs:element name="SmQuery" type="xoa:SmQueryType"/>
<xs:complexType name="SmQueryType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemContainerType">
<xs:sequence>
<xs:element name="Name" type="xs:string"/>
</xs:sequence>
<xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- External table delivery item class -->
<!-- This includes CSV and XLS files -->
<xs:element name="Table" type="xoa:TableType"/>
<xs:complexType name="TableType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemContainerType">
<xs:sequence>
<xs:element minOccurs="0" name="FieldMapping" type="xoa:FieldMappingType"/>
<xs:choice>
<xs:element name="DocRef" type="xs:string"/>
<xs:element name="Document" type="xoa:DocumentType"/>
</xs:choice>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- new branch -->
<!-- delivery item simple class -->
<xs:element abstract="true" name="DeliveryItemSimple" type="xoa:DeliveryItemSimpleType"/>
<xs:complexType abstract="true" name="DeliveryItemSimpleType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemType">
<xs:sequence>
<xs:element minOccurs="0" name="Alternate">
<xs:complexType>
<xs:choice>
<xs:element ref="xoa:Fax"/>
<xs:element ref="xoa:Internet"/>
<xs:element ref="xoa:Voice"/>
<xs:element ref="xoa:Fod"/>
<xs:element ref="xoa:Mbox"/>
<xs:element ref="xoa:Sms"/>
<xs:element ref="xoa:Telex"/>
<xs:element ref="xoa:DeliveryItemGeneric"/>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- mbox delivery item class -->
<xs:element name="Mbox" type="xoa:MboxType"/>
<xs:complexType name="MboxType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element name="UserId" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- telex delivery item class -->
<xs:element name="Telex" type="xoa:TelexType"/>
<xs:complexType name="TelexType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element name="Number" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- FOD delivery item class -->
<xs:element name="Fod" type="xoa:FodType"/>
<xs:complexType name="FodType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element name="Address" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- SMS delivery item class -->
<xs:element name="Sms" type="xoa:SmsType"/>
<xs:complexType name="SmsType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element ref="xoa:Phone"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- new branch -->
<!-- Complex delivery item class -->
<xs:element abstract="true" name="DeliveryItemComplex" type="xoa:DeliveryItemComplexType"/>
<xs:complexType abstract="true" name="DeliveryItemComplexType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element minOccurs="0" ref="xoa:InsertList"/>
<xs:element minOccurs="0" ref="xoa:Extension"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- fax delivery item class -->
<xs:element name="Fax" type="xoa:FaxType"/>
<xs:complexType name="FaxType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemComplexType">
<xs:sequence>
<xs:element ref="xoa:Phone"/>
<xs:element minOccurs="0" name="Att" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="From" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="To" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="Salutation" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- voice delivery item class -->
<xs:element name="Voice" type="xoa:VoiceType"/>
<xs:complexType name="VoiceType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemComplexType">
<xs:sequence>
<xs:element ref="xoa:Phone"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- internet delivery item class -->
<xs:element name="Internet" type="xoa:InternetType"/>
<xs:complexType name="InternetType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemComplexType">
<xs:sequence>
<xs:element ref="xoa:Email"/>
<xs:element minOccurs="0" name="Subject" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="From" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="Eformat" type="xoa:EformatType"/>
<xs:element minOccurs="0" name="Password" type="xs:string">
<xs:annotation>
<xs:documentation> Only used in
messageREACH. The password used
by this recipient to retrieve
pull attachments. </xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- fax delivery item class -->
<xs:element name="DeliveryItemGeneric" type="xoa:DeliveryItemGenericType"/>
<xs:complexType name="DeliveryItemGenericType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemComplexType">
<xs:sequence>
<xs:element name="Address" type="xs:string"/>
</xs:sequence>
<xs:attribute name="type" type="xoa:AddressType" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- Finally, delivery item list -->
<!-- delivery item list type -->
<xs:complexType name="DeliveryItemListType">
<xs:choice maxOccurs="unbounded">
<xs:element ref="xoa:List"/>
<xs:element ref="xoa:SmQuery"/>
<xs:element ref="xoa:Table"/>
<xs:element ref="xoa:DeliveryItemGeneric"/>
<xs:element ref="xoa:Fax"/>
<xs:element ref="xoa:Internet"/>
<xs:element ref="xoa:Voice"/>
<xs:element ref="xoa:Fod"/>
<xs:element ref="xoa:Mbox"/>
<xs:element ref="xoa:Sms"/>
<xs:element ref="xoa:Telex"/>
</xs:choice>
</xs:complexType>
<!--remove includes later
<xs:include schemaLocation="AddressType.xsd"/>
================ -->
<xs:complexType name="DestinationType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="type" type="xoa:AddressType"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!-- ===============================
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
=============================== -->
<!-- Elementary definitions go first -->
<xs:element name="CharacterSet" type="xs:string">
<xs:annotation>
<xs:documentation>use ISO names</xs:documentation>
</xs:annotation>
</xs:element>
<!-- Document type -->
<xs:simpleType name="DocFormatType">
<xs:restriction base="xs:string">
<xs:enumeration value="text"/>
<xs:enumeration value="XMF"/>
<xs:enumeration value="TIFF"/>
<xs:enumeration value="XAR"/>
<xs:enumeration value="PS"/>
<xs:enumeration value="PCL"/>
<xs:enumeration value="PDF"/>
<xs:enumeration value="MSW"/>
<xs:enumeration value="WAV"/>
<xs:enumeration value="RTF"/>
<xs:enumeration value="XLS"/>
<xs:enumeration value="HTML"/>
<xs:enumeration value="HTMLLITE"/>
<xs:enumeration value="unspec"/>
<xs:enumeration value="GIF"/>
<xs:enumeration value="JPEG"/>
<xs:enumeration value="PPT"/>
<xs:enumeration value="BMP"/>
<xs:enumeration value="VSD"/>
<xs:enumeration value="PUB"/>
<xs:enumeration value="MPP"/>
<xs:enumeration value="empty"/>
<!-- We do not need to know the document type for the -->
<!-- email attachments. -->
</xs:restriction>
</xs:simpleType>
<!-- Document Encoding format -->
<xs:simpleType name="DocEncodingFormat">
<xs:restriction base="xs:string">
<xs:enumeration value="text"/>
<xs:enumeration value="base64"/>
</xs:restriction>
</xs:simpleType>
<!-- Document embedded into the request -->
<xs:complexType name="DocDataType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="format" type="xoa:DocEncodingFormat" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!-- All supported stored object types -->
<xs:simpleType name="SosObjectType">
<xs:restriction base="xs:string">
<xs:enumeration value="tts"/>
<xs:enumeration value="vcs"/>
</xs:restriction>
</xs:simpleType>
<!-- The types of the sos stored objects -->
<xs:complexType name="SosObjectIdType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="sosType" type="xoa:SosObjectType" use="required"/>
<xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!-- Another Document type -->
<xs:complexType name="DocumentType">
<xs:sequence>
<xs:element name="DocType" type="xoa:DocFormatType"/>
<xs:element minOccurs="0" name="Filename" type="xs:string"/>
<xs:choice>
<xs:element name="DocData" type="xoa:DocDataType"/>
<xs:element name="DocCfs" type="xs:string"/>
<xs:element name="DocUrl" type="xs:anyURI"/>
<xs:element name="SosObject" type="xoa:SosObjectIdType"/>
</xs:choice>
<xs:element minOccurs="0" ref="xoa:CharacterSet"/>
</xs:sequence>
<xs:attribute name="ref" type="xs:string" use="optional"/>
</xs:complexType>
<!-- The document set type -->
<xs:complexType name="DocumentSetType">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="Document" type="xoa:DocumentType"/>
</xs:sequence>
</xs:complexType>
<!-- The document by value or by reference -->
<xs:complexType name="DocumentOrRefType">
<xs:choice>
<xs:element name="DocRef" type="xs:string">
<xs:annotation>
<xs:documentation>must refer to a document
in document_set</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Document" type="xoa:DocumentType"/>
</xs:choice>
</xs:complexType>
<xs:complexType name="EncodableStringType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="b64charset" type="xs:string" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!--includes for standalone validation
================ -->
<xs:simpleType name="HistoryActionType">
<xs:restriction base="xs:string">
<xs:enumeration value="inserted"/>
<xs:enumeration value="updated"/>
<xs:enumeration value="deleted"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="ItemCountType">
<xs:simpleContent>
<xs:extension base="xs:integer">
<xs:attribute name="type" type="xoa:HistoryActionType"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="HistoryType">
<xs:sequence>
<xs:element name="Action" type="xs:string"/>
<xs:element name="Operator" type="xs:string"/>
<xs:element name="Agent" type="xs:string"/>
<xs:element name="Time" type="xs:dateTime"/>
<xs:element name="ItemCount" type="xoa:ItemCountType"/>
</xs:sequence>
</xs:complexType>
<!-- ================
<xs:include schemaLocation="AddressType.xsd"/>
<xs:include schemaLocation="DestinationType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
<xs:include schemaLocation="JobIdType.xsd"/>
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
<xs:include schemaLocation="RecStatusType.xsd"/>
================ -->
<xs:simpleType name="JobCancelType">
<xs:annotation>
<xs:documentation>The set of cancellation types/options</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="All"/>
<xs:enumeration value="Deliveries"/>
<xs:enumeration value="Reports"/>
<xs:enumeration value="AcceptanceReport"/>
<xs:enumeration value="CancellationNotice"/>
<xs:enumeration value="Pulls"/>
<xs:enumeration value="FriendDeliveries"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="JobCancelItemType">
<xs:sequence>
<xs:element name="JobId" type="xoa:JobIdType">
<xs:annotation>
<xs:documentation>requested JobId</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="CancelType" type="xoa:JobCancelType"/>
<xs:element minOccurs="0" name="NotificationAddress" type="xoa:DestinationType"/>
<xs:choice minOccurs="0">
<xs:element name="NotificationType" type="xs:string"/>
<xs:element name="NotificationText" type="xoa:DocDataType"/>
</xs:choice>
</xs:sequence>
</xs:complexType>
&
Hi,
Not all data types from WSDL are supported during import. There is SAP Note about it.
please read it:
/people/kevin.liu/blog/2005/10/07/a-note-on-wsdl-and-xsd-imports--part-ii
regards,
wojtek
Message was edited by: Wojciech Gasiorowski
Similar Messages
-
Message Mapping - External Definitions
My Scenario
1) File1(Request with Employee Number) - Sent to XI (Async)
2) XI will send the Request over HTTP and will Receive the Response(Employee Details) (Synchronous)
3) The HTTP Response will be sent to File2(Employee Details) (Async)
The Request and Responses are XSD Messages. I have Imported them into External Definition in my Repository.
Created a File Request - Abstract - Asynchronous - Message interface
Created a HTTP Request-Response - Abstract - Synch - Message interface
Created a File Response - Abstract - Asynchronous - Message interface
Message Mapping: (I am stuck here)
I need to Map the File Request to HTTP Request
I need to Map the HTTP Response to File2Response
How can I creat the Message Mapping for the above situation?
Thanks.Hi,
You will need to create the following message mapping:
1. File Request - HTTP Request
2. HTTP Response - File Response
you can map Message Types to External Definitions and vice versa.
They should appear in the list for the relevant software component.
Or am I missimng something here ?
Cheers
colin. -
GForce4 MX420-T - Unable to see video on external TV/Monitor/VCR
I am unable to get any watchabe video out via the RCA or S-Video cable from my video card. I do get some garbled rubbish on the screen but it's just the odd bunch of diagonal white lines on a black screen.
I have tried this cable on other devices (Other than the Y adaptor that came with the card) and in the inputs of the divices that i want to watch the PC on and it works.
I have attempted to find a setting in the video card setup/config that allows me to specify the output to S-Video/RCA or PAL/NTSC but I am unable to find any setting like this.
Thanks in advanceQuote from: Rassilon on 12-August-05, 18:20:53
I LOVE your Firefox, do you mind if I grab a copy of it?
Go for it, I borrowed it from someone else in the forum. Then I found a bigger picture online. So far I have not found the original person who created it.
With the NVidia drivers, it should work. All you need to do is go into the graphic properties and have it output video to the correct device/cable. You should be able to have it clone the desktop or a second desktop. If it still doesn't work you will probably need to RMA the card.
What is the Y-adapter you mentioned in your first post?
Good Luck
Jeremy
After a bit of googling I extracted this from NVidias site.
1) Right-click on the Desktop and select Properties
2) Left-click on the tab labeled Settings. Then left-click on the Advanced button.
3) This will bring up the Advanced Properties. Left-click on the tab corresponding to the graphcs card that is installed in your PC. For example, if you have a GeforceFX 5800 Ultra graphics card, you will click on the tab labeled "GeforceFX 5800 Ultra". A window will pop up to the left of this panel. From this left side window, select nView Display Mode.
4) You should then see a panel similar to the one above. If you are using a single display video card, left-click the "Current Display" drop down menu and choose "TV". Then click on the "Apply button to confirm the change.
5) If you are using a dual display video card, left-click over the "nView Modes" drop down menu and then select "Clone Mode". Then left-click over the "Display Pair" drop down menu and choose your monitor configuration (i.e. if you are using an analog CRT monitor plus TV, select "Analog Display + TV"). Then select the "Apply button.
6) You should now see the display on your TV. A confirmation window will pop up prompting you to confirm the changes made. Select Yes to keep these settings. Otherwise, the display will revert back to your previous settings.
Hope This Helps -
** Unable to see message interfaces in ID under Business Systems
Hi Friends,
When I create sender / receiver agreement in ID by choosing the respective Business Systems I am not able to see my message interfaces. Then, I checked the SLD, our SWCV under Products are not assigned in the Business Systems.
Then, I have assigned our SWCV (by selecting the product, be selecting the SWCV) in tehcnical system and business systems, saved and log off from SLD.
But, still those message interfaces are not appeared while select the Business systems. Those interfaces are abstract interfaces. I tried to close the IR and ID, open it again, still the same problem.
What could be the reason ? Reply friends,
Thanking you
Jegathees P.Hi,
a new import of the Business System is not necessary.
1) Important is to activate the interface in the Integration Repository.
2) Checking in SLD that all installed check boxes are selected. In the Business System -> Installed Software -> select the Product and check that the SC is selected.
In IR it's enough to close the Business System and reopen it to see the new interfaces.
Regards
Patrick -
Using volume keys to see messages on external display on 8220
for some reason, this function sometimes work and sometimes doesn't work on my phone. I think I have the right settings as it sometimes work.
anyone know what the issue is?
thanks
Solved!
Go to Solution.Hi and welcome to the forums!
What have you tried to resolve the problem?
Start with a basic battery pull.
Bifocals
No data will be lost when doing the following: pull the battery while the device is ON. Replace after a minute, Let the device reboot 1-3 min, see if the problem is fixed.
Click Accept as Solution for posts that have solved your issue(s)!
Be sure to click Like! for those who have helped you.
Install BlackBerry Protect it's a free application designed to help find your lost BlackBerry smartphone, and keep the information on it secure. -
Messages not adviced in extern definition after import wsdl-file from WAS
Hi friends,
after importing the three wsld-files in repository (extern definitions) the messages are not adviced. The referendes to the files are fine, because the name is shown at the tab externe...
But i´m not shure wheather i tool the right link ant Web Service Navigator. It is right to download the default SAP WSDL Files or the default one? Because in the SAP WSDL-files there will be an exception during import in XI repository (tag sap:useFeatur). What is the problem that the messages are not shown on the tab messages in externe definitions?
Thanks in advance,
FrankI've the same problem. Here is my WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns:intf="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="blablabla.de" xmlns:tns2="http://net.jboss.org/jmx" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<schema targetNamespace="blablabla.de" xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<complexType name="MSOBean">
<sequence>
<element name="installationName" nillable="true" type="xsd:string"/>
<element name="requestId" nillable="true" type="xsd:string"/>
<element name="returnCode" type="xsd:int"/>
<element name="returnMessage" nillable="true" type="xsd:string"/>
</sequence>
</complexType>
<complexType name="MSIBean">
<sequence>
<element name="password" nillable="true" type="xsd:string"/>
<element name="project" nillable="true" type="xsd:string"/>
<element name="requestId" nillable="true" type="xsd:string"/>
<element name="userId" nillable="true" type="xsd:string"/>
</sequence>
</complexType>
</schema>
</wsdl:types>
<wsdl:message name="actualizeRequest">
<wsdl:part name="inData" type="tns1:MSIBean"/>
</wsdl:message>
<wsdl:message name="actualizeResponse">
<wsdl:part name="actualizeReturn" type="tns1:MSOBean"/>
</wsdl:message>
<wsdl:portType name="MSService">
<wsdl:operation name="actualize" parameterOrder="inData">
<wsdl:input message="impl:actualizeRequest" name="actualizeRequest"/>
<wsdl:output message="impl:actualizeResponse" name="actualizeResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="MyServicesSoapBinding" type="impl:MSService">
<wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="actualize">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="actualizeRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://blablabla.de" use="encoded"/>
</wsdl:input>
<wsdl:output name="actualizeResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://blablabla.de:8080/jboss-net/services/MyServices" use="encoded"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="MSServiceService">
<wsdl:port binding="impl:MyServicesSoapBinding" name="MyServices">
<wsdlsoap:address location="http://blablabla.de:8080/jboss-net/services/MyServices"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
No Idea. -
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??
-KenHi,
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.. -
Can not see messages in SXMB_MONI of ECC
Hi Friends,
Here I am facing some problem with SXMB_MONI of ECC. I am doing an XI upgrade from XI3.0 to PI 7.1.
when I am doing my interface upgrade I am unable to see messages in SXMB_MONI of ECC. As ECC is also got upgraded now BASIS is very confused about configuration.
when I went through some blogs I came across some suggestions like configuration in SXMB_ADM. In ECC the integration engine configuration what I did is
Role of Business System : Application System.
Corresponding Integ. Server : dest://<HTTP DEST>
One of my doubts:: Is <HTTP DEST> is the one which we are giving in XI/PI or the new one created for ECC. First BASIS set up <HTTP DEST> as the same one which was configured in PI. Then I went back to BASIS and tell them that ECC is having its own local Integration Engine, so we need to create <HTTP DEST> which connects to integration engine of ECC.
Then they created one <HTTP DEST> for ECC. but when I am doing connection test, Http response is coming as 400 BAD HTTP Response :: protocol error. I have no idea why it is behaving like that.
After when I go through some more blogs they are dealing with RFC destinations LCRSAPRFC and SAPSLDAPI. when I check it in ECC I didn't found RFC destination LCRSAPRFC but SAPSLDAPI is existing in ECC.
more over some blogs deal with the configuration in Transaction SLDAPICUST. when I check it in ECC no configuration was done in SLDAPICUST.
I already configured ENGINE_TYPE, IS_URL, LOGGING, LOGGING_PROPAGATION, LOGGING_SYNC under specific configuration data of SXMB_ADM of ECC.
Please let me know what needs to be done and let me out of this confusion. As I am a PI developer I am unaware of all these configurations. expecting replies from gurus....
Regards,
DASARIHi Friends,
Looking at some more blogs I got a doubt.
Actually my scenario is File - XI - RFC.
Now my doubt is whether we can see the messages which were going to ECC by RFC adapter ?
Looking at a thread I got confused whether SXMB_MONI can capture messages only if they are coming from Proxy or IDOC . please clarify me.
Regards,
Dasari. -
Cant see messages in the External Definitions
I'm imporing following wsdl into XI. However I cant see messages and seems to be there is some error in wsdl. Would someone help me please?..
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="urn:services.soap.a2z.com" xmlns:intf="urn:services.soap.a2z.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:services.soap.a2z.com">
<wsdl:types>
<schema targetNamespace="http://xml.apache.org/xml-soap" xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<complexType name="mapItem">
<sequence>
<element name="key" nillable="true" type="xsd:string"/>
<element name="value" nillable="true" type="xsd:string"/>
</sequence>
</complexType>
<complexType name="Map">
<sequence>
<element maxOccurs="unbounded" minOccurs="0" name="item" type="apachesoap:mapItem"/>
</sequence>
</complexType>
</schema>
</wsdl:types>
<wsdl:message name="exportGroupResponse">
<wsdl:part name="exportGroupReturn" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="importGroupRequest1">
<wsdl:part name="in0" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="importGroupResponse">
<wsdl:part name="importGroupReturn" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="importGroupResponse1">
<wsdl:part name="importGroupReturn" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="importGroupRequest">
<wsdl:part name="in0" type="xsd:string"/>
<wsdl:part name="in1" type="apachesoap:Map"/>
</wsdl:message>
<wsdl:message name="loadAdaptersResponse">
<wsdl:part name="loadAdaptersReturn" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="loadAdaptersRequest">
</wsdl:message>
<wsdl:message name="exportAdapterResponse">
<wsdl:part name="exportAdapterReturn" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="importAdapterRequest1">
<wsdl:part name="in0" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="exportAdapterRequest">
<wsdl:part name="in0" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="importAdapterResponse">
<wsdl:part name="importAdapterReturn" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="exportGroupRequest">
<wsdl:part name="in0" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="importAdapterResponse1">
<wsdl:part name="importAdapterReturn" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="importAdapterRequest">
<wsdl:part name="in0" type="xsd:string"/>
<wsdl:part name="in1" type="apachesoap:Map"/>
</wsdl:message>
<wsdl:portType name="Adapter">
<wsdl:operation name="importAdapter" parameterOrder="in0 in1">
<wsdl:input name="importAdapterRequest" message="impl:importAdapterRequest"/>
<wsdl:output name="importAdapterResponse" message="impl:importAdapterResponse"/>
</wsdl:operation>
<wsdl:operation name="importAdapter" parameterOrder="in0">
<wsdl:input name="importAdapterRequest1" message="impl:importAdapterRequest1"/>
<wsdl:output name="importAdapterResponse1" message="impl:importAdapterResponse1"/>
</wsdl:operation>
<wsdl:operation name="importGroup" parameterOrder="in0 in1">
<wsdl:input name="importGroupRequest" message="impl:importGroupRequest"/>
<wsdl:output name="importGroupResponse" message="impl:importGroupResponse"/>
</wsdl:operation>
<wsdl:operation name="importGroup" parameterOrder="in0">
<wsdl:input name="importGroupRequest1" message="impl:importGroupRequest1"/>
<wsdl:output name="importGroupResponse1" message="impl:importGroupResponse1"/>
</wsdl:operation>
<wsdl:operation name="exportAdapter" parameterOrder="in0">
<wsdl:input name="exportAdapterRequest" message="impl:exportAdapterRequest"/>
<wsdl:output name="exportAdapterResponse" message="impl:exportAdapterResponse"/>
</wsdl:operation>
<wsdl:operation name="exportGroup" parameterOrder="in0">
<wsdl:input name="exportGroupRequest" message="impl:exportGroupRequest"/>
<wsdl:output name="exportGroupResponse" message="impl:exportGroupResponse"/>
</wsdl:operation>
<wsdl:operation name="loadAdapters">
<wsdl:input name="loadAdaptersRequest" message="impl:loadAdaptersRequest"/>
<wsdl:output name="loadAdaptersResponse" message="impl:loadAdaptersResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="AdapterServiceSoapBinding" type="impl:Adapter">
<wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="importAdapter">
<wsdlsoap:operation/>
<wsdl:input>
<wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
</wsdl:input>
<wsdl:output>
<wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="importAdapter">
<wsdlsoap:operation/>
<wsdl:input>
<wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
</wsdl:input>
<wsdl:output>
<wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="importGroup">
<wsdlsoap:operation/>
<wsdl:input>
<wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
</wsdl:input>
<wsdl:output>
<wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="importGroup">
<wsdlsoap:operation/>
<wsdl:input>
<wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
</wsdl:input>
<wsdl:output>
<wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="exportAdapter">
<wsdlsoap:operation/>
<wsdl:input>
<wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
</wsdl:input>
<wsdl:output>
<wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="exportGroup">
<wsdlsoap:operation/>
<wsdl:input>
<wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
</wsdl:input>
<wsdl:output>
<wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="loadAdapters">
<wsdlsoap:operation/>
<wsdl:input>
<wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
</wsdl:input>
<wsdl:output>
<wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="AdapterService">
<wsdl:port name="AdapterService" binding="impl:AdapterServiceSoapBinding">
<wsdlsoap:address location="http://vn15:8000/soap/services/AdapterService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>Hi S T,
in the WSDL there occurs the situation that there are in one prtType multiple operations with the same name (e.g. portType "Adapter" contains two definitions for operation with name "importAdapter". Indeed, the original <a href="http://www.w3.org/TR/wsdl">WSDL specification</a> seems to allow this. However, in <a href="http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html">WS-I</a> it is forbidden (see R2304).
Therefore, the Integration Builder does not consider this document to be valid WSDL. This is a little bit tragic, as the portType definitions are not considered by the following steps anyway. A simple workaround would be to delete everything behind the message definitions.
Greetings Stephan -
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 KhalilHi, 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 to see structure under schema when Create External Definition
Hi ...we have scenario like RFC<>XI<>SOAP
The request payload(SOAPIN) for SOAP is:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<AddressValidator xmlns="http://tempuri.org/geostan3/AddressValidator">
<LicenseFile>string</LicenseFile>
<Z9Path>string</Z9Path>
<House>string</House>
<Street>string</Street>
</soap:Body>
</soap:Envelope>
and we are expecting response message from SOAP:
diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1">
- <AddressCheck xmlns="">
- <Address diffgr:id="Address1" msdata:rowOrder="0" diffgr:hasChanges="inserted">
<Addline1>220 W MAIN ST</Addline1>
<Addline2 />
<URB />
<Lastline>LOUISVILLE, KY 40202-1395</Lastline>
<Location>-85754010, 38256144</Location>
<OutBlock>211110049001067</OutBlock>
<OutCBSA>31140</OutCBSA>
<MatchCode>SE0</MatchCode>
<LocationCode>AS0</LocationCode>
<DPVConfirm />
<FootNote1 />
<FootNote2 />
<FootNote3 />
<Msg>OK</Msg>
</Address>
</AddressCheck>
so when we created external definition using wsdl file into XI, it showing only schema as SOAPOUT (I couldn't see those fields in XI/under schema).
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<AddressValidatorResponse xmlns="http://tempuri.org/geostan3/AddressValidator">
<AddressValidatorResult>
<xsd:schema>schema</xsd:schema>xml</AddressValidatorResult>
</AddressValidatorResponse>
</soap:Body>
</soap:Envelope>
SXMB_MONI showing(Response):
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:AddressValidatorResponse xmlns:ns0="http://tempuri.org/geostan3/AddressValidator">
- <ns0:AddressValidatorResult>
<ns1:schema xmlns:ns1="http://www.w3.org/2001/XMLSchema" />
</ns0:AddressValidatorResult>
</ns0:AddressValidatorResponse>
So my question is how do I map response fields to RFC response? Auctully this schema is like table structure which is having all response fields.
I could see all response structure with data in sxmb_moni-->Response Msg ID > inbound message>payloads(main document). Is there any way to send this response to RFC ?
or can you suggest me any other way to send this response to RFC.
Thanks,
Edited by: PILearn on Jun 2, 2008 10:21 PMHere you go..
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://tempuri.org/geostan3/AddressValidator" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="http://tempuri.org/geostan3/AddressValidator" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
<s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/geostan3/AddressValidator">
<s:import namespace="http://www.w3.org/2001/XMLSchema" />
<s:element name="AddressValidator">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="LicenseFile" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="LicensePassword" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="SearchPath" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Z9Path" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="House" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Street" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="AddLine2" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="AddLastLine" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="URB" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Matchmode" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Datum" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="AddressValidatorResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="AddressValidatorResult">
<s:complexType>
<s:sequence>
<s:element ref="s:schema" />
<s:any />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="DataSet" nillable="true">
<s:complexType>
<s:sequence>
<s:element ref="s:schema" />
<s:any />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="AddressValidatorSoapIn">
<wsdl:part name="parameters" element="tns:AddressValidator" />
</wsdl:message>
<wsdl:message name="AddressValidatorSoapOut">
<wsdl:part name="parameters" element="tns:AddressValidatorResponse" />
</wsdl:message>
<wsdl:message name="AddressValidatorHttpGetIn">
<wsdl:part name="LicenseFile" type="s:string" />
<wsdl:part name="LicensePassword" type="s:string" />
<wsdl:part name="SearchPath" type="s:string" />
<wsdl:part name="Z9Path" type="s:string" />
<wsdl:part name="House" type="s:string" />
<wsdl:part name="Street" type="s:string" />
<wsdl:part name="AddLine2" type="s:string" />
<wsdl:part name="AddLastLine" type="s:string" />
<wsdl:part name="URB" type="s:string" />
<wsdl:part name="Matchmode" type="s:string" />
<wsdl:part name="Datum" type="s:string" />
</wsdl:message>
<wsdl:message name="AddressValidatorHttpGetOut">
<wsdl:part name="Body" element="tns:DataSet" />
</wsdl:message>
<wsdl:message name="AddressValidatorHttpPostIn">
<wsdl:part name="LicenseFile" type="s:string" />
<wsdl:part name="LicensePassword" type="s:string" />
<wsdl:part name="SearchPath" type="s:string" />
<wsdl:part name="Z9Path" type="s:string" />
<wsdl:part name="House" type="s:string" />
<wsdl:part name="Street" type="s:string" />
<wsdl:part name="AddLine2" type="s:string" />
<wsdl:part name="AddLastLine" type="s:string" />
<wsdl:part name="URB" type="s:string" />
<wsdl:part name="Matchmode" type="s:string" />
<wsdl:part name="Datum" type="s:string" />
</wsdl:message>
<wsdl:message name="AddressValidatorHttpPostOut">
<wsdl:part name="Body" element="tns:DataSet" />
</wsdl:message>
<wsdl:portType name="AddressCheckSoap">
<wsdl:operation name="AddressValidator">
<wsdl:input message="tns:AddressValidatorSoapIn" />
<wsdl:output message="tns:AddressValidatorSoapOut" />
</wsdl:operation>
</wsdl:portType>
<wsdl:portType name="AddressCheckHttpGet">
<wsdl:operation name="AddressValidator">
<wsdl:input message="tns:AddressValidatorHttpGetIn" />
<wsdl:output message="tns:AddressValidatorHttpGetOut" />
</wsdl:operation>
</wsdl:portType>
<wsdl:portType name="AddressCheckHttpPost">
<wsdl:operation name="AddressValidator">
<wsdl:input message="tns:AddressValidatorHttpPostIn" />
<wsdl:output message="tns:AddressValidatorHttpPostOut" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="AddressCheckSoap" type="tns:AddressCheckSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
<wsdl:operation name="AddressValidator">
<soap:operation soapAction="http://tempuri.org/geostan3/AddressValidator/AddressValidator" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="AddressCheckHttpGet" type="tns:AddressCheckHttpGet">
<http:binding verb="GET" />
<wsdl:operation name="AddressValidator">
<http:operation location="/AddressValidator" />
<wsdl:input>
<http:urlEncoded />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="AddressCheckHttpPost" type="tns:AddressCheckHttpPost">
<http:binding verb="POST" />
<wsdl:operation name="AddressValidator">
<http:operation location="/AddressValidator" />
<wsdl:input>
<mime:content type="application/x-www-form-urlencoded" />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="AddressCheck">
<wsdl:port name="AddressCheckSoap" binding="tns:AddressCheckSoap">
<soap:address location="http://sap-ccs-geo02/geostan3/AddressValidator.asmx" />
</wsdl:port>
<wsdl:port name="AddressCheckHttpGet" binding="tns:AddressCheckHttpGet">
<http:address location="http://sap-ccs-geo02/geostan3/AddressValidator.asmx" />
</wsdl:port>
<wsdl:port name="AddressCheckHttpPost" binding="tns:AddressCheckHttpPost">
<http:address location="http://sap-ccs-geo02/geostan3/AddressValidator.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions> -
Generating Proxy in SAP620 for message interfaces with External definitions
Hi,
We need to generate ABAP proxy in SAP 6.20 for a message interface(XI 3.0) based on WSDL definition.As it is not possible to generate the proxies for WSDL in SAP 620,we installed APPINT620(level 5).Still we are unable to generate the proxy.Any ideas to solve this issue?
Thanks in millions,
S.BanukumarHi,
We have done a workaround to define the SAP(inbound/outbound) message interfaces manually as a copy of external definition structures.Based on the manually defined message interfaces,we could generate the proxy.By this way we could solve the problem.
Thanks,
S.Banukumar -
I am unable to see any POP3 or IMAP tab when I set up an account in my iphone 4S. Hence by default all my email accounts become IMAP and the messages are deleted from the server when I delete them from the iphone.
ok sorry everyone but i solved it myself but the solution is so nuts i've posted it here to help others who have the same problem.
to setup a comcast imap account on your iphone:
go to mail, contacts, etc in settings
under accts, select add account
select "other"
new screen, choose "add mail account"
now on the new acct screen you must enter your name, email address and password for your GMAIL acct ! (yes i said your gmail acct !, or some other acct with a NON comcast address).
hit next
then the acct verifies
when verified a screen will open with all the acct settings for this acct AND @ the top of the screen are the 2 buttons > imap or POP
select imap and THEN CHANGE ALL THE ACCOUNT information to the comcast account !
then hit next and the account will take a couple minutes to verify but it will verify and now you have a comcast imap acct set up on your iphone. The problem must be that when the iphone sends the initial verify acct info to comcast (if you enter that information first) the comcast server is simply not setup yet to signal the iphone that there is an imap option. -
Not able to see "External Definitions" in Integration Repository
Hi Experts,
I am working on PI 7.1.
In the Integration Repository Menu :
SAP Basis --->SAP Basis 7.10 ->http://sap.com/xi/XI/System ->
"Service Interfaces",
"Message Types"
"Fault Message Types",
"Data Types",
"Adapter Metadata"
only are visible.
We need the "External Definitions". Is it not available in the standard SAP PI 7.1 ?
Do we have to import it explicitly?
Kindly advice.
Thanks in advance
~ SurajHey NM,
Thanks a lot for your suggestion. problem got resolved when i did what you said (checking the attributes with developers user id's)
Thanks
Sourav -
"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!
PeterHello 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
Maybe you are looking for
-
Pdf file created in Word 2008 will not open in Acrobat 8.2.6 or any other Adobe program
I have created a 12 page newsletter in Microsoft Word Publisher 2008 and have done so many times before with no problem. Today, I have tried to save it as a .pdf file both in Save As and through the printer. Each .pdf file created in Word will not op
-
Error on clone database, oracle 10g release 2 for windows server 2008
Hi, OS: Windows Server 2008 X64 Oracle: oracle 10g release r2 for windows server 2008 An error occurred when creating a database, stop at last step, Screenshot: [http://temp.wsria.com/oracle_create_db.png|http://temp.wsria.com/oracle_create_db.png] t
-
Problem: Windows failed to start. A recent hardware or software change might be the cause 1) Insert your Windows installation disk and restart your computer File : \Boot\BCD Status : 0xc0000098 Info : The Windows Boot Configuration Data file doe
-
SOAP Error: DeliveryException: Connection reset
I am having a proxy to SOAP scenario.Synch scenario. It was fine for 5 months...just now got an alert...saying. <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Connection reset</SAP:AdditionalText> I checked in communication channel
-
All the free space on my hard drive has vanished!
My hard drive space has disappeared. About two months ago I freed up about 30 gigs and havent really downloaded anything since then. I checked last week and I had about 1 gig left. This was bad and I didnt know the cause of it. I deleted some things