Active Subscriptions

Via the batch interface a data file is created regularly (usually daily). Which comprises all active orders for a particular publication in a firm given client.

The actual selection criterion is defined in AVS.

The file is based on XML (eXtensible Markup Language). The entire XML-structure is transferred into one data file. The XML-structure consists of a Header-Part in which the general document descriptions (XML-Version, encoding, etc.) are stored and the order data in the <body>-tag.

The file is transferred to dsb’s WebDAV Server. The address of the server is: tbox.dsb.net. To be able to collect the data you need WebDAV-access. Your customer service will tell you that.

We reserve change in structure of element structure and element attributes (see therefore also section 2.)

In this modifications following points should be regarded: additional fields can be added without further notice. Therefore it is important to realize the access to the XML-structure with corresponding frameworks of the used program language (for example by means of JDOM in Java). Thereby the access of the recorded fields still work even when further substance is added to the structure.

Of course each fields can be accessed also “native“ this means over string operations but it must be observed not to search after corresponding fields (for example the first name in field “first name”) but first the under structure “business-partner“ must be extracted and there it can be searched after tag “first name”.

All orders are sent within a XML-document and therefore within a XML file. The subscriptions are summarized within the <body>-Tag. The elements of a single subscription-order are surrounded by a <subscription-order> or bei a <subscription> tag.

Schematic representation (new):

<?xml version='1.0' encoding='ISO-8859-1'?>
<message version='1.0' system='avs/3'>
<header>
<client></client>
</header>
<body>
<subscription-order>
<!-- comprises an order -->
</subscription-order>
...
<subscription-order>
<!-- further order -->
</subscription-order>
</body>
</message>

Schematic representation (deprecated):

<?xml version='1.0' encoding='ISO-8859-1'?>
<message version='1.0' system='avs/3'>
<header>
<client></client>
</header>
<body>
<subscription>
<!-- comprises an order -->
</subscription>
...
<subscription>
<!-- further order -->
</subscription>
</body>
</message>

The structure of the served XML fragments subscription-order (new) respectively
subscription (deprecated) has the same composition in the batch- as in the realtime modus.

Please use therefore the description for createOrderBuffered.

{% include “../../../xml_changes}}