SAS 9.1.3 Integration Technologies » Developer's Guide


Publish Package Interface
Publish/Retrieve Encoding Behavior
Publishing Packages
INSERT_CATALOG
INSERT_DATASET
INSERT_FDB
INSERT_FILE
INSERT_HTML
INSERT_MDDB
INSERT_PACKAGE
INSERT_REF
INSERT_SQLVIEW
INSERT_VIEWER
PACKAGE_BEGIN
PACKAGE_END
PACKAGE_PUBLISH
LDAP Channel Store Syntax
SAS Metadata Repository Channel Store Syntax
Retrieving Packages
COMPANION_NEXT
ENTRY_FIRST
ENTRY_NEXT
PACKAGE_DESTROY
PACKAGE_FIRST
PACKAGE_NEXT
PACKAGE_TERM
RETRIEVE_CATALOG
RETRIEVE_DATASET
RETRIEVE_FDB
RETRIEVE_FILE
RETRIEVE_HTML
RETRIEVE_MDDB
RETRIEVE_NESTED
RETRIEVE_PACKAGE
RETRIEVE_REF
RETRIEVE_SQLVIEW
RETRIEVE_VIEWER
Filtering Packages
Publishing Examples
Publishing in the Data Step
Publishing in a Macro
Publishing with FTP
Publishing Framework

Publish Package Interface

The Publish Package Interface consists of SAS CALL routines that enable you to write SAS programs, including stored processes, that create, populate, publish, and retrieve collections of information known as packages.

The process of publishing a package follows:

  1. A package is created using the PACKAGE_BEGIN CALL routine.

    This CALL routine assigns a name to the package and any optional name/value pairs that are associated with it.

    Name/value pairs are used to assign metadata to a package or individual package entries. This enables you to create filters that aid in information retrieval. The filters can be used both by subscribers to channels and by programs that search the package archive.

  2. A package is populated by adding package entries using the INSERT_* CALL routines.

    An entry can be a SAS file (for example, data set, catalog, or SAS MDDB), or almost any other kind of file, including HTML and images. You can also nest packages by including a package as an entry in another package. Entries are referenced in the order in which they were added to the package.

    Note: If inserting HTML file entries, see Publish/Retrieve Encoding Behavior.

  3. A package is published to a delivery transport using the PACKAGE_PUBLISH CALL routine.

    Supported transports are e-mail addresses, a message queue, subscribers to a pre-defined channel, a WebDAV-Compliant server, and an archive.

  4. A package is retrieved from a delivery transport using the PACKAGE_RETRIEVE* CALL routines.