|
Publishing Destination Types
A publishing destination type is the transport that the publisher selects for the delivery of a package to the intended audience. Supported destinations are as follows:
- E-mail
- specifies a common method for delivering a package to recipients whose identities are known to the publisher.
- Archive
- specifies a package that
is compressed and saved to a directory file. The archive can also be catalogued in an LDAP directory. The archive contains the contents of a package and metadata that is necessary for extracting the contents. An archive is compressed using ZIP
compression and is saved with an SPK extension. The archive is saved to the
specified location and remains available to users until its expiration date.
- Channel
- specifies a topic or identifier that acts as a conduit for related information. The channel
carries the information from the publisher who creates
it to the subscribers who want it.
The Publishing Framework administrator creates a channel for each distinct topic or audience. For example, users of a particular application might want a channel for discussion and data exchange, while the programmers of that application might want another channel to discuss technical problems and future enhancements.
The publisher must be aware of channels that have been defined in the Publishing Framework in order to make use of them.
- Message queue
- specifies a place in application messaging where one program (such as SAS Publisher) can send messages that will be retrieved by another program (such as SAS Package Retriever or a customized retrieval program). The two programs communicate asynchronously without any knowledge of the location of the other program or even whether the other program is running.
- Web Distributed Authoring and Versioning (WebDAV)-compliant server
- specifies an emerging industry standard
that is based on extensions to HTTP 1.1. It enables package publishers, programmers,
and package retrievers to collaborate on the development of files and collections
of files on remote Web servers. It also enables publishers to publish packages
to a Web-compliant server.
|