When determining how to render packages,
the publisher should consider the following:
-
the company's business requirements
-
the configuration of the business
enterprise (for example, hardware, software, business processes, and
communications protocols)
-
the package content (structured
and unstructured data)
-
the transport (such as archive,
channel, e-mail, message queue, or Web) that is used to deliver the
package
The following scenarios
depict business factors that might affect how a package is rendered:
Package Rendering to Meet Consumer Needs
|
|
|
Access to packages,
but have limited system storage resources
|
Render the package as
an archive.
|
Access to package without
having SAS software installed
|
Render the package as
an archive and attach the archive to e-mail for access by using SAS
Package Reader.
|
Only executive-level
summaries (for example, text reports, graphics, and Web links)
|
Render the package as
unstructured content to known consumers via e-mail or to unknown consumers
via subscription-based channels.
|
Access to SAS results,
but do not want to access the package for continued processing
|
Apply a template to
the SAS data package entry for viewing in e-mail and on the Web.
|
Access to SAS results,
but do not have Web access or do not use HTML
|
Apply a template in
plain-text format to the SAS results for viewing in e-mail.
|
Direct access to SAS
results for continued data processing
|
Deliver SAS results
package entries to message queues or archives to enable programmatic
access to SAS data.
|
To span a broad professional
range (executive, manager, programmer, and knowledge worker)
|
Apply name/value metadata
to the package and package entries to enable consumers to filter packages
or package entries for relevancy.
|
Before the publisher
can begin the publishing process, the administrator must first configure
the publishing environment, which might include archives, channels,
subscribers, and subscriptions.