The portal's
publish and subscribe features enable you to publish information to
other authorized users who want to receive the information.
From the
portal, you can publish the following items to a publication channel
or a WebDAV repository:
Note: You cannot
publish SAS Reports or SAS Information Maps.
A publication
channel is a virtual communication path that is identified with a
particular topic, organizational group, user audience, or other category.
A publication channel is similar to a radio channel that is identified
with a particular frequency.
For more information, see About Channels and Subscriptions.
You must
be granted permission to publish content. To determine whether you
have the necessary permission, contact your site administrator.
To publish
portal content to a publication channel or to a WebDAV repository:
-
Locate
the items that you want to publish and place them in a package. You
can use either of the following methods:
-
Use the toolbar to create a package
that contains only one content item. Follow these steps:
-
-
From the
viewer, click
Publish in the toolbar. The
Publish page appears.
-
Use your Bookmarks portlet to create
a package that includes one or more content items. Follow these steps:
-
Use the
search tool to find the content item(s) that you want to publish,
and bookmark these items.
For details, see Create a Bookmark.
-
Navigate
to the page that contains your Bookmarks portlet.
-
In the
Bookmarks portlet, select the check box for each content item you
want to publish. Select only those items that can be published, as
listed previously.
-
Click
Publish. The Publish page appears.
-
On the
Publish page, enter the package information as follows:
Name
Enter a name for the
package.
Description
Enter brief text that
describes the contents of the package.
Publish To
To publish the package
to a publication channel, select Channel from the drop-down box.
To publish the package
to a WebDAV repository, select
WebDav from
the drop-down box.
Expiration
From the drop-down
box, select the length of time that the package should remain available
in the channel or in the WebDAV repository.
Note: Expired packages
do not appear when the channel is displayed or when packages are searched.
However, expired packages are not automatically deleted from the channel
or from the WebDAV repository.
Name/Value pairs:
You can specify name/value
pairs that describe the contents of the package. Use the format name=value,
and place a comma between each entry, as in the following examples:
-
region=east,content=sales,year=2003
-
market=europe,content=customers,priority=high
The publish process
compares your entries with name/value pairs that are specified in
subscribers' profiles to determine which subscribers should receive
the package. (Subscribers whose profiles do not specify name/value
pairs automatically receive the package.)
Note: Name/value
pairs work only if the publishers of packages use the same name/value
pairs that subscribers use in their profiles. Users in your organization
should develop conventions for name/value pairs and publicize them
throughout the enterprise.
Items
If the package contains
multiple items, then you can change the order of items in the package.
Click an item name, and then click the up or down arrow to move the
item to a different position.
-
-
If you
are publishing to a channel, the
Select one or more channels step appears on the Publish page. This step lists all of the publication
channels to which you are authorized to publish. Do the following:
-
Click
on one or more channel names.
Note: To select multiple
channels, press the CTRL key on your keyboard while you are making
your selections.
The package
is made available to all of the channels' subscribers via the delivery
method that is defined in each subscriber's profile.
-
-
If you
are publishing to a WebDAV repository, the
Publish to
WebDAV Server step appears on the Publish page. Do the
following:
-
At
WebDAV URL, enter the URL of the location on the WebDAV
server that you want to publish to. Be sure to include the complete
URL, including http://. The URL must include a valid base path that
has been configured by your site administrator.
Here is
an example of a URL:
http://myHost:8080/SASContentServer/repository/default/sasdav/Users/sasdemo/
-
Select
a
URL type. If you select
Parent as the URL type, then you can select the check box to specify
Publish as a binary archive. The options are as follows:
Collection
The published items
are stored as a WebDAV collection that has exactly the same name that
you specified in the path. The published collection replaces any
files and nested directories that already exist in that path.
Parent without the binary archive option
A new WebDAV collection
(directory) is created underneath the specified path. The new directory
has a unique, automatically generated name, and the published items
appear under the new directory.
Parent with the binary archive option
An archive file that
contains the published items is created and appears underneath the
specified path. The archive file has a unique, automatically generated
name.
For example,
suppose you publish an information map, a link, and the file sales.doc
to the URL
http://myHost:8080/SASContentServer/repository/default/sasdav/sales
. The published files would appear in the WebDAV repository as described
below:
|
The files sas001.ref,
sas002.ref, sas003.ref, and sales.doc would be placed in the sales subdirectory under SASContentServer\repository\default\sasdav . This cautionary message is displayed:
The COLLECTION_URL option
causes any files and subdirectories in this location to be deleted
and replaced with the new collection. Do you want to continue with
this option?
|
Parent URL without the
binary archive option
|
A subdirectory such
as \sales\s4063982 would be created
under SASContentServer\repository\default\sasdav . The following files would be placed in the directory: sas001.ref,
sas002.ref, sas003.ref, and sales.doc.
|
Parent URL with the
binary archive option
|
An archive file with
a name such as s4067332.spk would be created. The file would be placed
in the sales subdirectory.
|
-
The published
information is written to the repository that you specified.