Establish the Content Pipeline

To establish the content pipeline, perform the following steps:
  1. Develop or modify applications that will be used to create the content to be published. These applications can take the form of stand-alone applications that are written in a visual programming language or SAS programs. Publishers must obtain or install the appropriate publishing application for their needs. For example, an individual or department that needs to publish data-intensive reports on a regular basis might use a SAS program for publishing, while a user who needs to send information to a changing number of users on an occasional basis might use the publishing functionality that is provided by SAS Enterprise Guide or SAS Information Delivery Portal.
  2. For the initial set of information channels, identify the users and groups that are initially subscribed to those channels. If the publishing framework has open access, then users can subscribe themselves to channels. Otherwise, administrators can define the subscribers for each channel.
  3. Determine how information is to be distributed to subscribers (whether by text- formatted e-mail or HTML-formatted e-mail, with a WebDAV server, or through a queue).
  4. Gather address information, which is necessary for defining subscribers.
  5. Create a PUBLISHERS group, and enable the PUBLISHERS group to authenticate to the content server (if it is a secured HTTP, FTP, or WebDAV server). Credentials can be included in your code or stored in metadata. The following example scenarios all require the publisher to have server credentials:
    • publishing to a subscriber with a delivery transport that is defined as a secured WebDAV server
    • publishing to a channel's persistent store that is defined as a secured WebDAV server
    • publishing to a channel's persistent store that is defined as an archive path that is a secured HTTP server
    • publishing to a channel's persistent store that is defined as an archive path that is a secured FTP server
    Note: Token authentication is supported, beginning with SAS 9.2. For more information about SAS token authentication, see SAS Intelligence Platform: Security Administration Guide.
    It is usually most efficient to create one metadata group that includes all publishers as members and give that group one login for each secured HTTP, FTP, or WebDAV server. Each server must be registered in the metadata in its own authentication domain. For example, the contents of the group's Accounts tab might as shown in the following table:
    Credentials for Group
    Authentication Domain
    User ID
    Password
    IISauth
    sharedIISid
    sharedIISpassword
    FTPauth
    sharedFTPid
    sharedFTPpassword
    Note: If you publish directly to subscribers who have their own WebDAV servers, each of those servers must be registered in its own authentication domain. The group's Accounts tab must include a login for each such server. For more information about credential management, see SAS Intelligence Platform: Security Administration Guide.