Documentos de Académico
Documentos de Profesional
Documentos de Cultura
SAS Business
Intelligence Client Tools
Course Notes
Introduction to the SAS Business Intelligence Client Tools Course Notes was developed by
Kari Richardson and Eric Rossland. Additional contributions were made by Mark Craver, Christine Vitron,
Bobbie Wagoner, and Kathy Wisniewski. Editing and production support was provided by the
Curriculum Development and Support Department. Hardware support was provided by the Education
Information Systems Department.
SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks
of SAS Institute Inc. in the USA and other countries. indicates USA registration.
Other brand and product names are trademarks of their respective companies.
Introduction to the SAS Business Intelligence Client Tools Course Notes
Copyright 2004 by SAS Institute Inc., Cary, NC 27513, USA. All rights reserved. Printed in the
United States of America. No part of this publication may be reproduced, stored in a retrieval system,
or transmitted, in any form or by any means, electronic, mechanical, photocopying, or otherwise, without
the prior written permission of the publisher, SAS Institute Inc.
Book code 60366, course code SBIOVR_003, prepared date 09Nov04.
Table of Contents
Course Description ................................................................................................................. vi
Prerequisites.......................................................................................................................... vii
General Conventions............................................................................................................. viii
Chapter 1
1.1
1.2
Chapter 2
2.1
Introduction................................................................................................................. 2-3
2.2
2.3
2.4
Chapter 3
3.1
Overview..................................................................................................................... 3-3
3.2
3.3
Chapter 4
4.1
4.2
4.3
4.4
iii
iv
Chapter 5
5.1
5.2
5.3
5.4
Chapter 6
6.1
6.2
6.3
6.4
Chapter 7
7.1
7.2
7.3
Creating a Stored Process from a SAS ETL Studio Job (Self-Study).......................... 7-33
7.4
Chapter 8
8.1
8.2
8.3
8.4
Chapter 9
9.1
9.2
9.3
Chapter 10
vi
Course Description
This training provides participants with a hands-on overview of features in SAS 9 in the areas of
foundation technologies, data warehousing, intelligent storage and business intelligence.
To learn more
A full curriculum of general and statistical instructor-based training is available
at any of the Institutes training facilities. Institute instructors can also provide
on-site training.
For information on other courses in the curriculum, contact the SAS Education
Division at 1-919-531-7321, or send e-mail to training@sas.com. You can also
find this information on the Web at support.sas.com/training/ as well as in the
Training Course Catalog.
For a list of other SAS books that relate to the topics covered in this
Course Notes, USA customers can contact our SAS Publishing Department at
1-800-727-3228 or send e-mail to sasbook@sas.com. Customers outside the
USA, please contact your local SAS office.
Also, see the Publications Catalog on the Web at support.sas.com/pubs for a
complete list of books and a convenient order form.
Prerequisites
None.
vii
viii
General Conventions
This section explains the various conventions used in presenting text, SAS language syntax, and examples
in this book.
Typographical Conventions
You will see several type styles in this book. This list explains the meaning of each style:
UPPERCASE ROMAN
is used for SAS statements and other SAS language elements when they
appear in the text.
italic
identifies terms or concepts that are defined in text. Italic is also used for
book titles when they are referenced in text, as well as for various syntax and
mathematical elements.
bold
monospace
is used for examples of SAS programming statements and for SAS character
strings. Monospace is also used to refer to variable and data set names, field
names in windows, information in fields, and user-supplied information.
select
indicates selectable items in windows and menus. This book also uses icons
to represent selectable items.
Syntax Conventions
The general forms of SAS statements and commands shown in this book include only that part of the
syntax actually taught in the course. For complete syntax, see the appropriate SAS reference guide.
PROC CHART DATA = SAS-data-set;
HBAR | VBAR chart-variables </ options>;
RUN;
This is an example of how SAS syntax is shown in text:
PROC and CHART are in uppercase bold because they are SAS keywords.
DATA= is in uppercase to indicate that it must be spelled as shown.
SAS-data-set is in italic because it represents a value that you supply. In this case, the value must be
the name of a SAS data set.
HBAR and VBAR are in uppercase bold because they are SAS keywords. They are separated by a
vertical bar to indicate they are mutually exclusive; you can choose one or the other.
chart-variables is in italic because it represents a value or values that you supply.
</ options> represents optional syntax specific to the HBAR and VBAR statements. The angle
brackets enclose the slash as well as options because if no options are specified you do not include
the slash.
RUN is in uppercase bold because it is a SAS keyword.
ix
1.2
1-2
Middle
Tier
Server
Tier
4
1-3
1-4
Client Tier
In the most basic terms, if an application is installed on
the machine that the user is sitting at, that machine is the
client tier.
There are three different types of SAS client applications.
Java
Clients
The SAS Business Intelligence (BI) client tools cannot execute SAS code on their own. They have to
request code submission and other services from a SAS server.
Middle Tier
The middle tier is where the Web applications reside and
execute. This tier also contains the infrastructure that
supports the execution of these applications, such as the
Java Application Server or the Java Servlet Container
SAS Web Infrastructure Kit (WIK)
webDAV server.
Java
Java Application
Application Server
Server or
or
Java
Java Servlet
Servlet Container
Container
SAS
SAS Web
Web Infrastructure
Infrastructure Kit
Kit
webDAV
webDAV Server
Server
WebDAV (Web-Based Distributed Authoring and Versioning) is a set of extensions to the HTTP
protocol that allows users to collaboratively edit and manage files on remote Web servers.
Server Tier
The server tier is the machine where one or more
SAS servers is installed and accessed by the BI tools.
There are different types of SAS servers, including:
Metadata
Server
Workspace
Server
Middle
Tier
HTTP
HTTP Server
Server
SDK
SDK
webDAV
webDAV
Server
Server
Java
Java Servlet
Servlet
Container
Container
Web
Web Infrastructure
Infrastructure Kit
Kit
Server
Tier
SAS
SAS99
Foundation
Foundation
Metadata
Metadata
Server
Server
SAS/CONNECT
SAS/CONNECT
Server
Server
Workspace
Workspace
Server
Server
Stored
Stored Process
Process
Server
Server
OLAP
OLAP
Server
Server
1-5
1-6
Metadata Workspace
Server
Server
Stored
Process
Server
SAS/
OLAP
CONNECT
Server
Server
SAS OLAP
Cube Studio
SAS Information
Map Studio
SAS Enterprise
Guide
SAS Web
Report Studio
SAS Information
Delivery Portal
x
x
Security Concepts
In the SAS Intelligence environment, security consists of:
Authentication the process of verifying the identity of a
person or process within the guidelines
of a specific security policy
Authorization
...
11
Security Concepts
An authentication provider is a technology that servers
or applications can use to verify that users are who they
say they are.
By default, the authentication provider for a SAS server is
the host operating system of the machine on which the
server is running.
12
The SAS Metadata Server and SAS OLAP Server can also use alternative authentication providers.
SAS Web applications run under third-party servers that can use a variety of authentication providers.
1-7
1-8
Introduction ..................................................................................................................2-3
2.2
2.3
2.4
2-2
2.1 Introduction
2.1 Introduction
Windows Clients
Browser Clients
...
Power Users
Business Analyst (Jacques)
No DBMS or programming
Strong Excel
Ad hoc queries
OLAP
Create reports
Publish reports
Custom reports
Understands business metrics
Information Consumers
C-level Execs
Annotation
E-mail
Middle Management
(Henri)
Drill down
Manipulation
Annotation
Data Modeler
(Marcel)
Business View
manager
Understands
physical
data model
SQL programmer
Report Administrator
(Robert)
Report Builder
Schedule reports
Monitor queue
Operational Consumers
Sales
Marketing
Customer Service
Finance
Tech Support
2-3
2-4
SAS Information
Map Studio
Data Modeler
(Marcel)
Business View
manager
Understands
physical
data model
SQL programmer
Report Administrator
(Robert)
Report Builder
Schedule reports
Monitor queue
...
These slides represent an example of which BI tools might be used by each group and does not
serve as a recommendation.
SAS Information
Map Studio
...
2.1 Introduction
Annotation
E-mail
SAS Information
Delivery Portal
Middle Management
(Henri)
Drill down
Manipulation
Annotation
Sales
Marketing
Customer Service
Finance
Tech Support
...
2-5
2-6
12
13
2-7
2-8
14
15
2-9
16
By identifying data sources in metadata, the administrator has the ability to control access and change
the location of data sources without changing the applications that use the data. Resources, tables, reports,
and stored processes can be secured by user or by group.
17
2-10
18
Many properties can be specified when defining a SAS program as a stored process, including where it
should run, where the program is stored, the name of the program, and how the results of the program will
behave.
19
20
21
SAS ETL Studio is targeted at the same user community that used SAS/Warehouse Administrator.
SAS/Warehouse Administrator is still available in SAS9, but nothing has changed since Release 8.2
of the SAS System.
2-11
2-12
...
22
23
24
25
2-13
2-14
26
27
28
29
2-15
2-16
30
32
33
2-17
2-18
34
35
36
37
2-19
2-20
38
39
2-21
40
SAS does not need to be installed on the local machine in order to access SAS data sets or SAS Stored
Processes using the SAS Add-In for Microsoft Office.
2-22
42
43
2-23
44
SAS Web Report Studio requires data to be defined in an Information Map and does not work directly
with a data table. Both tabular reports and graphs can be created using the Report Wizard or the Report
Builder.
45
2-24
46
47
48
49
2-25
2-26
50
51
Overview .......................................................................................................................3-3
3.2
3.3
Case Study..................................................................................................................3-16
3-2
3.1 Overview
3.1 Overview
Course Data
The data used in this
course is from Orion Star
Sports & Outdoors, which
is a fictitious retail company selling sports and
outdoor products
has retail stores in many countries throughout the
world
sells products in retail stores, through catalog mail
orders, and over the Internet
utilizes the Orion Star Club to track purchases,
enabling analyses of buying patterns and providing
a basis for CRM activities and targeted product
offerings.
3
3-3
3-4
The United States hosts the headquarters as well as most of the administrative functions. Each country
has a retail company associated with it, and all offices were operational within the whole time range of
the data (1998 through early 2003) except the Belgian office, which opened in 1999.
3.1 Overview
3-5
3-6
3.1 Overview
3-7
3-8
Customer names, as well as street addresses, are fictitious, but real city names, county/region names, and
country names are used.
This data is controlled by means of pointers (ID columns), as is often seen where geographical data is
gathered from official sources that are maintained externally to the organization. This approach facilitates
changes to information such as postal codes and street names.
3.1 Overview
3-9
3-10
10
3.1 Overview
3-11
11
The Information Systems Department has built a data warehouse by extracting data from Online
Transactional Processing Systems (OLTP) and Enterprise Resource Planning (ERP) systems, as
well as data from external sources.
The business users use the data warehouse
to create data marts
to perform advanced analyses
for querying and reporting.
Management and C-level executives use the SAS Business Intelligence tools to access the information
stored in the data warehouse.
3-12
13
Normalized
(relational)
model
Dimensional
model
...
14
3-13
3-14
The normalized data model contains a number of Start_Date and End_Date columns that are used
to ensure an accurate history of changes. Therefore, an item can exist more than once in a particular table
but only once within a particular time interval.
The Product and Organization tables are organized hierarchically. They use product-level and
organization-level IDs to determine the placement of an entity within the appropriate hierarchy.
3-15
15
The dimensional data model is the result of an ETL (Extract, Transform, and Load) process and represents
one possible data mart. The dimensional model is a star schema with a fact table that contains orders. The
dimension tables represent data for time, geography, customers, products, suppliers, and employees.
3-16
17
18
19
Define
Data Libraries
Create
Stored Processes
Register
Source Tables
Define
Target Tables
Create
Information Maps
Metadata
Create
ETL Jobs
Create Reports
Create
OLAP Cubes
3-17
3-18
4.2
4.3
4.4
4-2
4-3
The SAS Intelligence Value Chain is a strategic framework for delivering enterprise intelligence,
emphasizing the incremental value each component brings, and the strategic value gained from
integrating individual components within the framework of an enterprise-wide strategy.
From data manipulation tools to business reporting, along with interfaces to unparalleled analytic
capabilities, SAS delivers reliable and easy-to-use technologies that leverage historical investments to
drive immediate results.
Each component of the SAS Intelligence Architecture leverages the sharing of common metadata and a
common repository.
No one component is isolated, because communication can occur wherever there is a need for metadata
sharing and exchange.
All components take advantage of, and can utilize, metadata.
The exploitation of this centralized and shareable metadata further enhances the value achieved with
each component while driving down the cost of implementation.
4-4
Metadata Definitions
SAS Management Console manages resources and
controls them by creating and maintaining metadata
definitions for each resource or control.
The metadata definitions created
in SAS Management Console are
stored in a repository on a SAS
Metadata Server, where they are
available for other applications
to use.
SAS Metadata Server
The SAS Open Metadata Architecture is a general-purpose metadata management facility that provides
common metadata services for applications.
4-5
4-6
Metadata Profile
When SAS Management Console is invoked, a metadata
profile is selected that specifies
the metadata server to which metadata definitions will
be written
the active metadata repository
information required to connect to the metadata
server.
10
When a metadata profile is defined, the server to which the application connects is specified along with
the user ID it uses to connect to the server. When an application opens a metadata profile, it has access
to the metadata on the specified server based on the security credentials of the user ID under which the
connection was made.
4-7
4-8
Metadata
Repository
MainRepos
ARepos
BRepos
...
11
After you open the metadata profile to connect to the metadata server, you can begin using the
SAS Management Console to create metadata definitions. As you create definitions, they are stored
in the active repository on the metadata server.
12
4-9
Repositories
SAS Management Console can be used to set up
a hierarchy of repositories on the metadata server,
consisting of different repository types including:
Foundation specify the parent repository for all other
Repositories repositories on the server. This
repository contains resource definitions
that are used throughout the enterprise.
Project
specify development repositories that
Repositories can be used for change management.
...
13
In addition to these two repository types, a third type can also be defined:
Custom
Repositories
A repository that is dependent upon another repository inherits metadata from the repository on which it
is dependent.
4-10
14
15
Metadata Users
Metadata users may have their own metadata identity
and/or belong to a user group. All users who can access
the metadata server implicitly belong to a special group
named PUBLIC.
There are several different types of users in the metadata,
including these:
SAS
Administrator
(sasadm)
sasadm)
16
Metadata Server
17
SASMain
Foundation
Workspace Server
Stored Process Server
PUBLIC
OLAP Server
sasadm
sasdemo
...
4-11
4-12
19
Application Management
plug-ins for configuring SAS applications.
20
4-13
Metadata
Manager
Schedule
Manager
21
User Manager
License Manager
allows you to view information about the SAS licenses installed on a machine, as
well as details about the machine.
XMLMap Manager
allows you to import and create XMLMaps, which are XML files that describe
how the SAS XML LIBNAME engine should interpret XML markup.
4-14
Plug-In Information
Because each plug-in has its own functions, the
SAS Management Console menu bar and toolbar change
whenever you select a node within the navigation tree.
Different nodes within a single plug-in can activate
different menu items and tools.
22
The Help for each plug-in is only available when the plug-in is active. For example, in order to view the
Help for the Metadata Manager plug-in, you must first select the Metadata Manager plug-in or an object
inside the plug-in in the navigation tree.
24
4-15
4-16
Menu Bar
...
25
The menu bar provides six standard menus and one that is controlled by the selected plug-in:
File
provides selections for opening objects, changing or closing the current metadata profile,
and viewing properties for an object.
Edit
View
provides selections for refreshing the information displayed in the application and for
moving up a level in the navigation tree.
Actions
provides selections that are valid only for the current plug-in. (If no plug-in is selected, the
Actions menu is not present. The Actions menu items are different for each plug-in.)
Tools
Roadmaps
provides access to roadmaps, which are user assistance documents designed to guide you
through SAS Management Console tasks.
Help
provides options for selecting help for SAS Management Console or for the current plugin. Help for a specific plug-in is only available when the plug-in is selected in the
navigation tree
4-17
Toolbar
26
...
4-18
Context Bar
27
...
The context bar identifies the active repository, which is the metadata repository to which you are
storing metadata definitions. You can select the repository that you want to access from the Repository
drop-down list.
4-19
Navigation Tree
28
...
The navigation tree displays an organized list of all of the installed plug-ins and the objects that are
associated with each plug-in. The plug-ins are organized into two main categories:
Environment Management
Application Management
Selecting a plug-in icon in the navigation tree activates the plug-in and displays information for that
plug-in in the display area. To display the objects associated with the plug-in in the navigation tree,
click the plus sign next to the plug-in icon to expand its contents (not all plug-ins are expandable).
4-20
Display
Area
29
...
The display area is used to display detailed information about objects selected in the navigation tree. The
information displayed depends not only on the object selected in the navigation tree, but also on the plugin that is active. Some plug-ins (such as the User Manager) utilize the display area for entering metadata.
If you select an object (plug-in or other object) in the navigation tree that contains sub-folders, the display
area lists the folders. If you select a folder in the navigation tree, the display area lists the objects that are
contained in the folder.
If you select an object in the navigation tree that does not contain any sub-folders, the display area
displays any metadata definitions that are associated with that object. For example, if you select a server
definition in the navigation tree, the display area lists all of the connections that have been defined for the
server.
Status Line
30
...
The status line, at the bottom of the SAS Management Console window, displays the following
information:
number of objects selected or the number of objects contained in the currently selected folder
or plug-in
domain and user ID defined in the metadata profile used to log on to the active metadata server
machine and port number of the active metadata server.
4-21
4-22
This demonstration shows how to use the SAS Management Console to define a data library.
The values shown above will be different than those used in class.
4-23
4-24
Select
7. Specify Orion Star Gold Library as the Name of the new library.
Select
4-25
b. Select
Using the
button only allows you to browse the machine where the SAS
Management Console is running. If the path is located on a different server, it must be
typed in manually.
4-26
Select
.
in the New Path Specification window.
e. Select
f.
Select
Select
Select
4-27
4-28
11. The new library should now appear in the display area of SAS Management Console.
12. To view the LIBNAME statement that will be created from the metadata, right-click
Orion Star Gold Library and select Display Libname.
Select
32
Source Designer
The Source Designer is a wizard-driven
interface that enables you to define the
physical layout of existing tables using a
data dictionary or metadata information
from the source system.
The result of running the Source Designer
successfully is a metadata registration
that describes the data source.
33
4-29
4-30
This demonstration shows how to register the metadata for the tables in the Source Tables Library.
1. To invoke the Source Designer, right-click Orion Star Gold Library and select Import
Tables.
2. Select SASMain as the server to connect to, because it is the server where the data resides.
Select
4-31
4. Because the wizard was invoked from the library you want to import tables for, accept the defaults by
selecting
.
5. Select
Select
4-32
Select
7. The tables are now listed in the display area of SAS Management Console.
4-33
4-34
10. On the Authorization tab, grant the Read permission to the PUBLIC group by selecting the
appropriate check box.
11. Select
5.2
5.3
5.4
5-2
5-3
5-4
5-5
When you open a metadata profile whose default repository is change-managed, metadata in the
change-managed repository is displayed in the Inventory tree and the Custom tree. Metadata in the
Project repository is displayed in the Project tree.
The Project tree contains any metadata that has been checked out of the change-managed repository
and any new metadata objects that have been added.
Typically, users will not have the appropriate privilege to directly add or update metadata directly in
a change-managed repository. You must check metadata objects out of and into the change-managed
repository.
To update an existing metadata object that is under metadata source control, use the Inventory tree or
the Custom tree to check out the object from the change-managed repository. The object will appear
in the Project tree, where you can update the object's metadata.
After an object has been checked out by one person, it is locked so that it cannot be updated by
another person until the object has been checked back in.
You do not have to check out a library in order to add metadata about a table in that library.
If two or more parent objects share a common object such as a table, a primary key, a note, or a
document, and you check out one of these parent objects, only you will be able to check out the
other parent objects that share the common object. (Other users will not be able to access the
common object that you have checked out, and the shared object is required in order to check out
a parent object that uses that shared object.) For example, suppose that two jobs use the same source
table. If you check out Job 1, only you will be able to check out Job 2.
When you add a new metadata object, it goes directly into the Project repository. The object will
appear in the Project tree, where you can update the object's default metadata.
The Fetch option is used to get a copy of a metadata object for testing purposes. The copied object is
not checked out, so the original object is not locked. The copied object can be modified, but it cannot
be checked in. Fetched items will remain in the Project repository until they are deleted.
When you are finished working with all objects in the Project repository (and the Project tree), use
the Check In feature to remove the objects from the Project repository and store them in the changemanaged repository. A check-in operation checks in all of the metadata objects that are in the Project
repository. You cannot check in some objects and leave other objects in the Project repository,
therefore it may be convenient to work with small sets of related objects in the Project repository.
To remove a metadata object from the Project repository, use the Delete option or the Undo Check
Out option. To remove a metadata object from both the Project repository and the change-managed
repository, use the Destroy option.
5-6
For example, you could use a data modeling tool to create a model for a set of tables, save the model in
CWM format, and then use the Metadata Importer wizard to import the model into a metadata repository.
In SAS ETL Studio, you could view the properties of each table and verify that the appropriate metadata
was imported. The tables could then be used in SAS ETL Studio jobs.
The Process Library in SAS ETL Studio contains two data quality transformation templates: Create
Match Code and Apply Lookup Standardization. These templates enable you to increase the value
of your data through data analysis and data cleansing.
10
For details about creating your own Java plug-ins, see the plug-in appendix to the SAS ETL Studio
User's Guide.
5-7
5-8
11
12
14
Menus and
Tools
15
5-9
5-10
Shortcut Bar
16
Metadata Importer
Metadata Exporter
Process Designer
continued...
17
...
Options
...
18
Tree View
The SAS ETL Studio Tree View enables you to
view the metadata
associated with
the current
metadata
repository
display different
views or trees
Tree View
of the current
repository.
19
5-11
5-12
Tree View
There are several tabs available in the tree view area:
Inventory Tree
continued...
20
...
The items in the Inventory tree view are grouped according to a set of predefined groups that an ETL user
will typically define from within SAS ETL Studio (tables, OLAP cubes, jobs, and so on).
Tree View
Custom Tree
continued...
21
...
The items in the Custom tree view are grouped according to whatever groups the ETL user has defined
(Source Tables, Target Tables, Sales Cubes, and so on). These groups could be determined by object
types, intended uses for the objects, data marts, lines of business, and so on.
5-13
Tree View
Process Library Tree
22
...
Selecting one of the transformations creates a template in the process view, with drop zones into which
the user may drag-and-drop items.
Addititional tabs may be available in the tree view area depending on the selected options and
settings.
5-14
23
The Analysis folder in the Process Library tree includes the following templates:
Correlations
Correlations Report
Distribution Analysis
Frequency
Frequency Report
Summary Statistics
The Data Transforms folder in the Process Library tree includes the following templates:
Append
creates a single target table by combining data from several source tables.
Apply Lookup
Standardizations
Data Transfer
Data Validation
Extract
selects multiple sets of rows from a source and writes those rows to a
target.
loads source data into a fact table and translates business keys into
generated keys.
Mining Results
integrates a SAS Enterprise Miner model into a SAS ETL Studio data
warehouse. Typically used to create target tables from a SAS Enterprise
Miner model.
SAS Rank
ranks one or more numeric variables in the source and stores the ranks in
the target.
SAS Sort
reads data from a source, sorts it, and writes the sorted data to a target.
SAS Splitter
selects multiple sets of rows from one source and writes each set of rows
to a different target.
loads source data into a dimension table, detects changes between source
and target rows, updates change tracking columns, and applies generated
key values. This transformation implements slowly changing dimensions.
SQL Join
selects multiple sets of rows from one or more sources and writes each set
of rows to a single target.
Standardize
Surrogate Key
Generator
Transpose
User-Written Code
5-15
5-16
The Output folder in the Process Library tree contains the following template:
List Data
The Publish folder in the Process Library tree includes the following templates:
Publish to Archive
Publish to Email
Publish to Queue
24
25
...
5-17
5-18
Overview Window
The Overview window shows you the complete process
from the process view.
From within the Overview window, you can control which
part of the process is displayed in the Process View
window.
26
27
Source Designer
The Source Designer is a wizard-driven
interface that enables you to define the
physical layout of existing tables using a
data dictionary or metadata information
from the source system.
The result of running the Source Designer
successfully is a metadata registration
that describes the data source.
28
Unlike the SAS Warehouse Administrator product, which requires that you create Operational Data
Definitions (ODDs) one table at a time, the Source Designer enables you to input the metadata from
multiple tables with one pass through the wizard.
If the table is stored in an ERP System, the corresponding Data Surveyor will be invoked. The Data
Surveyor contains information about the metadata of the source system.
If the table is a flat file, you can use a wizard to define the record layout.
The Source Designer can be invoked by following these steps:
Click on the Source Designer icon from the Shortcut bar.
Select Tools Source Designer.
Right-click on the Source Tables group and select New Object Source Table.
5-19
5-20
Target Designer
The Target Designer is a wizard that
allows metadata to be entered for a target.
In designing the target table, you can
access any metadata about any
source tables and columns registered
in the metadata repository
override any metadata that was
imported from another source and add
new columns to the target table
create indexes on the target table
being created.
29
Target Designer
The person designing the target table has full control over
the type of table being built.
The types of targets that can be built include
database types that are supported by the
SAS/ACCESS products
SAS data sets (including both data files and data views)
SAS/SHARE data sets
SPDE tables.
30
5-21
5-22
31
An empty job can be created, without importing metadata from any predefined target table, by clicking
without selecting the metadata for a table. Objects from the tree view can then be dragged
and dropped into the empty job.
You can invoke the New Job wizard by following these steps:
Click on the Process Designer icon from the Shortcut bar.
Select Tools Process Designer.
Right-click on the Jobs group and select New Object Job.
5-23
Additional Wizards
Other wizards available to provide assistance with various
tasks in SAS ETL Studio include
Metadata Importer
Metadata Exporter
Cube Designer
Transformation Generator wizard.
You can also install optional data surveyor wizards, which
provide access to the metadata in enterprise applications,
such as PeopleSoft, SAP R/3, Siebel, and Oracle.
32
These wizards can be invoked from the Shortcut Bar or the Tools pull-down menu of SAS ETL Studio:
Metadata Importer
enables you to import metadata from other applications that support the
Common Warehouse Metamodel (CWM) format. Optional bridges are
available for other formats.
Metadata Exporter
enables you to export metadata to other applications that support the Common
Warehouse Metamodel (CWM) format. Optional bridges are available for other
formats.
Cube Designer
is a target designer that enables you to create a cube, a data store that supports
Online Analytical Processing.
Transformation
Generator
5-24
Options Window
The Options window can be used to define standard
settings for the SAS ETL Studio interface.
There are several tabs in the Options window:
General
Process
Editor
Metadata Tree
SAS Server
Data Quality.
33
Using the Options window tabs, you can control the following:
General
controls the overall display of SAS ETL Studio and the functionality of the wizards.
Process
Editor
controls the look and feel of the SAS text editor for generated code.
Metadata Tree
controls the tree view in the middle portion of SAS ETL Studio.
SAS Server
specifies the SAS server to be used with SAS ETL Studio, and tests the connection to
the server.
Data Quality
specifies options to control the locale, the types of files to be used by the data quality
plug-ins, and the location of the Quality Knowledge Base (QKB).
Create
Stored Processes
Register
Source Tables
Define
Target Tables
Metadata
Create
Information Maps
Create
ETL Jobs
Create Reports
Create
OLAP Cubes
34
Create
Stored Processes
Register
Source Tables
Define
Target Tables
35
Metadata
Create
Information Maps
Create
ETL Jobs
Create Reports
Create
OLAP Cubes
5-25
5-26
Define
Data Libraries (+)
2. Define Source
Tables Metadata
3.
Define Target
Tables Metadata
4.
Define and
Run Jobs
36
Define
Data Libraries (+)
Libraries
2.
Define Source
Tables Metadata
3.
Define Target
Tables Metadata
4.
Define and
Run Jobs
Jobs
Source Tables
Target Tables
Exercises
37
Demo
Exercises
...
Define
Data Libraries (+)
2.
Define Source
Tables Metadata
3.
Define Target
Tables Metadata
4.
Define and
Run Jobs
Orders
Demo
Order_Item
Exercises
Product_List
...
38
Define
Data Libraries (+)
2.
Define Source
Tables Metadata
3.
Define Target
Tables Metadata
4.
Define and
Run Jobs
OrderFact
ProductDim
Demo*
Exercises
...
5-27
5-28
Define
Data Libraries (+)
2.
Define Source
Tables Metadata
3.
Define Target
Tables Metadata
4.
Define and
Run Jobs
40
Populate the
ProductDim table
Demo
Exercises
...
Source Tables
41
...
SQL Join
...
42
Loader
43
...
5-29
5-30
Source Table
...
44
SAS Extract
45
...
Loader
...
46
Define
Data Libraries (+)
Libraries
2.
Define Source
Tables Metadata
3.
Define Target
Tables Metadata
4.
Define and
Run Jobs
Jobs
Source Tables
Target Tables
Exercises
47
Demo
Exercises
5-31
5-32
This demonstration shows how to create a logical grouping in the Custom tree view to organize your
warehouse metadata. It also shows how to create a library definition and store it in the new logical group.
1. Invoke SAS ETL Studio by selecting Start All Programs SAS SAS ETL Studio 9.1.
2. Select the metadata profile BIArchitecture, then select
Select
Select
5-33
5-34
The first step in using SAS ETL Studio to build the Orion Star marketing data mart is to create groups
in the Custom tree view. These groups are simply logical groupings of the metadata that comprise the
repository. There is no corresponding physical file structure for the groups that are created. The groups
can be defined using whatever logical grouping is relevant to your organization.
4. Select the Custom tab in the tree view area of SAS ETL Studio.
5. Select
The Foundation repository already has an Ungrouped group, which already contains several items.
These were created during the configuration of the SAS Intelligence Architecture. Do not delete
these files, as some will be used in future demonstrations and exercises.
6. Right-click Foundation and select New Group from the pop-up menu. The default name of the new
group is Untitled.
5-35
5-36
10. Under SAS Libraries, choose SAS Base Engine Library, then select
11. Type Target Tables Library in the Name field and select
5-37
5-38
12. Type Target in the Libref field, select BASE in the Engine field (default), then click
define a new path because what you want is not in the list of available items.
to
14. Select
items list.
Select
5-39
to close the Browse window. Verify the path selected above is now in the Selected
5-40
5-41
5-42
17. Move the new library to the Libraries group using one of the methods below:
Click on Target Tables Library, drag-and-drop it on top of the Libraries group.
Right-click on Target Tables Library, select Group, expand Foundation, select
Libraries, select
5-43
Exercises
Create several logical grouping in the Custom tree view to organize your warehouse metadata.
If you did not follow along with the demonstration, complete the steps of the demonstration to define the
Libraries group and Target Tables Library.
1. Create Logical Groups
Create the following logical groups:
Source Tables
Target Tables
Jobs
Libraries (if you did not follow along with the demonstration).
2. Add Library Definitions
Use the New Library Wizard to create a metadata definition for the following libraries and move them
to the appropriate group:
Library Name:
Libref:
Srcdata
Library Type:
Path:
C:\Workshop\winsas\sbip\Orion_Star_15AUG03\ordetail
Server:
SASMain
5-44
Library Name:
Libref:
Target
Library Type:
Path:
C:\Workshop\winsas\sbiovr\DataMarts
Server:
SASMain
5-45
50
The Source Designer supports a number of specific data formats that have been licensed for your
site. The specific format will often give better results than the generic format, which has not been
optimized for particular kinds of data. Use the format that most closely matches your data
whenever possible.
51
...
5-46
Define
Data Libraries (+)
2.
Define Source
Tables Metadata
3.
Define Target
Tables Metadata
4.
Define and
Run Jobs
Orders
Demo
Order_Item
Exercises
Product_List
52
5-47
The next step in the implementation of the Orion Star marketing data mart is to define the source table to
be used in the ETL process.
1. Select Source Designer from the Shortcut bar of the SAS ETL Studio desktop.
2. Select SAS as the metadata import source type.
Select
5-48
Select
4. Select the source table ORDERS from the Select Tables list.
Select
Select
5-49
5-50
Exercises
55
56
...
Selecting Cube Designer in the first window of the Target Designer will launch the Cube Designer
wizard, which is discussed in the next chapter.
5-51
5-52
Define
Data Libraries (+)
2.
Define Source
Tables Metadata
3.
Define Target
Tables Metadata
4.
Define and
Run Jobs
OrderFact
ProductDim
Demo*
Exercises
The next step in the implementation of the Orion Star marketing data mart is to use the Target Table
Designer to define the target tables for the ETL process.
1. Select Target Designer from the Shortcut bar of the SAS ETL Studio desktop.
2. Select Target Table as the type of target to design.
Select
5-53
5-54
Select
can be used to display the interface where you can specify notes, user
responsibilities, table attributes, and extended attributes for the target table you are defining.
Order_ID
Product_ID
Quantity
Total_Retail_Price
CostPrice_Per_Unit
Order_Type
ORDERS table
Order_Date
Delivery_Date
Select
5-55
5-56
5. Review and verify the metadata that was imported for each of the columns.
.
.
Sort Order
Informat
Format
Is Nullable
indicates whether or not the column can contain null or missing values.
Select
5-57
The type of file selected in the DBMS field controls the type of storage intended to be utilized
for the new target table. The selection arrow shows a list of DBMSs that are valid in the
current context (that is, SAS, Oracle, SAP, Sybase, and so on).
To add a new library definition, select
.
To edit an existing library definition, select
To specify encryption, compression, or other valid SAS data set or view options, select
.
Select
5-58
The metadata definition for the target table OrderFact is now defined.
8. Move the table OrderFact to the Target Tables group.
5-59
12. Select the Delivery_Date row so that the new columns will be added to the end of the list.
New columns are added after the row of information that is currently selected.
13. Select
A valid SAS variable name starts with a character and has a maximum of 32 characters.
A valid length is 2 to 8 for numeric types and up to 32,767 for character types. The
description is the label that gets associated with the column when it is displayed in
selection lists in SAS ETL Studio or other SAS applications.
5-60
14. Repeat the steps above to add the following new columns:
Name
Description
Type
Order_Qtr
Quarter Order
was Placed
numeric
Order_Month
Month Order
was Placed
numeric
Delivery_Time
Number of
Days Until
Delivery
numeric
15. Select
5-61
Exercises
Create the target table metadata for several target tables.
4. Add the OrderFact Target Table Definition (if you did not follow along with the demonstration)
Create metadata for the OrderFact target table in the Target Tables group.
Define the following new columns to the OrderFact table:
Name
Description
Type
Order_Year
numeric
Order_Qtr
numeric
Order_Month
numeric
numeric
The Product_Group column must be added manually to the target table metadata.
Metadata for the rest of the columns can be imported from the Product_List source table.
5-62
60
The New Job wizard can also be used to create an empty job. After you have an empty job, you can create
a process flow diagram by dragging and dropping tables and transformations into the Process Designer
window.
61
...
Define
Data Libraries (+)
2.
Define Source
Tables Metadata
3.
Define Target
Tables Metadata
4.
Define and
Run Jobs
62
Populate the
ProductDim table
Demo
Exercises
5-63
5-64
At this point, source tables have been defined and the data in those tables can be viewed. Target table
definitions have also been specified, but no data exists in any of the target tables. The next task is to
define a job, where metadata can be specified that will allow the extraction, transformation and loading
of the source table data to the target tables.
1. Select Process Designer from the Shortcut bar of the SAS ETL Studio desktop. This activates the
New Job wizard.
Select
5-65
5-66
Select
Tables can have similar names make sure to select OrderFact and not Order_Fact.
.
5-67
This completes the steps for the New Job wizard, writes the job metadata to the repository and opens
the Process Designer window.
In the Process Designer window, there should be an icon for the OrderFact target table, the Loader
icon, and an empty icon labeled Place table or transform here.
The Place table or transform here icon is simply a placeholder for the source data you intend to load
into the target table. This could be used for a single table, multiple tables, or a transformation.
The Loader icon represents the physical loading of data into the target table. The load process
metadata can be accessed via the properties of the Loader icon.
5-68
The target table icon should reflect the table that will be loaded when the job is run and is added
automatically if you specified a target table in the New Job wizard.
In this demonstration, you want to load the OrderFact table by using an SQL Join to the Orders and
Order_Item source tables.
5. Select the Process Library tab in the tree view area of SAS ETL Studio.
6. Expand the Data Transforms folder and locate the SQL Join transformation.
7. Drag the SQL Join transformation to the Process Designer window and drop it in the area labeled
Place table or transform here.
The Process Designer view will update to show the SQL Join transformation and two new
placeholders for the tables to be joined.
If you want to simply load a single source data table into the target data table, then
you can drag and drop the table from the Source Tables group into the icon
labeled Place table or transform here. If a more complex data transformation is
required, you can drag and drop one of the supplied data transformations (from
the Process Library tab) into the empty icon.
8. From the Custom tab of the tree view area, locate the Source Tables group element and expand.
9. Drag the table ORDERS onto one of the Place table or transform here boxes.
10. Drag the table ORDER_ITEM onto the other Place table or transform here box.
To add additional tables to an SQL Join, drag and drop the additional tables onto the
SQL Join icon.
5-69
5-70
Notice the name of the target table. This is a temporary table that will be used as input for
the next step of the process. At this point, this is not the final target table that you will load.
5-71
The temporary target table does not have the new columns that you created in the OrderFact table. You
can add them here by right-clicking in the background of the target table variable list, selecting
New Column and manually entering the column attributes. Because you have already defined those
columns, you can simply import that metadata here without having to enter the information manually,
again. Importing the column metadata also ensures consistency.
13. Right-click in the background of the Target table variable listing and select Import Columns from
the pop-up menu.
14. Expand the repository Foundation, the group Target Tables , and the table OrderFact and move the
variables Order_Year, Order_Qtr, Order_Month and Delivery_Time to the Selected Columns list.
Select
tab.
. These additional variables now show up in the Target table list on the Mapping
5-72
You now need to derive mappings for each of the new columns. There are no columns in the source table
that can be mapped directly to the new target table columns, but you can derive a value from the columns
that do exist in the source table.
15. Right-click Order_Year and select Expression from the pop-up menu.
16. In the Expression Builder window, select Date and Time to display a listing of all date/time
functions. Double-click the Year(date) function (or select it and click
).
The Expression Text field is populated with the function syntax and the placeholder for the argument
is highlighted.
An expression can be typed directly into the Expression Text window, or it can be built by
using the functions, data sources, and buttons within the Expression Builder.
5-73
17. To fill the high-lighted place holder (<numValue>) with a valid column, select the Data Sources tab.
Expand the ORDERS table and select Order_Date.
Select
5-74
18. Select
Select
to return to the SQL Join Properties window. A warning message may appear:
5-75
Exercises
In this exercise, you will define a job and enter metadata that will allow the extraction, transformation,
and loading of the source table data to the target tables.
Qtr(Order_Date)
Order_Month
Month(Order_Date)
Delivery_Time
5-76
Select
to close the SQL Join Properties window and return to the Process Designer
window.
or File Close.
Close the Process Designer window and save the changes by selecting
Move the Populate the OrderFact table job to the Jobs group in the Custom tab
of the tree view.
IMPORTANT: Make sure to close the Process Designer window and save the changes
before continuing on to the next step.
5-77
The ProductDim table contains a new column that does not exist in the source tables and
must be derived. Derived expressions cannot be done as part of the step to load the job.
The Extract data transformation will extract data and allow expressions to be derived
for new columns.
Add Product_List from the Source Tables group as the input source for the Extract.
Add a new column to the Extract and derive expressions (in the Extract properties, Mappings tab):
Import Product_Group from the ProductDim target table
Create an expression to load the Product_Group column by reading the value in
Product_Ref_ID and writing it out using the product. user-defined format.
HINT: The PUT function can be used to read a data value from a column and write it out using
a custom format - put(Product_Ref_ID, product.).
The format name product. will need to be typed manually (do not forget the .).
Move the new job from the Ungrouped group to the Jobs group.
5-78
1. Open the Process Designer window for the Populate the OrderFact Table job by expanding the Jobs
group (on the Custom tab of the tree view). Right-click on the Populate the OrderFact Table job
and select View Job (or double-click the job).
2. Right-click on the Loader icon and select Properties.
3. Select the Load Technique tab and specify a Load Technique of Refresh.
5-79
removes all the rows from the target and copies all the rows from the source into the target
Append
appends the rows from the source to the end of the target
Update
inserts any rows that are in the source but not in the target
The Before Loading options can affect performance when loading data into the target table:
Drop Table
deletes and re-creates the entire target. Selecting Drop Table minimizes the
physical size of the target
Truncate Table
marks existing rows as deleted and retains those rows in physical storage. New
rows are appended to the existing rows
Drop Indexes
specifies that any indexes on the table are to be deleted before loading. The
appropriate indexes are then re-created after loading based on target metadata
For information on additional options, see the online help for the Loader Properties window.
5-80
5. Select the Mapping tab. To map the new columns created earlier, right-click in the Target table area
and select Quick Map.
6. Select
Quick Map works only if the columns specified for both the source and target have the same
metadata attributes. If this is not the case, 1-1 mappings can be created by selecting the
column in the source area, selecting the column in the target area, then right-clicking and
selecting New Mapping from the pop-up menu.
to return to the Process Designer window.
5-81
7. To load the target table, submit the job by right-clicking in the background of the Process Designer
window, then select Submit from the pop-up menu (a status window displays while processing is
occurring).
8. If the Source Code Execution window closes without displaying any error message, the job ran.
Select the Log tab at the bottom of the Process Designer to view the log information from this job.
Warning messages from the APPEND procedure (the last step in the code) are expected.
9. Close the Process Designer window by selecting File Close and save the changes if prompted.
5-82
10. To view the data, right-click on the OrderFact table in the Target Tables group (on the Custom tab
from the tree view). Select View Data from the pop-up menu.
Scroll to the right when viewing the data to make sure that the derived expressions for the
new columns resulted in valid data.
5-83
Exercises
In this exercise, you complete the final step of creating the ETL job, loading the target table.
5-84
69
70
71
72
5-85
5-86
73
74
75
Change Management
SAS ETL Studio enables you to create metadata objects
that define sources, targets, and the transformations that
connect them. These objects are saved to one or more
metadata repositories.
The change management feature (or more specifically,
metadata source control) enables multiple SAS ETL
Studio users to work with the same metadata repository at
the same time without overwriting each other's changes.
76
5-87
5-88
Change Management
Change management features in SAS ETL Studio include:
menus that support change management operations
such as check out and check in
the Inventory tree and the Custom tree for working
with metadata that is contained in a change-managed
repository
the Project tree for working with metadata that is
contained in a project repository
an audit history for each metadata object.
77
5-89
Active in the Inventory tree or the Custom tree. Copies the metadata for one or
more objects from a change-managed repository into the project repository.
Locks the objects in the change-managed repository.
Check In Repository
Active when you select the project repository icon in the Project tree. Moves
all metadata from the project repository to the appropriate change-managed
repository.
Undo Checkout
Active in the Project tree. "Undoes" the check-out state of the selected object.
After you complete this action, the object is removed from the project
repository and is no longer checked out.
Destroy
Active for checked-out objects in the Project tree. The object is deleted from
the project repository, and upon check in, it is also deleted from the
appropriate change-managed repository. You cannot undo a Destroy operation.
Make sure that the object to be destroyed is not required in any SAS ETL
Studio job.
Fetch
Active in the Inventory tree or the Custom tree. Use to get a copy of a
metadata object for testing purposes. The copied object is not checked out
from the change-managed repository, so the original object is not locked. The
copied object can be modified, but it cannot be checked in. Fetched items will
remain in the project repository until they are deleted.
Add to Project
Active in the Project tree. Displays the Check Out wizard, which copies the
metadata for one or more objects from a change-managed repository into the
project repository. Locks the objects in the change-managed repository.
History
Active for some objects in the Inventory tree, the Custom tree, and the Project
tree. Lists all change management transactions for the selected object.
5-90
Change Management
After an object has been checked out by one person, it
is locked so that it cannot be updated by another person
until the object has been checked back in.
The only people who can change the metadata in a
change-managed repository are
the person who started the metadata server
administrators who have write access to the repository
any users who are authorized to use a project repository
for the change-managed repository.
78
5-91
5-92
Libref:
Srcdata
Library Type:
Path:
C:\Workshop\winsas\sbip\Orion_Star_15AUG03\ordetail
Server:
SASMain
to access the
to access the
g. Repeat steps a f to define the metadata for the Order_Item source table from the Source Tables
Library.
h. Repeat steps a f to define the metadata for the Product_List source table from the Source Tables
Library.
5-93
.
.
Columns to Select:
PRODUCT_LIST
Product_ID
Product_Name
Product_Ref_ID
Select
e. Review and verify the metadata that was imported for each of the columns.
5-94
f. Select
.
.
5) Select
appear; select
5-95
to close the SQL Join Properties window and then File Close to close the
e. Select
Process Designer window.
7. Define a Job to Load the ProductDim Table
a. Select the Process Designer from the Shortcut bar of the SAS ETL Studio desktop. This will
activate the New Job wizard.
b. Type Populate the ProductDim Table in the Name field. Select
c. Select the table ProductDim from the Select Tables list. Select
.
.
e. Select the Process Library tab in the tree view area of SAS ETL Studio.
f. Expand the Data Transforms folder and locate the process Extract.
g. Drag Extract to the area labeled Place table or transformation here in the Process Designer
window.
h. Select the Custom tab in the tree view area, expand the Source Tables group, and drag the table
Product_List over the area labeled Place table or transformation here in the Process Designer
window.
5-96
o. Select
select
p. Select
5-97
q. Select File Close to close the Process Designer window and select
changes.
to save the
5-98
c. Select the Load Technique tab and specify a Load Technique of Refresh.
d. Activate the radio button Drop Table.
5-99
e. Select the Mapping tab. To map the new columns created earlier, right-click in the Target table
area and select Quick Map.
f. Select
g. To load the target table, submit the job by right-clicking in the background of the Process
Designer window, then select Submit from the pop-up menu.
h. Select
i. Select the Log tab at the bottom of the Process Designer to view the log information from this job.
j. Close the Process Designer window by selecting File Close and save the changes if prompted.
k. To view the data, right-click the ProductDim table in the Target Tables group (on the Custom tab
from the tree view). Select View Data from the pop-up menu.
5-100
6.2
6.3
6.4
6-2
What Is OLAP?
OLAP (Online Analytical Processing) is a software
technology that enables users to dynamically analyze
data that is stored in multidimensional database tables.
Because of the way the data and its relationships are
stored, they are readily available for detailed queries and
analysis.
What Is OLAP?
Central to the OLAP storage process are cubes.
A cube is a set of data that is organized and structured
in a hierarchical, multidimensional arrangement, often
with numerous dimensions and levels of data.
6-3
6-4
What Is OLAP?
The classification information in the data is organized
into dimensions.
For example, a TIME dimension might have all input
columns related to time (date, month, year) grouped as
levels.
Dimension levels can then be organized into a hierarchy.
The hierarchy determines the logical order of the levels in
a dimension. The logical order makes it possible for users
to drill down into the cube data.
What Is OLAP?
Cubes also contain measures, which are based on
numeric analysis columns in the input tables.
These numeric values are summarized and stored in
the cube for quick access and analysis during a query.
Examples of measures include sales figures and
operational costs.
Queries in SAS OLAP Cube Studio are performed using the industry standard MDX language
(multidimensional expression language), which is similar to SQL but can use cubes as input.
This provides improved performance over previous releases of SAS.
6-5
6-6
...
When the OLAP user requests a piece of metadata, the SAS Metadata Server handles
accessing metadata from the repository
providing the metadata to the SAS OLAP Cube Studio client
writing the metadata back out to the repository.
The SAS OLAP Server is only used for viewing cube data, not for building cubes. Neither
SAS OLAP Cube Studio nor SAS ETL Studio have an OLAP viewer for viewing cubes;
therefore, the SAS OLAP Server does not have to be running when using either of these
client tools.
10
Month
1
1
2
2
3
3
1
1
2
2
3
3
Units
6
4
7
5
8
6
7
3
5
7
9
5
SalesAmount
300
200
350
250
400
300
350
150
250
350
450
250
11
The values shown above for SalesPerson are shortened on future slides for space
consideration reasons.
6-7
6-8
12
The SUMMARY procedure provides data summarization tools that compute descriptive statistics for
variables across all observations or within groups of observations. By default PROC SUMMARY does
not display output. PROC SUMMARY is similar to the MEANS procedure.
13
Sales
Person Month _TYPE_ _FREQ_
0
12
.
1
4
1
1
4
2
1
4
3
JLee
2
6
.
TMunch
2
6
.
JLee
3
2
1
JLee
3
2
2
JLee
3
2
3
TMunch
3
2
1
TMunch
3
2
2
TMunch
3
2
3
Total
Units
72
20
24
28
36
36
10
12
14
10
12
14
Total
Sales
3600
1000
1200
1400
1800
1800
500
600
700
500
600
700
14
The output data set created by PROC SUMMARY contains two special variables:
_TYPE_
_FREQ_
12
72
Total
Sales
3600
6-9
6-10
1
2
3
1
1
1
4
4
4
Total
Sales
20
24
28
1000
1200
1400
16
JLee
TMunch
2
2
6
6
36
36
Total
Sales
1800
1800
17
JLee
JLee
JLee
TMunch
TMunch
TMunch
1
2
3
1
2
3
3
3
3
3
3
3
2
2
2
2
2
2
Total
Sales
10
12
14
10
12
14
500
600
700
500
600
700
19
6-11
6-12
Sales
Total
Obs Person Month _TYPE_ _FREQ_ Units
7
8
9
10
11
12
JLee
JLee
JLee
TMunch
TMunch
TMunch
1
2
3
1
2
3
3
3
3
3
3
3
2
2
2
2
2
2
10
12
14
10
12
14
Sales
Total
Obs Person Month _TYPE_ _FREQ_ Units
5
6
JLee
TMunch
2
2
6
6
Total
Sales
500
600
700
500
600
700
Total
Sales
36 1800
36 1800
...
20
Sales
Total
Obs Person Month _TYPE_ _FREQ_ Units
7
8
9
10
11
12
JLee
JLee
JLee
TMunch
TMunch
TMunch
1
2
3
1
2
3
3
3
3
3
3
3
2
2
2
2
2
2
10
12
14
10
12
14
Sales
Total
Obs Person Month _TYPE_ _FREQ_ Units
5
6
21
JLee
TMunch
2
2
6
6
36
36
Total
Sales
500
600
700
500
600
700
Total
Sales
1800
1800
...
23
Sales
Total
Obs Person Month _TYPE_ _FREQ_ Units
7
8
9
10
11
12
24
JLee
JLee
JLee
TMunch
TMunch
TMunch
1
2
3
1
2
3
3
3
3
3
3
3
2
2
2
2
2
2
Total
Sales
10
12
14
10
12
14
500
600
700
500
600
700
Sales
Total
Obs Person Month _TYPE_ _FREQ_ Units
2
1
1
4
20
3
2
1
4
24
4
3
1
4
28
Total
Sales
1000
1200
1400
...
6-13
6-14
Sales
Total
Obs Person Month _TYPE_ _FREQ_ Units
7
8
9
10
11
12
JLee
JLee
JLee
TMunch
TMunch
TMunch
1
2
3
1
2
3
3
3
3
3
3
3
2
2
2
2
2
2
10
12
14
10
12
14
Total
Sales
500
600
700
500
600
700
Sales
Total Total
Obs Person Month _TYPE_ _FREQ_ Units Sales
2
1
1
4
20 1000
3
2
1
4
24 1200
4
3
1
4
28 1400
...
25
Sales
Total
Obs Person Month _TYPE_ _FREQ_ Units
7
8
9
10
11
12
JLee
1
JLee
2
JLee
3
TMunch 1
TMunch 2
TMunch 3
3
3
3
3
3
3
2
2
2
2
2
2
10
12
14
10
12
14
Total
Sales
500
600
700
500
600
700
Sales
Total Total
Obs Person Month _TYPE_ _FREQ_ Units Sales
2
1
1
4
20 1000
3
2
1
4
24 1200
4
3
1
4
28 1400
26
...
continued...
28
29
JLee
JLee
JLee
TMunch
TMunch
TMunch
1
2
3
1
2
3
3
3
3
3
3
3
2
2
2
2
2
2
10
12
14
10
12
14
Total
Sales
500
600
700
500
600
700
6-15
6-16
30
Menus and
Tools
33
6-17
6-18
Shortcut Bar
...
34
35
Options
Create OLAP
Schema
Source
Designer
Cube Designer
Navigation Tree
The navigation tree displays an organized list of the
cubes, OLAP schemas, and tables registered in the
selected SAS Metadata Repository.
Navigation
Tree
36
Status Bar
The status bar is located at the bottom of the SAS OLAP
Cube Studio application window. It displays short status
messages for the application.
Status Bar
37
6-19
6-20
Messages Window
The Messages window displays application messages
such as:
Application Server Error: Attempted
connection to Application Server failed.
Verify that the server is running.
To resize the Messages window, use your mouse to drag
the top edge of the window up or down. When you close
the window, your resized setting is saved.
To toggle the display of the Messages window, select
View Message Window.
38
Messages Window
Messages
Window
39
CAUTION:
Other SAS OLAP Cube Studio elements, such as the Properties dialog box and the
SAS Log window, are displayed in the same area as the Messages window. For this
reason, when resizing the Messages window, make sure that you leave enough room
for SAS OLAP Cube Studio to display those other elements.
40
The same Cube Designer Wizard is also available from SAS ETL Studio.
6-21
6-22
41
SAS OLAP Server names for cubes, dimensions, hierarchies, measures, and member properties follow
These guidelines assume that the SAS Workspace Server is running with the
VALIDVARNAME= system option set to ANY.
If a hierarchy is balanced, then all of its branches descend to the same leaf (bottom) level. In addition,
each member has a parent level that is positioned immediately above it. However, hierarchies are not
always balanced and sometimes they contain missing hierarchy members. This type of hierarchy is a
ragged hierarchy. The Ragged Hierarchies tab enables you to set options to handle the missing members
(character and numeric) for all levels and hierarchies within the cube.
42
43
6-23
6-24
...
44
45
Hierarchy
an arrangement of members of a
dimension into levels that are based on
parentparent-child relationships. Each hierarchy
provides a navigational path that enables
users to drill down to increasing levels of
detail.
Level
For example, in a Time dimension, a hierarchy might consist of Year, Quarter, Month, and Day (which are
the levels).
46
47
6-25
6-26
...
48
In this window you can also save the PROC OLAP code that is created by the wizard.
Measures
Delivery_Time:
Average
Minimum
Maximum
OrionStar
Quantity:
Average
Total_Retail_Price:
49
Product Dimension
Order_Type
Product_ID
Sum
...
The OrionStar cube will be built from the OrderFact detail table and consists of two dimensions and
several measures.
Building a Cube
This demonstration illustrates building a cube using SAS OLAP Cube Studio.
1. Invoke the SAS OLAP Cube Studio by selecting Start All Programs SAS
SAS OLAP Cube Studio 9.1.
2. Select the metadata profile BIArchitecture, then select
6-27
6-28
Select
4. Select the Cube Designer from the Shortcut bar to access the Cube Designer wizard.
Select
6-29
6-30
e. Select
to navigate to C:\Workshop\winsas\sbiovr\DataMarts\Cubes in the
Path field (the folder Cubes must be created).
f.
The path to where the cube is to be created is not a libref but a physical file
location. Within the specified path, the cube is stored in a directory that uses the
name of the cube. For example, if you enter the path specification above, then the
cube will be stored in C:\Workshop\winsas\sbiovr\DataMarts\Cubes\OrionStar.
6-31
g. Select
to get to the Advanced Cube Options window. The Ragged Hierarchies tab
enables you to set options to handle the missing members globally for all levels and hierarchies.
1) Select A blank space for the Character Missing Member option on the
Ragged Hierarchies tab.
2) Select A single period for the Numeric Missing Member option on the
Ragged Hierarchies tab.
Select
Select
6-32
6. In the Select a Detail Table list, select Foundation to see the registered data sources, select
OrderFact as the input source.
Select
7. Activate the No table for Drill-Through radio button (this is the default).
Select
8. Select
Select
6-33
6-34
10. Select
Select
11. Select
6-35
to define a hierarchy.
12. Specify a Name of Time, a Caption of Time Hierarchy (Year, Quarter, Month) and
choose the 3 available levels of Order_Year, Order_Qtr, and Order_Month.
Select
Select
6-36
e. Select
f.
g. Select
h. Select
i.
Select
to define a hierarchy.
j.
k. Select
l.
Select
m. Select
6-37
6-38
Select
6-39
Select
16. In the Cube Designer Member Property window, member properties can be added, modified and
deleted for the levels in the cube.
Select
17. In the Cube Designer Generated Aggregations window, you define aggregations to be generated
for the cube in addition to any automatically generated aggregations.
Select
6-40
18. To complete the cube design, write the metadata to the repository and create the cube, verify the
information is correct, and select
.
19. Check the Log Frame for messages and to verify that the cube was created successfully.
20. If the cube was created successfully, it will be listed in the Cube group:
6-41
6-42
22. A SAS OLAP cube is stored as a set of files on the operating system the OrionStar cube is stored at
C:\Workshop\winsas\sbiovr\DataMarts\Cubes\OrionStar:
6-43
Exercises
6-44
53
Chapter 8 shows how to view a SAS OLAP cube using SAS Enterprise Guide. Chapter 12 shows how to
view a SAS OLAP cube using the Information Delivery Portals Visual Data Explorer.
54
6-45
1. Select Start All Programs SAS SAS Management Console to invoke the SAS Management
Console. Login using the BIArchitecture metadata profile and the username and password provided
by the instructor.
6-46
7. Right-click the OrionStar cube and select Properties from the pop-up menu.
8. Select the Authorization tab in the OrionStar Properties window.
9. Select the PUBLIC group, then click on the check box to grant this group Read permission.
10. Select
1. Open an empty Excel spreadsheet by selecting Start All Programs Microsoft Office
Microsoft Excel.
2. Select Data PivotTable and PivotChart Report to access the PivotTable and PivotChart
Wizard.
3. Select External data source as the location of the data to analyze and PivotTable as the kind of
report to create.
Select
to access the
6-47
6-48
5. Select the OLAP Cubes tab, then double-click <New Data Source> to access the
Create New Data Source window.
6. Specify OrionStar as the name of the data source and choose SAS OLAP Data Provider 9.1 as
the OLAP provider.
Select
The name of the data source can be anything you want to call it.
to access the Data Link Properties window.
OrionStar
User ID:
Password:
5451 (default)
SAS Protocol:
ProtocolBridge (default)
Select
The name of the data source here must match the name of a data source registered in the
metadata.
to return to the Create New Data Source window.
6-49
6-50
8. In the Create New Data Source window, the third item should indicate a default connection. If not
already selected, select OrionStar as the cube for item 4.
Select
Select
Select
Select
6-51
6-52
The PivotTable Field list should now appear in front of your Microsoft Excel spreadsheet.
13. To populate the PivotTable with data from the SAS OLAP cube source:
a. Drag and drop Product Hierarchy from the PivotTable Field list into the
Drop Row Fields Here area of the PivotTable.
b. Drag and drop Time Hierarchy from the PivotTable Field list into the
Drop Column Fields Here area of the PivotTable.
c. Drag and drop Average Quantity and Average Delivery_Time from the
PivotTable Field list into the Drop Data Items Here area of the PivotTable.
6-53
6-54
14. Double-click on the cell that contains the value of 1998 (Year level). This will drill to the next level in
the Time Hierarchy, the quarters:
15. Select File Exit to close Excel, do not save the changes.
6-55
Exercises
6-56
7.2
7.3
7.4
7-2
7-3
7-4
Instead of embedding the SAS code into client applications, you can centrally maintain and manage this
code from the server. This gives you the ability to change your SAS programs and at the same time ensure
that every client that invokes a stored process will always get the latest version available.
7-5
7-6
Existing or new SAS code can be converted to a stored process and that stored process registered in the
SAS Management Console.
Beginning with version 3, SAS Enterprise Guide is the preferred method for working with stored
processes because it provides the ability to create, register, and test stored processes from one interface.
10
11
7-7
7-8
12
Because the stored process server runs under the SASSRV user ID, stored process code can access two
macro variables to identify the user:
Macro Variable
Description
_metaperson
specifies the person metadata name that is associated with the _METAUSER
login variable. The value of this variable can be UNKNOWN.
_metauser
specifies the login username that is used to connect to the metadata server.
Example: These macro variables can be used in the stored process code in a FOOTNOTE statement to
identify who executed the stored process:
footnote "This program was executed by &_METAPERSON - &_METAUSER";
Make sure to use double quotes around the string so that the macro variable values will be
resolved.
7-9
Workspace Server
The Workspace Server
is a single user server
provides a new process that is started for each client
each server is started with the client identity, so there
are some security advantages.
13
If you want to use a stored process to provide data to an information map, it must be executed
on a workspace server, and that workspace server must be the same one that runs the information
map.
14
7-10
This demonstration shows the metadata information stored for a sample stored process.
1. Start the SAS Management Console by selecting Start All Programs SAS
SAS Management Console, select the BIArchitecture metadata profile and enter the username and
password provided by the instructor.
The physical programs for the Stored Process Samples are stored in
C:\Program Files\SAS\SAS 9.1\inttech\sample.
7-11
7-12
5. Right-click on the Hello World sample and select Properties from the pop-up menu.
6. The General tab provides the name, description, and keywords for the stored process.
Keywords are useful when you search for a specific stored process in applications such as the
SAS ID Portal.
7. The Execution tab provides important information about which server the stored process will be
executed on, where the stored process source code is located, and input and output options.
7-13
7-14
Execution properties:
SAS Server
Source Repository
The directory where the physical SAS program is stored. This is not the
metadata repository. It is an operating system location where the SAS
program resides.
Source file
The name of the .sas file that contains your Stored Process.
Output
transient result
package
permanent result
package
None
7-15
8. The Parameters tab is where parameters are defined for the stored process. Parameters used in stored
processes are similar to those used in SAS Application Dispatcher programs. You pass parameters to
the SAS program, which then uses them as macro variables that can change the behavior and output
of the program.
The Hello World sample has no parameters. It can run without any additional information
from the user.
7-16
9. The Authorization tab is used to determine who can view, use, and update the stored process.
10. Select
17
Stored processes must be .sas file (or PDS members on z/OS) in SAS9.
If you want to execute an SCL or SOURCE catalog entry, you must write a wrapper
.sas program that uses PROC DISPLAY or %include to execute the entry. The SCL list
of parameter values familiar to SAS/IntrNet SCL developers is not created automatically
when using PROC DISPLAY, so you must use GLOBAL macro variables to access input
parameters.
7-17
7-18
18
19
7-19
20
When you assign a libref in your metadata, using the LIBNAME statement, there is an advanced
option that allows you to identify that the library is preassigned. If you select that option, you can
leave the LIBNAME statement out all together, as long as the stored process server has the
METAAUTOINIT option specified as an object spawner parameter. The default is set to
NOMETAAUTOINIT.
METAAUTOINIT
Specifies whether the IOM server should connect back to the SAS Metadata
Server during startup in order to obtain additional configuration information such
as object server parameters and preassigned libraries. When METAAUTOINIT is
specified, the server uses the provided META* options to connect to the SAS
Metadata Server. With NOMETAAUTOINIT, IOM server startup does not
connect back to the SAS Metadata Server.
7-20
Parameters are initialized differently for the stored process server and the workspace server. The stored
process server sets parameter values before the stored process begins to execute. This means the first line
of code in the stored process can access any input parameter macro variable. The workspace server does
not set input parameters into macro variables until it reaches a comment line in the stored process.
A stored process that does not contain the comment line will never receive input parameters when
executed on a workspace server.
It is recommended that you begin all stored processes (regardless of the server types) with %global
declarations for all of your input parameters, followed by the *ProcessBody; comment.
22
7-21
7-22
This demonstration shows how to manually create and register a stored process using an existing
SAS program.
1. Start a SAS Display Manager session using Start All Programs SAS BIArchitecture
Start SAS.
This shortcut uses some of the same configuration files as your stored process server, so
it provides a similar environment for testing. A benefit of this is that the Orion formats are
already defined to this SAS session. If you invoke SAS outside of this environment, you
receive format errors when you run this code.
2. Copy the following program in to the Enhanced Editor and submit it.
%let num=20;
options obs=#
libname orgold
"C:\Workshop\winsas\sbip\Orion_Star_15AUG03\orgold";
title "Listing of Orion Gold Customer";
proc print data=orgold.customer_dim label;
var customer_name customer_id;
run;
3. Verify that there are no ERROR messages in the log and that the program produced the desired
output.
4. Update the program with the stored process macros and remove the %LET statement.
REMOVE
%let num=20;
%global num;
*ProcessBody;
%stpbegin;
options obs=#
libname orgold
"C:\Workshop\winsas\sbip\Orion_Star_15AUG03\orgold";
title "Listing of Orion Gold Customer";
proc print data=orgold.customer_dim label;
var customer_name customer_id;
run;
%stpend;
5. Select File Save As and save the updated program to
C:\Workshop\winsas\sbiovr\StoredProcesses\customerlist.sas.
7-23
7-24
7. Locate the Stored Process Manager and select New Folder from the pop-up menu.
The folder in the metadata repository is only a logical way to organize the stored process
metadata. The physical programs are stored in a folder on the file system.
8. Enter Training for the Name field and Stored Process programs for the SAS 9.1
training course for the Description.
Select
7-25
9. Right-click the new folder Training and select New Stored Process.
10. Specify Orion Customer List for the Name field. Specify an appropriate description and
keywords, if desired.
Select
11. Select
.
to change the SAS Server to SASMain Logical Stored Process Server.
Make sure you change the SAS server to a stored process server. Stored processes can run on
a workspace server, but this example needs the STP server because streaming results is the
goal.
7-26
12. Select
window.
13. Select
to add a new Source Repository. This opens the Manage Source Repositories
A Source Repository is not the same thing as a metadata repository. The Source Repository
is the physical location where SAS programs are stored. You first need to allocate a storage
location that your servers can access to hold your stored processes. This storage location,
or repository, is implemented as a file system directory with the stored processes instances
represented as files, by name, with a .sas extension if appropriate for the file system.
to open the Add Repository window.
7-27
Select
Select
15. Select
7-28
17. Select
Select
.
Double-check the settings of this window carefully. It is easy to make a mistake in
this window. If you misspell any of the names or choose the wrong options, your
stored process will not work, and the problem can be hard to debug later.
18. Select
7-29
Select
7-30
Select
20. The new stored process is now visible in the Training folder.
7-31
Exercises
Manually create and register a stored process using an existing SAS program.
7-32
7.3 Creating a Stored Process from a SAS ETL Studio Job (Self-Study)
7-33
26
...
Because most SAS ETL Studio jobs do not create ODS output, stored processes created from SAS ETL
Studio do not include the %STPBEGIN and %STPEND macros. If the SAS ETL Studio job does create
ODS output, the %STPBEGIN and %STPEND macros can be added manually to the program created by
the Stored Process Wizard.
7-34
27
In order to run this stored process, the user must have authority on the operating system and the
metadata to update the OrderFact table. If the stored process is running on a Stored Process
server, the user ID is sassrv. If the stored process runs on a Workspace Server, it runs under the
ID of the client.
7.3 Creating a Stored Process from a SAS ETL Studio Job (Self-Study)
7-35
This demonstration shows how to create a stored process from an existing ETL Studio job.
1. Start SAS ETL Studio by selecting Start All Programs SAS SAS ETL Studio, select the
BIArchitecture metadata profile and enter the username and password provided by the instructor.
7-36
4. Right-click on Populate the ProductDim table and select Stored Process New.
The New Stored Process Wizard opens.
5. Select
7. Select
7.3 Creating a Stored Process from a SAS ETL Studio Job (Self-Study)
7-37
9. Type Load the ProductDim Table as the name of the new stored process and enter a
description and keywords (if desired).
Select
Select
7-38
This .sas file will be created in the specified location by the New Stored Process Wizard.
Select
15. Because there are no parameters for this stored process, select
7.3 Creating a Stored Process from a SAS ETL Studio Job (Self-Study)
7-39
16. To edit the stored process, right-click on the job, select Stored Processes stored process name
Properties.
17. To delete the stored process, right-click on the job, select Stored Processes
stored process name Delete.
7-40
.
to change the SAS Server to SASMain Logical Stored Process Server.
Gender Type
Gender
Description:
Gender Type
Boolean properties:
Required
Default value:
m. Select
n. Select
7-41
7-42
8.2
8.3
8.4
8-2
8-3
8-4
SAS OLAP
Server
SAS Stored
Process Server
In order to use SAS Enterprise Guide with the SAS Metadata Repository, you need to first identify the
metadata server in the SAS Enterprise Guide Administrator.
1. Select Start All Programs SAS Enterprise Guide Administrator.
By default, the SAS Enterprise Guide Administrator will display the Local server.
If the Configuration Wizard was used to configure the SAS Installation, a SAS Metadata
Repository already defined with the name ITConfig Metadata Repository should be listed.
8-5
8-6
5. To ensure that the correct metadata repository has been selected, select
next to the
SAS Metadata Repository ID field to open the Select Repository window.
6. In the Select Repository window, select Foundation.
Select
7. Select
.
to close the Modify Repository window.
8-7
8-8
Setup SAS Enterprise Guide so that it uses the SAS Metadata Repository for servers and channels.
9. Select the Usage tab in the Repository Manager.
10. Select Use the active SAS Metadata repository in the Servers, Libraries, and Binders section.
11. Select Use the active SAS Metadata repository in the Channels section.
Select
10
...
8-9
8-10
Process Flow
Task List
Server List
11
Binder List
12
Task Status
What is
Project
Process
Flow
Task List
Task Status
What is?
Stored
Process List
Binder List
Style
Manager
Server List
...
13
The Maximize Workspace button changes the size of the active window to fill the entire
SAS Enterprise Guide workspace.
14
8-11
8-12
1. Select Start All Programs SAS Enterprise Guide 3.0 to invoke SAS Enterprise Guide.
2. Select New Project in the Welcome window.
8-13
3. Because this is the first time SAS Enterprise Guide has been run on this computer, there is no current
default server. Select
in the message box to open the Options window so that you can
change the default server.
a. Select Administration from the list in the left side of the Options window.
Select
8-14
6. Because this stored process has a parameter, a window prompts you for the value.
Select
8-15
A HTML output item is added to the Process Flow window and the HTML report is displayed.
To view the log, right-click on the stored process and select Open Log.
When done viewing the report, close the HTML window and Log window if opened (select
).
8-16
If prompted for credentials, enter the user ID and password provided by the instructor, and deselect
Remember these credentials.
Select
8-17
Select
12. The table is added to the Project and opened, however no data is displayed in SAS Enterprise Guide.
8-18
8-19
18. Select
Setting permissions on the library will apply that permission to all tables that are currently in
the library as well as those that may be added in the future. Permissions can also be granted
on individual tables within a library.
.
8-20
20. Return to SAS Enterprise Guide and re-open the OrderFact table by double-clicking the icon in the
Process flow window data should now be displayed.
8-21
23. Use drag and drop to assign Order_Year to the Group analysis by role.
8-22
24. Select Statistics in the navigation list on the left to change the statistics in the report. Select
Frequencies and percentages from the Frequency table options.
25. Select
The results return to the SAS Enterprise Guide application as an HTML page.
).
8-23
8-24
17
18
19
...
8-25
8-26
This demonstration shows how to create, register and run stored processes using SAS Enterprise Guide.
1. Right-click on One-Way Frequencies task in the Process Flow window and select Create Stored
Process.
2. In Step 1 of the wizard, accept the default name and enter a description and keywords (if desired).
Select
3. In Step 2, select
process metadata item.
Select
Select
8-27
8-28
5. In Step 3, set the Execution server to SASMain Logical Stored Process Server SAS Stored
Process Server - 9.1.
6. Select the Source file path of C:\Workshop\winsas\sbiovr\StoredProcesses.
7. Accept the default source filename (this is the file that is being created for you by the SAS Enterprise
Guide Stored Process Wizard).
Select
8-29
Select
This window shows the LIBNAME statement that will be added to the new program in order
to access the source table. By default, these are set up using the Metadata Libname Engine.
.
8-30
9. Accept the defaults in Step 5 since this stored process has no parameters.
Select
If parameters were needed to run this stored process, they would be added in this step.
.
10. Step 6 allows you to choose how the output will be packaged. Select Streaming output, since the
results of this stored process will be streamed back to the application that is was called from.
Select
Select
12. A message window displays indicating the stored process was successfully saved:
Select
8-31
8-32
14. Open the Stored Process List window to see this new stored process by selecting View
Stored Process List.
8-33
8-34
18. Right-click on this new code node and select Create Stored Process. The Stored Process Wizard
opens.
19. In Step 1, accept the default Name and specify a Description of Generated by Enterprise
Guide.
Select
8-35
21. In Step 3, verify that the execution server is SASMain Logical Stored Process Server SAS
Stored Process Server 9.1, the source file path is C:\Workshop\winsas\sbiovr\StoredProcesses,
accept the default source filename and select
8-36
22. In step 4, the wizard can help build parameters based on macro variables in the code.
a. Select
f.
Select the Constraints tab to limit the possible choices for this parameter.
1) Select Integer range as the type of constraint.
2) Click the boxes to provide values for the Minimum, Maximum, and Increment options.
3) Set the value of Minimum to 1.
4) Set the value of Maximum to 10000.
5) Set the value of Increment to 5.
Select
g. This parameter is saved and a message window opens, notifying you that no additional macro
variables have been located in the code:
Select
8-37
8-38
Select
23. For Step 5, verify that Streaming output is selected, then choose
Select
8-39
8-40
Select
27. The new stored process has been added to the project and the Stored Process List window.
28. In the Process Flow window, right-click on the new stored process and select Run this Stored
Process.
29. A dialog window opens requesting a value for the parameter num. Enter 8 then select
8-41
8-42
22
The OLAP viewer in SAS Enterprise Guide supports OLAP cubes from SAS9 and MDDBs
from SAS 8.2.
23
This demonstration shows how to use SAS Enterprise Guide to view OLAP data.
Select
8-43
8-44
Select
8-45
4. The Open OLAP Cube window will display the available cubes in your repository. Select OrionStar
(click the check box), then select
.
8-46
5. The OLAP Analyzer will display the cube and allow you to navigate through the dimensions.
To work with the OLAP Analyzer more easily, maximize that window by selecting
View Maximize Workspace, and turn off the Cube View Manager window by selecting
.
7. Change the chart to a pie chart by right-clicking on the chart and selecting Chart Type Pie.
8. Change the view of the pie chart by right-clicking on the chart and selecting Put Groups On
Stack.
9. Close SAS Enterprise Guide by selecting File Exit (do not save the changes).
8-47
8-48
9.2
9.3
9-2
9-3
9-4
These business users are already familiar with Excel and Word and use the products daily. The ability to
run SAS programs within these programs provides tremendous flexibility and functionality.
Capabilities
With the SAS Add-In for Microsoft Office, you can
embed SAS reports and analytics into Microsoft Office
applications using stored processes
exchange data between SAS servers and Microsoft
Office
manipulate results and distribute them with existing
Microsoft Office functionality.
Requirements
The following are the system requirements for installing
and using the SAS Add-in for Microsoft Office:
Windows NT 4, Windows 2000, Windows XP
Office 2000 or greater
SAS Add-In for Microsoft Office.
SAS Metadata
Server
SAS Workspace
Server
Stored Process
Server
...
The SAS Add-In for Microsoft Office does not interact with the SAS OLAP Server. Microsoft
Excel can access SAS OLAP cubes using the pivot table functionality built into Excel.
9-5
9-6
SAS Analysis
Toolbar
10
14
15
16
...
9-7
9-8
...
17
19
...
9-9
9-10
20
Selecting
expressions.
21
22
9-11
9-12
23
9-13
1. Invoke Microsoft Excel by selecting Start All Programs Microsoft Office Microsoft Excel.
2. Select SAS Options from the pull-down menu.
3. The SAS Add-In displays an information window while it connects to the SAS Metadata Server.
9-14
4. If prompted, enter the user name and password provided by your instructor.
Select
This tab is where you can set the number of observations to display as each page of data is
requested from the SAS Server.
This tab can be used to set how the results are returned, HTML or CSV.
Using this tab you can also select whether or not the SAS log should be displayed.
9-15
9-16
This tab is where you can select the image format for graph. The valid values are as follows:
ActiveX
ActiveX image
GIF
JPEG
PNG.
9. Change the default SAS server to use SASMain instead of Local (the default).
9-17
9-18
11. Select
9-19
Run a Stored Process Using the SAS Add-In for Microsoft Office
12. Select SAS Browse SAS Programs from the pull-down menus (or select
on the toolbar).
a. Expand the Stored Processes tree (select Stored Processes Samples) and select Stored
Processes.
b. Select Sample: Frequency Analysis of Municipalities.
c. Select
Sample stored processes are automatically provided with the Web Infrastructure Kit.
These samples can be run to verify that the system is configured properly and to sample
the capabilities of stored processes.
.
9-20
The program results are streamed back to an Excel worksheet which is given the name of the
stored process.
The results are displayed in a read-only worksheet, so the values cannot be updated. To edit the
worksheet, select Tools Protection Unprotect Sheet.
If you always want the sheet unprotected, you can specify that by selecting SAS
Options and then deselecting the Protect data worksheet check box on the Data tab.
9-21
When an analysis is selected to be sent to Word, the stored process runs again to incorporate
any changes that were made to the data source before the analysis is seen. After the output is
available in the Word document, the document can be edited and new text added using the
functionality of Microsoft Word.
9-22
14. You can also run stored processes directly from Microsoft Word. Select SAS
Browse SAS Programs.
a. If prompted, enter the user name and password provided by your instructor.
b. Navigate to the stored processed created earlier by expanding the tree (select Stored Processes
Training).
c. Select Orion Customer List.
Select
9-23
15. Because this stored process has a parameter, you are prompted to enter a value. Type 10 and select
.
The output from the Stored Process is streamed back to the cursor position in the current
document unless the Insert results into current document option is
deselected on the Results tab of the SAS Options in Word.
16. Close Word by selecting File Exit (do not save the changes).
9-24
Managing Favorites
17. Back in Excel, select SAS My SAS Favorites Manage Favorites.
18. Add a stored process sample to My SAS Favorites.
a. Expand Stored Processes and Samples, select Stored Processes.
b. Right-click Sample: Frequency Analysis of Municipalities.
c. Select Add to Favorites.
22. Select My SAS Favorites from the toolbar, notice that the newly added favorites are on the list:
9-25
9-26
25. Drag the Sample: Frequency Analysis of Municipalities and drop it into the new folder Samples.
26. Select
Select
If you cannot read the entire name of a table, use the View Mode icon on the toolbar
to change the view to Detail or List.
9-27
9-28
The first page of data is streamed back to an Excel worksheet which is given the name of the
library reference and table name.
28. Click on the range of records (1-5000) from the SAS Data Analysis toolbar to change the starting
point (or select SAS Navigate SAS Data Source Go To Record).
9-29
9-30
The default number of rows that is displayed can be changed from the Data tab of the SAS
Options window in Excel.
The arrow tools on the SAS Data Analysis toolbar allows scrolling through the data. The arrows with the
bars next to them take you all the way to the beginning or end of the data. The single arrows scrolls one
page of data at a time (5,000 rows by default).
30. Select
31. Select
on the SAS Data Analysis toolbar (or select SAS Filter SAS Data Source).
b. Select
in the first box and select the desired column name, Customer Country.
c. Select
in the second box and specify the filter criteria, Is equal to.
9-31
9-32
d. Select
e. Select
f.
Select
.
in the last box and specify a condition (AND) in order to create combination filter.
h. Select
i.
Select
9-33
9-34
j.
Select
The Advanced Expression Editor is very similar to the editor in SAS ETL Studio.
k. Select
filter to the data.
to close the Advanced Expression Editor window and apply the specified
l.
to close the More Data Options window and apply the specified filter to the
Select
data.
The expression is evaluated on the Workspace Server and the first page of filtered data is
returned to Excel.
to
9-35
9-36
on the SAS Data Analysis toolbar, or select SAS Sort SAS Data Source.
b. Select
d. Select
to close the More Data Options window and sort the data.
The data is sorted on the Workspace Server and the first page of sorted data is returned to
Excel.
9-37
9-38
b. Select
available columns.
d. Select Statistics in the list on the left, then select Frequencies and percentages.
9-39
9-40
Select
9-41
The frequency task runs and displays the results in the worksheet that is given the name of the
SAS task.
35. Close Excel by selecting File Exit (do not save the changes).
9-42
Exercises
Filter the data so that the only items displayed are those where Outdoor is contained within
product group.
9-43
9-44
f. Select File Exit to close Word (do not save the changes).
g. Select SAS My SAS Favorites Manage Favorites.
h. Expand Stored Processes and Samples.
i. Select Stored Processes and right-click on Sample: European Demographic Data Detail.
j. Select Add to Favorites.
l. Select My SAS Favorites from the toolbar notice that the newly added favorite is on the list.
.
.
e. Select the filter icon on the SAS Data Analysis toolbar (or select SAS
Filter SAS Data Source).
9-45
9-46
g. Select
to close the More Data Options window and apply the specified filter.
h. Select File Exit to close Excel (do not save the changes).
10-2
A Problem
In most businesses, there are many information
consumers who need reports from business data, but
relatively few IT professionals available to meet their
requests.
Information
Consumers
Overworked IT
3
There is often a backlog of requests that cannot be filled quickly enough to meet the business needs.
A Solution?
One way to reduce this backlog is to empower the
end users so that they can create more of their own
reports, leaving IT to the business of managing and
developing mission critical applications.
Allowing end users access to business data gives them
the ability to create reports quickly and make changes
as often as needed.
10-3
10-4
COUNTY
MUNICIPALITY
STREETID: DECIMAL(15)
STREETNAME: CHARACTER(30)
STREETCODE: NUMERIC(8)
ZIPCODE: NUMERIC(3) (FK)
ZIPCODE: NUMERIC(3)
MUNICIPALITY: CHARACTER(18)
COUNTY: CHARACTER(18)
CUSTOMER
CUSTTYPE
ORGANIZATION
CUSTTYPE: NUMERIC(3)
CUSTOMERNO: NUMERIC(8)
CUSTTYPENAME: CHARACTER(18)
CUSTGROUP: NUMERIC(3)
CUSTGROUPNAME: CHARACTER(40)
SOCIAL_SECURITYNO: CHARACTER(15)
NAME: CHARACTER(30)
ADDRESS: CHARACTER(30)
STREETID: DECIMAL(15) (FK)
STREETNO: NUMERIC(3)
CUSTTYPE: NUMERIC(3) (FK)
ACCMAN: NUMERIC(3)
ORGNAME: CHARACTER(40)
ORGLEVEL: NUMERIC(3) (FK)
ORGREFID: NUMERIC(3) (FK)
ORGLEVEL
ORDER
ORGLEVEL: NUMERIC(3)
PRODUCT
ORDERID: NUMERIC(8)
PRODUCTNO: NUMERIC(8)
ORGTEXT: CHARACTER(40)
PRODUCTNAME: CHARACTER(18)
SUPPLIERID: NUMERIC(3) (FK)
PRODUCTNIV: NUMERIC(3) (FK)
PRODUCTREFID: NUMERIC(8) (FK)
ITEMS
SUPPLIER
SUPPLIERID: NUMERIC(3)
SUPPNAME: CHARACTER(30)
SUPPADDRESS: CHARACTER(30)
SUPPSTREETNO: NUMERIC(3)
SUPPZIPCODE: NUMERIC(3)
PRICELIST
PRODLEVEL
PRODLEVEL: NUMERIC(3)
ENDDATE: DATE
UNITPRICE: NUMERIC(8)
PRODTEXT: CHARACTER(40)
Information Map
STREETCODE
COUNTY
MUNICIPALITY
STREETID: DECIMAL(15)
STREETNAME: CHARACTER(30)
STREETCODE: NUMERIC(8)
ZIPCODE: NUMERIC(3) (FK)
ZIPCODE: NUMERIC(3)
MUNICIPALITY: CHARACTER(18)
COUNTY: CHARACTER(18)
CUSTOMER
CUSTTYPE
CUSTTYPE: NUMERIC(3)
CUSTOMERNO: NUMERIC(8)
CUSTTYPENAME: CHARACTER(18)
CUSTGROUP: NUMERIC(3)
CUSTGROUPNAME: CHARACTER(40)
SOCIAL_SECURITYNO: CHARACTER(15)
NAME: CHARACTER(30)
ADDRESS: CHARACTER(30)
STREETID: DECIMAL(15) (FK)
STREETNO: NUMERIC(3)
CUSTTYPE: NUMERIC(3) (FK)
ORGANIZATION
ACCMAN: NUMERIC(3)
ORGNAME: CHARACTER(40)
ORGLEVEL: NUMERIC(3) (FK)
ORGREFID: NUMERIC(3) (FK)
ORGLEVEL
ORDER
ORDERID: NUMERIC(8)
ACCMAN: NUMERIC(3) (FK)
CUSTOMERNO: NUMERIC(8) (FK)
ORDERDATE: DATE
DELIVERDATE: DATE
ITEMS
ORDERID: NUMERIC(8) (FK)
ITEMS: NUMERIC(3)
PRODUCTNO: NUMERIC(8) (FK)
AMOUNT: NUMERIC(8)
PRICE: NUMERIC(8)
PRODUCT
PRODUCTNO: NUMERIC(8)
PRODUCTNAME: CHARACTER(18)
SUPPLIERID: NUMERIC(3) (FK)
PRODUCTNIV: NUMERIC(3) (FK)
PRODUCTREFID: NUMERIC(8) (FK)
PRICELIST
PRODUCTNO: NUMERIC(8) (FK)
STARTDT: DATE
ENDDATE: DATE
UNITPRICE: NUMERIC(8)
ORGLEVEL: NUMERIC(3)
ORGTEXT: CHARACTER(40)
SUPPLIER
SUPPLIERID: NUMERIC(3)
SUPPNAME: CHARACTER(30)
SUPPADDRESS: CHARACTER(30)
SUPPSTREETNO: NUMERIC(3)
SUPPZIPCODE: NUMERIC(3)
PRODLEVEL
PRODLEVEL: NUMERIC(3)
PRODTEXT: CHARACTER(40)
...
10-5
10-6
Because SAS Information Maps consist of metadata, they can contain all the information that allows the
application to generate query code.
Metadata about the data sources
The data source can be SAS data sets, SAS9 OLAP cubes, or a third party database such as Oracle,
Teradata, DB2, or MS Excel. Information maps can access anything that SAS can read.
Metadata about data relationships
Multiple relational data tables can be combined or joined. This allows the application to optimize queries,
regardless of the data source.
Metadata about the data items and their usage
The information map can store metadata that controls the display and usage of the data items. For
example, you can decide that a certain data item should not be used in a sort or to compute statistics.
Metadata about business rules
Standard calculations and filters can be predefined, so business users do not need to re-create them every
time they are needed.
10-7
10
Builds
warehouse
metadata
Business
Metadata
SAS Information
Map Studio
Reads
warehouse
metadata
Reporting
Report
Builds
Viewing
Information
Maps
Reads
Information
Maps
SAS Metadata
Server
Ad-hoc
Reporting
Builds and
reads report
metadata
11
The SAS Metadata Server manages the metadata and provides security, while the SAS Web Report Studio
product enables the user to create reports.
10-8
12
13
14
Data modelers or data architects are typically someone in an IT or MIS unit. This person works very
closely with the business domain experts to understand the types of questions they need to ask as well
as the business context in which they are asked.
continued...
15
10-9
10-10
continued...
16
17
18
...
10-11
10-12
20
Menu Bar
Contains the drop-down menus for SAS Information Map Studio. Many of the menu
functions are also available from the toolbar and from pop-up menus.
Toolbar
Contains buttons that enable quick access to many of the functions that are available
from the menu bar.
Repository Tree
Displays the information maps in the metadata repository. You can display or hide
the Repository Tree by clicking the View Repository button on the toolbar.
Presentation Tab
Displays the physical data source, data items, and filters for the information map
that is currently open. The Physical Data tree displays the physical data source that
you selected for the map. The Information Map tree displays the information map's
data items and filters.
Properties Tab
Contains the properties table for the information map's data items and filters. You
can select a data item or filter in the left pane to display its properties in the right
pane. From the right pane, you can edit the properties.
Relationships Tab Displays tables, their columns, and the relationships (joins) between tables. You can
create and modify the relationships between tables. You can also add or remove
tables for your information map.
Menus and
Tools
...
21
Repository
Tree
22
...
10-13
10-14
Presentation
Tab
23
Properties
Tab
24
...
Relationships
Tab
25
Information maps can be created from one or more data tables or a single OLAP cube.
Joining Tables
When joining tables, the default
relationship is an inner join, which
returns only matching rows.
Outer joins can also be used to return non-matching rows.
The modifiers left, full, and right determine which table
contributes the non-matching rows.
Left
26
Full
Right
10-15
10-16
...
27
Property
Description
specifies a descriptive name for the data item; the maximum length is 60
characters.
Description
specifies a description for the data item, which can be viewed by the information
map consumer.
Classification
Aggregation
specifies aggregate functions that the information map consumer can use for
summarizing measure values.
Format
specifies a format for the data item. A description of the format and an example of
a formatted value are displayed to the right of format type and name.
Permissions
Value Generation
Permissions are applicable only to relational data items and OLAP data
items that represent hierarchies.
the method that is used to generate a list of data item values for a filter. When this
data item is selected for a filter, the method that you choose is used to populate a
selection list that the user of a filter definition window can select values from.
Value generation options apply only to relational data items that do not
have an expression type of Date , Time, or Timestamp.
10-17
28
29
This can be an important distinction for performance reasons. If you have a data item that is
complicated to calculate and the map is tied to large data sources, it may be faster and more
efficient if the data item is created in the data warehouse or physical data source. If storage space
is important, it may be better to calculate the field in the information map because the value is not
stored physically.
10-18
This demonstration shows how to use SAS Information Map Studio to build a simple information map.
10-19
Information Map Studio opens without an information map loaded. To create a new information map,
start by inserting a new data source.
You can also access a wizard to create a new information map by selecting
File New using Wizard from the pull-down menus.
To load an exiting information map, select it from the Repository Tree.
10-20
4. Select
to add data.
The Data Type selection allows you to select either tables or cubes. You can build an information
map from one or more table on the same server, or one cube.
Select
The Physical Data Previewer displays the columns in the selected data source.
.
10-21
10-22
Numeric fields have a blue circle icon ( ) and character fields use a red triangle ( ).
10-23
Begin creating the information map by selecting fields in the Physical Data tree and moving them to the
Information Map tree.
6. Select
10-24
The properties of each data item can be edited using its properties window, which can be accessed by
double-clicking on the field name
right-clicking on the field and selecting Properties
selecting the Properties tab.
7. Right-click on the Customer Age data item and select Properties from the pop-up menu.
10-25
Select
It is important to choose the proper classification for each data item in the information map
because this setting cannot be changed in the applications that use the information map.
to close the properties window for Customer Age.
10-26
The icon for Customer Age changes to something that looks like a ruler (
measure.
) this indicates it is a
10-27
on the toolbar.
Select
10-28
10. Select
Select
You cannot edit the SQL code shown in the Show Generated Query window, but you can
copy the code into another application and modify it there.
when done viewing the code.
11. Select
12. Select
10-29
10-30
13. Select File Save to save the information map. The Save As window opens:
a. Select the location to save the map by selecting BIP Tree ReportStudio Maps.
b. Enter Customer List in the Name field.
c. Enter a Description of Orion Star Gold Customer Listing.
Select
If this map is intended for use in SAS Web Report Studio, you must save your
information maps in the Foundation/BIP Tree/ReportStudio/Maps folder.
to save the information map and return to the main window.
10-31
Creating Filters
Create a filter to subset data by age and gender. Because Customer Age is already defined in the
information map as a measure, it needs to be added again so it can be used to create a categorical filter.
14. Select Customer Age in the Physical Data tree then select
tree.
10-32
15. Double-click Customer Age1 to open the Data Item Properties window. Change the Data item name
to Age Category and select
16. Select
10-33
10-34
f.
to move the expression just built into the Filter combinations box.
The expression built on Age Category is cleared from the Subset list at the top of the
window and should now appear in the Filter Combinations area.
10-35
g. Create the second portion of the filter by selecting Customer Gender from the drop-down list for
the Subset field.
h. Select Is equal to from the drop-down list for the Condition field.
i.
j.
Select
k. Select
Character values used in filters are case sensitive and must be enclosed in quotes.
to add the expression to the Filter combinations area.
10-36
e. Select
f.
Select
g. Select
10-37
10-38
b. Select
When a new data item is created, you must define the expression before you can enter
any properties for that data item (other than the name).
to open the Expression Editor.
10-39
10-40
f.
Select the Data Sources tab, expand Physical Data and CUSTOMER_DIM, locate Customer
Birth Date from the Customer List information map and select
Both Business Data and Physical Data are available so that you can create an expression
for a new data item based on physical data that may not be in your information map.
g. Select
Select
10-41
to close the Expression Editor window and return to the properties window for
h. Select
the new data item.
i.
Select the Classifications/Formats tab and change the format type from Date/Time to Numeric,
specify BEST as the format, and set the width to 2.
j.
Select
10-42
1) Select Customer First Name, Customer Birth Date, and Customer Birthday Month.
2) Select Display a detailed list of values.
3) Select Limit the query to 100 rows.
4) Select
5) Select
6) Select
20. Save the information map by selecting File Save (or by selecting
on the toolbar).
10-43
10-44
22. Expand the Orion Star Gold Library and select ORDER_FACT.
Select
10-45
10-46
25. Right-click on Cost Price Per Unit and set the Classification to Measure.
10-47
26. Select the Relationships tab to define how the tables will be joined together.
Select Customer ID from the CUSTOMER_DIM table, drag and drop on top of Customer ID in the
ORDER_FACT table. By default, this creates an inner join on the two columns.
If your information map contains more than one table, you must define relationships for the
tables.
This tab is disabled if your information map is based on an OLAP data source.
By default, this creates an inner join on the two columns.To change the type of relationship, rightclick on the line connecting the tables and select Properties from the pop-up menu.
10-48
27. Select
d. Select
e. Select
f.
Select
10-49
10-50
28. Select File Save As to save the information map with a new name.
a. Specify Customer Orders for the Name.
b. Retain the folder specification of BIP Tree/ReportStudio/Maps/.
c. Specify Orion Star Gold Customer Order Information as the Description.
Select
Exercises
10-51
10-52
c. Select Cubes as the Data type, OrionStar as the data source, and
d. Select
10-53
Select
10-54
g. Select
h. Select
i. Select
The Data Selection and Query Options for Test window for OLAP data sources is
different from the one used for table data souces.
to add all items to the test query.
to run the test.
j. Select
k. Select
l. Select
m. Select
to close the Data Selections and Query Options for Test window.
10-55
10-56
11-2
Info
Map
Reporting
Applications
SAS ODS
Style
Info
Map
Colors
Data
Model
View
Language
XML
Serialization
SAS
Report
Table
Embedded
Data
URL
Formats
Text
Image
Graph
Report Components
within technologies
and solutions
11-3
11-4
Users can interact with the report by performing operations such as drilling, sorting, filtering, ranking,
exporting, and group break navigation using the Table of Contents. This is feasible because SAS Web
Report Studio stores reports in the common SAS Report Model XML format.
SAS Workspace
Server
SAS OLAP
Server
...
11-5
11-6
10
11
This demonstration shows how to use SAS Web Report Studio to create a report.
Select
11-7
11-8
After logging on, the main window of SAS Web Report Studio is displayed.
There are many options from the main window, including the ability to view an existing
report, create a new report, and set SAS Web Report Studio preferences.
The default interface is the Report Wizard you can switch to the Report Builder by
.
selecting
Notice that this is the first of five steps to create a report.
To navigate between the steps, choose either
or
11-9
11-10
Select
11-11
When a data source has been selected, the data items are displayed. Select the desired data items and use
to move them to the Selected Data Items: list.
Select
11-12
If there are any filters in the information map they will be available in the filter box the data
item(s) the filter is based on.
11-13
11-14
7. Select
9. Select
10. Select
Select
11-15
Select
The default for group breaks is to have a new page for each value. This option produces a
table of contents to navigate to each page of output.
to advance to the next step (step 4).
11-16
Select
Select
11-17
11-18
The report is displayed in the browser. Because the report is grouped by Customer Gender, a table of
contents area is displayed on the left to enable users to page between the values.
15. View information for the next group by selecting Males in the Table of Contents.
Across the top of this report preview there are a set of buttons.
Modify
Options
Save
Create New
The icons at the top of each section provide additional functionality for the section.
Edit options
Export table/graph
Table/graph information
11-19
11-20
17. Select My folders and specify Customer Sales Analysis as the Report name.
Select
19. The Actions button to provides the ability to issue various commands for the selected report.
11-21
11-22
21. In the Copy Report window, select Shared folders and then Reports.
Select
22. Choose
Select
The list of reports is displayed showing the new name of the report.
11-23
11-24
26. Select the Report Creation tab and supply default header text of
Orion Star Marketing Data Mart.
Select
27. Select
.
to close out of SAS Web Report Studio.
11-25
11-26
Exercises
11-27
c. Create a new report using the Orion Star Customer Listing information map and the
Customer Country, Customer Age, and Customer Gender data items.
Select
Select
11-28
Select
f. Create a table using all the fields and a bar graph using Customer Age as the vertical axis,
Customer Country as horizontal axis, and divide the bars by Customer Gender.
Select
Select
11-29
11-30
h. Save the report in My folders with the name Customer Age Analysis
1) Select
3) Select
i. Log off SAS Web Report Studio and close the browser.
1) Select
11-31
11-32
12-2
12-3
Using a centralized search tool, you can search for information from across the enterprise that is appropriate
for your role in the organization.
12-4
Page
Portlet
...
You can create, add, edit, rearrange, and remove pages in your personal portal. Pages can be shared either
publicly or with a group of users.
A page can contain any number of portlets.
Content Types
Some of the main content types that can be added to
portlets are
links
SAS Information Maps
SAS Reports
Stored Processes
Alerts.
12-5
12-6
Link
...
SAS
Information Map
SAS Reports
10
SAS Stored
Process
11
12-7
12-8
12
Stored processes that run in the background display the message Stored Process/<name> submitted for
background processing when you execute them. This message means that you can continue working on other
tasks while processing continues in the background. When the stored process finishes executing, a notice
appears in your Alerts portlet. You can then click the alert message to see the results of the stored process.
In order for stored processes to execute in background, the portal must be installed with WebDAV
support.
Description
application
file
package
publication channel
What Is WebDav?
WebDAV is a set of extensions to HTTP, the HyperText
Transfer Protocol, to allow remote collaborative authoring.
HTTP does a very good job of letting users browse
content already published on the Web, but it is not very
good at allowing users to post their own content.
WebDAV makes the Web writable as well as readable, in
a standard, interoperable, way.
14
With just HTTP, there is no standard way to move a file, to lock or unlock it, or to add metadata or
properties to the file. WebDAV standardizes all those functions.
12-9
12-10
Xythos WebDav
Xythos
is a secure WebDav server
uses a relational database
is not required for the SAS Information Delivery Portal,
but some important features are not supported if
Xythos is not part of the installation.
15
The Xythos WebFile Server (WFS) is a scalable, Internet-based file management solution, that allows users to
securely store, modify, and share files from any Web-enabled device. Additionally, WFS is a full-featured
WebDAV (level 2) server, providing users with file management functionality via any WebDAV-enabled client
application. Using WebDAV and other Web standards, WFS helps enterprise customers find and share
information from any Internet location while improving file system security and reducing the load on e-mail
systems.
To find out more about Xythos, go to their Web site: http://www.xythos.com/home/xythos/index.html
Content Classification
The content contained within the pages and portlets can
be classified as one of the following:
Public
Group
Personal.
16
17
12-12
18
19
Depending on which software your organization has installed, the features that are listed above might
be available only to users who are authorized as content administrators.
continued...
...
20
21
SAS Workspace
Server
Stored Process
Server
...
12-14
http://localhost:8080/Portal
23
This demonstration shows how to use the SAS Information Delivery Portal.
12-16
4. Select
The initial content displayed contains one page with two portlets:
Page
My Collection Portlet
Bookmarks Portlet
A collection portlet is a portlet that contains a list of portal content items. To use a collection
portlet, click the name of an item in the list. Depending on the content type, the portal will
either display the item or launch a new application in your browser window.
A bookmark portlet is a predefined portlet that enables you to maintain a list of content items
that you want to refer to later. Bookmarks are generally used to maintain a list of content items
for short-term use.
12-18
6. The Name or Description of the portlet can be changed, and keywords can be added to help in searches.
Select
7. The Create tab is selected by default. Create a new link by entering a name, description, URL, and
keywords for the SAS Web site.
Select
12-20
8. Select the Search tab to search for existing content to add. To search for all available content, type an
asterisk in the Keywords field, select the Select All check box.
9. Select
10. The available content is displayed. Select the box next to the following items to add to the Collection
porlet:
Customer Age Analysis.srx (report)
Customer List (information map)
Orion Customer List (stored process)
Select
11. Select
.
when you are finished added content to the Collection portlet.
You may need to scroll the to the bottom of the page to find the
button.
12-22
12. Type Orion Star Marketing Data Mart in the Name field and Information built in
class in the Description field.
13. Select
15. Select
12-24
16. Select Customer List to view the data surfaced by the information map using the Visual Data Explorer.
17. Display data in the Visual Data Explorer by selecting the following in the Available items list:
Customer Age
Customer Country
Select
Select
18. Select
.
.
12-26
19. Select Orion Customer List to run and view the results of the stored process.
20. Select
and
The stored process is executed using the parameter specified, and the results are streamed back to the
portal window.
22. Select
12-28
24. Select the Search tab, type an asterisk in the Keywords field, and select
25. Select the check box for Alerts Portlet and SAS Information Maps Navigator.
Select
26. Select
12-30
Select
12-32
29. Select Orion Star Cube from the SAS Information Maps Navigator portlet to open the Visual Data
Explorer and load the OLAP data surfaced by the information map.