cancel
Showing results for 
Search instead for 
Did you mean: 

DtReport structure and Alerts Settings from sender AS2 Reports adapter

Former Member
0 Kudos

Hi,

I have imported DtReport for MDN's from SeeBurger AS2 adapter documentation as external definition into PI. However, in the mapping, when I select DtReport as source, I could see only the following structure:

-


<?xml version="1.0" encoding="UTF-8"?>

<ns0:DtReport xmlns:ns0="http://uri.seeburger.com/dt/master/schema">

<ns0:clientId/>

<ns0:correlationId/>

<ns0:category/>

<ns0:state/>

<ns0:finalReport/>

<ns0:freeText/>

<ns0:specificData/>

<ns0:reportAttachment/>

<ns0:archiving/>

</ns0:DtReport>

-


But when I import the test MDN message that we received it has key and value elements underneath the tag 'specificData'. How do I get these two elements from external definitation?? Anything that I should in External References??

How does the following 'Alerts Settings' work from sender AS2 Reports adapter:

Enable alerts

Negative transmission report alert

Negative delivery repot alert

Negative receipt report alert

Thanks,

Riya

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Guys,

Any help would be appreciated. Has anyone worked on SeeBurger AS2 adapter MDN DtReport to send an email if the transmission is not success??

Regards,

Riya

Former Member
0 Kudos

How does your XSD look like that you use as external definition? Is the element specific data marked as unbounded?

Former Member
0 Kudos

Hi Florian,

Thats right, element specific data marked as unbounded and Type keyValue Type.

Regards,

Riya

Former Member
0 Kudos

Could you please post your XSD so I can have a look at it?

Former Member
0 Kudos

Here is the XSD:

-


?xml version="1.0" encoding="ISO-8859-1"?

xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:att="http://uri.seeburger.com/bisas/message/schema" xmlns:tns="http://uri.seeburger.com/dt/master/schema" xmlns="http://uri.seeburger.com/dt/master/schema" targetNamespace="http://uri.seeburger.com/dt/master/schema" elementFormDefault="qualified" attributeFormDefault="unqualified"

xsd:import namespace="http://uri.seeburger.com/bisas/message/schema" schemaLocation="attachments.xsd" /

xsd:include schemaLocation="dtglobaltypes.xsd" /

xsd:include schemaLocation="dtarchiving.xsd" /

xsd:element name="DtReport" type="tns:DtReportType" /

xsd:complexType name="DtReportType"

xsd:sequence

xsd:element name="clientId" default="000" type="tns:stringLength3Type"

xsd:annotation

xsd:documentation

Logical System ID

/xsd:documentation

/xsd:annotation

/xsd:element

xsd:element name="correlationId" type="tns:uuidType" /

xsd:element name="category" type="tns:reportCategoryType" /

xsd:element name="state" type="tns:reportStateType" /

xsd:element name="finalReport" type="xsd:boolean"

xsd:annotation

xsd:documentation

True if this report is the last one for the given correlationId

E.g. if this report is a deliveryReport but there is also a remaining ReadReceipt, then finalReport would have the value &apos;false&apos;

/xsd:documentation

/xsd:annotation

/xsd:element

xsd:element name="freeText" type="xsd:string" minOccurs="0" /

xsd:element name="specificData" type="tns:keyValueType" minOccurs="0" maxOccurs="unbounded"

xsd:annotation

xsd:documentation

Optional report data specific to the components and protocols

/xsd:documentation

/xsd:annotation

/xsd:element

xsd:element name="reportAttachment" type="att:AttachmentRefType" minOccurs="0"

xsd:annotation

xsd:documentation

Optionally holds the report as attachment in its raw format.

/xsd:documentation

/xsd:annotation

/xsd:element

xsd:element name="archiving" type="tns:archivingType" minOccurs="0" maxOccurs="unbounded" /

/xsd:sequence

/xsd:complexType

xsd:complexType name="responseReportHandlingType"

xsd:annotation

xsd:documentation

Information in a DtResponse about the report handling of the sent payload.

/xsd:documentation

/xsd:annotation

xsd:sequence

xsd:element name="reportsExpected" type="xsd:boolean"

xsd:annotation

xsd:documentation

True if at least one report is pending (false if the one and only report is contained in response).

/xsd:documentation

/xsd:annotation

/xsd:element

xsd:element name="expectedReports" type="tns:expectedReportsType" minOccurs="0" maxOccurs="unbounded"

xsd:annotation

xsd:documentation

List of expected reports - also including the one optionally included in the response.

If reportsExpected is true then this list must contain at least one entry, else it must be empty.

/xsd:documentation

/xsd:annotation

/xsd:element

xsd:element name="dtReport" type="tns:DtReportType" minOccurs="0"

xsd:annotation

xsd:documentation

Optional report if it was synchronously received.

/xsd:documentation

/xsd:annotation

/xsd:element

/xsd:sequence

/xsd:complexType

xsd:complexType name="initiationReportHandlingType"

xsd:annotation

xsd:documentation

Information in a DtRequestInitiation about the report handling of the received payload.

/xsd:documentation

/xsd:annotation

xsd:sequence

xsd:element name="reportsExpected" type="xsd:boolean"

xsd:annotation

xsd:documentation

True if at least one report was requested.

/xsd:documentation

/xsd:annotation

/xsd:element

xsd:element name="preparedReports" type="tns:preparedReportsType" minOccurs="0" maxOccurs="unbounded" /

/xsd:sequence

/xsd:complexType

xsd:complexType name="expectedReportsType"

xsd:sequence

xsd:element name="category" type="tns:reportCategoryType" /

xsd:element name="timeoutDate" type="xsd:dateTime" /

xsd:element name="deliveryState" type="tns:deliveryStateType" /

/xsd:sequence

/xsd:complexType

xsd:complexType name="preparedReportsType"

xsd:sequence

xsd:element name="category" type="tns:reportCategoryType" /

xsd:element name="timeoutDate" type="xsd:dateTime" minOccurs="0" /

xsd:element name="reportMessage" type="att:AttachmentRefType" /

/xsd:sequence

/xsd:complexType

xsd:simpleType name="reportCategoryType"

xsd:restriction base="xsd:NCName"

xsd:enumeration value="DeliveryReport"

xsd:annotation

xsd:documentation

Report informing about the state of the delivery on a physical base

/xsd:documentation

/xsd:annotation

/xsd:enumeration

xsd:enumeration value="ReceiptReport"

xsd:annotation

xsd:documentation

Report informing about the state of the receipt on a semantic base

/xsd:documentation

/xsd:annotation

/xsd:enumeration

xsd:enumeration value="TransmissionReport"

xsd:annotation

xsd:documentation

Report informing about the state of the transmission on a physical base

/xsd:documentation

/xsd:annotation

/xsd:enumeration

/xsd:restriction

/xsd:simpleType

xsd:simpleType name="deliveryStateType"

xsd:restriction base="xsd:NCName"

xsd:enumeration value="DELIVERED"

xsd:annotation

xsd:documentation

Delivery proceeded

/xsd:documentation

/xsd:annotation

/xsd:enumeration

xsd:enumeration value="PENDING"

xsd:annotation

xsd:documentation

Delivery pending

/xsd:documentation

/xsd:annotation

/xsd:enumeration

/xsd:restriction

/xsd:simpleType

xsd:simpleType name="reportStateType"

xsd:restriction base="xsd:NCName"

xsd:enumeration value="SUCCESS"

xsd:annotation

xsd:documentation

Positive report

/xsd:documentation

/xsd:annotation

/xsd:enumeration

xsd:enumeration value="FAILURE"

xsd:annotation

xsd:documentation

Negative report

/xsd:documentation

/xsd:annotation

/xsd:enumeration

xsd:enumeration value="EXPIRED"

xsd:annotation

xsd:documentation

No report received in time

/xsd:documentation

/xsd:annotation

/xsd:enumeration

/xsd:restriction

/xsd:simpleType

/xsd:schema

-


Edited by: Riya Patil @SAP on Feb 4, 2010 9:05 PM

Edited by: Riya Patil @SAP on Feb 4, 2010 9:05 PM

Former Member
0 Kudos

Obviously something went wrong, I do not see the XSD data.

Just open the XSD and copy and paste the content.

Thanks.

Former Member
0 Kudos

Its weird, thats what I was trying to do, but its deleting the elements with tags. Just posted without tags. Let me know if its any use?

Riya

Former Member
0 Kudos

Hi,

Is there a way that I could send you XSD?

Regards,

Riya

Former Member
0 Kudos

Maybe the best would be to replace the tags with $ characters and format the whole XSD with line breaks so it would be easier to read. But someone might have a better idea ...

Former Member
0 Kudos

Bases on the data you posted the element specific data seems to be unbounded:

xsd:element name="specificData" type="tns:keyValueType" minOccurs="0" maxOccurs="unbounded"

Can you please double check coloumn "Occurences" on tab definition of message mapping after you imported the source structure again?

Former Member
0 Kudos

Florian,

When I use DtReport.xsd in mappaing, I see specificData element with 0...Unbounded Occurence and keyValue Type, without sub-elements key and value under specificData. Same is the case with reportAttachment with 0...1Occurence and att:AttachmentRefType, without sub-elements.

There are total 4 xsd's: DtReport.xsd, attachments.xsd, dtglobaltypes.xsd and dtarchiving.xsd.

And DtReport.xsd has 3 external references attachments.xsd, dtglobaltypes.xsd and dtarchiving.xsd

Do know how do I link all these 4? I think some where I need to give Source as something??

Any help would be appreciated.

Regards,

Riya

manish_bhalla2
Contributor
0 Kudos

Hi Riya,

Did you manage to get this to work? I am struggling with the same issue myself () and was wondering how you solved this.

Thanks

Manish

Answers (0)