Use of External Definition
Hi all,
could you please explain me the use of External Definition?
why it is used and where it is used? how to use?
please expecting the answer............
Regards
sasi
Hi Sasi,
Personally, I am using the External Defenitions as a basis for my Message Interfaces from the MDM syndicator. I am importing the XSD files based on the XML files from the MDM syndicator. In this way I have the complete structure for input/output to the MDM server.
Of course it can be used to import other predefined structures.
In other words, it saves you a lot of time
Please award points if the answer was helpful to you.
Cheers,
Auke
Similar Messages
-
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
JeromeHi 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 -
Hi Friends,
There is a requirement for external definition to import. I got one file from client text file having xml data. So i have save as to .XSD format and tested in XI while uploading into external definitions.
As per my knowledge, .XSD/wsdl/dtd file can be used for external definitions. And, it acts as Message type so create MI .
So , if we request from client , is there specific format is there for .XSD??? Is it only message type else data type possible ???
How to guide the client to get the .XSD files?
Thank you
DevaHi Deva,
first convert XML file in to XSD,for that you can use XML Editors ALTOVA XML Spy or Styalus studio to conver XML to XSD.
you can get free trail versions available.
The XML to XSD conversion process very easy , just google it.
if you have XSD then you no need to create Data type and Message Type.
Regards,
Raj -
How to remove namespaces in mapping when using External Definition
Hi,
I read in the blog (/people/sameer.shadab/blog/2005/12/05/how-to-remove-namespaces-in-mapping--xi) that you are able to remove namespaces in mapping by deleting the value from XML Namespace under the Message Type. However, is it possible to do this when you are using External Definition (xsd) ? The blog only describe how to do this if you define a Data Type.Hi ,
No ..it is not possible to remove the namespace once you imported into IR of external defintion.You can remove your namesapce from external definition before importing into IR.
Sekhar -
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>
I have tried importing the modified xsd into external definition. but how i should relate it to standard idoc which I have mapped earlier?.</i>
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 -
Can't use Data type created with External Definition
Hi,
In the repository, I would like to transport a very complexe DataType from one XI system to an other one. As I don't want to spend a week to create data types, I created a new External Definitions and loaded my XSD schema (that I exported as XSD from Source system) with Messages parameter set to "From All Available Global Elements". I don't set the "Source". I can see the "Imported Document" and "WSDL", but the Messages and External References tabs are empty. Furthermore, I can't use my new message type in a Outbound Asyncrhronous Message Interface.
Here is a very small XSD file that I use to test my scenario.
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://veilleux.1" targetNamespace="http://veilleux.1">
<xsd:complexType name="SimpleType1">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
bdfdbef1df9711daa2c9001125f86068
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Name" type="SimpleType2">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
bdfdbef0df9711daa821001125f86068
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="SimpleType2">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
0fecc852df9811da899a000f206d294f
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Name" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
ac58afc0df9711da86af001125f86068
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Any one can help me please.
Thanks, DavyHello Moorthy,
My XSD is correct since it's XI itself that generated it from real Data Type on my source System (but I tested it in Internet Explorer and it looks fine).
I tried to select my ExternalDefinition as source in MessageMapping, but XI doesn't let me specify it (Apply button is disabled when I select my ExternalDefinition).
I'm pretty sure that it is related to the fact that I should have a Data Type in "Messages" and "External References" tabs and I have nothing. My XSD is legal, but it seems that XI can't automatically create the data type from it.
Do you have any other idea?
Thanks, Davy -
Can External Definition be used or Receiver File content conversion (CSV)?
Hi Experts,
I'm a newbie to SAP PI and I started working on file to File(FCC) scenario in which I am provided with the receiver structure as an External definition. The structure is like
Name
Place
Designation
Salary
hike
Can I use the same structure (External Definition) for the receiver file content conversion or do I need to create another specific structure?
Can I convert the target CSV file to UTF-8 encoding?
Please help.
Regards,
TaroHi,
Can the above specified structure be used for receiver FCC? Does this work? Can this be converted to UTF-8?
If it can be used, how do we specify the parameters for FCC then as there's no root element?
Regards,
Taro -
Using SAPR/3 IDOC in PI as External definition,type of communication channe
Hi,iam using IDOC Structure as an external definition in PI ,I JUST want to know the procedure for file to idoc using external defintion for idoc structure in the reciever side and what is the communication channel needed for recieving external definition at reciever side.
will be waiting for you rresponse.
bye.
regards.
VarmaHi
Use the following steps:
1. Select the software component that you want to import an IDoc type for.
Check the settings for the software component version. Make sure the
attribute Import of RFC and IDoc Interfaces from SAP Systems Permitted
is selected and that the technical connection data for importing from the
SAP system is maintained.
2. Under the Imported Objects node choose Import RFC/IDoc from the context
menu.
3. Enter a valid user and password and choose Continue.
You need to use a receive IDoc Communication Channel but in case of sender no need to create a communication channel.
Regards
Monika -
Idoc as external definition for occurance change - interface use
Hello,
never used this.
Found this blog from Michael
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Question is...
When I import the Idoc as external definition then I need to add it into a message interface because it cannot be used
like original Idoc which is used as message interface?
Thank you in advance !
Best regards
DirkWhen I import the Idoc as external definition then I need to add it into a message interface because it cannot be used
like original Idoc which is used as message interface?
You dont have to use it in Message interface....the standard IDOC can be used in the Interface Mapping Directly....even Michal mentioned the same in the blog Step 6....in case you missed it.
Regards,
Abhishek. -
External definition and used them as Data Type Templates
hi all
how to Develop external definition and used them as Data Type Templates .
Thank u
SwariHI
External Definitions: If a definition of the message structure exists in wsdl, xsd, dtd formats, we can use it in the integration repository by importing it as an external definition.
External Definations:
An external definition enables you to import a local WSDL, XSD, or DTD file to the Integration Repository and specify which parts of the schema to extract as the description for a message. You can use these extracted message schema as:
Output or input messages in message interfaces
Source or target structures for message mappings
There is a series of standard schema for describing the message structure at runtime. WSDL (Web Service Description Language), XSD (XML Schema Definition Language), or DTDs (Document Type Definitions) are often used to describe message schema. If a description of the message structure already exists in one of the above formats, you can use it in the Integration Repository by importing it as an external definition rather than re-entering it manually using the data type editor.
Have a look at
http://help.sap.com/saphelp_nw04/helpdata/en/43/ce49ef1019087ae10000000a1553f6/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ba/d4c23b95c8466ce10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm
cheers -
Possible? Using External Definitions for data type/message type definitions
Hi all,
i want to use external definitons in my own data type definitions. Is that possible? And if yes, how?
I imported many definitions via a mass import. Now I also want to use these definitions for further interfaces (than the imported ones). The most convenient would be of course to just use them as a custom created type. Can I somehow "convert" an external definition to a data type/message type?
KR
FelixHello Felix,
The External defination which you has been imported that cant use in DT and MT but yeah you can use this in Service interface.
you cant modify that External defination if you want to do that then 1st of all modify it and then reimport it as an another external defination.
and creating service interface with this ED you can use it in your message mapping .
i hope this will help to you to clear your doubt.
Monica -
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 -
Using an external hard drive with Airport Extreme
I'd like to use an external hard drive to store movies and music through my Airport Extreme. The drive is connected to a powered usb hub which is connected to the Extreme. I can see the drive in Airport Utility but I can't figure out how to use it.
Hi,
I have just tried to set up an Airport Extreme with an external hard drive at home. I have 4 computers connected to the "network" - an iMac, a MacBookPro and 2 x windows machines. A printer is connected wirelessly to the two Macs.
I cannot find the hard drive - I have tried the steps mentioned by Bob Timmons Mar 17 2010, but the only things I see under "Shared" in Finder are the iMac and the printer - not the Airport Extreme (seems odd??), not the windows machines, and most importantly, not the hard drive connected to the USB port on the Airport Extreme.
I therefore expect that the iMac and printer are connected wirelessly and directly, rather than through my network (& I'm happy for the printer to be connected this way, but I do need the PCs and the hard drive all networked).
According to my network connection, (in top bar on the screen) I am definitely connected to the network - yet nothing else shows in finder??
I do, however, see the USB hard Drive when I go into Finder>Applications>Utilities>AirportUtility.app, under my Airport Extreme >Disks. I've also gone through all the set up procedures for "File Sharing."
I have read other posts about formatting the hard drive ether FAT32 or NFTS - is this something I now need to do?? If so, which one should I use, and once I do it, will I then see it?
Presumably, in order to format the Hard Drive, I will need to disconnect it from the Airport Extreme, and connect it directly to one of the Macs too?
My apologies for so many questions, but this is all very technical stuff for the non-techie layperson.
Many thanks for any help anyone can provide on one or more of the questions / issues.
Martin -
Scratch Disc Questions using Firewire External Drive & Imac
Hello. I've read through the existing questions regarding scratch disc and Photoshop, yet can't seem to find an answer to my questions. I would greatly appreciate any tips/advice. Here is my setup and situation:
I am running an iMac with a 2.16 intel core 2 duo processor, 3 GB memory, and running OS X version 10.6.4. I am currently using versions cs3 and cs4 of Photoshop, but plan to upgrade to cs5 soon.
The problem I am having is when running Photoshop, my computer becomes very slow. After reading about possible reasons, I came across a couple of sources (including Adobe themeselves) mentioning that the scratch disc should be a designated drive seperate from the drive containing the operating system. Since I am using an iMac that only allows for one internal drive, my only apparent option seems to be an external drive.
Many people say don't use an external drive, but if you are going to; use an eSATA or firewire. The imac does have firewire 800 capabilities. Should I consider this?
Now I'm wondering if it's a bad idea to purchase a macbook for my next computer (what I wanted to do) because it will also only have one drive, not allowing for a seperate drive for the scratch disc. Any thoughts? I've read around the net but haven't found any definitive answers.Designer,
Photoshop benefits greatly from having a scratch disk on a separate physical drive, not on the boot disk or on another partition of the boot disk. It's almost not worth connecting via Firewire 400 because the transfer limitations don't allow much performance improvement. But using a Firewire 800 connection gives excellent performance.
Running Photoshop on a one-drive machine is a little frustrating due to the performance hit without the separate scratch drive.
Rich -
Multi-Mapping Error in PI 7.1 - External Definitions
Hi all,
We have just upgraded to PI 7.1 from 7.0 and run into an issue with message multi-mappings, just wondered if anyone else had met the same issue and worked it out...
When creating a message mapping, we are using as the target an external definition which is defined by an XSD generated by a third party tool (Seeburger).
When I map 1:1 (1 source message to one target message) in the message mapper, all is fine but if I try to create a multi mapping, I get an error. The process is:
a) I have a message mapping with one target message, defined as an External Definition.
b) I then go to Signature tab and add a second target message as an External Definition
c) Click back to Definition tab
d) Get the error "Object XXXXX | YYYYY not found" - where XXXXX is the external def name and YYYYY is the namespace (the SWCV namespace that is, not the XML namespace)
This only seems to happen with External Definitions which are autogenerated and I strongly suspect that is has to do with the fact that the tool that generates them always does so without an XML namespace. I have not proved this though (other Ext Defs with namespaces work for multi-mappings but that is not the only difference so I can't be sure that is the issue but have a strong hunch. This problem did not occur in 7.0.
Anyone got any ideas?
Thanks,
ChrisHi,
This would not be of much help but, I was able to encounter this issue in XI 3.0.
What we did was to manually edit the XSD and add a namespace to it. I'm not sure if PI 7.1 is able to handle mutiple namespaces, so we limited it to this value <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> and made sure that this value is used for all the External Definitions used in the multi-mapping.
Regards,
Maybe you are looking for
-
How do I use more than one iPhone on a single iTunes user id
Just got the family iPhones, all the phones are sending me texts back that I send to them, and my texts are going to their contacts too. We all sync to a family iTunes account. Any help would be appreciated
-
I have a email address . It is not possible to buy icloud storage for it or to add to my first account where i have plenty of icloud storage available. <Email Edited by Host>
-
Mail subject search is not finding All copies why?
mail 6.3 using a subject search (in the small spotlght) - is not finding All copies in my folders and subfolders why? I have done indexing for all mail folders and that did not correct it.
-
I have downloaded a .wmv file and want to view it. Can you view this type of file through iMovie or QuickTime? Thanks, Cheryll
-
Creating User Exit Variable in BeX
Hi All, Urgent help required. I need to create User Exit for a variable which reads value from other variable value which user enter during pop up. Ex: I need get value for the vaiable "ZACTFY" from the variable value "ZSCENARI". Value of this ZSCENA